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
  3. Veritas NetBackup™ Deduplication Guide
  5. Recovering MSDP
  7. Recovering from an MSDP storage server failure
Veritas NetBackup™ Deduplication Guide

Recovering from an MSDP storage server failure

To recover from a permanent failure of the storage server host computer, use the process that is described in this topic.

NetBackup recommends that you consider the following items before you recover:

  • The new computer must use the same byte order as the old computer.

    Warning:

    If the new computer does not use the same byte order as the old computer, you cannot access the deduplicated data. In computing, endianness describes the byte order that represents data: big endian and little endian. For example, SPARC processors and Intel processors use different byte orders. Therefore, you cannot replace an Oracle Solaris SPARC host with an Oracle Solaris host that has an Intel processor.

  • Veritas recommends that the new computer use the same operating system as the old computer.

  • Veritas recommends that the new computer use the same version of NetBackup as the old computer.

    If you use a newer version of NetBackup on the new computer, ensure that you perform any data conversions that may be required for the newer release.

    If you want to use an older version of NetBackup on the replacement host, contact your Veritas support representative.

Table: Recover from an MSDP storage server failure

Step

Task

Procedure

Step 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:

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

Step 2

Delete the storage units that use the disk pool

See the NetBackup Administrator's Guide, Volume I:

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

Step 3

Delete the disk pool

See Deleting a Media Server Deduplication Pool.

Step 4

Delete the deduplication storage server

See Deleting an MSDP storage server.

Step 5

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 6

Delete the credentials on deduplication servers

If you have load balancing servers, delete the NetBackup Deduplication Engine credentials on those media servers.

Step 7

Configure the new host so it meets deduplication requirements

When you configure the new host, consider the following:

  • You can use the same host name or a different name.

  • You can use the same Storage Path or a different Storage Path. If you use a different Storage Path, you must move the deduplication storage to that new location.

  • If the Database Path on the original host is different that the Storage Path, you can do one of the following:

    • You can use the same Database Path.

    • You can use a different Database Path. If you do, you must move the deduplication database to the new location.

    • You do not have to continue to use a different Database Path. You can move the databases directory into the Storage Path and then specify only the Storage Path when you configure the storage server.

  • You can use the host's default network interface or specify a network interface.

    If the original host used a specific network interface, you do not have to use the same interface name.

  • If you had configured the previous MSDP storage server to use MSDP Encryption using KMS service, you must use the same configuration for the new MSDP storage server.

See About MSDP storage servers.

See About MSDP server requirements.

Step 8

Connect the storage to the host

Use the storage path that you configured for this replacement host.

See the computer or the storage vendor's documentation.

Step 9

Install the NetBackup media server software on the new host

See the NetBackup Installation Guide for UNIX and Windows:

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

Step 10

Reconfigure deduplication

You must use the same credentials for the NetBackup Deduplication Engine.

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

More Information

Deleting credentials from a load balancing server

Feedback

Was this page helpful?
Previous

Recovering from an MSDP storage server disk failure

Next

Recovering the MSDP storage server after NetBackup catalog recovery

Feedback

Was this page helpful?