Daniel Nashed's Blog

Domino Backup notifications and central logging

Domino Backup can be configured in 5 minutes if you have deduplicating storage locally or available over a file share.
Some of my customers use it specially for smaller servers which don't need larger backup infrastructure.
This could be hosted servers or smaller admin or gateway servers.

But it would also work for larger servers if the storage is performing well.
There can be a second backup tier in the back-end.
Domino Backup isn't only a great backup solution.
It also provides functionality which other backup implementations don't provide out of the box.

Beside restoring documents and folders back into the original database, there are a couple of other flexible options like changing replica ID, disabling replication. DAOS restore integration and a lot more.

One interesting details is is logging, which is implemented in the "Notes way".
You can fully configure in which case a backup log should be send and to which recipient.

Here is a production example from a customer who ran into a backup error where one database could not be backuped, because the database was corrupted.

Logging can be defined in very detail even the standard log configuration only provides the options to send backup logs Always, when warnings came up or only in error case.

• Log document always or just in error case
• A formula to define the target recipient
• There is even a way to customize the log form
• In addition the mail contains additional fields beside subject and body with status information, so you can email those log documents into a central database.
   

• Comments [0]