Veritas NetBackup (tm) Server / Enterprise Server 7.7.1 - 7.7.3 Cloud Configuration Package 2.1.16

Veritas NetBackup (tm) Server / Enterprise Server 7.7.1 - 7.7.3 Cloud Configuration Package 2.1.16

Article: 100031406
Last Published: 2018-07-24
Ratings: 4 2
Product(s): NetBackup

Problem

Veritas NetBackup (tm) Server / Enterprise Server 7.7.1 - 7.7.3 Cloud Configuration Package 2.1.16

Solution

This package contains an update to the CloudProvider.xml configuration file for NetBackup 7.7.1 - 7.7.3. This file contains setting details for the cloud providers that are configurable with NetBackup.

This package adds support for the following new cloud providers and locales: 
  • Amazon Europe (Paris) region
  • Iron Mountain Iron Cloud certificate change

Below are support notes regarding this package:

  • NetBackup only supports Bucket creation for Google Nearline Storage Class. Use the Google Portal to create other Google Storage Class buckets.
  • NetBackup 7.7.3 requires an EEB to support CMCC Cloud Storage (S3)
  • NetBackup 7.7.3 requires an EEB to support RedHat Ceph (S3)
  • NetBackup 7.7.3 requires an EEB to support Fujitsu ETERNUS CD10000 (S3)
  • NetBackup 7.7.3 requires an EEB to support SUSE Enterprise Storage (S3)
  • NetBackup supports Amazon VPC on all regions except US East (N. Virginia)
The presence of a Storage Provider in the CloudProvider.xml file does not indicate, expressed or implied, support of the device on the target NetBackup Server / Enterprise Server platform. For the current list of Cloud Providers supported with NetBackup, refer to the following links: Veritas recommends downloading and installing this package:

    If your configuration contains a Cloud storage solution that requires this package. For information on the minimum cloud configuration package required for your solution, see the NetBackup HCL, above. Installation of this package and the latest NetBackup Device Mappings package is required to properly configure that storage.

    If you are configuring Iron Mountain Iron Cloud, also install the updated cacert.pem file included in this package, following the directions below.

To enable NetBackup Cloud features, download and install the latest NetBackup Device Mappings file. For a link to the latest Device Mappings packages, refer to the NetBackup HCL, above.

These files are for the following NetBackup configuration only and will not work with earlier NetBackup releases:
  • NetBackup Master Server 7.7.1 or later with NetBackup Media Server 7.7 or later. NetBackup Media Server version cannot be later than its NetBackup Master Server version.
 
Installation Procedure
 
Note: You must perform the following procedures only on the NetBackup Master Server that is installed on a cloud-supported platform.
 
**************************************
 
Windows Installation Instructions
 

**************************************
 
These instructions assume that NetBackup is installed at the default location of C:\Program Files\VERITAS\. If NetBackup is installed at a different location, substitute that path for C:\Program Files\VERITAS\ in the instructions below:
 
1. Copy the existing CloudProvider.xml and CloudInstance.xml files from the following location to an alternate location.
If you are configuring Iron Mountain Iron Cloud, also copy the cacert.pem file.
Default file location in NetBackup:
   In version 7.7.1 - C:\Program Files\Veritas\NetBackup\bin\ost-plugins
   In version 7.7.2 and later - C:\Program Files\Veritas\NetBackup\db\cloud
   Note: You can revert this file, if needed.

2. Copy the existing cloudstorejava.conf file from the following location to an alternate location.
Default file location in NetBackup:
   C:\Program Files\Veritas\NetBackup\Java
   NOTE: You can revert this file, if needed.

3. Download and extract the zip file package to a temporary folder.  
This will create four files in the temporary location:
   * Readme.txt (this file)
   * CloudProvider.xml
   * cacert.pem
   * cloudstorejava.conf

4. Stop all NetBackup services.

5. Copy the new CloudProvider.xml file from the temporary location, in step 3, to the location mentioned in step 1.

6. If you are configuring Iron Mountain Iron Cloud, copy the new cacert.pem file from the temporary location, in step 3, to the location mentioned in step 1.
   This will need to be done on all media servers using this cloud storage.  If you have made any changes to the original file they will be lost.  
   
7. Copy the new cloudstorejava.conf file from the temporary location, in step 3, to the location mention in step 2.

8. Start all NetBackup services.  

9. Run the following command. If the command outputs a list of cloud providers, the new CloudProvider.xml was updated successfully. If the command does not output a list of cloud providers or outputs an error message, refer to the troubleshooting section below.
    <NB_INSTALL_PATH>\NetBackup\bin\admincmd\csconfig cldprovider -l
 
 
**************************************
 
UNIX / Linux Installation Instructions
 

**************************************
 
These instructions assume that NetBackup is installed at the default location of /usr/openv/.  If NetBackup is installed at a different location, substitute that path for /usr/openv/ in the instructions below:
 
1. Copy the existing CloudProvider.xml and CloudInstance.xml files from the following location to an alternate location.
If you are configuring Iron Mountain Iron Cloud, also copy the cacert.pem file.
Default file location in NetBackup:
   In version 7.7.1 - /usr/openv/lib/ost-plugins
   In version 7.7.2 and later - /usr/openv/netbackup/db/cloud
   Note: You can revert this file, if needed.

2. Copy the existing cloudstorejava.conf file from the following location to an alternate location.
Default file location in NetBackup:
   /usr/openv/java/cloudstorejava.conf
   Note: You can revert this file, if needed.
   
3. Download and extract the zip file package to a temporary folder.  
This will create four files in the temporary location:
   * Readme.txt (this file)
   * CloudProvider.xml
   * cacert.pem
   * cloudstorejava.conf

4. Stop all NetBackup services.

5. Copy the new CloudProvider.xml file from the temporary location, in step 3, to the location mention in step 1.

6. If you are configuring Iron Mountain Iron Cloud, copy the new cacert.pem file from the temporary location, in step 3, to the location mentioned in step 1.
   This will need to be done on all media servers using this cloud storage.  If you have made any changes to the original file they will be lost.  
   
7. Copy the new cloudstorejava.conf file from the temporary location, in step 3, to the location mentioned in step 2.

8. Start all NetBackup services.  

9. Run the following command. If the command outputs a list of cloud providers, the new CloudProvider.xml was updated successfully. If the command does not output a list of cloud providers or outputs an error message, refer to the troubleshooting section below.
   <NB_INSTALL_PATH>/netbackup/bin/admincmd/csconfig cldprovider -l
 
 
**************************************
 
Troubleshooting
 
**************************************
 
NetBackup Cloud service fails to start

NetBackup fails to display a list of Cloud Providers in the admin console, or command line, after updating the CloudProvider.xml file. This is due to NetBackup encountering an entry conflict between the new CloudProvider.xml and the current CloudInstance.xml. To resolve the issue, perform the following:
 
Note: These steps are only to be performed on the NetBackup Master Server.
 
1. Stop all NetBackup services.
 
2. Revert the CloudProvider.xml and CloudInstance.xml file. Refer to the installation section above for file locations.
 
3. Start all NetBackup services.
 
4. Run the following command:
   For Windows: <NB_INSTALL_PATH>\NetBackup\bin\admincmd\csconfig cldinstance -i
   For Unix/Linux: <NB_INSTALL_PATH>/netbackup/bin/admincmd/csconfig cldinstance -i

5. Record the output of Cloud Instances in the previous step.
 
6. Stop all NetBackup services.
 
7. Move both the CloudProvider.xml and CloudInstance.xml files, in the NetBackup directory, to an alternate location. The CloudInstance.xml is stored at the same location as the CloudProvider.xml. You can revert these files, if needed.
 
8. Copy the new CloudProvider.xml file, from the update package, into the NetBackup CloudProvider.xml location. Refer to the Installation section above for the default NetBackup CloudProvider.xml location.
 
9. Start all NetBackup services.
  
10. Run the following command. If the command outputs a list of cloud providers, the CloudProvider.xml was updated successfully.
   For Windows: <NB_INSTALL_PATH>\NetBackup\bin\admincmd\csconfig cldprovider -l
   For Unix/Linux: <NB_INSTALL_PATH>/netbackup/bin/admincmd/csconfig cldprovider -l
  
11. Use the NetBackup csconfig command to add missing Cloud Instances, recorded in step 5. For instructions on how to use the csconfig command, use the command help option: csconfig --help.
 
Note: Until missing Cloud Instances are added, NetBackup jobs to these Cloud Provider storage solutions will fail.


 
Related Articles

Was this content helpful?