Are you using DAOS in production? At first I was excited at the possibility of implementing this new feature system-wide, however, now I am have reservations.
Specifically, the process needed to do point-in-time restores of DAOS-enabled databases. Say I pull an nsf from a 6 month old restore and the associated transaction logs. Then, I have to run a daos command to determine what NLO files are missing from the current activy NLO directory. At that point, if I had Tivoli storage manager, it would take a simple command to have Tivoli read the file of missing NLO’s and restore them. However, since I do not have Tivoli, I would need to hunt and peck thru my backups and do individual restores of those NLO files. This is not spelled out in the Admin Guide and the documenation on doing backups for DAOS is overly simplified.
What I am thinking of doing is only implementing DAOS on nsf’s that are not backed up.
I think the Admin Guide’s lack of detail on the DAOS restore process guidelines, and its casual treatment of backup guidelines for DAOS should be reviewed.
The issue is other backup software vendors do not have the flexibility that TSM does. You could run more frequent full backups of the NLO’s so restoring would be less of an issue but it still won’t be as easy as TSM.
One of my clients has decided to extend the NLO deletion deferral date to 180 days (this means that even if the last document referencing an NLO file is deleted, Domino won’t delete the NLO for until 180 days have passed). That way, we have a window of 6 months during which we would never have to ‘hunt and peck’ for NLO files.
By the time 6 months is over, we expect that our backup vendor (symantec) will have shipped their new version with full DAOS support.