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. NetBackup™ Deduplication Guide
  3. MSDP cloud support
  4. About NetBackup support for AWS Snowball Edge
  5. Reconfigure NetBackup to work with S3
  6. Bucket is in a default AWS Region
NetBackup™ Deduplication Guide

Bucket is in a default AWS Region

For the case of reconfiguring NetBackup to work with S3 after performing backups to AWS Snowball Edge when the bucket is in a default AWS region, use the following procedure. You can also use the following procedure if you encounter an error for unique host name.

To reconfigure NetBackup to work with S3 after a backup is performed

  1. Verify that the backup policies and the SLP targeting the AWS Snowball Edge are deactivated. If not, deactivate them before proceeding with the reconfiguration steps.

    Run the following command to suspend the secondary operation for SLP:

    /usr/openv/netbackup/bin/admincmd/nbstlutil inactive -lifecycle <slp_name>

  2. To get the storage server name created for the custom instance, run the following and note the storage server which was configured when you created the disk pool.

    /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -i -in <name of your instance>

  3. To remove the storage server from the custom instance, run:

    /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -rs -in <instance name> -sts <storage server name from step 2>

  4. To add a storage server to an amazon.com instance, run:

    /usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in amazon.com -sts <storage server name from step 2>

  5. Run: /usr/openv/netbackup/bin/admincmd/csconfig r to refresh the cloud instance.
  6. Up the AWS Snowball Edge volume: /usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate -stype PureDisk -dp <disk_pool_name> -dv <disk_volume_name> -state UP
  7. Log on to the NetBackup web UI.
  8. Go to your Disk pool in the NetBackup web UI and update the credentials with credentials of your AWS account.
  9. Restart the pdde services on the media server:
    • /usr/openv/pdde/pdconfigure/pdde stop

    • /usr/openv/pdde/pdconfigure/pdde start

  10. In the NetBackup web UI, go to Storage > Disk storage > Disk pools, select the disk pool and click on Update disk volume.
  11. Run the following and verify Status = UP: /usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype PureDisk -U -dp <disk_pool_name>
  12. Open the Disk pool details page in NetBackup web UI and verify that the Service host is updated to the AWS service host for the region in the Cloud details section.
  13. Activate backup policies or activate the secondary operation processing in the SLP, you can use the following command to activate secondary operations in the SLP:

    /usr/openv/netbackup/bin/admincmd/nbstlutil active -lifecycle <slp_name>

  14. Perform the restore and verify the data. Use the NetBackup web UI to verify the images.

Feedback

Was this page helpful?
Previous

Reconfigure NetBackup to work with S3

Next

Bucket is in a non-default AWS Region (or storage already exists in the AWS region)

Feedback

Was this page helpful?