Failed to complete the initial configuration on a CloudCatalyst appliance media server

Failed to complete the initial configuration on a CloudCatalyst appliance media server

Article: 100042691
Last Published: 2019-05-14
Ratings: 1 2
Product(s): Appliances

Problem

 

When you perform the initial configuration on a NetBackup 5240 CloudCatalyst Appliance media server, you may encounter the errors that mentioned in the "Error messages" field.

To solve these issues and complete the initial configuration, you need to reset the appliance media server and try again.


Cause

When an appliance media server is disconnected with the master server because of network problem or any other reasons, some cloud relative settings on the media server cannot be automatically deleted from the master server. The uncleaned settings block the subsequent initial configuration process on the appliance media server.

Error messages

- [Error] Failed add storage server operation.
- [Error] Unable to initialize local storage cache
- [Error] Unable to configure the cloud storage server. The appliance may be unconfigurable.  Please factory reset the appliance and retry the configuration.

 

Cause

When an appliance media server is disconnected with the master server because of network problem or any other reasons, some cloud relative settings on the media server cannot be automatically deleted from the master server. The uncleaned settings block the subsequent initial configuration process on the appliance media server.

Solution

 

On the appliance media server, do the following:

1. Log on to the NetBackup Appliance Shell Menu.

2. Navigate to Main > Support

3. Run the following command: FactoryReset

4. Restart the appliance.

 

On the appliance master server, do the following:

 

1. To verify if any storage unit exists, run the following command: # bpstulist -label stu_cc_mediahostname
If the storage unit is existed, you must delete is by using command: # bpstudel -label stu_cc_ mediahostname


2. To verify if any disk pool "dp_cc_mediahostname" exists, run the following command: # nbdevquery -listdp
If the disk pool "dp_cc_mediahostname" is existed, you must delete is by using command: # nbdevconfig -deletedp -stype PureDisk_amazon_cryptd -dp dp_cc_mediahostname


3. To list the storage server, run the following command: # nbdevquery -liststs


4. Find the storage server that you want to delete (take Amazon as an example), run the following command:
# nbdevconfig -deletests -storage_server mediahostname_amazon -stype PureDisk_amazon_cryptd


5. To list the storage servers that attach to the cloud instance "amazon.com", run the following command: # csconfig cldinstance -i amazon.com


6. If "mediahostname_amazon" is in the storage server list, you need to delete it from the cloud instance "amazon.com" by using the command: # csconfig cldinstance -rs -at S3 -in amazon.com -sts mediahostname _amazon


7. To check if the "mediahostname" is deleted from the host list, run the following command: # nbemmcmd -listhosts
If the "mediahostname" is not deleted from the EMM, you must manually delete it by using the commands:


# /usr/openv/netbackup/bin/admincmd/nbemmcmd -deletehost -emmname masterhostname -machinename mediahostname -machinetype media


# /usr/openv/netbackup/bin/admincmd/nbemmcmd -deletehost -emmname masterhostname -machinename mediahostname -machinetype ndmp

For more information about the NetBackup command usage, refer to the NetBackup Command Reference Guide.

 

Was this content helpful?