Novell EDIRECTORY 8.8 - GUIDE, Manual, Page: 374 / 574

Backing Up and Restoring Novell eDirectory 375
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
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
Section 14.3, “Using Roll-Forward Logs,” on page 389 .
• Specify a new location for the roll-forward logs (don't use the default).
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.
• Document where the roll-forward logs are placed, so that you can find them in the event of
a failure.
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.
• Monitor disk space on the disk partition/volume where the roll-forward logs are stored, so
that you can prevent it from filling up.
If roll-forward logs cannot be created because no more disk space is available, eDirectory
will stop responding on that server.
• Restrict access to where the roll-forward logs are kept, so that unauthorized users cannot
see them.
• If a restore is necessary, make sure you re-create the roll-forward log configuration on the
server after the restore is complete. The settings are reset to the default during a restore.
After turning on the roll-forward logs, you must also do a new full backup.
‰
If you use NICI, ensure that your eDirectory backups include NICI security files.
Otherwise, you will not be able to restore the encryption keys, and you won't be able to read
encrypted data. For more information about NICI security, see the
NICI Administration Guide
(http://www.novell.com/documentation/beta/nici27x/index.html) and the TID on backing up
NICI files (http://support.novell.com/cgi-bin/search/searchtid.cgi?/10098087.htm) .
‰
For multiple-server trees, if you are using the Backup eMTool to back up a server, you should
upgrade all the servers that share replicas with it to eDirectory 8.5 or later.
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” on page 380 and “Restore Verification Is Backward Compatible Only with eDirectory
8.5 or Later” on page 388 .
‰
(NetWare
®
only) Review the issues with file system rights in “Preserving Rights When
Restoring File System Data on NetWare” on page 388 . Test for potential problems and take
preventive action if necessary.
‰
Periodically check the backup log file to make sure that unattended backups were successful.
‰
Do a cold backup before upgrading a server, as described in Section 16.6, “Upgrading
Hardware or Replacing a Server,” on page 512 .
‰
For multiple-server trees, ensure that all eDirectory partitions are replicated on more than one
server, for fault tolerance.