Robert Steen and Marcin Nalewajko, along with several other members of the IBM Domino team, led a discussion on Archiving and recovering IBM DAOS-enabled databases. See below for the presentation, audio replay, and Q&A from the event.
|Presentation & Audio Recording|
Open Mic - Archiving and recovering IBM DAOS-enabled databases.pdf
Archiving and recovering IBM DAOS-enabled databases - Open Mic - 16 Oct 2013 .mp3
Q1. What strategy is SAVDOMBRM considered?
SAVDOMBRM is not covered specifically. Refer to this DAOS article for additional information on backup options for IBM i.
Q2. What is the maximum pruning interval?
The default is 30 days but you can set it to any value you wish; however, more then 90 days not recommended.
Q3. What is the harm in setting the prune interval to more than 90 days?
Prune interval is only relevant to attachments not used in any database. If you need to resync DAOS it will take more time. Setting this value too high will incur the cost of an accumulation of unferenced NLO files.
Q4. We have one server out of three (clustered) DAOS enabled. We are considering making a second server DAOS enabled. In relation to the DAOS server in the cluster, are there any gotchas when doing so now (rather than at the same time)?
No gotchas. You can enable DAOS at different times without issue since DAOS is configured per server even if they are in a cluster. If you have the NLOs encrypted they can't be copied between servers or restored to a server other than the one they were created on. They also can't be stored in the same repository.
Q5. Server-based archiving happens on a non-DAOS server, but users pointed to the DAOS server often archive their email themselves, pushing it to the archive server. Could this be a problem?
This shouldn't be a problem. the attachment will be copied to the non-DAOS enabled server as the documents are archived & the attachments will be stored in the .nsf. This process actually uses the replicator task, and the use of DAOS for attachments is invisible to this process.
Q6. We have a 77GB database; is the 64GB physical limit a myth?
You can go higher than 64gb physical but it is not supported. On newer releases of Domino we do not allow a database to grow beyond 64GB due to possible corruption issues. Release 8.5.3 introduced support for logical NSF sizes in excess of 64GB.
Q7. What is the best way for backup the NLO files? How do we know which NLO files erase from backup in the time?
Monitoring your DDM environment and setting up a resync. See "DAOS: How to setup resynchronization events with DDM"
Q8. We use Backup Exec 2012 which is DAOS aware. what does everybody else use?
Tivoli Data Protection for Domino.
Q9. Would DAOS need to be switched off for while upgrading a Domino?
You shouldn't have to disable DAOS to upgrade your server.
Q10. To move the DAOS directory outside from data directory, would I just need to force the resync of DAOS after the move?
See technote #1415153 - "How can I move the location of the DAOS subdirectory"
Q11. Are there any command line tools to monitor DAOS activity? Like DAOSest?
There are several commands you can use to check on DAOS in your environment such as 'tell daosmgr status' or 'show stat daos.*'See the following Help topics for details:
Q12. Is there a method to restore NLO files automatically from backup when you have the list of missing NLO files?
Currently there is no way to restore missing NLO files. There is a tool that can restore all NLO files, but not specific ones. The tool is only available via Interim Fix (hotfix) currently. Also, it is possible that the NLOs aren't missing but the references are incorrect. A resync force will cause resync to start over at the beginning, rebuilding the DAOS ID Table and the DAOS Object Index no matter what state the catalog was previously in.
Q13. Which is the minimum version of Tivoli that support DAOS?
IBM Tivoli Storage Manager for Mail, Data Protection for Lotus Domino, Version 6.3. See this article for details.
Q14. Are NLOs encrypted with the server public or private keys or just the server ID name?
It would be the public key. the server would use the private key to decrypt it. For details, see the "Deciding on encryption for NLO files" section of the DAOS Deployment Guide. Also refer to the following articles:
-- Supported Key sizes in Notes/Domino
-- Deploying FIPS 140-2 certified ID and document encryption
Q15. So the missing NLO command has to be passed after resync the catalog?
If you've resynchronized your DAOS catalog to make sure the references are correct, then the easiest way to check if they are still missing is to use the listnlo missing command.
Q16. I'm awaiting plan approval to purge email on 3-5-7 year purge interval. In the meantime, I'm DAOS enabling email less than 90 days but not DAOS enabling archives because of their exponential growth. Thoughts on this?
If you don't DAOS enable the archives, you will lose the benefit considering the archives are probably the biggest part of your data. And you'll get all of the penalties because you will still have to back up the NLOs separately if you don't have software that's aware of that. You'll still have to put in a process to have backups of your NLOs, and after you archive the databases will be swelling with the files that are taken out of DAOS. So instead of reusing them both, your archive databases and live databases, you're basically creating more files than needed.
Regarding your purge interval being seven years, even if you follow the strategy with the yearly backup, you can set up a full backup straightaway after you enable DAOS on them, then once this is approved, it will still be significantly smaller than if you kept the archive separate w/ the attachments and not enable DAOS. There's really no problem with enabling it because even if you delete the documents itself the prune interval by default is 30 days. Even if you really want to get rid of the additional attachments you could prune 0 (zero), which should be done with caution, but you could still after the decision is made get rid of all of the overhead nearly straightaway.
Q17. It would be advantageous situation if there was another DAOS folder for the archive map point that would solely keep the attachments in there for the archive. Then you would just be doing differentials and maybe one yearly full.
We usually go around that problem by creating an archive server, where you have a separate server for just that purpose and then you can adjust your plans for that. For example it could be a slower machine with more storage.
Q18. While trying to restore NLO files, we have a problem where users cannot create local replicas of these archives because replication blocks it saying "the file does not exist." Is there any way to bypass that?
You can't be in the process of restoring the attachments and at the same time the user creating a local replica. If there's an immediate need to have an archive locally that can be done by creating a copy of the databases and then you could run Fixup on it to remove the pointers. But that should done w/ extreme caution and only in very specific cases.
Q19. We have both TSM and TDP. We use TDP to back up our Domino servers and we have it set in the Global Config doc to disable DAOS encryption, so any server running DAOS is not encrypting NLO files. Can we do a restore to a secondary server that we want to use for just restores? Any type of issues with this kind of setup?
One thing you need to be aware of is the setting to disable the encryption of NLO files is not dynamic and would require a server restart for it to be enabled. So just to be aware of that before you make any of the NLOs, or if there are any NLOs that are encrypted just be aware of that and take precaution for those.
Q20. So when we delete NLOs and TSM does its backup of the existing databases just doing a normal incremental will it then delete those NLOs from the backup as well, or maintain that backup?
If it's incremental it's incremental. So if you delete them they will stay on your backup still. It all depends on the setting as well. It wouldn't make sense to keep only backups of NLOs that are still live on the server. That's why the yearly strategy comes into play here .If you don't devise the backups completely from the very beginning to the end you'll end up with something that grows constantly.
- wiki article: Archiving and recovering IBM Lotus DAOS-enabled databases
- wiki article: IBM Lotus Domino Attachment and Object Service (DAOS) deployment guide
- developerWorks "IBM Notes and Domino" product page
- technote #7015114 : Tivoli Field Guide - Data Protection for Domino Support for Domino 8.5
- technote #1448358 - Understanding the DAOS prune operation
- technote #1420878 : Where can I get more information on Domino Attachment and Object Service (DAOS)?
- Help topic: DAOS Manager Tell commands
For more information about our Open Mic webcasts, visit the IBM Collaboration Solutions Support Open Mics page. Follow highlights from these Open Mics live on Twitter using #ICSOpenMic or following us on Twitter @IBM_ICSsupport.