Veritas 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 advanced 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's cloud tiering
- 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 master 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
- 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
Configuring NetBackup for Amazon Snowball with Amazon Snowball client
In this method data is first staged on the NetBackup media server and then using the Amazon Snowball client, data is moved to the Amazon Snowball device.
Ensure that you have enough space on the file system you plan to use for staging.
To configure NetBackup to transfer data to Amazon Snowball using the Amazon Snowball client
- Create the cloud storage server with default instance.
Note:
An Amazon Snowball device can be used to transfer data only from the region from where the device is obtained. Thus, ensure that all the buckets in storage server belong to same region.
Create different bucket(s) for Amazon Snowball when you configure the disk pool. These buckets are used to create an import job in the AWS console.
Note:
It is recommended to create the buckets from the NetBackup Administration Console. However, if you create buckets from the AWS console, ensure that only characters that are supported by NetBackup are used.
- Create an import job in the AWS console. Select the buckets that were created during the disk pool creation. Refer to the AWS documentation for detailed steps.
- Ensure that the media server has enough space to stage the backup data.
- Update the following storage server properties:
AMZ:OFFLINE_TRANSFER_MODE: FILESYSTEM
AMZ:TRANSFER_DRIVE_PATH: <absolute path where the data must be backed up>
Note:
Set these properties back to NONE after you have transferred the data to the Amazon Snowball device.
- For live data, create the storage lifecycle policy, backup policy and run the backup for initial seeding.
For old data, use the bpduplicate command and duplicate the images on the storage unit.
See the NetBackup Commands Reference Guide.
- Install the Amazon Snowball client on the media server. Refer to the AWS documentation for detailed steps.
Using the Amazon Snowball client, transfer the backup data from the media server to the Amazon Snowball device.
- After the data transfer is complete:
Deactivate the backup policy or postpone the secondary operation processing in the SLP till the device is in transit.
Set the storage server properties you have configured in step 4 to NONE.
- Ship the device to the cloud vendor. Refer to the AWS documentation for detailed steps.
After the backup job is complete, the backup data is staged on the media server. Then run the Amazon Snowball client copy command to transfer the data to the Amazon Snowball device: Following is an example:
snowball cp --recursive <TransferDrivePath/MyBucket/Image> s3://MyBucket/Logs
Refer to the AWS documentation for detailed steps.