Symantec 7 instruction

106Disaster recovery

Recovering from a permanent deduplication storage server failure

Warning: The new host must use the same byte order as the old host. If it does not, you cannot access the deduplicated data.

(In computing, endianness describes the byte order that represents data: big endian and little endian. For example, Sun SPARC processors and Intel processors use different byte orders. Therefore, you cannot replace a Solaris SPARC host with a host that has an Intel processor.

Table 8-2	Process to recover from a permanent media server failure
Task	Procedure

Change the disk volume state and disk pool state to DOWN

Configure the new host so it meets deduplication requirements

Move the storage to the new host.

Install the NetBackup media server software on the new host

Delete the credentials on media servers

See “Changing the deduplication disk volume state” on page 77.

See “Changing the deduplication pool state” on page 77.

Use the same host name as the failed server.

See “About deduplication servers” on page 21.

See “About deduplication server requirements” on page 23.

Ensure that the storage and database are mounted at the same locations.

See the storage vendor's documentation.

See the NetBackup Installation Guide for UNIX and Linux.

See the NetBackup Installation Guide for Windows.

See “About the deduplication license key” on page 42.

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

See “Deleting credentials from a load balancing server” on page 75.

Add the credentials to the storage server

Add the NetBackup Deduplication Engine credentials to the storage server.

See “Adding NetBackup Deduplication Engine credentials” on page 74.

Get a configuration file	If you did not save a storage server configuration file before
template	the failure, get a template configuration file.
	See “Getting the storage server configuration” on page 68.
Edit the configuration file	See “Editing a storage server configuration file” on page 68.

Image 106

Symantec 7 manual Process to recover from a permanent media server failure

Contents

Symantec NetBackup Deduplication Guide Symantec NetBackup Deduplication Guide Legal Notice Symantec Corporation Ellis Street Mountain View, CA Technical Support Contacting Technical Support Licensing and registration Maintenance agreement resources Contents Paths Chapter Deduplication client backup process Disaster recoveryRecovering from a deduplication storage server disk failure Preparing for disaster About NetBackup deduplication This chapter includes the following topics About NetBackup deduplication options NetBackup deduplication options Type Description See the NetBackup PureDisk Getting Started Guide How deduplication works See Media server deduplication process on Page Planning your deployment Planning your deduplication deployment Deployment task Where to find the information Deployment overview About the NetBackup Media Server Deduplication Option About the deduplication storage type See About deduplication servers on NetBackup media server deduplication About deduplication servers About deduplication nodes Host Description About deduplication server requirements About media server deduplication limitations About NetBackup Client Deduplication See the NetBackup PureDisk Deduplication Option Pddo Guide About client deduplication host requirements NetBackup client deduplicationAbout client deduplication requirements About NetBackup Deduplication Engine credentials About client deduplication limitations About firewalls and the deduplication hosts About the network interface for deduplicationAbout scaling deduplication About optimized duplication of deduplicated data About compression and encryptionOptimized deduplication copy requirements Page Page Optimized deduplication copy limitations About deduplication performance When When Description How file size may affect the deduplication rate Task Procedure Volume To migrate from PureDisk to NetBackup deduplication Migrating from another storage type to deduplication See the NetBackup Administrators Guide for Unix and Linux About provisioning the storage About deduplication storage requirements About deduplication storage capacity About the deduplication storage pathsPage Page Installing deduplication About installing deduplication About the deduplication license key Licensing NetBackup deduplicationReplacing the deduplication storage server host computer See Deleting credentials from a load balancing server on Uninstalling media server deduplication See Adding a load balancing server on Purediskdbuser folder Disable media server deduplication Opt/pdshared Configuring deduplication Configuring deduplication Configuring a deduplication storage server Deduplication configuration tasks Network interface About deduplication poolsStorage paths Load balancing servers, if any Configuring a deduplication pool Media server deduplication pool properties Disk volume Property Description Configuring a deduplication storage unit Per volume Deduplication storage unit properties Disk type Deduplication storage unit recommendations Increase the Maximum concurrent jobs gradually Throttle traffic to the media servers Configuring backups Enabling client deduplication Configuring optimized deduplication copy behavior Configuring optimized deduplication copyYou can configure optimized copy of deduplicated backups Adding a load balancing server To configure the number of storage lifecycle policy retriesBehavior file resides in the following directories Management Credentials Storage Server About the deduplication configuration file Editing the deduplication configuration file Pd.conf file settings Debuglog Setting Default value Possible values Action Optduptimeout Maximgmbsize See Resetting the deduplication registry on Managing deduplication Managing deduplication servers Changing deduplication storage server properties Determining the deduplication storage server state Deleting a deduplication storage serverChange the value Click OK Editing a storage server configuration file Getting the storage server configurationFollowing is example output See Getting the storage server configuration on Alternative, the file may be an edited configuration file Setting the storage server configurationDeleting a load balancing server configuration file Removing a load balancing server To remove a media server from a deduplication node Viewing deduplication storage servers Viewing deduplication storage server attributes Resetting the deduplication registry Procedure differs on Unix and on Windows Adding NetBackup Deduplication Engine credentials Managing NetBackup Deduplication Engine credentialsYou can manage existing credentials in NetBackup Deleting credentials from a load balancing server Changing NetBackup Deduplication Engine credentialsFor sshostname, use the name of the storage server Changing deduplication disk pool properties Managing deduplication disk poolsSelect the storage server, then select Edit Change Disk volume state is UP or Down Changing the deduplication disk volume stateChanging the deduplication pool state State is either UP or Down Deleting a deduplication poolDetermining the deduplication pool state Disk pool state is UP or Down To determine disk pool state Determining the deduplication disk volume stateViewing deduplication disk pools State is either UP or DOWN. The following is example output Monitoring the deduplication rates Monitoring deduplication activityYou can monitor deduplication activity Many factors affect deduplication performance Viewing disk reports1describes the disk reports available Disk reports Report Description Monitoring deduplication processes Monitoring deduplication logs NetBackup Deduplication Manager logs Log files are in the /storagepath/log/spad directory Save the file Run the following command For bpbrm About VxUL logs Monitoring deduplication storage capacity and usage About deduplication capacity and usage reporting Option Description Credentials Storage Servers About deduplication container files Viewing capacity within deduplication container files Following are background maintenance processes Deleting backup imagesAbout maintenance processing Disabling deduplication for a client NetBackup Deduplication Engine queue processing Managing deduplication About maintenance processing Troubleshooting installation issues Installation on Suse Linux fails Cannot configure deduplication storage server Troubleshooting configuration issuesSelect one of the following options Disk pool wizard does not display a volume Troubleshooting operational issuesVerify that the server has sufficient memory Backup jobs fail Volume state changes to Down when volume is unmounted Errors, delayed response, hangs Viewing disk errors and eventsDeduplication event codes and messages Event # NetBackup Message example Severity 1002 Task session start request on server An unexpected signal Usage of one or more system Troubleshooting Deduplication event codes and messages Preparing for disaster Moving images off-site Recovering from a deduplication storage server disk failure See About the deduplication license key on Information about recovering the master server is available See the NetBackup Troubleshooting Guide Process to recover from a permanent media server failure Process to recover from a permanent media server failure Page 1is a diagram of the storage server components Deduplication server components Separates the file’s metadata from the file’s content Media server deduplication process Component Description Bptm process moves the data to the PureDisk plug-in Deduplication to a PureDisk storage pool Deduplication client backup process Deduplication client components Deduplication client backup process Deduplication client backup to a PureDisk storage pool About deduplication fingerprinting Data removal process Index Page