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 the disaster recovery for cloud LSU
  5. Common disaster recovery steps
  6. Reuse cloud LSU as read-only
NetBackup™ Deduplication Guide

Reuse cloud LSU as read-only

Step

Task

Procedure

1

Get LSU name before you reuse cloud LSU configuration.

Run any of the following commands to get the LSUs (disk volumes) on this MSDP server.

/usr/openv/netbackup/bin/admincmd/nbdevquery -listdp -stype PureDisk -U

/usr/openv/netbackup/bin/admincmd/nbdevquery -listdv -stype PureDisk -U

Sample output:

Disk Pool Name             : my-aws-pool
Disk Type                  : PureDisk
Disk Volume Name           : my-aws-lsu

Disk volume name is LSU name. In this sample, LSU name is my-aws-lsu.

2

Prepare a template file and save it.

Config template example 1 :

V7.5 "operation" "reuse-lsu-cloud" string
V7.5 "cmsCredName" "your-cms-cred-name" string
V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string
V7.5 "lsuCloudBucketName" "bucket-name" string
V7.5 "lsuCloudBucketSubName" "lsuname" string
V7.5 "requestCloudCacheCapacity" "1017" string

Configuration template example 2 with encryption enabled:

V7.5 "operation" "reuse-lsu-cloud" string
V7.5 "cmsCredName" "your-cms-cred-name" string
V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string
V7.5 "lsuCloudBucketName" "bucket-name" string
V7.5 "lsuCloudBucketSubName" "lsuname" string
V7.5 "lsuKmsServerName" "FQDN-KMS-server-host" string
V7.5 "requestCloudCacheCapacity" "1017" string

3

Check if lsuCloudAlias exist.

Run the following command to list the instances to check if lsuCloudAlias exist.

/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -i | grep <lsuname>

If an alias does not exist, run the following command to add them.

/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in <cloud_privder_name> -sts <storageserver> -lsu_name <lsuname> [-storage_class <storage class or tier>]

Note:

The storage class must match the storage class that was selected during the initial configuration of LSU on the source storage server. The jobs may fail if the incorrect storage class is specified.

The jobs may fail if the incorrect storage class is specified.

Run the following command to find the cloud_privder_name:

/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -l

4

Reuse cloud LSU configuration.

Run the following command for each LSU to configure the cloud LSU.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server <storageserver> -stype PureDisk -configlist /root/dr-lsu.txt

Feedback

Was this page helpful?
Previous

Reuse cloud LSU

Next

Consolidating the cloud LSU

Feedback

Was this page helpful?