Specifications

Lotus Redbooks Wiki – IBM Lotus Notes and Domino V8.5 Deployment Guide
165
These actions will put all the attachments back into the database. Then, you'll be able to create a new
replica or move the database to another DAOS-enabled server.
Note: You do not need to do these actions if you create a replica or move a DAOS-enabled database to a
Domino server 6.x, 7.x or 8.0.x, or a Domino 8.5 server without DAOS configured. The attachments will
come back into the database automatically with no further action required.
Although the physical file size of the database is reduced, if quotas are implemented in an environment, they
will still be enforced. Even with DAOS implemented, the quota still checks against the Notes database size,
which is calculated based on the current database size plus the attachments. This is working as designed to
take into consideration the possibility of rolling back a database to a non-DAOS state.
In a clustered environment, it is important to keep in mind that the DAOS catalog and DAOS store are
server-independent, meaning that every server has their own separate DAOS catalog and store. These
components are not synchronized in a clustered environment. Even though the Notes databases are
clustered, their attachment references in the DAOS catalog are different, depending on which server you
open the database.
DAOS Backup and Restore
This section provides some information on how backup and restore works when DAOS is enabled on a
Domino 8.5 server. This information is applicable to both single and clustered Domino servers because the
DAOS catalog and store are specific for each server.
All backup solutions supported on Domino 8.5 should still work on DAOS-enabled servers. As mentioned
earlier, DAOS is transparent to existing C-API calls. If you run a backup client on your Domino server that
supports Transactional Logging, backups and restores remain unchanged from an NSF perspective. For a
server with DAOS configured, you will have to modify your Domino server backup job to include the DAOS
store. One recommendation would be to do full backups of the DAOS store during weekends, and
incremental backups during weekdays because NLO files are either added or deleted, not modified.
Running DAOS on a Domino server provides important cost savings from a backup perspective:
• Reduced backup volume - Takes less tapes to backup a server
• Reduced backup processing - Takes less time to backup a server
Restoring a Notes database on a Domino 8.5 with DAOS may require some manual steps in some specific
cases, because there is no existing backup APIs integrating with DAOS. For example, when you do a point-
in-time database restore, the NSF gets restored as expected, but you have to make sure that all NLO files
contained in the NSF at the time it was backed up, are present in the DAOS store. This step is done
manually and separately, meaning that once the NSF is restored, you have to restore the NLO files from
DAOS store. There is a simple command that will let you know which NLO files are missing from the
restored NSF file. This will assist you in only selecting the missing NLO files from your backups instead of
restoring the whole DAOS store. The command is the following:
tell daosmgr listnlo missing
IMPORTANT NOTE: NLO files are encrypted with the server key by default, thus not portable between
servers.
Once restored, you run this command from the server console to resynchronize the DAOS catalog with the
DAOS store:
load tall daosmgr resync
But the frequency of this manual step could be reduced if you find a good balance on how long to hold onto
DAOS objects (NLOs), once the last reference is deleted. You will never be able to eliminate it completely