Veritas NetBackup™ Cloud Administrator's Guide
- About NetBackup cloud storage
- About the cloud storage
- About the Amazon S3 cloud storage API type
- About protecting data in Amazon for long-term retention
- Protecting data using Amazon's cloud tiering
- About using Amazon IAM roles with NetBackup
- Protecting data with Amazon Snowball and Amazon Snowball Edge
- 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
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.
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.
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:TRANSFER_DRIVE_PATH: <absolute path where the data must be backed up>
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.