Replicating the backup images from the IRE domain to the production domain
If the backup images at the production domain are lost for some reasons, you may need to replicate the backup images from the IRE domain back to the production domain. You can also replicate these backup images to a new domain.
To replicate the backup images from the IRE domain to the production domain
- Ensure that NetBackup certificate authority (NBCA) or an external certificate authority (ECA) are configured on the IRE storage server.
For BYO media server: See the step 1 of the Configuring A.I.R. for replicating backup images from production environment to IRE BYO environment topic.
See Configuring A.I.R. for replicating backup images from production environment to IRE BYO environment.
For WORM storage server, Flex Scale, and Access Appliance: See the step 2 of the Configuring data transmission between a production environment and an IRE WORM storage server topic.
See Configuring data transmission between a production environment and an IRE WORM storage server.
- On the IRE primary server, configure replication target using a command line.
Create a configuration file for adding a replication target with the following information:
V7.5 "operation" " " string
The value must be set-replication to add a new replication target.
V7.5 " rephostname" " " string
Specifies the replication target host name.
V7.5 "replogin" " " string
Specifies the replication target storage server username.
V7.5 "reppasswd" " " string
Specifies the replication target storage server password.
V7.5 "repsourcevolume" " " string
Specifies the replication source volume name.
V7.5 "reptargetvolume" " " string
Specifies the replication target volume name.
Run the following command to apply the configuration file to add replication target:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <IRE storage server name> -stype PureDisk -configlist <config file name>
Run the following command to update the disk pool information on the primary server:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -updatedp -stype PureDisk -dp <IRE disk pool name>
Sample:
[admin@ire-primary ~]# cat add-replication.txt V7.5 "operation" "set-replication" string V7.5 "rephostname" "msdp-prod.example.com" string V7.5 "replogin" "pduser" string V7.5 "reppasswd" "pdpass" string V7.5 "repsourcevolume" "PureDiskVolume" string V7.5 "reptargetvolume" "PureDiskVolume" string [admin@ire-primary ~]# /usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server msdp-ire.example.com -stype PureDisk -configlist add-replication.txt Storage server msdp-ire.example.com has been successfully updated [admin@ire-primary ~]# /usr/openv/netbackup/bin/admincmd/nbdevconfig -updatedp -stype PureDisk -dp dp-ire The following replication properties have been added to the disk pool : ReplicationSource Replication sources and/or targets have changed for disk volumes: PureDiskVolume Update of disk pool replication properties succeeded
- Ensure that the production primary server has one import SLP that targets the relevant MSDP storage unit. Create it if it does not exist.
- Run the following command on the IRE primary server to manually replicate the backup images to the production domain.
/usr/openv/netbackup/bin/admincmd/nbreplicate -backupid <backup id> -cn <local copy number> -rcn <copy number plus 101> -slp_name reverse-air -target_sts <production MSDP storage server name>
For example,
/usr/openv/netbackup/bin/admincmd/nbreplicate -backupid client1_1234567890 -cn 1 -rcn 102 -slp_name reverse-air -target_sts msdp-prod.example.com
Note:
Before you start the replication, ensure that the backup image with the same backup ID does not exist in the production domain. If it exists, you must expire the image at the production domain first. Otherwise, the new replicated image will not get automatically imported by the import SLP at the production primary server.