We are moving to 8.5 and enabling transaction logging and DAOS.
I have a couple of questions about backup:
What features should I be looking for in a backup solution? Most importantly, anything I should avoid?
Based on your experience, do you recommend any specific software?
I guess, with DAOS enabled, restoring only a database from backup won’t do the job as NLO files should be restored aswell?
Many thanks for your input
Mael
Subject: Backup answers
For a detailed look at the b/r issues, check out the article on the Wiki:http://www-10.lotus.com/ldd/dominowiki.nsf/dx/daos-backup-and-restore
To answer your questions specifically…
The only new requirement for backup relative to previous versions of Domino is the ability to back up the NLO files in the DAOS directory tree as flat files. You should be able to do that with any generic b/r application, as no special treatment is necessary for them.
The NSF files should be backed up using a solution that works with the Domino backup/restore API, the identical way it is done with earlier versions of Domino. If you shut Domino down, you can use a generic b/r application on the NSF files also.
Well, obviously I’m biased towards Tivoli, but there are several vendors that offer Domino b/r solutions.
It depends. When the reference count for an NLO goes to 0, it is not deleted immediately. The deferred deletion interval has a default of 30 days, and is configurable. Part of the reason that the deferred delete interval is there is to help avoid needing to restore NLO files.
If the interval is set to 30 days, and the NSF you are restoring is (for example) 15 days old, none of the NLO files will have been deleted. In that situation, restoring the NSF really is the only thing you have to do. If the NSF you’re restoring is (for example) 60 days old, some of the NLO files will probably still exist in the DAOS repository, so you only need to restore the missing ones. You can get a list of the missing NLO files for a given NSF with the Domino console command:
tell daosmgr listnlo missing somefile.nsf
You can also redirect the output to a file so that the file can be used as input to your restore program:
tell daosmgr listnlo -o output.txt missing somefile.nsf
Subject: Re Backup answers
Many thanks, Patrick.
Mael