Configuring NetBackup for Amazon Snowball with Amazon S3 API interface
When you backup data to the Amazon Snowball device using the Amazon S3 interface, data is moved directly from the source to the Amazon Snowball device using the Amazon S3 APIs.
To configure NetBackup to transfer data to Amazon Snowball using the S3 API interface
- Create a temporary storage server (non-CloudCatalyst) and disk pool to create or list the buckets that you plan to use for the device import job.
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.
- Delete the temporary storage server (non-CloudCatalyst) and disk pool.
- Create an import job in the AWS console. Refer to the AWS documentation for detailed steps.
- Install the Amazon Snowball S3 adapter on a different host. Refer to the AWS documentation for detailed steps.
- (Optional) To use SSL protocol for communication with the Amazon Snowball adapter, append the certificate provided to the Amazon Snowball adapter on the command line as it is to
/usr/openv/var/global/wmc/cloud/cacert.pemfile on the media server. Ensure that the format and length of the newly copied certificate matches with the existing certificates incacert.pem.See Configuring SSL for Amazon Snowball and Amazon Snowball Edge.
- Add a custom instance for the device.
Set the custom instance's cloud storage properties with details of the host on which you have installed the Amazon Snowball S3 adapter.
Set the following in the General Settings tab:
Provider type: Amazon or Amazon GovCloud depending upon the end point for which you have ordered the device.
Service host: IP or host name of the adapter
Service endpoint: Leave blank
HTTP Port: Default is 8080. Or enter the port you have configured.
HTTPS port: Default is 8443. Or enter the port you have configured.
Endpoint access style: Path Style
Set the following in the Region Setting tab:
Location constraint: Region from where you have ordered the device.
Service host: IP or host name of the adapter
Note:
An Amazon Snowball Edge device can be used to transfer data only from the region from where the device is obtained. Thus, use the location constraint and service host of the region from where the device is obtained.
- Create a storage server for the device using the custom instance.
- Update the following storage server property:
AMZ:OFFLINE_TRANSFER_MODE: PROVIDER_API
- For live data, create the NetBackup 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 properties 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.
Also, note down the object size (for non-CloudCatalyst) that was configured.
- 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.