What’s the strategie for backup and restore of DAOS enabled databases. For example with TSM, will attachment being backuped with the database or should the be backuped separately.
regards Werner
Subject: Same tools…new procedure
Since the attachments are no longer in the NSFs, you will need to back up both the NSFs and the NLO files in the DAOS repository.
The NSFs should be backed up with the existing tools and procedures that use the Domino API. All the NLO files in the DAOS directory tree should be backed up as flat files. You should back up the NLO files after you back up the NSF files to ensure that all referenced NLOs are backed up. This is important if the server is operational during the backup process, and new NLOs may be created in the backup duration. Note that NLOs are never modified by Domino after they are created. An incremental backup of NLO files is ideal for this situation, and can significantly reduce your backup resource costs.
NLO files have a reference count. When that reference count goes to 0, the NLO is marked as a candidate for deletion. There is a (configurable) deferred deletion interval in the server doc that controls how long those NLOs wait until they are finally deleted. The default is 30 days. We recommend that you make sure it is greater than the time between your backups to make sure every NLO is backed up at least once.
If a restore of an NSF is done before the deferred deletion interval, the NLOs will still be there, and all attachments will be accessible.
If the restore is done after the interval, some NLOs may have been deleted, and will need to be individually restored. The command ‘tell daosmgr listnlo missing somefile.nsf’ will display a list of the NLO files that are referenced by the NSF, but do not exist in the DAOS repository, and need to be restored. Once those NLO files are restored, all attachments will be accessible again.
Subject: Thanks for your comments.
We’ll try this in out beta environment.