domino 8.5 backup and restore
TRANSCRIPT
Data Protection for Domino Support for Domino8.5Using Data Protection for Domino to Backup and Restore Domino 8.5with DAOS
By Peter SymondsVersion 1.0
iii
Copyright Notice
Copyright IBM Corporation 2009. All rights reserved. May only be used pursuantto a Tivoli Systems Software License Agreement, an IBM Software LicenseAgreement, or Addendum for Tivoli Products to IBM Customer or LicenseAgreement. No part of this publication may be reproduced, transmitted,transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic,optical, chemical, manual, or otherwise, without prior written permission ofIBM Corporation. IBM Corporation grants you limited permiss ion to make hardcopyor other reproductions of any machine -readable documentation for your own use,provided that each such reproduction shall carry the IBM Corporation copyrightnotice. No other rights under copyright are granted without prior writtenpermission of IBM Corporation. The document is not intended for production andis furnished “as is” without warranty of any kind. All warranties on thisdocument are hereby disclaimed, including the warranties of merchantability andfitness for a particular purpose.
U.S. Government Users Restricted Rights -- Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corporation.
Trademarks
IBM, the IBM logo, Tivoli, the Tivoli logo, AIX, Cross -Site, NetView, OS/2,Planet Tivoli, RS/6000, Tivoli Certified, Tivoli Enterprise, Tivoli EnterpriseConsole, Tivoli Ready, and TME are trademarks or registered trademarks ofInternational Business Machines Corporation or Tivoli Systems Inc. in theUnited States, other countries, or both.
Lotus is a registered trademark of Lotus Development Corporation.Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.UNIX is a registered trademark of The Open Group in the Unite d States and othercountries.C-bus is a trademark of Corollary, Inc. in the United States, other countries,or both.PC Direct is a trademark of Ziff Communications Company in the United States,other countries, or both and is used by IBM Corporation unde r license.ActionMedia, LANDesk, MMX, Pentium, and ProShare are trademarks of IntelCorporation in the United States, other countries, or both. For a complete listof Intel trademarks, see http://www.intel.com/sites/corporate/trademarx.htm.SET and the SET Logo are trademarks owned by SET Secure Electronic TransactionLLC. For further information, see http://www.setco.org/aboutmark.html.Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Sun Microsystems, Inc. in the Un ited States and other countries.
Other company, product, and service names may be trademarks or service marks ofothers.
Notices
References in this publication to Tivoli Systems or IBM products, programs, orservices do not imply that they will be availabl e in all countries in whichTivoli Systems or IBM operates. Any reference to these products, programs, orservices is not intended to imply that only Tivoli Systems or IBM products,programs, or services can be used. Subject to valid intellectual property orother legally protectable right of Tivoli Systems or IBM, any functionallyequivalent product, program, or service can be used instead of the referencedproduct, program, or service. The evaluation and verification of operation inconjunction with other products, except those expressly designated by TivoliSystems or IBM, are the responsibility of the user. Tivoli Systems or IBM mayhave patents or pending patent applications covering subject matter in thisdocument. The furnishing of this document does not give you any license tothese patents. You can send license inquiries, in writing, to the IBM Directorof Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504 -1785,
iv
U.S.A.
v
vii
About the Tivoli Field Guides
SponsorTivoli Customer Support sponsors the Tivoli Field Guide program.
AuthorsThose who write field guides belong to one of these three groups:
Tivoli Support and Services Engineers who work directly with customers Tivoli Customers and Business Partners who have experience using Tivoli software in a
production environment Tivoli developers, testers, and architects
AudienceThe field guides are written for all customers, both new and existing. They are applicable toexternal audiences including executives, project leads, technical leads, team members, and tointernal audiences as well.
Types of Field GuidesTwo types of Tivoli Field Guides describe how Tivoli products work and how they are used in reallife situations:
Field Guides for technical issues are designed to address specif ic technical scenarios orconcepts that are often complex to implement or difficult to understand, for example:endpoint mobility, migration, and heartbeat monitoring.
Field Guides for business issues are designed to address specific business practices tha thave a high impact on the success or failure of an ESM project, for example: changemanagement, asset Management, and deployment phases.
PurposesThe Field Guide program has two major purposes:
To empower customers & business partners to succeed with Ti voli software bydocumenting and sharing product information that provides accurate and timelyinformation on Tivoli products and the business issues that impact an enterprise systemsmanagement project
To leverage the internal knowledge within Tivoli Cust omer Support and Services and theexternal knowledge of Tivoli customers and Business Partners
AvailabilityAll completed field guides are available free to registered customers and internal IBM employeesat the following Web site:
http://www.ibm.com/software/sysmgmt/products/support/Field_Guides.html
Authors can submit proposals and access papers by e -mail:
ix
Table of Contents
USING DATA PROTECTION FOR DOMINO TO BACKUP ANDRESTORE DOMINO 8.5 WITH DAOS......................................................... I
Sponsor................................ ................................ ................................ ...viiAuthors ................................ ................................ ................................ ...viiAudience ................................ ................................ ................................ .viiTypes of Field Guides ................................ ................................ ............ viiPurposes................................ ................................ ................................ .viiAvailability ................................ ................................ .............................. vii
USING DATA PROTECTION FOR DOMINO TO BACKUP ANDRESTORE DOMINO 8.5 WITH DAOS........................................................ 1
OVERVIEW ................................................................................................... 1
DOMINO SERVER BACKUP AND RESTORE STRATEGYCONSIDERATIONS ...................................................................................... 1
USE DATA PROTECTION FOR DOMINO TO BACKUP NSF AND NTF DATABASES .............. 2
USE THE TIVOLI STORAGE MANAGER BACKUP-ARCHIVE CLIENT TO BACKUP NLO FILES
................................ ................................ ................................ ................................ ......... 2
USE THE TIVOLI STORAGE MANAGER BACKUP-ARCHIVE CLIENT TO BACKUP
EXECUTION AND CONFIGURATION FILES ................................ ................................ ......... 2
OTHER CONSIDERATIONS ................................ ................................ ................................ . 3
DOMINO DATABASE BACKUP ................................................................ 3
INCREMENTAL BACKUPS................................ ................................ ................................ .. 3
SELECTIVE BACKUPS ................................ ................................ ................................ ....... 4
DOMINO TRANSACTION LOG ARCHIVE............................................... 5
DOMINO DATABASE RESTORE............................................................... 5
x
RESTORE PROCESSING ................................ ................................ ................................ ..... 6
ACTIVATION ................................ ................................ ................................ .................... 6
DETERMINE THE MISSING NLO FILES ................................ ................................ ............. 6
RESTORE THE MISSING NLO FILES................................ ................................ .................. 7
RESYNCHRONIZE THE DAOS CATALOG ................................ ................................ .......... 7
RESTORE AT DOCUMENT LEVEL ................................ ................................ ...................... 7
DISASTER RECOVERY ............................................................................... 8
RESTORE OF ARCHIVED TRANSACTION LOGS .................................. 9
EXAMPLE...................................................................................................... 9
SETUP PROCESSING ................................ ................................ ................................ .......... 9
BACKUP PROCESSING................................ ................................ ................................ ..... 10
Backup the Database ................................ ................................ .................. 10Backup the NLO Files ................................ ................................ .................. 11
CREATE THE CONDITION TO BE RECOVERED FROM ................................ ....................... 12
RESTORE PROCESSING ................................ ................................ ................................ ... 12
Restore the Database ................................ ................................ .................. 12Activate the Restored Database ................................ ................................ ..13Restore the NLO File ................................ ................................ ................... 16Restore at Document Level ................................ ................................ .........17
1
Data Protection for Domino Support for Domino8.5Using Data Protection for Domino to Backup and Restore Domino 8.5with DAOS
Data Protection for Domino provides a full c apacity to backup and restore Domino 8.5 NSF andNTF databases and transaction logs either offline or online. This document provides an overviewof the Data Protection for Domino product and describes the additional steps necessary tobackup and restore Domino 8.5 NLO files.
1OverviewWith version 8.5, IBM Lotus Domino server employs the Domino attachment and object service tosave significant space at the file level by sharing data identifie d as identical between databases(applications) on the same server in NLO files. In databases that use DAOS, the Domino serverno longer saves a separate and complete copy of every document attachment. Instead, theserver saves a reference to each attached file in an NLO file, and it refers to the same NLO filefrom multiple documents in one or more databases on the same server. NLO files may be presenton a Domino 8.5 server if DAOS is enabled on the server, and DAOS participation has beenelected for some of the NSF databases.
NLO files are not supported by Data Prot ection for Domino. They must be backed up andrestored using the Tivoli Storage Manager Backup -Archive Client. If DAOS is not enabled for anindividual NSF, and/or on the server, the current Data Protection for Domino backup and restoreprocedures should be followed.
2Domino Server Backup and Restore StrategyConsiderationsYou can choose different backup strategies depending on your specific requirements regardingnetwork traffic, backup window, and acceptable restore times. Your choice of strategy will includeselecting the type of backup commands to use and the type of transaction logging to be done onthe Domino server.
2
Use Data Protection for Domino to Backup NSF andNTF DatabasesData Protection for Domino provides backup and restore functions for t he Domino NSF and NTFdatabases (including template files) and associated transaction logs. However, Data Protectionfor Domino does not provide a complete disaster recovery solution for a Domino server by itself.You need to use the Tivoli Storage Manager Backup-Archive Client in conjunction with DataProtection for Domino for a complete disaster recovery solution.
Use the Tivoli Storage Manager Backup -ArchiveClient to Backup NLO FilesData Protection for Domino does not process NLO files; instead , the Tivoli Storage ManagerBackup-Archive Client must be used to backup and restore NLO files. NLO files are not modifiedonce they are created, so only new NLO files need to be processed when doing an incrementalbackup.
The backup of the NLO files should be d one after the backup of the NSF and NTF databases.This will ensure that the NLO files in the backup are a superset of what is referenced by the NSFdatabases.
The DAOS deferred delete interval should be set to be longer than the interval between backups.If the backups are done weekly, the shortest recommended DAOS deferred delete interval is 8days. Setting the delete interval longer than the backup interval will guarantee that all NLO fileswill be backed up. If there is a retention limit for backups, th e DAOS delete interval should be setto longer than that retention limit to ensure that all referenced NLO files will exist if a NSFdatabase is restored from the oldest backup.
Use the Tivoli Storage Manager Backup -ArchiveClient to Backup Execution and Configuration FilesThere are many files that are part of the Domino server installation, such as execution andconfiguration files, which include the DAOS configuration file, daos.cfg . This configuration file isnot supported by Data Protection for Domi no; therefore, this must be part of your recoverystrategy. For example, database link files have an nsf extension but are not considereddatabases and are not backed up by Data Protection for Domino. These files must be recoveredin a disaster recovery situation. A comprehensive disaster recovery plan can be achieved usingthe Tivoli Storage Manager Backup -Archive Client in conjunction with Data Protection for Domino.
Personal copies (replicas) of Domino databases that are stored on Notes clients (not on theDomino server) are not protected by Data Protection for Domino. You can use the Tivoli StorageManager Backup-Archive Client on the Notes client platform to backup and restore these files orrely on Domino server replication if you need to recover them .
3
Other ConsiderationsTo restore an individual Notes document, you must restore the entire database with an alternatename. Choose a time when the document existed for both the restore /pit and activate /applylogscommands but before the document was de leted, and then copy the desired document using theNotes client.
Data Protection for Domino can only backup transaction logs from a Domino server that hasarchival logging in effect. Transaction logs cannot be backed up from a Domino server that hascircular or linear logging in effect.
When using archival transaction logging, the frequency of the archivelog command use dependson the size of your log and the rate of change for logged databases. Perform archival transactionlogging several times per day if you generate a large volume of changes at a rapid rate.
When restoring a group of logged databases for which transactions need to be applied, activatethem together when possible. This avoids restoring the same transaction log files multiple times.Restored transaction log files are deleted during a database recover y by the Domino server.Activating and applying logs to the database separately requires retransmitting log files for eachdatabase.
3Domino Database BackupData Protection for Domino can perform full and incremental online backups of individual NSFand NTF databases when archival logging is in effect. If archival loggin g is not in effect, only fulloffline backups of NSF databases can be performed.
NSF and NTF databases should be backed up usi ng Data Protection for Domino to ensure thatan internally consistent image of the NSF is saved and that the Domino transaction logs arearchived as part of the backup process. Attempting to back up an NSF or NTF database withoutusing Data Protection for Domino while the Domino server is running (and possibly in the processof modifying the file) may result in an unusable image being saved.
Data Protection for Domino provides two types of database backups: incremental and selective.
Incremental BackupsAn incremental backup will perform a full online backup of Domino databases under the followingconditions:
1. The database is within the Domino data path or symbolically linked to the Domino datapath by directory or database links.
2. The database is not excluded from backup by exclude statements within the TivoliStorage Manager include-exclude options file.
4
3. If the database is logged, the DBIID has changed.
4. If the database is not logged, it has been modified since the last backup occurred (dataand non-data modification dates are checked).
5. The database is new or newly included in the backup.
The incremental command includes a function that determines if active backup database copiesexist on the Tivoli Storage Manager server that were deleted from the Domino server or excludedfrom backup. If so, they are marked inactive so automatic expiration of these backup copies canoccur according to defined management class parameters for backup files.
The incremental command normally specifies a wild card qualified name, and the databases thatmatch the wild card qualification and meet the selection criteria for an incremental backup will bebacked up.
It is recommended to use the Tivoli Storage Manager Backup -Archive Client incrementalcommand to backup NLO files because once they are written they are never changed. If selectivebackups of the NLO files are made, each additional backup of the same file results in an identicaladditional backup. If incremental backups of the NLO files are made, only a single backup file iscreated.
When backing up NSF and NLO files, first backup the NSF databases and then backup the NLOfiles.
The Data Protection for Domino command to incrementally backup NSF databases is
domdsmc incr database_selection_criteria
The Tivoli Storage Manager Backup-Archive Client command to incrementally backup all NLOfiles is
dsmc incr /local.notesdata/daos/* -su=yes
Notice that the Tivoli Storage Manager Client incremental backup command of the NLO files mustspecify the fully qualified path name of the NLO files to be backed up.
Selective BackupsA selective backup unconditionally backs up the specified databases, unless they are excludedfrom backup through exclude statements within the Tivoli Storage Manager include -excludeoptions file.
It is not recommended to use the Tivoli Storage Manager Backup -Archive Client selectivecommand to backup NLO files because once they are written they are never changed. If selectivebackups of the NLO files are made, each additional backup of the same file results in anadditional identical backup.
When backing up NSF, NTF, and NLO files, first backup the NSF and NTF databases and thenincrementally backup the NLO files .
The Data Protection for Domino command to selectively backup NSF databases is
5
domdsmc sel database_selection_criteria
The Tivoli Storage Manager Backup -Archive Client command to incrementally backup all NLOfiles is
dsmc incr /local.notesdata/daos/* -su=yes
4Domino Transaction Log ArchiveData Protection for Domino provides the capability to create archives of transaction logs whenarchival logging is in effect. There are no changes required in archiving Domino transaction logswhen DAOS is enabled.
A transaction log captures database changes so full database backups are not required asfrequently. Updates to a logged database are recorded in the Domino server transaction log.Changes to a database since the last full backup can be applied from the transaction log after thebackup is restored from the last full backup. Enabling transaction logging for al l databases on aDomino server is not required, so the backup process must handle both logged and non -loggeddatabases. Domino allows the active transaction log to be backed up , as well.
The Data Protection for Domino archive log capability stores filled t ransaction log files on theTivoli Storage Manager Server so that space allocated for these files can be reused by theDomino logger. The archivelog command is available when transaction logging on the Dominoserver is enabled in archival mode. Filled tran saction log files must be archived frequently enoughto ensure the transaction log never fills completely and stops the Domino server.
Transaction log files stored on the Tivoli Storage Manager server are automatically restored asneeded for a database recovery.
Archived transaction log files are retained on the Tivoli Storage Manager server as long as adatabase backup exists that needs these log files for a complete recovery.
The Data Protection for Domino command to archive the Domino server transaction log is
domdsmc archivelog
Note: When circular or linear loop logging is used on the Domino server (or when logging isdisabled on the Domino Server), transaction log files are not archived.
5Domino Database Restore
6
The restoration of a Domino NSF or NT F database is a two-step recovery process. The first stepis to use the Data Protection for Domino domdsmc restore command to restore one or moredatabases from the Tivoli Storage Manager server backup storage to the Domino server.
The second step is to use the Data Protection for Domino domdsmc activate command to bringthe restored databases online for use by the Domino server and optionally apply transactionsfrom the transaction log to update the database to the latest level.
These two steps can be combined into one step by specifying the /activate=yes option on therestore command.
When the restored NSF database is enabled for DAOS, then one or more NLO files may alsoneed to be recovered and additional steps are required. The first step is to determine if there areany missing NLO files referenced by the restored NSF databases. If there are missing NLO files,a second additional step is necessary to use the Tivoli Storage Manager Backup -Archive Client torestore the required NLO files.
Restore ProcessingThe restore process retrieves previously backed up copies of the databases to be restored fromthe Tivoli Storage Manager server and restores them to the Domino server storage. You canrestore the database with the original name (replace), with a diffe rent database file name, to thesame name in a different Domino server directory, or to a different Domino server.
The Data Protection for Domino command to restore an NSF database is
domdsmc restore database_name –into restored_database_name
ActivationAfter the NSF and NTF database(s) have been restored, the Data Protection for Dominodomdsmc activate command is used to apply any changes to the restored databases from therecovery logs and to activate the NSF and NTF databases that are being restored.
This activation step brings restored databases online for use by the Domino server. You canoptionally apply transactions from the transaction log to update the database. Transactions canbe applied up to a specific point in time or up through the most recen t changes recorded in thetransaction log. If archival logging is in effect, Data Protection for Domino automatically restoresarchived transaction log files as needed.
The Data Protection for Domino command to activate and apply logs to one or more databa ses is
domdsmc activate –applylogs
Determine the Missing NLO Files
7
Issue the DAOS Manager tell daosmgr listnlo command from the Domino server console todiscover the names of any missing NLO files that are referenced by the restored NSF databases.If the DAOS deferred delete interval is longer than the age of the restored backup, there will beno missing NLO files. However , if the age of the backup is greater than the DAOS deferred deleteinterval, you may also have to restore the missing NLO files.
The server command to determine the NLO files that must also be restored is
Tell daosmgr listnlo –o missingnlo.txt missing nsf_database_name
The file missingnlo.txt contains a list of NLO files that are referenced by the restored NSFdatabase that are not found on the Domino server. {They are output in fully -qualified form.}
Restore the Missing NLO FilesUse the Tivoli Storage Manager Backup -Archive Client dsmc restore command to restore themissing NLO files.
Note the option –latest on the restore command. This option specifies that the latest copy,whether active or inactive, should be used. If this option is not specified and the nlo file has beenexpired by an incremental backup, you will get the message “ANS1302E No object on servermatch query” and the restore operation will fail.
dsmc restore –filelist missingnlo.txt –latest
Resynchronize the DAOS CatalogIn order to ensure DAOS has the correct reference counts after the missing NLO files have beenrestored, you should run the tell daosmgr resync command from the Domino server console.
If the catalog is still synchronized after the restoration, this command will simply close.
Restore at Document LevelData Protection for Domino restores Domino databases at the database level. To restore adocument in a database, the entire database and the necessary NLO files must first be restoredand then copied to the “live” NSF database.
A database can be restored to the production server under a temporary name , and the desireddocument can be copied to the appropri ate database. If, for performance reasons, the productionserver cannot be used in the restore process, the database can be restored to an alternate serverand copied to the production server. It is recommended that you perform alternate server restoreswhen possible to reduce demands on the Domino production server. Alternate server restorescan be performed to an alternate partition or to a separate Domino server by using the followingsteps:
1. Inform the user of the location of the restored NSF .
8
2. The user can copy the necessary documents from the restored NSF to the live NSF .3. When the user has finished copying the data from the restored NSF to the live NSF,
delete the restored NSF.4. If the document includes a DAOS attachment, restore any missing NLO files and
resynchronize the DAOS catalog with the tell daosmgr resync command to repair thereference counts.
6Disaster RecoveryYou need to use the Tivoli Storage Manager Backup -Archive Client in conjunction with DataProtection for Domino for a complete disast er recovery solution. Disaster recovery of a Dominoserver requires rebuilding the directory structure, restoring the non -database files with the TivoliStorage Manager Backup-Archive Client, and recovering the database files to the latest level withData Protection for Domino. The following steps outline the process to be followed whilerecovering a Domino server. The existence of NLO files only changes the first step where NLOfiles are recovered along with other non -database files such as notes.ini.
1. Make sure the new installation is configured in the same manner as the damaged one(for example, the same directory structure, d irectory location, and logdir path).
2. Use the Tivoli Storage Manager Backup -Archive Client to recover the non-databaseDomino server files such as notes.ini, cert.id and server.id. If a Domino attachment andobject service is present, the NLO files should also be r ecovered at this time.
3. Use a text editor to modify the notes.ini file for the Domino server with this setting:TRANSLOG_Status=0
4. Use Data Protection for Domino to restore the transaction log file to be used in the logrecovery procedure. This should be the last transaction log file archived prior to the lossof the active transaction log.
5. Delete the contents of the Domino t ransaction log directory except for the log file restoredin Step 4.
6. Use a text editor to modify the notes.ini file for the Domino server with these settings:TRANSLOG_Recreate_Logctrl=1TRANSLOG_Status=1
7. Use Data Protection for Domino to restore (but no t to activate) the databases you wantto recover to the latest level within the archived log extents.
8. Use the Tivoli Storage Manager Backup -Archive Client to recover the latest NLO files.9. Use Data Protection for Domino to activate the databases you are rec overing and apply
transaction logs. (The TRANSLOG_Recreate_Logctrl parameter in the notes.ini file willbe automatically reset to 0).
10. Launch the Domino server. With the disaster recovery complete, it is now safe to start theDomino server and execute server tasks and functions.
11. Use the Selective backup function in Data Protection for Domino to perform full backupsof all databases. (This is recommended to ensure proper recoverability using subsequenttransaction log files).
12. Use Data Protection for Domino to archive the transaction log. The transaction log fileused in the recovery procedure will be modified and available for archiving. Thistransaction log will also have the ID of the current logger.
7
9
Restore of Archived Transaction LogsThis Data Protection for Domino function allows a single, archived transaction log file to berestored independently of a routine database restore. Restoring a single, archived transaction logfile assists with disaster recovery operations. By retrieving the most recent a rchived log file, it ispossible to rebuild the Domino transaction log control file. This allows archived transaction logfiles to be used to recover restored database backups to a more current state, even after a loss ofthe active transaction log. Note t hat more than one archived transaction log file can be restored ata time.
The Data Protection for Domino command to restore an archived log is
Domdsmc restorelogarchive log_name
8ExampleThis chapter provides a complete example of restoring an individua l document and its attachmentin a Notes database that uses the Domino attachment and object service.
Setup ProcessingThe first step in this process is to create a Notes database with the DAOS enabled. Once thedatabase has been created, add a new docume nt (containing an attachment) to the database.The picture below shows the test Journal database entry with a jpg file attached :
10
The Domino 8.5 server stores the attachment in an NLO file. If you look in thenotesdata/DAOS/0001 directory with the UNIX Is command, you should see an NLO filecorresponding to the document and its attachment.
> lsFB662CBD45033E03F65E0F278F44F4206A3C429300014752.nlo
Backup ProcessingBackup the DatabaseYou should backup the database with Data Protection for Domino after all changes have beenmade to the test database.
The following shows the results of issuing a Data Protection for Domino command to backup thetest database:
> domdsmc sel myattachjou1.nsf
IBM Tivoli Storage Manager for Mail:Data Protection for Lotus DominoVersion 5, Release 5, Level 1.02(C) Copyright IBM Corporation 1999, 2008. All rights reserved.
11
ACD5221I The /opt/tivoli/tsm/client/domino/bin64/domdsmc_notes/domdsm.log log file has beenpruned successfully.
Starting Domino database backup...Initializing Domino connection...Querying Domino for a list of databases, please wait...
Backing up database myattachjou1.nsf, 1 of 1.Full: 0 Read: 958464 Written: 958464 Rate: 7,090.91 Kb/SecBackup of myattachjou11.nsf completed successfully.
Total Domino databases inspected: 1Total Domino databases backed up: 1Total Domino databases excluded: 0
Throughput rate: 7,037.59 Kb/SecTotal bytes transferred: 958,464Elapsed processing time: 0.13 Secs
Backup the NLO FilesThe NLO files in the DAOS directory should be backed up with the Tivoli Storage ManagerBackup-Archive Client after the database file has been backed up. Backing up the NLO files afterbacking up the NSF databases using the Domino attachment and object service will ensure thatthe NLO files in the backup are a superset of what is referenced by the NSF databases.
Notice that the Tivoli Storage Manager Backup -Archive Client command specifies the fullyqualified name of the NLO files to be backed up, “/local/notesdata/DAOS/* -su=yes. The“DAOS/*” indicates that everything in the DAOS directory and everything in the next level are tobe backed up.
The following shows the results of issuing a Tivoli Storage Manager Backup-Archive Clientincremental backup command to backup NLO files:
> dsmc incr /local/notesdata/DAOS/* -su=yesIBM Tivoli Storage ManagerCommand Line Backup-Archive Client Interface Client Version 6, Release 1, Level 0.0 Client date/time: 12/09/2008 16:43:08(c) Copyright by IBM Corporation and other(s) 1990, 2009. All Rights Reserved.
Node Name: SJTLNX07NOTESSession established with server FVTSERIES5_V55: Windows Server Version 5, Release 5, Level 0.0 Server date/time: 12/09/2008 16:42:39 L ast access: 12/09/2008 15:17:05
Incremental backup of volume ‘/local/notesdata/DAOS/*’
Normal File--> 84,091/local/notesdata/DAOS/0001/FB662CBD45033E03F65E0F278F44F4206A3C429300014752.nlo[Sent]
Successful incremental backup of '/local/notes data/DAOS/*'
12
Total number of objects inspected: 1Total number of objects backed up: 1Total number of objects updated: 0Total number of objects rebound: 0Total number of objects deleted: 0Total number of objects expired: 0Total number of objects failed: 0Total number of bytes transferred: 82.15 KBData transfer time: 0.00 secNetwork data transfer rate: 315,966.79 KB/secAggregate data transfer rate: 38.51 KB/secObjects compressed by: 0%Elapsed processing time: 00:00:02
Create the Condition to be Recovered FromAt this point, the database containing the attachment has been created and the database andNLO files have been backed up. Now you can create the condition to be recovered from. In thisexample there is only one NLO file, which simplifies discovering the NLO file to be deleted. Ifthere are multiple NLO files, you can use the creation date of the files to find the NLO file createdwhen the jpg file was attached to the document in question.
If you have multiple databases or documents that attach the same file, there will be only one NLOentry and the creation date of the NLO file will correspond to the date of the f irst attachment. Youcan still delete the NLO file, but its deletion will affect all databases and documents that referencethat attachment.
First delete the document in myattachjou1.nsf containing the attachment, then swit ch to theDAOS directory and remove the NLO file containing the attachment for myattachjou1.nsf. Theexample below changes to the DAOS/0001 directory, lists the files in that directory , and thendeletes the NLO file.
> cd /local/notesdata/DAOS/0001> lsFB662CBD45033E03F65E0F278F44F4206A3 C429300014752.nlo> rm *> ls
Restore ProcessingRestore the DatabaseThe first step in restoring an individual document in a database is to restore a down level copy ofthe database containing the document to be recovered to an alternate directory. In th is example,the directory recoverDir is the alternate directory used to restore the down level database.
The following shows the results of issuing a Data Protection for Domino command from thedatabase to the alternate directory recoverDir.
> domdsmc rest myattachjou1.nsf -into=recoverDir/myatachjou1r.nsfIBM Tivoli Storage Manager for Mail:
13
Data Protection for Lotus DominoVersion 5, Release 5, Level 1.02(C) Copyright IBM Corporation 1999, 2008. All rights reserved.
Starting Domino database restore...
Initializing Domino connection...Logging on to the Tivoli Storage Manager server, please wait...Transaction Logging hardware-assisted data compression is enabled.Restart Analysis (0 MB): 100%12/05/2008 04:04:57 PM Recovery Manager: Restart Recovery c omplete. (0/0 databasesneeded full/partial recovery)Querying Tivoli Storage Manager server for a list of database backups, please wait...
Clearing DBIID 72D4BCAC for DB /local/notesdata/recoverDir/myattachjou1r.nsf.dad12/05/2008 04:04:57 PM Recovery M anager: Assigning new DBIID for/local/notesdata/recoverDir/myattachjou1r.nsf.dad (need new backup for media recovery).12/05/2008 04:04:57 PM Informational - The database/local/notesdata/recoverDir/myattachjou1r.nsf.dad has caused the DAOS catalog to be come outof sync. Deletions will be postponed. Please run 'tell daosmgr resync' at the next convenientopportunity to re-synchronize.
Restoring database myattachjou1.nsf, 1 of 1, to /local/notesdata/recoverDir/myattachjou1r.nsf.dadFull: 0 Read: 958464 Written: 958464 Rate: 18,352.94 Kb/SecRestore of myattachjou1.nsf completed successfully.
Total database backups inspected: 1Total database backups requested for restore: 1Total database backups restored: 1Total database activated: 0
Throughput rate: 18,352.94 Kb/SecTotal bytes transferred: 958,464Elapsed processing time: 0.05 Secs
Notice that the restore operation issued the following informational message
12/05/2008 04:04:57 PM Informational - The database/local/notesdata/recoverDir/myattachjou1r.nsf.dad has caused the DAOS catalog to become outof sync. Deletions will be postponed. Please run 'tell daosmgr res ync' at the next convenientopportunity to re-synchronize.
This is a good time to issue the tell daosmgr resync command on the Domino server console.
Activate the Restored DatabaseThe Data Protection for Domino restore command places the restored database in anintermediate state that does not allow the restored database to be accessed until the activ ationcommand is issued. If the UNIX Is command is used to verify that the database exists, you willnotice a dad extension.
notes@sjtlnx07:/local/notesdata/ recoverDir> lsmyattachjou1r.nsf.dad
14
You must issue the Data Protection for Domino activate command to make the databaseavailable.
> domdsmc activate
IBM Tivoli Storage Manager for Mail:Data Protection for Lotus DominoVersion 5, Release 5, Level 1.02(C) Copyright IBM Corporation 1999, 2008. All rights reserved.
Starting Domino database activation...
Initializing Domino connection...Logging on to the Tivoli Storage Manager server, please wait...
Activating database recoverDir/myattachjou1r.nsf, 1 of 1,Clearing DBIID 72D4BCAC for DB /local/notesdata/recoverDir/myattachjou1r.nsf.dad12/05/2008 04:07:55 PM Recovery Manager: Assigning new DBIID for/local/notesdata/recoverDir/myattachjou1r.nsf.dad (need new backup for media recovery).Activate of recoverDir/myattachjou1r.nsf completed successfully.
Total pending databases inspected: 1Total pending databases requested for activation: 1Total pending databases activated: 1
Recovery is not complete at this point. The Notes database has been recovered, and the deleteddocument can be viewed.You can access the document in recoverDir/myattachjou1r.nsf now, and it looks like everything isrestored.
15
But when you try to view the attachment, a “File does not exist” erro r is displayed.
16
And the server console also shows a missing file message
> 12/05/2008 04:11:13 PM Admin Process: Searching Administration Requests database12/05/2008 04:14:35 PM The database /local/notesdata/recoverDir/myattachjou1r.nsf attemptedto access a missing file:/local/notesdata/DAOS/0001/FB662CBD45033E03F65E0F278F44F4206A3C429300014752.nlo:File does not exist12/05/2008 04:14:35 PM HTTP Web Server: Lotus Notes Exception - File does not exist[/recoverDir/myattachjou1r.nsf/e7a291052e43 215e852567240071e2ad/76044acbc0793e938825751600607984/Body/M2/Water%20lilies.jpg?OpenElement]
You can also easily discover the names of the missing file(s) by issuing the tell daosmgr listnlocommand and then examining the file lis tnlo.txt.
tell daosmgr listnlo recoverDir/myattachjou1r.nsf
> 12/05/2008 05:08:38 PM DAOSMGR: ListNLO started forNSF:/local/notesdata/recoverDir/myattachjou1r.nsf12/05/2008 05:08:38 PM DAOSMGR: ListNLO output file: /local/notesdata/listnlo.txt12/05/2008 05:08:38 PM DAOSMG R: ListNLO completed - 1 entries processed
cat /local/notesdata/listnlo.txt/local/notesdata/DAOS/0001/FB662CBD45033E03F65E0F278F44F4206A3C429300014752.nlo
Restore the NLO FileThe following shows the results of issuing a Tivoli Storage Manager Backup -Archive Clientcommand to restore the missing NLO file.
Note the option –latest on the restore command. This option specifies that the latest copy,whether active or inactive should be used. If this option is not specified and the NLO file has beenexpired by an incremental backup, you will get the message “ANS1302E No object on servermatch query” and the restore operation will fail.
> dsmc rest/local/notesdata/DAOS/0001/FB662CBD45033E03F65E0F278F44F4206A3C429300014752.nlo -latestIBM Tivoli Storage ManagerCommand Line Backup/Archive Client Interface Client Version 5, Release 5, Level 1.0 Client date/time: 12/05/2008 16:17:39(c) Copyright by IBM Corporation and other(s) 1990, 2008. All Rights Reserved.
Node Name: SJTLNX07NOTESSession established with server FVTSERIES5_V55: Windows Server Version 5, Release 5, Level 0.0 Server date/time: 12/05/2008 16:17:09 Last access: 12/05/2008 16:07:25
Restore function invoked.
Restoring 84,091/local/notesdata/DAOS/0001/FB662CBD45033E03F65E0F278F 44F4206A3C429300014752.nlo[Done]
17
Restore processing finished.
Total number of objects restored: 1Total number of objects failed: 0Total number of bytes transferred: 82.15 KBData transfer time: 0.00 secNetwork data transfer rate: 50,245.48 KB/secAggregate data transfer rate: 26.28 KB/secElapsed processing time: 00:00:03notes@sjtlnx07:/local/notesdata/recoverDir>
Once the missing NLO file has been restored, you can view the document an d its attachment
Restore at Document LevelNow that the backup copy of the database has been restored to the alternate database inrecoverDir, the individual document can be copied to the “live” NSF database using the followingsteps:
1. Inform the user of the location of the restored database, recoverDir/myattachjou1r.nsf2. The user can copy the necessary documents from the restored database,
recoverDir/myattachjou1r.nsf, to the live database, myattachjou1.nsf
18
3. When the user has finished copying the data fro m the restored database to the livedatabase, delete the restored database r ecoverDir/myattachjour.nsf.