|
|
The environment is a Domino clustered environment with four Domino servers as members of the Domino cluster. Server A is identified as your backup server and runs archive-style transaction logging. Servers B, C, and D run circular or linear-style logging. To provide load balancing across all the servers, replicas of all databases exist on all four servers in your Domino cluster. A successful full backup of all databases was completed earlier in the week. Successful incremental backups of the archival-style transaction logs are completed every four hours, with the last one completing 2 hours ago. At 2:30 pm, a user complains that the database acme.nsf is corrupted, while he modified the database on server C over the last 30 minutes. Unfortunately, because the environment is a Domino cluster environment, the corruption is replicated to all four member servers. The users state that the database was in a consistent state when they began to modify the database.
To restore a database to a consistent state do the following:
On server A, perform a point-in-time recovery of the database acme.nsf. Select the database acme.nsf from the last successful backup of the database (for example, a full backup that was completed successfully earlier in the week). Begin the restore.
On the Lotus Notes tab of the Restore Marked Files dialog box, select the option. Select the option. Specify today's date at 2:00 pm (the time that the user started to modify the database) as the point-in-time for recovery.
After the restore or recovery is successful, a version of acme.nsf from 2:00 pm today should exist on server. Verify the consistency of acme.nsf on server A. If all is as expected, from server A create new replicas of acme.nsf on servers B, C, and D. Cluster replication should now be functional on servers A, B, C, and D, with a consistent version of acme.nsf.