Please enter search query.
Search <product_name> all support & community content...
Article: 100032774
Last Published: 2016-07-25
Ratings: 0 1
Product(s): NetBackup & Alta Data Protection
Problem
Each step through the Configure Cloud Storage Server wizard makes changes to NetBackup which remain in place even if the wizard fails or is cancelled before completion. The residue from a failed or cancelled wizard will remain in the NetBackup database and configuration files until it is manually addressed. You might not be able to re-run the wizard properly until the residue is removed.This article discusses the steps needed to manually remove the residue which is created during full or partial completion of the Configure Cloud Storage Server wizard.
Solution
It is common for the Configure Cloud Storage Server wizard to fail at this point for a variety of reasons.Use the following steps to identify and remove the NetBackup residue which remains from progressing to this point in the wizard
Note: Although these examples reference Hitachi Cloud, the technique can be applied to any Cloud Provider1a. List and identify Cloud Provider Instances
C:\Program Files\Veritas\NetBackup\bin\admincmd>
csconfig cldinstance -l
amazon.com (amazon - s3.amazonaws.com)
amazongov.com (amazongov - s3-us-gov-west-1.amazonaws.com)
amazongovfips.com (amazongov - s3-fips-us-gov-west-1.amazonaws.com)
google.com (google - storage.googleapis.com)
MyCloudStorageServer (hitachi - hds-rosspt.az-symccloud.content.us-az1.cloud.hds.com )
amazongov.com (amazongov - s3-us-gov-west-1.amazonaws.com)
amazongovfips.com (amazongov - s3-fips-us-gov-west-1.amazonaws.com)
google.com (google - storage.googleapis.com)
MyCloudStorageServer (hitachi - hds-rosspt.az-symccloud.content.us-az1.cloud.hds.com )
verizon.emea.com (verizon - storage-ams1a.cloud.verizon.com)
verizon.us.com (verizon - storage-iad3a.cloud.verizon.com)
verizon.us3.com (verizon - storage-ushaa.cloud.verizon.com)
Successfully fetched Cloud Instance list
verizon.us.com (verizon - storage-iad3a.cloud.verizon.com)
verizon.us3.com (verizon - storage-ushaa.cloud.verizon.com)
Successfully fetched Cloud Instance list
1b. Remove the identified Cloud Provider Instance
C:\Program Files\Veritas\NetBackup\bin\admincmd>
csconfig cldinstance -r -in MyCloudStorageServer
Successfully removed cloud instance
Note: If you are trying to delete a non-custom instance (like amazon.com) NetBackup will produce an expected error. NetBackup does not allow you to delete a non-custom instance.
Example:
C:\Program Files\Veritas\NetBackup\bin\admincmd>
csconfig cldinstance
-r
-in amazon.com
Failed to remove cloud instance.
Please see csconfig logs for more details
Failed to remove cloud instance.
Please see csconfig logs for more details
2a. List nbemm hosts to identify the configured Cloud host
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbemmcmd -listhosts
NBEMMCMD, Version: 7.7.3
The following hosts were found:
server test.labdomain.com
master test.labdomain.com
ndmp test.labdomain.com
media test2.labdomain.com
ndmp MyCloudStorageServer
Command completed successfully.
NBEMMCMD, Version: 7.7.3
The following hosts were found:
server test.labdomain.com
master test.labdomain.com
ndmp test.labdomain.com
media test2.labdomain.com
ndmp MyCloudStorageServer
Command completed successfully.
2b. Remove the necessary 'ndmp' Cloud host from nbemm
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbemmcmd -deletehost -machinename MyCloudStorageServer
-machinetype ndmp
NBEMMCMD, Version: 7.7.3
Command completed successfully.
NBEMMCMD, Version: 7.7.3
Command completed successfully.
3. Cycle NetBackup services
bpdown
bpup
bpup
Use the following steps to identify and remove the NetBackup residue produced after fully completing the "Configure Cloud Storage Server" wizard
Note: Although these examples reference Hitachi Cloud, the technique can be applied to any Cloud Provider1a. Identify images residing on the Cloud Disk Pool (see step 4a to identify the Cloud Disk Pool name. See step 5a to identify the stype)
C:\Program Files\Veritas\NetBackup\bin\admincmd>
bpimmedia -dp MyCloudPool
-stype hitachi_raw
IMAGE test.labdomain.com test.labdomain.com_1469543728 test_testing 13 0 0
FRAG 1 1 1470753328 6 MyCloudPool hds-rosspt test.labdomain.com 0
FRAG 1 1 1470753328 6 MyCloudPool hds-rosspt test.labdomain.com 0
1b. Expire valid images residing on the Cloud Disk Pool
1b.1. To expire individual backup images, execute:
C:\Program Files\Veritas\NetBackup\bin\admincmd> bpexpdate -backupid <backup_image_id> -d 0 -M <Master_server_name> -force_not_complete
1b.2. To expire all backup images on the Cloud Disk Pool, execute:
C:\Program Files\Veritas\NetBackup\bin\admincmd> bpexpdate -stype hitachi_raw - dp MyCloudPool -force_not_complete
Note: Can see an Image Cleanup task in Activity Monitor for each expired image
C:\Program Files\Veritas\NetBackup\bin\admincmd> bpexpdate -backupid <backup_image_id> -d 0 -M <Master_server_name> -force_not_complete
1b.2. To expire all backup images on the Cloud Disk Pool, execute:
C:\Program Files\Veritas\NetBackup\bin\admincmd> bpexpdate -stype hitachi_raw - dp MyCloudPool -force_not_complete
Note: Can see an Image Cleanup task in Activity Monitor for each expired image
2. Perform image cleanup
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbdelete -allvolumes -force
C:\Program Files\Veritas\NetBackup\bin\admincmd> bpimage -cleanup -allclients
C:\Program Files\Veritas\NetBackup\bin\admincmd> bpimage -cleanup -allclients
3a. List all Storage Units to identify the Cloud Storage Unit
C:\Program Files\Veritas\NetBackup\bin\admincmd>
bpstulist -l
MyCloudPool-stu 0 test.labdomain.com 0 -1 -1 1 0 "*NULL*" 1 1 524288 MyCloudStorageServer 10 6 0 0 0 0 MyCloudPool test.labdomain.com 3235031
MyCloudPool-stu 0 test.labdomain.com 0 -1 -1 1 0 "*NULL*" 1 1 524288 MyCloudStorageServer 10 6 0 0 0 0 MyCloudPool test.labdomain.com 3235031
3b. Delete the Cloud Storage Unit
C:\Program Files\Veritas\NetBackup\bin\admincmd>
bpstudel -label MyCloudPool-stu
4a. List all Disk Pools (to identify the name of the Cloud Disk Pool)
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbdevquery -listdp
V7.5 MSDP-Pool 1 47.00 47.00 1 98 80 -1 test.labdomain.com
V7.5 AdvDiskPool 1 20.00 20.00 1 98 80 -1 test.labdomain.com
V7.5 MyCloudPool 1 8589934592.00 8589934592.00 1 98 80 -1 MyCloudStorageServer
V7.5 MSDP-Pool 1 47.00 47.00 1 98 80 -1 test.labdomain.com
V7.5 AdvDiskPool 1 20.00 20.00 1 98 80 -1 test.labdomain.com
V7.5 MyCloudPool 1 8589934592.00 8589934592.00 1 98 80 -1 MyCloudStorageServer
4b. Identify the name of the Disk Volume associated with the Cloud Disk Pool (use "nbdevquery -liststs" to get the stype)
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbdevquery -listdv -stype hitachi_raw
-U
Disk Pool Name : MyCloudPool
Disk Type : hitachi_raw
Disk Volume Name : hds-rosspt
Disk Media ID : @aaaaj
Total Capacity (GB) : ---
Free Space (GB) : ---
Use% : 0
Status : UP
Flag : ReadOnWrite
Flag : AdminUp
Flag : InternalUp
Num Read Mounts : 0
Num Write Mounts : 1
Cur Read Streams : 0
Cur Write Streams : 0
Num Repl Sources : 0
Num Repl Targets : 0
Disk Pool Name : MyCloudPool
Disk Type : hitachi_raw
Disk Volume Name : hds-rosspt
Disk Media ID : @aaaaj
Total Capacity (GB) : ---
Free Space (GB) : ---
Use% : 0
Status : UP
Flag : ReadOnWrite
Flag : AdminUp
Flag : InternalUp
Num Read Mounts : 0
Num Write Mounts : 1
Cur Read Streams : 0
Cur Write Streams : 0
Num Repl Sources : 0
Num Repl Targets : 0
4c Down the Cloud Disk Pool identified in Step 4a
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbdevconfig -changestate -stype hitachi_raw
-dp MyCloudPool
-dv hds-rosspt
-state DOWN
successfully changed the state of disk volume
successfully changed the state of disk volume
4d Delete the Cloud Disk Pool identified in Step 4a
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbdevconfig -deletedp -stype hitachi_raw -
dp MyCloudPool
Disk pool MyCloudPool has been deleted successfully
Disk pool MyCloudPool has been deleted successfully
5a. List the Storage Servers to identify the name of the Cloud Storage Server
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbdevquery -liststs
V7.5 test.labdomain.com BasicDisk 5
V7.5 test.labdomain.com AdvancedDisk 5
V7.5 test.labdomain.com PureDisk 9
V7.5 MyCloudStorageServer hitachi_raw 9
V7.5 test.labdomain.com BasicDisk 5
V7.5 test.labdomain.com AdvancedDisk 5
V7.5 test.labdomain.com PureDisk 9
V7.5 MyCloudStorageServer hitachi_raw 9
5b. Delete the Cloud Storage Server
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbdevconfig -deletests -storage_server MyCloudStorageServer
-stype hitachi_raw
Storage server MyCloudStorageServer has been successfully deleted
Storage server MyCloudStorageServer has been successfully deleted
6a. List and identify Cloud Provider Instances
C:\Program Files\Veritas\NetBackup\bin\admincmd>
csconfig cldinstance -l
amazon.com (amazon - s3.amazonaws.com)
amazongov.com (amazongov - s3-us-gov-west-1.amazonaws.com)
amazongovfips.com (amazongov - s3-fips-us-gov-west-1.amazonaws.com)
google.com (google - storage.googleapis.com)
MyCloudStorageServer (hitachi - hds-rosspt.az-symccloud.content.us-az1.cloud.hds.com )
amazongov.com (amazongov - s3-us-gov-west-1.amazonaws.com)
amazongovfips.com (amazongov - s3-fips-us-gov-west-1.amazonaws.com)
google.com (google - storage.googleapis.com)
MyCloudStorageServer (hitachi - hds-rosspt.az-symccloud.content.us-az1.cloud.hds.com )
verizon.emea.com (verizon - storage-ams1a.cloud.verizon.com)
verizon.us.com (verizon - storage-iad3a.cloud.verizon.com)
verizon.us3.com (verizon - storage-ushaa.cloud.verizon.com)
Successfully fetched Cloud Instance list
verizon.us.com (verizon - storage-iad3a.cloud.verizon.com)
verizon.us3.com (verizon - storage-ushaa.cloud.verizon.com)
Successfully fetched Cloud Instance list
6b. Remove the identified Cloud Provider Instance
C:\Program Files\Veritas\NetBackup\bin\admincmd>
csconfig cldinstance -r -in MyCloudStorageServer
Successfully removed cloud instance
Successfully removed cloud instance
Note: If you are trying to delete a non-custom instance (like amazon.com) NetBackup will produce an expected error. NetBackup does not allow you to delete a non-custom instance.
Example:
C:\Program Files\Veritas\NetBackup\bin\admincmd>
csconfig cldinstance
-r
-in amazon.com
Failed to remove cloud instance.
Please see csconfig logs for more details
Failed to remove cloud instance.
Please see csconfig logs for more details
7a. List nbemm hosts to identify the configured Cloud host
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbemmcmd -listhosts
NBEMMCMD, Version: 7.7.3
The following hosts were found:
server test.labdomain.com
master test.labdomain.com
ndmp test.labdomain.com
media test2.labdomain.com
ndmp MyCloudStorageServer
Command completed successfully.
NBEMMCMD, Version: 7.7.3
The following hosts were found:
server test.labdomain.com
master test.labdomain.com
ndmp test.labdomain.com
media test2.labdomain.com
ndmp MyCloudStorageServer
Command completed successfully.
7b. Remove the necessary 'ndmp' Cloud host from nbemm
C:\Program Files\Veritas\NetBackup\bin\admincmd>
nbemmcmd -deletehost -machinename MyCloudStorageServer
-machinetype ndmp
NBEMMCMD, Version: 7.7.3
Command completed successfully.
NBEMMCMD, Version: 7.7.3
Command completed successfully.
8. Cycle NetBackup services
bpdown
bpup
bpup