Consolidating the cloud LSU
Starting with NetBackup version 11.1, cloud LSUs can now be consolidated from one MSDP media server to another. These steps must be repeated for each cloud LSU you plan to move.
Important considerations and recommendations before consolidation:
Do not perform these steps on an image sharing server. Use the NetBackup web UI to add additional image sharing LSUs.
Ensure the cloud LSU name is unique on the target MSDP media server. If the name already exists, the migration fails.
Both the source and the target MSDP media servers should be on the latest NetBackup version.
The following settings are not retained when a cloud LSU is moved:
Cloud cache capacity
Maximum concurrent jobs
Fragment size
Other metadata
These must be manually reviewed and reconfigured on the target media server after the move.
Before the consolidation, deactivate, delete, or update all backup policies that target the LSU being moved. Ensure that they now point to the cloud LSU on the target media server.
If KMS is enabled on the source media server, it must also be enabled on the target. If moving the cloud LSU across NetBackup domains, ensure that the KMS keys are imported into the new domain.
All policies targeting the cloud LSU must be updated or deactivated before the consolidation.
Table: Cloud LSU consolidation
Step | Task | Description |
|---|---|---|
1 | Deactivate backup policies. | In the NetBackup web UI, deactivate all backup policies that target the cloud LSU you plan to move. This step prevents backup or restore operations during the migration. |
2 | Fetch the original LSU information. | Use the web UI to view the disk pool details for the original cloud LSU and record the following:
|
3 | Reuse cloud LSU. | Run reuse steps on the target MSDP media server only. See Reuse cloud LSU. Cloud cache settings are not transferred to the new storage server. Specify requestCloudCacheCapacity value accordingly based on the new storage server's storage availability. In a Cloudscale deployment, all services within the media pod must be restarted to refresh the cloud LSU to storage server mapping. |
4 | Create a disk pool on the target server. | On the primary server, run: /usr/openv/netbackup/bin/admincmd/nbdevconfig -previewdv -storage_servers <storage server name> -stype PureDisk | grep <LSU name> > /tmp/dvlist /usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -dp <disk pool name> -stype PureDisk -dvlist /tmp/dvlist -storage_servers <storage server name> |
5 | Update the catalog images. | If the LSU is moved within the same NetBackup domain, run the following command on the primary server: /usr/openv/netbackup/bin/admincmd/bpimage -newserver "target storage server" -oldserver "original storage server" -newdiskpool "new disk pool name" -olddiskpool "original disk pool name" If moving across domains, perform a two-phase import. See NetBackup Administrator's Guide, Volume I. |
6 | Delete old storage server-related configurations. | Run the following command on the old MSDP server. /usr/openv/netbackup/bin/bp.start_all Perform the following steps from the Recovering from an MSDP storage server failure topic. See Recovering from an MSDP storage server failure.
|
7 | Create a new storage unit targeting your new disk pool. | In the NetBackup web UI, create a storage unit pointing to the new disk pool. See the NetBackup Web UI Administrator's Guide. |
8 | Update existing policies to target the new storage unit. | In the web UI:
|