
Backing Up and Restoring Novell eDirectory
435
n
ov
do
cx (e
n)
11
Ju
ly 20
08
If your tree is designed this way, in the event of a disaster you could get your tree structure up and
running again quickly by restoring just that one server (or small group of key servers) and making
sure the replicas it holds are designated as the master replicas.
After your tree structure is responding again, you could then move to the task of restoring other
servers that were lost, using just the full and incremental backup files. Because you don't have the
roll-forward logs, the verification of the restore process will fail for these other servers. To bring
them back into the tree, you would remove them from the replica ring, change all their replica
information to external references using DSRepair, and then re-add the replicas to the servers using
replication from the copy on the DSMASTER server. These steps are documented in
Section 16.9,
“Recovering the Database If Restore Verification Fails,” on page 477
.
If a disaster occurs in which you lose many servers but not all, the issues with replicas will probably
be complex, and you should contact Novell Support.
16.2.7 Transitive Vectors and the Restore Verification Process
A transitive vector is a time stamp for a replica. It is made up of a representation of the number of
seconds since a common specific point in history (January 1, 1970), the replica number, and the
current event number. Here's an example:
s3D35F377 r02 e002
In the context of backup and restore, it's important because the transitive vector is used to verify that
the server restored is in sync with the replica rings it participates in.
Servers that hold replicas of the same partition communicate with each other to keep the replicas
synchronized. Each time a server communicates with another server in the replica ring, it keeps a
record of the transitive vector the other server had when they communicated. These transitive
vectors allow the servers in a replica ring to know what information needs to be sent to each replica
in the ring to keep all the replicas synchronized. When a server goes down, it stops communicating,
and the other servers don't send updates or change the transitive vector they have recorded for that
server until the server starts communicating again.
When you restore eDirectory on a server, the restore verification process compares the transitive
vector of the server being restored to the other servers in the replica ring. This is done to make sure
that the replicas being restored are in the same state that the other servers expect.
If the transitive vector on the remote server is ahead of the local vector, then data is missing from the
restore, and the verification fails. (For example, data might be missing because you did not turn on
continuous roll-forward logging before the last full or incremental backup, you did not include the
roll-forward logs in the restore, or the set of roll-forward logs you provided for the restore was not
complete.)
By default the restored eDirectory database is not opened if it is inconsistent with the other replicas.
For an example of the log file entry when transitive vectors don't match, see
“Overview of How the
Backup eMTool Does a Restore” on page 428
.
For a description of compatibility issues that could cause the restore verification to fail, see
“Restore
Verification Is Backward Compatible Only with eDirectory 8.5 or Later” on page 436
.
For information on what to do if the restore verification fails, see
Section 16.9, “Recovering the
Database If Restore Verification Fails,” on page 477
.
Содержание EDIRECTORY 8.8 SP3
Страница 4: ...novdocx en 11 July 2008...
Страница 72: ...72 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 120: ...120 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 132: ...132 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 190: ...190 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 238: ...238 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 262: ...262 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 288: ...288 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 320: ...320 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 348: ...348 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 388: ...388 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 492: ...492 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 586: ...586 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 599: ...The eDirectory Management Toolbox 599 novdocx en 11 July 2008 Click Help for details...
Страница 600: ...600 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...
Страница 614: ...614 Novell eDirectory 8 8 Administration Guide novdocx en 11 July 2008...