Veritas NetBackup™ Cloud Administrator's Guide

Cloud storage backups fail

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.

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.

See Viewing cloud storage job details.

See NetBackup cloud storage log files.

This is applicable to media server versions 7.7.x to 8.1.2 only.

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.

See NetBackup CloudStore Service Container startup and shutdown troubleshooting.

While you configure a cloud storage server, you must ensure that the media server and the master server are of the same version.

Cloud backups may fail in the following scenario:

You selected Use any available media server while 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 Only use the following media servers while you configure the storage unit and select the media server with a version same as master server from the Media Servers pane.

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:

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:

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:

This issue arises only if higher bandwidth is available between NetBackup and the cloud storage.

To troubleshoot you can perform one of the following: