Configuring NetBackup optimized duplication or replication behavior
You can configure some optimized duplication and replication behaviors for NetBackup. The behaviors depend on how NetBackup duplicates the images, as described in the following table.
Table: Optimized duplication behavior
Behavior | Description |
|---|---|
Duplication by using NetBackup Vault or the bpduplicate command |
If you use NetBackup Vault or the bpduplicate command for duplication, you can configure the following behaviors:
|
Duplication or replication by using a storage lifecycle policy | If a storage lifecycle policy optimized duplication or replication job fails, NetBackup waits 2 hours and retries the job again. NetBackup repeats the retry behavior until the job succeeds or the source backup image expire. You can change the number of hours for the wait period. See “To configure the storage lifecycle policy wait period”. |
If you use a storage lifecycle policy for duplication, do not configure optimized duplication behavior for NetBackup Vault or the bpduplicate command, and vice versa. NetBackup behavior may not be predictable.
Caution:
These settings affect all optimized duplication jobs; they are not limited to a specific NetBackup storage option.
To configure the number of duplication attempts
- On the master server, create a file named OPT_DUP_BUSY_RETRY_LIMIT. Add an integer to the file that specifies the number of times to retry the job before NetBackup fails the job.
The file must reside on the master server in the following directory (depending on the operating system):
UNIX:
/usr/openv/netbackup/db/configWindows:
install_path\NetBackup\db\config.
To configure optimized duplication failover
- On the master server, add the following configuration option:
RESUME_ORIG_DUP_ON_OPT_DUP_FAIL = TRUE
See Setting NetBackup configuration options by using the command line.
Alternatively on UNIX systems, you can add the entry to the bp.conf file on the NetBackup master server.
To configure the storage lifecycle policy wait period