Veritas NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the Amazon S3 cloud storage API type
- Protecting data in Amazon Glacier for long-term retention
- Protecting data using Amazon's cloud tiering
- About EMC Atmos cloud storage API type
- About Microsoft Azure cloud storage API type
- About OpenStack Swift cloud storage API type
- Configuring cloud storage in NetBackup
- Scalable Storage properties
- Cloud Storage properties
- About the NetBackup CloudStore Service Container
- About the NetBackup media servers for cloud storage
- Configuring a storage server for cloud storage
- NetBackup cloud storage server properties
- Configuring a storage unit for cloud storage
- Changing cloud storage disk pool properties
- Monitoring and Reporting
- Operational notes
- About unified logging
- About legacy logging
- Troubleshooting cloud storage configuration issues
- Troubleshooting cloud storage operational issues
Cloud storage backups fail
See the following topics:
A message similar to the following is in the job details:
Critical bptm(pid=28291) accelerator verification failed: backupid= host_name_1373526632, offset=3584, length=141976576, error= 2060022, error message: software error Critical bptm(pid=28291) image write failed: error 2060022: software error Error bptm(pid=28291) cannot write image to disk, Invalid argument end writing; write time: 0:02:31 Info bptm(pid=28291) EXITING with status 84 Info bpbkar(pid=6044) done. status: 84: media write error media write error(84)
This error may occur in the environments that have more than one cloud storage server. It indicates that NetBackup Accelerator backups of a client to one cloud storage server were later directed to a different cloud storage server.
For Accelerator backups to cloud storage, ensure the following:
Always back up each client to the same storage server. Do so even if the other storage server represents storage from the same cloud storage vendor.
Always use the same backup policy to back up a client, and do not change the storage destination of that policy.
If the cloud storage server WRITE_BUFFER_SIZE property exceeds the total swap space of the computer, backups can fail with a status 84.
Adjust the WRITE_BUFFER_SIZE size to a value lower than the computer's total swap space to resolve this issue.
A message similar to the following is in the job details:
Info bptm(pid=xxx) start backup Critical bptm(pid=xxxx) image open failed: error 2060029: authorization failure Error bpbrm(pid=xxxx) from client gabby: ERR - Cannot write to STDOUT. E rrno = 32: Broken pipe Info bptm(pid=xxxx) EXITING with status 84
A message similar to the following appears in the bptm log file:
Container container_name is not Veritas container or tag data error, fail to create image. Please make sure that the LSU is created by means of NBU.
This error indicates that the volume was created by using the cloud storage vendor's interface.
You must use the NetBackup Disk Pool Configuration Wizard to create the volume on the cloud storage. The wizard applies a required partner ID to the volume. If you use the vendor interface to create the container, the partner ID is not applied.
To resolve the problem, use the cloud storage vendor's interface to delete the container. In NetBackup, delete the disk pool and then recreate it by using the Disk Pool Configuration Wizard.
When an AIX media server backs up large files, you may encounter memory issues. These memory issues can result in failed backups. The backups fail with a NetBackup status code 84 (media write error) or a NetBackup status code 87 (media close error). Change the AIX ulimit size to unlimited to resolve this issue. Be sure to stop and restart the NetBackup services or daemons after you change the ulimit value.
The following are examples:
ulimit -m unlimited
ulimit -d unlimited
ulimit -s unlimited
If the NetBackup CloudStore Service Container is not active, backups cannot be sent to the cloud storage.
NetBackup does not validate that the CloudStore Service Container is active when you use NetBackup commands to configure NetBackup cloud storage. Therefore, any backups that initiate in such a scenario fail.
While you configure a cloud storage server, you must ensure that the media server and the master server are of the same version.
This limitation does not apply to the existing cloud storage servers.
Cloud backups may fail in the following scenario:
You selectedwhile you configured the storage unit and NetBackup uses a media server with version different than the master server version during cloud storage configuration.
To resolve this issue, do the following:
Select Media Servers pane.while you configure the storage unit and select the media server with a version same as master server from the
The cloud backups and restore operations failing with error code 83 or error code 2106 may occur due to any one of the following reasons:
The media server's date and time settings are skewed (not in sync with the GMT/UTC time).
The storage server credentials that are provided are incorrect.
Perform the following:
Change the media server's date and time settings so that it is in sync with the GMT/UTC time.
Update the storage server credentials. Use the tpconfig command to update the credentials. For more information, see the NetBackup Commands Reference Guide.
If the cloud storage backups fails because of certificate issues, verify the following:
cacert.pemfile is present on both NetBackup master and media server in following locations:
cacert.pemfile is not present, run the nbcertcmd -getCACertificate on the master server. After running this command, restart the NetBackup CloudStore Service Container.
See the NetBackup Commands Reference Guide for a complete description of the command.
This cacert.pem file is a NetBackup-specific file. This file includes the CA certificates generated by the NetBackup authorization service.
cacert.pemfile is same on the NetBackup master and media server.
That the machine certificate is present in following locations:
If the security certificate is not present, run the bpnbaz -ProvisionCert on the master server. After running this command, restart the NetBackup CloudStore Service Container on the master and media server.
The NetBackup CloudStore Service is active.
The NetBackup Administration Console on the Security Management > Global Security Settings > Secure Communication tab.option on the NetBackup master server is selected if the media server is of the version 8.0 or earlier. The option is available in the
On the media server, if the certificate deployment security level if set to Very High, automatic certificate deployment is disabled. An authorization token must accompany every new certificate request. Therefore, you must create an authorization token before deploying the certificates.
See the 'Creating authorization tokens' topic in the NetBackup™ Security and Encryption Guide for detailed steps.
NetBackup consumes the available bandwidth to it's maximum potential and pushes the requests accordingly, however the Amazon S3 complaint cloud is not able to process the number requests.
The cloud vendor returns error 503 to slow down the requests and the backup job fails with the following errors:
In the media server
bptm:4940:<media_server_name>: AmzResiliency: AmzResiliency::getRetryType cURL error: 0, multi cURL error: 0, HTTP status: 503, XML response: SlowDown, RetryType: RETRY_EXHAUSTED
In the media server
bpbrm Exit: client backup EXIT STATUS 41: network connection timed out
This issue arises only if higher bandwidth is available between NetBackup and the cloud storage.
To troubleshoot you can perform one of the following:
Configure bandwidth throttling to reduce the number of requests.
Reduce the number of read/write buffers.
Talk to your cloud vendor to increase the number of parallel requests limit. This might incur extra cost.