NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the cloud storage vendors for NetBackup
- About the Amazon S3 cloud storage API type
- Amazon S3 cloud storage vendors certified for NetBackup
- Amazon S3 storage type requirements
- Permissions required for Amazon S3 cloud provider user
- Amazon S3 cloud storage provider options
- Amazon S3 cloud storage options
- Amazon S3 cloud storage server configuration options
- Amazon S3 credentials broker details
- About private clouds from Amazon S3-compatible cloud providers
- About Amazon S3 storage classes
- Amazon virtual private cloud support with NetBackup
- About protecting data in Amazon for long-term retention
- Protecting data using Amazon S3 Intelligent Tiering (LIFECYCLE)
- About using Amazon IAM roles with NetBackup
- About NetBackup character restrictions for Amazon S3 cloud connector
- Protecting data with Amazon Snowball and Amazon Snowball Edge
- Configuring NetBackup for Amazon Snowball with Amazon Snowball client
- Configuring NetBackup for Amazon Snowball with Amazon S3 API interface
- Using multiple Amazon S3 adapters
- Configuring NetBackup with Amazon Snowball Edge with file interface
- Configuring NetBackup for Amazon Snowball Edge with S3 API interface
- Configuring SSL for Amazon Snowball and Amazon Snowball Edge
- Post backup procedures if you have used S3 API interface
- About Microsoft Azure cloud storage API type
- About OpenStack Swift cloud storage API type
- Configuring cloud storage in NetBackup
- Before you begin to configure cloud storage in NetBackup
- Configuring cloud storage in NetBackup
- Cloud installation requirements
- Scalable Storage properties
- Cloud Storage properties
- About the NetBackup CloudStore Service Container
- Deploying host name-based certificates
- Deploying host ID-based certificates
- About data compression for cloud backups
- About data encryption for cloud storage
- About NetBackup KMS for encryption of NetBackup cloud storage
- About external KMS for encryption of NetBackup cloud storage
- About cloud storage servers
- About object size for cloud storage
- About the NetBackup media servers for cloud storage
- Configuring a storage server for cloud storage
- Changing cloud storage server properties
- NetBackup cloud storage server properties
- About cloud storage disk pools
- Configuring a disk pool for cloud storage
- Saving a record of the KMS key names for NetBackup cloud storage encryption
- Adding backup media servers to your cloud environment
- Configuring a storage unit for cloud storage
- About NetBackup Accelerator and NetBackup Optimized Synthetic backups
- Enabling NetBackup Accelerator with cloud storage
- Enabling optimized synthetic backups with cloud storage
- Creating a backup policy
- Changing cloud storage disk pool properties
- Certificate validation against Certificate Revocation List (CRL)
- Managing Certification Authorities (CA) for NetBackup Cloud
- Monitoring and Reporting
- Operational notes
- NetBackup bpstsinfo command operational notes
- Unable to configure additional media servers
- Cloud configuration may fail if NetBackup Access Control is enabled
- Deleting cloud storage server artifacts
- Using csconfig reinitialize to load updated cloud configuration settings
- Enabling or disabling communication between primary server and legacy cloud storage media servers
- Troubleshooting
- About unified logging
- About legacy logging
- NetBackup cloud storage log files
- Enable libcurl logging
- NetBackup Administration Console fails to open
- Troubleshooting cloud storage configuration issues
- NetBackup Scalable Storage host properties unavailable
- Connection to the NetBackup CloudStore Service Container fails
- Cannot create a cloud storage disk pool
- Cannot create a cloud storage
- Data transfer to cloud storage server fails in the SSL mode
- Amazon GovCloud cloud storage configuration fails in non-SSL mode
- Data restore from the Google Nearline storage class may fail
- Backups may fail for cloud storage configurations with Frankfurt region
- Backups may fail for cloud storage configurations with the cloud compression option
- Fetching storage regions fails with authentication version V2
- Backup from snapshot parent jobs are failing with the status code 160
- Troubleshooting cloud storage operational issues
- Cloud storage backups fail
- Stopping and starting the NetBackup CloudStore Service Container
- A restart of the nbcssc (on legacy media servers), nbwmc, and nbsl processes reverts all cloudstore.conf settings
- NetBackup CloudStore Service Container startup and shutdown troubleshooting
- bptm process takes time to terminate after cancelling GLACIER restore job
- Handling image cleanup failures for Amazon Glacier vault
- Cleaning up orphaned archives manually
- Restoring from Amazon Glacier vault spans more than 24 hours for single fragment
- Restoring from GLACIER_VAULT takes more than 24 hours for Oracle databases
- Troubleshooting failures due to missing Amazon IAM permissions
- Restore job fails if the restore job start time overlaps with the backup job end time
- Post processing fails for restore from Azure archive
- Troubleshooting Amazon Snowball and Amazon Snowball Edge issues
- Index
Enabling or disabling communication between primary server and legacy cloud storage media servers
This is applicable for media server version 7.7.x to 8.1.2 only.
The NetBackup CloudStore Service Container (nbcssc) service that runs on older cloud storage media servers uses port 5637 to communicate with the primary server. Starting with release 8.2, nbcssc service is no longer deployed. The NetBackup Web Management Console (nbwmc) and the NetBackup Service Layer (nbsl) services now handle that functionality.
Even when you upgrade your primary server to 8.2 or later, the legacy cloud storage media servers continue to use the legacy cloud service for communicating with the primary server. The NetBackup 8.2 primary server, however, does support legacy cloud storage media servers. To allow communication between an 8.2 primary server and the older media servers, you have to open port 5637 on the primary server.
To enable nbwmc service communication on port 5637
- Run the following command on the primary server:
UNIX:
# usr/openv/wmc/bin/install/configurePorts -addLegacyCloudService
Windows:
<install_path>\NetBackup\wmc\bin\install\configurePorts -addLegacyCloudService
- Restart the
nbwmcservice for the changes to take effect. - Run the following command to provision a hostname-based certificate for the media server:
UNIX:
# usr/openv/netbackup/bin/admincmd/bpnbaz -ProvisionCert <media_server>
Windows:
<install_path>\NetBackup\bin\admincmd\bpnbaz -ProvisionCert <media_server>
In case of an appliance, run the following commands instead:
UNIX:
# usr/openv/netbackup/bin/bpnbat -AddMachine <appliance_hostname>
Windows:
<install_path>\NetBackup\bin\bpnbat -AddMachine <appliance_hostname>
- Restart the cloud storage services on the media server.
Even though older versions of media servers are supported, it is recommended that you upgrade such media servers to version 8.2 or later. After upgrading all the legacy media servers, you can disable nbwmc service usage on port 5637.
To disable nbwmc service communication on port 5637
- Run the following command on the primary server:
UNIX:
# usr/openv/wmc/bin/install/configurePorts -removeLegacyCloudService
Windows:
<install_path>\NetBackup\wmc\bin\install\configurePorts -removeLegacyCloudService
- Restart the
nbwmcservice for the changes to take effect.