Configuring the AIR in NetBackup for OpenStack
After the AIR is configured between two NetBackup primary servers, the backup copy from the source NetBackup primary server is replicated to the target NetBackup primary server. You can import all the protections, recovery points, and the required metadata. After import of protections, you can recover the instance from the older backup copy.
To configure the AIR in NetBackup for OpenStack
- Configure NBOSVM with source primary server using NBOSVM configurator UI.
- Create a trusted relationship between source and target NetBackup primary servers.
See Configuring Auto Image Replication (A.I.R.) topic of the NetBackup Deduplication Guide.
- On the source NetBackup primary server, add a replication target.
See Setting up the MSDP replication target topic of the NetBackup Deduplication Guide.
- Create an Import SLP on the target NetBackup primary server.
See Configuring a storage lifecycle policy (SLP) for A.I.R. topic of the NetBackup Deduplication Guide.
- Create a replication SLP on source NetBackup primary server.
See Configuring a storage lifecycle policy (SLP) for A.I.R. topic of the NetBackup Deduplication Guide.
- Create a protection plan on source NetBackup primary server.
- Create a protection on the Horizon UI with the protection plan.
- Run a backup job.
To get the images on the target NBOSVM
- On the target NBOSVM, import the protections from NetBackup by using the backup images stored on the universal share.
nbosjm protection-import-to-new-cloud
The protections are listed as orphaned protections. The project and user of the OpenStack cloud A do not exist on the OpenStack cloud B.
Note:
After you import the protection in another cloud, when you enable the global job scheduler, all the protections that have scheduler trust enabled are displayed as broken because the protections do not have instances attached to them. Update the protection and assign an instance to it to enable the scheduler trust.
- List the orphaned protections.
Orphaned protections are the protections that are no longer linked to an active tenant or user within the cloud. To identify and list all orphaned protections that do not have tenant_id or user_id associated with the current cloud environment, run the following command:
nbosjm protection-get-orphaned-protections-list [--migrate_cloud {True,False}]
--migrate_cloud Set to True if you want to list policies from other clouds as well. The default value is False.
- Assign protections to a new tenant or user.
nbosjm protection-reassign-protections [--old_tenant_ids <old_tenant_id>] [--new_tenant_id <new_tenant_id>] --protection_plan_id <protection_plan_id> [--user_id <user_id>] [--migrate_cloud {True,False}] [--map_file <map_file>]--old_tenant_ids The IDs of the old tenants from which you want to assign the protections.
--new_tenant_id The ID of the new tenant to which you want to assign the protections.
--protection_plan_id The ID of the protection plan to which you want to assign the protections.
--user_id The user ID to which you want to assign the protections.
--migrate_cloud Set to True if you want to assign the protections from other clouds also. The default value is False
--map_file The file path with the file name of map file. The file format is YAML.
- Run the following command to see the status of the import job.
nbosjm get-protection-import-status