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
- Troubleshooting
- About unified logging
- About legacy logging
- Troubleshooting cloud storage configuration issues
- Troubleshooting cloud storage operational issues
Configuring NetBackup for Amazon Snowball and Amazon Snowball Edge for NetBackup CloudCatalyst Appliance
To configure NetBackup for Amazon Snowball and Amazon Snowball Edge for NetBackup CloudCatalyst Appliance
- Configure Appliance with Cloud Catalyst storage server.
- Create an import job in the AWS console. Select the bucket that was created during configuring the appliance. Refer to the AWS documentation for detailed steps.
- After the device arrives and is configured in your environment, create and Amazon custom cloud storage instance. Configure the instance with the Snowball Adapter IP, Address/Hostname, ports, Access style, and Location constraint.
- Move the storage server that is created under default-shipped cloud storage instance, to the newly created custom cloud storage instance.
Find the instance to which the storage server belongs to. Run the following command:
csconfig cldinstance -i
Remove the storage server from the discovered instance. Run the following command:
csconfig cldinstance -rs -in cloud storage instance name -sts storage server name
See the NetBackup Commands Reference Guide.
Add a new storage server with the same name, under the new cloud storage instance. Run the following command:
csconfig cldinstance -as -in Cloud Storage Instance name -sts storage server name
See the NetBackup Commands Reference Guide.
Also ensure that you have configured the SSL settings as per your requirements.
- (Required for Snowball Edge) Update the storage server credentials from the media server that is attached to the storage server. Run the following command:
tpconfig -update -storage_server storage server name -stype storage server type -sts_user_id [user ID] -password password
See the NetBackup Commands Reference Guide.
Ensure that SSL settings are done correctly.
- Update the following storage server property:
AMZ:OFFLINE_TRANSFER_MODE: PROVIDER_API
Update the other storage properties according to the information that is noted in step 3.
- 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.
- 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 property you have configured to NONE.
Save the properties. You need this information during the post-backup process.
Take an image capture of storage server properties from Administration console or use nbdevconfig -getconfig command. See the NetBackup Commands Reference Guide.
- Ship the device to the cloud vendor. Refer to the AWS documentation for detailed steps.
Note:
After backups are imported into the cloud bucket, before restore you need to perform the post backup procedures. See Post backup procedures if you have used S3 API interface.