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. Managing deduplication
  4. Managing MSDP servers
  5. Changing the MSDP storage server name or storage path
Veritas NetBackup™ Deduplication Guide

Changing the MSDP storage server name or storage path

Two aspects of a NetBackup deduplication configuration exist: the record of the deduplication storage in the EMM database and the physical presence of the storage on disk (the populated storage directory).

Warning:

Deleting valid backup images may cause data loss.

See About changing the MSDP storage server name or storage path.

Table: Changing the storage server name or storage path

Step

Task

Procedure

Step 1

Ensure that no deduplication activity occurs

Deactivate all backup policies that use deduplication storage.

See the NetBackup Administrator's Guide, Volume I:

http://www.veritas.com/docs/DOC5332

Step 2

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:

http://www.veritas.com/docs/DOC5332

Step 3

Delete the storage units that use the disk pool

See the NetBackup Administrator's Guide, Volume I:

http://www.veritas.com/docs/DOC5332

Step 4

Delete the disk pool

See Deleting a Media Server Deduplication Pool.

Step 5

Delete the deduplication storage server

See Deleting an MSDP storage server.

Step 6

Delete the configuration

Delete the deduplication configuration.

See Deleting the MSDP storage server configuration.

Step 7

Delete the deduplication host configuration file

Each load balancing server contains a deduplication host configuration file. If you use load balancing servers, delete the deduplication host configuration file from those servers.

See Deleting an MSDP host configuration file.

Step 8

Delete the identity file and the file system table file

Delete the following files from the MSDP storage server, depending on operating system:

UNIX:

/storage_path/data/.identity
/storage_path/etc/puredisk/fstab.cfg

Windows:

									storage_path\data\.identity
									storage_path\etc\puredisk\fstab.cfg

Step 9

Change the storage server name or the storage location

See the computer or the storage vendor's documentation.

See Use fully qualified domain names.

See MSDP storage path properties.

Step 10

Reconfigure the storage server

When you configure deduplication, select the host by the new name and enter the new storage path (if you changed the path). You can also use a new network interface.

See Configuring MSDP server-side deduplication.

Step 11

Import the backup images

See the NetBackup Administrator's Guide, Volume I:

http://www.veritas.com/docs/DOC5332

Feedback

Was this page helpful?
Previous

About changing the MSDP storage server name or storage path

Next

Removing an MSDP load balancing server

Feedback

Was this page helpful?