How MSDP restores work

The following two methods exist to for MSDP restore operations:

Table: MSDP restore types

Type	Description
Normal restore	The MSDP storage server first rehydrates (that is, reassembles) the data. NetBackup then chooses the least busy media server to move the data to the client. (NetBackup chooses the least busy media server from those that have credentials for the NetBackup Deduplication Engine.) The media server bptm process moves the data to the client. The following media servers have credentials for the NetBackup Deduplication Engine: The media server that hosts the storage server. Although the media server and the storage server share a host, the storage server sends the data through the media server bptm process on that host. A load balancing server in the same deduplication node. See About MSDP load balancing servers. A deduplication server in a different deduplication node that is the target of optimized duplication. See About the media servers for MSDP optimized duplication within the same domain. You can specify the server to use for restores.
Restore directly to the client	The storage server can bypass the media server and move the data directly to the client. NetBackup does not choose a media server for the restore, and the restore does not use the media server bptm process. You must configure NetBackup to bypass a media server and receive the restore data directly from the storage server. See Configuring MSDP restores directly to a client . By default, NetBackup rehydrates the data on the storage server except for client-side deduplication clients. Those clients rehydrate the data. You can configure NetBackup so that the data is rehydrated on the storage server rather than the client. See the RESTORE_DECRYPT_LOCAL parameter in the MSDP `pd.conf` file. See MSDP pd.conf file parameters. See Editing the MSDP pd.conf file.

Type

Description

Normal restore

The MSDP storage server first rehydrates (that is, reassembles) the data. NetBackup then chooses the least busy media server to move the data to the client. (NetBackup chooses the least busy media server from those that have credentials for the NetBackup Deduplication Engine.) The media server bptm process moves the data to the client.

The following media servers have credentials for the NetBackup Deduplication Engine:

The media server that hosts the storage server.
Although the media server and the storage server share a host, the storage server sends the data through the media server bptm process on that host.
A load balancing server in the same deduplication node.
See About MSDP load balancing servers.
A deduplication server in a different deduplication node that is the target of optimized duplication.
See About the media servers for MSDP optimized duplication within the same domain.

You can specify the server to use for restores.

Restore directly to the client

The storage server can bypass the media server and move the data directly to the client. NetBackup does not choose a media server for the restore, and the restore does not use the media server bptm process.

You must configure NetBackup to bypass a media server and receive the restore data directly from the storage server.

See Configuring MSDP restores directly to a client .

By default, NetBackup rehydrates the data on the storage server except for client-side deduplication clients. Those clients rehydrate the data. You can configure NetBackup so that the data is rehydrated on the storage server rather than the client. See the RESTORE_DECRYPT_LOCAL parameter in the MSDP pd.conf file.

See MSDP pd.conf file parameters.

See Editing the MSDP pd.conf file.

More Information

Specifying the restore server

How MSDP restores work

Feedback

Feedback