mmrecov nsrck & nsrdr

Recovering critical NetWorker server databases

Protecting a NetWorker server including its critical databases requires careful planning and preparation. The recovery methods described in this section may not work if the NetWorker server is not adequately protected. The databases that are critical to the recovery of a NetWorker server include the bootstrap and the client file indexes.

A bootstrap includes the:

· Media database: Contains the volume location of each save set.

· Resource files: Contains all of the resources, such as NetWorker clients and backup groups, that are defined on the NetWorker server.

The client file indexes include tracking information for each file that belongs to a client’s save sets. There is one client file index for each NetWorker client.

Starting in NetWorker 8.1 there is a command line program named nsrdr that simplifies the recovery of the NetWorker server’s media database, resource files, and client file indexes. Previously, you had to use the mmrecov command to recover the media database and resource files, and the nsrck command to recover client file indexes. These commands are still available.

Use the procedures in this section to recover lost or corrupted bootstrap or client file indexes. If your server databases are not corrupted and you only need to restore expired save set entries into the client file index or the media database, you can use the procedures in Recovering expired save sets. Save sets are removed from the client file index when their browse policy time has expired. Save set entries are removed from the media database when their retention policy time expires.

The nsrdr command is flexible. You can run the nsrdr program in fully interactive mode and respond to questions or you can run the program silently with command line options. You can recover the media database, resource files, and all client file indexes in one operation, or recover just one item by itself. If you are recovering client file indexes, you can also recover the indexes for just one or a small number of NetWorker clients instead of recovering all client file indexes for all clients in one operation.

The following examples depict some co mmon command line usages with the nsrdr

command and its options.

· To recover the bootstrap data and selected client file indexes only:
nsrdr -I client1 client2 client3
where each client name is separated with a space.

· To recover the bootstrap data and selected cl ient file indexes by using an input file:
nsrdr -f pathfile_name -I
where file_name is an ASCII text file with one client name on each line.

· To skip the bootstrap recovery and recover selected client file indexes by using an input file:
nsrdr -c -f pathfile_name -I
where file_name is an ASCII text file with one client name on each line.

· To skip the recovery of bootstrap data and recover all client file indexes:
nsrdr -c –I
To skip the recovery of bootstrap data and recover selected client file indexes:
nsrdr -c -I client1 client2

· To skip the recovery of bootstrap data and recover selected client file indexes from a specified date:
nsrdr -c -t date/time -I client1 client2
where the date/time is the date and/or time from which the client file indexes are recovered. The date/time format is specified in MM/DD/YYYY format or any date and time accepted by the nsr_getdate command.

· To run nsrdr in non-interactive mode and to recover the bootstrap data and all client file indexes:
nsrdr -a -B bootstrap_ID -d device -I

Log Location:

Bootstrap backup on a storage node:
When the server’s bootstrap save set is backed up, the data writes to a device that is local to the NetWorker server. A bootstrap cannot be backed up to a remote device, but a bootstrap can be cloned or staged to a remote device. When the mmrecov command is used to recover a bootstrap save set, the data must be recovered from a local device.

· mmrecov to recover the bootstrap save set.

· To recover the entire media database or an entire CFI, you should use mmrecov and nsrck –L7, respectively. These are discussed in the module, Recovering a NetWorker.

· Before using mmrecovto recover the entire media database, you should attempt to correct the damage using nsrck –m.

· Recovering the bootstrap save set with mmrecov requires that NetWorker be running,, if corrupt resource files cause nsrd to abort during startup, simply remove or rename the /nsr/res directory. When nsrd starts, if /nsr/res does not exist, nsrd will create the same default set of resources that are configured when NetWorker server software is initially installed. After configuring a device resource, you can then use mmrecov to recover a recent backup of the resource directory.

Advertisements

About Ahmad Sabry ElGendi

https://www.linkedin.com/pub/ahmad-elgendi/94/223/559
This entry was posted in E20-597. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s