For information on creating replicas, see Adding a Replica.
Backup eMTool writes the backup files to a directory you specify on the server, but has no way of placing the data directly to tape. File system backup should be set to run after the eDirectory backup has run, to place the database backup files on tape for safe storage.
You must turn on roll-forward logging for servers that participate in a replica ring. If you don't, when you try to restore from your backup files you will get errors and the database will not open. The restore by default won't open a database that shares replicas with other servers unless it is restored back to the state it was in at the moment before it went down.
In a single-server environment, roll-forward logging is not required for the restore verification process, but you can use it if you want to be able to restore eDirectory to the moment before it went down instead of just to the last backup.
Here is a list of the main issues you must address when you turn on roll-forward logging. For more information, see Using Roll-Forward Logs.
The logs must be local to the server. For fault tolerance, they must not be stored on the same disk partition/volume or the same storage device as eDirectory. You might want a separate disk partition/volume just for roll-forward logs.
To find out the location when the server is healthy, you can look it up in iManager in Backup Configuration, or in the eMBox Client using the getconfig option. But if the server has a failure that affects eDirectory (such as a hardware failure), you won't be able to look up the location of the roll-forward logs.
If roll-forward logs cannot be created because no more disk space is available, eDirectory will stop responding on that server.
The restore verification process is backward compatible only with 8.5 or later. For more information about the restore verification, see Overview of How the Backup eMTool Does a Restore and Restore Verification Is Backward Compatible Only with eDirectory 8.5 or Later.
In addition to making objects available when a server is down, such as during maintenance, replicating your partitions also provides fault tolerance in a case where you lose a server, such as a hardware failure. If a server in a multiple-server tree holds a partition that is not replicated, and the server has a failure, there's a risk that you might not be able to recover the partition. It's best to make sure all partitions are replicated. For more information on why you might not be able to recover an unreplicated partition in a multiple-server tree, see Overview of How the Backup eMTool Does a Restore, Using Roll-Forward Logs, and Recovering the Database If Restore Verification Fails.
For information on replication, see Replicas and Managing Partitions and Replicas.
iManager lets you do backup and restore tasks remotely, outside the firewall, but it does not support cold backup and advanced tasks.
The eMBox Client is installed with eDirectory on the server, and you can also use it on workstations with Sun JVM 1.3.1. For information on installing and configuring the eMBox Client, see Using the eMBox Command Line Client.
See Using DSMASTER Servers as Part of Disaster Recovery Planning.