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
NetBackup™ Deduplication Guide

Common disaster recovery steps

Following are the common disaster recovery steps:

  • Configure/Reconfigure MSDP local storage

  • Reuse cloud LSU

Configure/Reconfigure MSDP local storage

Step

Task

Procedure

1

Delete the deduplication configuration.

/usr/openv/pdde/pdconfigure/scripts/installers/PDDE_deleteConfig.sh

2

Delete the NetBackup deduplication Engine credentials on load balancing servers.

/usr/openv/volmgr/bin/tpconfig -delete -storage_server <sts_hostname> -stype PureDisk -sts_user_id <user_id> -all_hosts

/usr/openv/volmgr/bin/tpconfig -add -storage_server <sts_hostname> -stype PureDisk -sts_user_id <user_id> -password <your_passwd>

3

Redirect the command output to a file to prepare the config template.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -getconfig -storage_server <sts_hostname> -stype PureDisk >/root/local-lsu.txt

The content of the file local-lsu.txt

V7.5 "storagepath" " " string
V7.5 "spalogin" " " string
V7.5 "spapasswd" " " string
....
V7.5 "kmsservername" " " string
V7.5 "keygroupname" " " string    
V7.5 "extendedcapabilities" " " string
V7.5 "imagesharingincloud" "false" string

4

Generate the config template.

Make changes to the template file local-lsu.txt and delete all other entries that are not needed.

Parameters:

/root/local-lsu.txt
V7.5 "storagepath" "/Storage" string
V7.5 "spalogin" "my-user-name" string
V7.5 "spapasswd" "my-password" string
V7.5 "spalogretention" "90" int
V7.5 "verboselevel" "3" int

For more information about the parameters, See Editing an MSDP storage server configuration file.

5

Reuse or create storage path

/usr/openv/netbackup/bin/admincmd/nbdevconfig -setconfig -storage_server sts_hostname -stype PureDisk -configlist /root/local-lsu.txt

Reuse cloud LSU

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 "lsuCloudUser" "your-acct-id" string
V7.5 "lsuCloudPassword" "your-secret" string
V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string
V7.5 "lsuCloudBucketName" "bucket-name" string
V7.5 "lsuCloudBucketSubName" "lsuname" string

Configuration template example 2 with encryption enabled:

V7.5 "operation" "reuse-lsu-cloud" string
V7.5 "lsuCloudUser" "your-acct-id" string
V7.5 "lsuCloudPassword" "your-secret" 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

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 alias do 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>

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

5

Recover spad/spoold metadata from cloud.

For each cloud LSU perform the previous four steps, and then run the following command.

/usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddr <lsuname>

Note:

The time to execute this command depends on the size of the containers.

Run the following command to get the catalog recovery status:

/usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddrstatus <lsuname>

6

Restart storage server.

/usr/openv/netbackup/bin/bp.kill_all

/usr/openv/netbackup/bin/bp.start_all

7

Start MSDP online check to recreate refdb.

/usr/openv/pdde/pdcr/bin/pddecfg -a enabledataintegritycheck -d <dsid>

/usr/openv/pdde/pdcr/bin/pddecfg -a startdatafullcheck -d <dsid>

/usr/openv/pdde/pdcr/bin/crcontrol --processqueue --dsid <dsid>

Note:

-d and --dsid options are optional parameters and applicable for cloud LSU only. Use /usr/openv/pdde/pdcr/bin/pddecfg -a listcloudlsu to get cloud LSU dsid value. If given disd value is "0", local LSU is processed.

Feedback

Was this page helpful?
Previous

About the disaster recovery for cloud LSU

Next

Disaster recovery for cloud LSU in Flex Scale

Feedback

Was this page helpful?