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™ Deduplication Guide
  3. MSDP cloud support
  4. About the disaster recovery for cloud LSU
Veritas NetBackup™ Deduplication Guide

About the disaster recovery for cloud LSU

If the disk on which the NetBackup software resides or the disk on which the deduplicated data resides fails, you can use the following steps to recover the system and data depending on different scenarios.

After recovery, your NetBackup deduplication environment functions normally. Any valid backup images on the cloud LSU storage are available for restores.

Before you start disaster recovery, ensure that:

  • NetBackup media server software is installed and connected with master server successfully.

  • The storage server is reinstalled and configured.

  • KMS encryption in cloud LSU is enabled and the KMS server is ready.

  • Cloud LSU of Amazon S3 Glacier, Deep Archive, and Microsoft Azure Archive supports cloud disaster recovery only in Scenario 1 and Scenario 3.

Scenario 1: Storage server name has not changed and the local storage is lost

Step

Task

Procedure

0

Reinstall and configure storage server

See the NetBackup Administrator's Guide, Volume I.

1

Create an empty local LSU

Refer to the "Configure/Reconfigure MSDP local storage" topic.

2

Reuse Cloud LSU

Refer to the "Reuse Cloud LSU" topic.

Scenario 2: Storage server name has changed and the local storage is lost

Step

Task

Procedure

1

Expire the backup images

Expire all backup images that reside on the deduplication disk storage.

Warning:

Do not delete the images. They are imported back into NetBackup later in this process. If you use the bpexpdate command to expire the backup images, use the -nodelete parameter.

See the NetBackup Administrator's Guide, Volume I.

2

Delete old storage server-related configurations

Refer to the "Recovering from an MSDP storage server failure" topic.

Delete the storage units that use the disk pool.

Delete the disk pool.

Delete the deduplication storage server.

Delete the deduplication host configuration file.

3

Configure new storage server.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9

4

Create an empty local LSU.

Refer to the "Configure/Reconfigure MSDP local storage" topic.

5

Reuse cloud LSU.

Refer to the "Reuse Cloud LSU" topic.

6

Create disk pool for cloud LSUs.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -stype PureDisk -dp dpname -storage_server sts_hostname -dvlist filename

7

Import the images back.

Do two-phase import.

See the NetBackup Administrator's Guide, Volume I.

Scenario 3: Storage server name has not changed and the local storage is not lost

Step

Task

Procedure

0

Reinstall and configure storage server

See the NetBackup Administrator's Guide, Volume I.

1

Reuse existing local storage path

Refer to the "Configure/Reconfigure MSDP local storage" topic.

2

Restart storage server.

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

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

Scenario 4: Storage server name has changed and local storage is not lost

Step

Task

Procedure

1

Expire the backup images.

Expire all backup images that reside on the deduplication disk storage.

Warning:

Do not delete the images. They are imported back into NetBackup later in this process. If you use the bpexpdate command to expire the backup images, use the -nodelete parameter.

See the NetBackup Administrator's Guide, Volume I.

2

Delete old storage server-related configurations.

Refer to the "Recovering from an MSDP storage server failure" topic.

Delete the storage units that use the disk pool.

Delete the disk pool.

Delete the deduplication storage server.

Delete the deduplication host configuration file.

3

Configure new storage server.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -creatests -storage_server "storage server" -stype PureDisk -media_server "media server" -st 9

4

Reuse existing local storage path

Refer to the "Configure/Reconfigure MSDP local storage" topic.

5

Restart storage server.

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

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

6

Create disk pool for cloud LSUs.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -createdp -stype PureDisk -dp dpname -storage_server sts_hostname -dvlist filename

7

Import the images back.

Do two-phase import.

See the NetBackup Administrator's Guide, Volume I.

Common disaster recovery steps
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 root -all_hosts

/usr/openv/volmgr/bin/tpconfig -add -storage_server sts_hostname -stype PureDisk -sts_user_id root -password xxx

3

Get the config template.

/usr/openv/netbackup/bin/admincmd/nbdevconfig -getconfig -storage_server sts_hostname -stype PureDisk

4

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

Reuse cloud LSU configuration.

For each cloud LSU:

nbdevconfig -setconfig -storage_server sts_hostname -stype PureDisk -configlist /path/to/dr-lsu.txt

Config template example 1:

V7.5 "operation" "reuse-lsu-cloud" string
V7.5 "lsuCloudUser" "XXX" string
V7.5 "lsuCloudPassword" "XXX" string
V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string
V7.5 "lsuCloudBucketName" "XXX" string
V7.5 "lsuCloudBucketSubName" "XXX" string

Configuration template example 2 with encryption enabled:

V7.5 "operation" "reuse-lsu-cloud" string
V7.5 "lsuCloudUser" "XXX" string
V7.5 "lsuCloudPassword" "XXX" string
V7.5 "lsuCloudAlias" "<storageserver_lsuname>" string
V7.5 "lsuCloudBucketName" "XXX" string
V7.5 "lsuCloudBucketSubName" "XXX" string
V7.5 "lsuKmsServerName" "XXX" string

If alias does not exist, you can use the csconfig command to add them.

/usr/openv/netbackup/bin/admincmd/csconfig cldinstance -as -in amazon.com -sts <storageserver> -lsu_name <lsuname>

2

Recover spad/spoold metadata from cloud.

For each cloud LSU:

/usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddr lsu1

3

Restart storage server.

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

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

Warning:

The time taken can be high if the siz eof the containers is large. Use the following command to get the status:

/usr/openv/pdde/pdcr/bin/cacontrol --catalog clouddrstatus lsu

4

Start MSDP online check to recreate refdb.

/usr/openv/pdde/pdcr/bin/pddecfg -a enabledataintegritycheck

/usr/openv/pdde/pdcr/bin/pddecfg -a startdatafullcheck

/usr/openv/pdde/pdcr/bin/crcontrol --processqueue

Feedback

Was this page helpful?
Previous

About the tool updates for cloud support

Next

About Image Sharing using MSDP cloud

Feedback

Was this page helpful?