3.2.- REGULACIÓN NORMATIVA ACTUAL

Before you begin a Lotus data recovery, ensure that the appropriate configurations are set, including the required NML parameters and environment variables. Chapter 2, “Software Configuration

Procedures” provides details on the required configurations.

To specify the Lotus database files for recovery, set the

NSR_BACKUP_PATHS parameter in the NML configuration file.

Performing data recovery ^5-5 Place quotation marks around any filepaths or time values that

contain spaces in the following:

◆ The NSR_BACKUP_PATHS parameter setting.

◆ The NSR_RECOVER_TIME parameter setting.

◆ The nsrnotesrc command options.

CAUTION

!

Filepaths are case-sensitive. If you are uncertain about the case of filenames, use the nsrinfo command to verify the backup entries in the NetWorker client file index.

The following examples describe the parameters for Lotus database recoveries. In each case, after the parameters are set in the NML configuration file, perform the recovery by entering the following command at the command-line prompt:

nsrnotesrc -z config_filepath

where config_filepath is the complete pathname of the configuration file.

Example 5-1 Recovery of a previous database version

By default, the NML software recovers the most recent backup available. The following parameter setting in the NML configuration file specifies a recovery of an earlier version of a database.

LOTUS {

Notes_ExecDirectory = /opt/lotus/notes/latest/solaris NSR_RECOVER_TIME = "Wed December 14 2005 14:23"

}

The NSR_RECOVER_TIME parameter value is the time in nsr_getdate format of the database backup to be restored.

Note: The browse time cannot be earlier than the time of the first backup because the client file index does not have any entries before that time.

Example 5-2 Recovery of specific Lotus databases

The following parameter settings in the NML configuration file specify a recovery of Lotus database files named account.nsf and names.nsf:

◆ On UNIX or Linux:

NSR_BACKUP_PATHS = /lotusdata/account.nsf, /lotusdata/names.nsf

◆ On Windows:

NSR_BACKUP_PATHS = C:\Lotus\Domino\data\account.nsf, C:\Lotus\Domino\data\names.nsf

Example 5-3 Recovery of all Lotus data in a directory

The following parameter settings in the NML configuration file specify a recovery of all the Lotus database files within the directory /space/notesdata/mail.

◆ The NetWorker client where the files originated is jupiter.emc.com.

◆ The NetWorker server from which the backup is recovered is mars.emc.com.

LOTUS {

Notes_ExecDirectory = /opt/lotus/notes/latest/solaris NSR_BACKUP_PATHS = /space/notesdata/mail

NSR_CLIENT = jupiter.emc.com NSR_SERVER = mars.emc.com }

Example 5-4 Recovery of all Lotus database files

The following parameter settings in the NML configuration file specify a recovery of all the Lotus database files associated with a given NetWorker client.

LOTUS {

Notes_ExecDirectory = /opt/lotus/notes/latest/solaris NSR_BACKUP_PATHS = NOTES:

NSR_RECOVER_TIME = "Tue December 13 2005 19:23"

}

The NSR_RECOVER_TIME parameter value is the time in

nsr_getdate format when a full backup was performed on the client.

Performing data recovery ^5-7 CAUTION

!

Use the NOTES: option with caution because the NML software attempts to restore the data for all partitions of a partitioned Domino server, or for all Domino installations when there are multiple Domino installations on the client.

Note: If the NOTES: option is used without specifying the backup time, only the latest versions of all the backed-up Lotus databases are recovered.

Example 5-5 Recovery of a database with a change of the DBIID

When recovering a database that may still be in use, use the NSR_DBIID parameter to change (or zap) the DBIID. The Domino server does not allow two databases to exist with the same instance ID. Changing the DBIID and relocating the database to another directory prevents error messages from appearing in the Recovery Manager in the Domino server.

The following parameter settings in the NML configuration file specify a recovery of the backed-up database named budget2005.nsf to the directory C:\tmpdir and a change of the DBIID:

LOTUS {

Notes_ExecDirectory = C:\Lotus\Domino\Data

NSR_BACKUP_PATHS = C:\Lotus\Domino\Data\budget2005.nsf NSR_DBIID = 1

NSR_RELOCATION_DEST = C:\tmpdir }

CAUTION

!

After you change the DBIID of a recovered database, you cannot recover any subsequent changes to the database until the next full backup is performed. Perform a full ad hoc backup after changing the DBIID of a recovered database. If an incremental backup is the next backup performed on a database after a DBIID change, NML automatically performs a full backup of the database file instead.

Example 5-6 Recovery of a full backup without the transaction logs

The following parameter settings in the NML configuration file specify a recovery of the full backup of database accounting.nsf to the directory C:\temp and a change of the database’s DBIID, without applying the transaction logs:

LOTUS {

Notes_ExecDirectory = C:\Lotus\Domino\Data NSR_APPLY_LOGS = FALSE

NSR_BACKUP_PATHS = C:\Lotus\Domino\Data\accounting.nsf NSR_DBIID = 1

NSR_RELOCATION_DEST = C:\temp }

If you recover a point-in-time full backup of a database by using the parameter NSR_RECOVER_TIME without the parameter setting NSR_APPLY_LOGS=FALSE, the following error message might appear:

Recovery Manager: Backup was later than recovery point in time.

In this case, use the parameter setting NSR_APPLY_LOGS=FALSE to prevent the error message.