428 Novell eDirectory 8.8 Administration Guidenovdocx (en) 11 July 200816.2.3 Overview of How the Backup eMTool Does a RestoreBefore restoring, you need to collect all your backup files by following the instructions inSection 16.4, “Preparing for a Restore,” on page 442. When you direct the Backup eMTool to beginthe restore through iManager or the eMBox Client, the process is done by the Backup eMTool asfollows:1. The DS Agent is closed.2. The active DIB (Data Information Base) set is switched from the DIB set named NDS to a newDIB set named RST.(The existing NDS database is left on the server; if the restore verification fails it will onceagain become the active DIB set.)3. The restore is performed, restoring to the DIB set named RST.4. The DIB set is disabled.The login disabled attribute is set on the pseudo server, preventing the DS Agent from beingable to open using this DIB set.5. The roll-forward log settings are reset to the default. You can prevent this by using -s switch.This means that after a restore, roll-forward logging on the server is always set to off, and thelocation of the roll-forward logs is reset to the default.(If you want roll-forward logging turned on for this server, you must plan to re-create yourconfiguration for roll-forward logging after a restore, to make sure it is turned on and the logsare being saved in a fault-tolerant location. After turning on the roll-forward logs, you mustalso do a new full backup.)6. Verification of the restored RST database is performed.The server attempts to verify the consistency of the data that has been restored. It does this bycontacting every server that it shares a replica with and comparing the transitive vectors.The output from this verification process is printed in the log file.If the transitive vector on the remote server is ahead of the local vector, then data is missingfrom the restore, and the verification fails.Here is an example of the information that's recorded in the log file if verification fails for oneof the replicas, showing the transitive vectors that were compared:Roll-forwardlogging for anindividual serverNot designed to provide this. Lets you keep a record of transactions in thedatabase since the last backup, so you canrestore a server to the state it was in at themoment before it went down. In a multiple-server environment, this allows you torestore a server to the synchronization statethat the other servers expect. Roll-forwardlogging is off by default. For moreinformation, see Section 16.3, “Using Roll-Forward Logs,” on page 437.Issue Legacy TSA for NDS Backup Backup eMTool “Hot Continuous Backup”
