Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ Cloud Administrator's Guide
  3. About the cloud storage
  4. About the Amazon S3 cloud storage API type
  5. Protecting data with Amazon Snowball and Amazon Snowball Edge
  6. Configuring NetBackup for Amazon Snowball with Amazon Snowball client
Veritas NetBackup™ Cloud Administrator's Guide

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

  1. 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.

    See Configuring cloud storage in NetBackup.

  2. 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.
  3. Ensure that the media server has enough space to stage the backup data.
  4. 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.

    See NetBackup cloud storage server connection properties.

  5. 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.

  6. 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.

  7. 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.

  8. Ship the device to the cloud vendor. Refer to the AWS documentation for detailed steps.
Example of Amazon client command to move data to Amazon Snowball device

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.

Feedback

Was this page helpful?
Previous

Protecting data with Amazon Snowball and Amazon Snowball Edge

Next

Configuring NetBackup for Amazon Snowball with Amazon S3 API interface

Feedback

Was this page helpful?