NetBackup Cloud configuration issues post upgrade if master server is running on an unsupported operating system and media server is acting as a Cloud Master Host

Article: 100044766
Last Published: 2019-06-21
Ratings: 1 0
Product(s): NetBackup

Problem

This is applicable to NetBackup 8.2 and later versions.

Consider a NetBackup environment where a media server that is configured for cloud storage is promoted as a Cloud Master Host and the NetBackup master server is running on an unsupported operating system such as Solaris x86 or Windows Server 2008.

If the NetBackup master server is upgraded to NetBackup 8.2 or later, then after the upgrade is completed, the master server begins to function as the Cloud Master. The media server no longer works as a Cloud Master Host. This may cause a communication failure between the master server and the media server and may affect the cloud configuration operations.


Cause

This issue occurs because starting with NetBackup 8.2 release, the NetBackup CloudStore configuration service is hosted only on the master server. The NetBackup Web Management Console (nbwmc) service now performs all the cloud storage configuration operations.


Solution

If you are performing a rolling upgrade (as in, upgrading one server at a time), then upgrade your NetBackup servers in the following order:

  • First, upgrade the NetBackup master server that is running on an unsupported operating system such as Solaris x86 or Windows Server 2008
  • Copy the CloudInstance.xml file, and update or merge the cacert.pem and any other certificate file from the media server (promoted as Cloud Master Host) to the upgraded master server, as specified in this technote
  • Then, upgrade the media server that is promoted as the Cloud Master Host
  • Update the master server name and port number in the cloudstore.conf file, as specified in this technote

Note: Veritas recommends that you do not create any new cloud storage servers until the media server that is promoted as the Cloud Master Host is upgraded successfully.

To ensure that the Cloud configuration works seamlessly after an upgrade, you must perform the following additional steps manually:
  1. Verify that the NetBackup master server is upgraded successfully.
  2. Manually copy the CloudInstance.xml file from the existing Cloud Master Host (media server) to the upgraded master server as follows:
From Media Server (promoted as Cloud Master Host) To Master Server (upgraded)
Windows: <install_path>\Veritas\NetBackup\db\cloud Windows: <install_path>\Veritas\NetBackup\var\global\wmc\cloud
UNIX: /usr/openv/netbackup/db/cloud UNIX: /usr/openv/var/global/wmc/cloud

 

If prompted, replace the CloudInstance.xml file that already exists on the master server. The file is created automatically when you upgrade the master server.

  1. Update and merge the cacert.pem and any other certificate files from the existing Cloud Master Host (media server) to the upgraded master server as follows:
From Media Server (promoted as Cloud Master Host) To Master Server (upgraded)
Windows: <install_path>\Veritas\NetBackup\db\cloud Windows: <install_path>\Veritas\NetBackup\var\global\wmc\cloud
UNIX: /usr/openv/netbackup/db/cloud UNIX: /usr/openv/var/global/wmc/cloud

 

  1. Now upgrade the media server that is promoted as the Cloud Master Host.
  2. After the media server (Cloud Master Host) is upgraded successfully, make the following changes in the cloudstore.conf file on all the media servers that are configured for cloud storage:
    1. Update the master server name to the master server that is upgraded.
      Use the following parameter:
      CSSC_MASTER_NAME=<upgradedmasterserverFQHN>

    2. Update the port number to 5637.
      Use the following parameter:
      CSSC_PORT=5637

The cloudstore.conf file is located in the following directory:
UNIX: /usr/openv/var/global/wmc/cloud
Windows: <install_path>\Veritas\NetBackup\var\global\wmc\cloud

  1. Restart the NetBackup CloudStore Service Container (nbcssc) on all the older media servers (only version 7.7.3 to 8.1.2 are supported) that are configured for cloud storage.
    If you have upgraded the cloud storage media servers, this step is not applicable.

Was this content helpful?