Novell EDIRECTORY 8.8 - GUIDE, Manual

Page: 380 / 574

Backing Up and Restoring Novell eDirectory 381
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
7. If verification is successful, RST is renamed to NDS and the login disabled attribute is cleared
so it becomes the active eDirectory database on the server. If verification fails, the RST DIB is
not renamed, and the active DIB set is set back to NDS.
If verification fails, see
Section 14.9, “Recovering the Database If Restore Verification Fails,”
on page 425 for how to recover the server. (It's possible to force the RST database to be
activated and unlocked using advanced restore options, but this is not recommended unless
suggested by Novell Support.)
14.2.4 Format of the Backup File Header
The backup files contain a header that you can read to learn important information such as
• The filename of the backup file when it was created.
This is helpful if the filename has been changed since the backup was created.
• The current roll-forward log at the time of this backup.
If this is the last backup in the set you are restoring from (such as the last incremental backup in
a set of one full backup and three incremental backups), this helps you because it indicates the
first roll-forward log that you need for a complete restore.
• The replicas this server held.
This is helpful if you did not have the placement of your replicas documented. If you
experienced a disaster in which many servers were lost, the list of replicas shown in the backup
file header might help you decide which servers to restore first.
• The names of the files that were included in the backup as specified in a user include file.
• The number of files in the backup set for that backup.
The header of the backup file for each individual backup is in XML format. Immediately following
the header is the backup data from the database in binary code. (Because of the inclusion of binary
data at the end of the file, parsing the file would give errors, but the XML header complies with
XML standards.) In cases where the backup spanned more than one file, the header information is
included in each file in the set.
WARNING: When opening a backup file, just view the header—make sure you don't try to save or
modify the file, or it might become truncated. Most applications can't save the binary data correctly.
The following is the DTD for the XML header. (The DTD is included as part of the header in the
backup file as well, for your reference.)
<?xml version=”1.0” encoding=”UTF-8” standalone=”yes” ?>
<!DOCTYPE backup [
<!ELEMENT backup (file|replica)*>
<!ELEMENT file (#PCDATA)>
<!ELEMENT replica EMPTY>
<!ATTLIST backup version CDATA #REQUIRED
backup_type (full|incremental) #REQUIRED
idtag CDATA #REQUIRED
time CDATA #REQUIRED
srvname CDATA #REQUIRED
dsversion CDATA #REQUIRED
compression CDATA “none”