470
Novell eDirectory 8.8 Administration Guide
no
vd
ocx
(e
n)
6 Ap
ril 20
07
16.10.3 Scenario: Losing an Entire Server in a Multiple-Server
Environment
Bob is the administrator for 15 servers at GK Designs Company. He does full backups every
Saturday night and incremental backups nightly, running the eDirectory backup shortly before the
file system backup to tape.
All of the servers are participating in replica rings. Bob uses roll-forward logging for all the servers.
An electrical fire destroys one of the servers in a branch across town. Fortunately, all but one of the
partitions held by this server are also replicated on other servers. Bob had turned on roll-forward
logs on that server, but they were lost along with all the other server data, so he can't restore the
eDirectory database on that server to the state it was in just before the server went down.
However, he is able re-create the server's eDirectory identity by restoring with the existing backup
files. Because Bob can't include the roll-forward logs in the restore, the server does not match the
synchronization state that the other servers expect (see
“Transitive Vectors and the Restore
Verification Process” on page 423
), so the restore verification process is not successful. This means
that by default the eDirectory database is not opened after the restore.
Bob addresses the situation by removing this server from the replica rings, using DSRepair to
change all the outdated replica information on the server to external references, and then re-adding a
new copy of each partition to this server using replication from the other servers that hold the up-to-
date replicas. (These steps are described in
Section 16.9, “Recovering the Database If Restore
Verification Fails,” on page 462
.)
The one partition on this server that Bob had not replicated was a container that held network
printing objects for the branch office location, such as a fax/printer and a wide-format color printer.
This partition information can't be recovered by the method noted above because no other server has
a replica. Bob must re-create the objects in that partition, and this time he chooses to replicate them
on other servers for better fault tolerance in the future.
Bob also re-creates the roll-forward log configuration after the server is back on line (because the
restore turns it off and resets the settings to the default), and creates a new full backup as a baseline.
16.10.4 Scenario: Losing Some Servers in a Multiple-Server
Environment
Joe administers 20 servers across three locations. At one location, a pipe bursts and water destroys 5
out of 8 servers.
Joe has eDirectory backups for all the servers. However, all the servers participate in replica rings,
and he is concerned about bringing them back into the tree without the roll-forward logs, which
were also lost. He is not sure which servers to restore eDirectory on first or how to address
inconsistencies between replicas. Because of the complex issues involved, he calls Novell Support
for help in deciding how to restore.
16.10.5 Scenario: Losing All Servers in a Multiple-Server
Environment
Delores and her team at Human Resources Consulting, Inc. administer 50 servers at one location.
Summary of Contents for EDIRECTORY 8.8 SP2
Page 4: ...novdocx en 6 April 2007...
Page 116: ...116 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 128: ...128 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 255: ...256 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 406: ...408 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 563: ...566 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 573: ...576 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
Page 601: ...604 Novell eDirectory 8 8 Administration Guide novdocx en 6 April 2007...
