Save set recover from the command prompt

Save set recover:

The save set selection recovery method, or save set recover enables you to recover data without browsing and selecting the files for recovery. Unlike a browsable recovery, a save set recover does not inspect the client file index for information about each selected file. 


When you perform a save set recovery, NetWorker recovers the last full backup first, then recovers incremental backups in the chronological backup order. 

Use a save set recovery in the following scenarios:


• To recover many files or all the data in a save set, for example, if there is a total disk failure. When you perform a save set recovery, you do not select   individual files or directories for recovery.

• To recover data from a recyclable save set. 

• To recover data on a host with limited memory resources. A save set recovery requires less memory than a browsable recovery.




1. Connect to the target host with the root account on UNIX or the Administrator on Windows.

2. Use the mminfo command to display information about the save set of the data that you want to recover.

For example, type: mminfo -av -r volume,savetime,client,ssid,cloneid,name

Output similar to the following appears:

volume            date                 client                 ssid              clone      id name
backup.001 05/03/2015  bu_iddnwserver 3644194209 1362492833  C:\ddlib
clone.001   05/03/2015   bu_iddnwserver 3644194209 1362493448  C:\ddlib

To recover the all the data from a backup save set, type the following command:

recover -S ssid - i_recover_option

where:

-S ssid is the SSID of the backup save set.

-i_recover_option

• iN does not recover the file when a conflict occurs.
• iY overwrites the existing file when a conflict occurs.
• iR renames the file when a conflict occurs. The recover process appends a .R to each recovered file name.


recover -S 3644194209 -iR

To recover the all the data from a clone save set, type the following command:

recover -S ssid/cloneid

*ssid is the SSID of the backup save set.

*clonied is the cloneid of the clone save set.

recover -S 3644194209/1362493448

To recover a single directory from the clone save set and relocate the data to a new directory location, type the following command:

recover -S ssid/cloneid -d destination_dir original_dir


Example : Performing a recover in interactive mode

1. Type: recover

2. To select the files or directories to recover:

a. Specify the directory to browse, for example:

recover> cd /var/adm

b. Select the file or directory for recovery:

recover> add file_name

3. To view the selected files or directory:

recover> list

4. To view the list of the volumes that NetWorker requires to recover the data:

recover> volumes

5. To recover the files to a location that differs from the original location, type:

recover> relocate path

6. To start the recovery operation, type:

recover> recover

7. When the recovery process completes, messages similar to the following appear:

Received 1 file(s) from NSR server `jupiter'

Recover completion time: Tue Jan 21 08:33:04 2009

recover>

8. To close the recover program, type Quit.


Example: Performing a recover in non-interactive mode:
To recover a directory /testdir on client mar

To recover a directory /testdir on client mars to a new directory /newdir on client mars, type:

recover -d /newdir -a /testdir


Example: Save set recover from command line


To recover a directory /testdir from a save set with a ssid of 12345678 and overwrite any existing files with the same name, type this command:

recover -S 12345678 -iY /testdir

Example: Performing a directed recover

To recover a directory c:\mydir that was backed up on client mars to client jupiter, type:


1. On client mars, type:

recover -R jupiter -iY

2. Add the c:\mydir directory:

recover> add c:\mydir

3. Recover the files:

recover> recover

Also check below commands:

recover -a -s NetWorker_servername -c source_host -S ssid/cloneid -d destination_directory -R destination_host -i_recover_option [directory_name]

-a used to perform the recovery in non-interactive mode. You cannot use the -a option with the -R option. You cannot use the -a option to restore 
 Windows SYSTEM or VSS save sets.

-s NetWorker_servername specifies the name of the source client’s NetWorker server.

-c source_host—Specifies the source host.

-S ssid/cloneid used to perform a save set recover.

-d destination_directory

- i_recover_option

• iN does not recover the file when a conflict occurs.
• iY overwrites the existing file when a conflict occurs.
• iR renames the file when a conflict occurs. The recover process appends a .R to each recovered file name.

◆ source_directory—Specifies the initial directory in which to begin browsing.

Note ; Also check below links

<https://community.emc.com/blogs/moinmansuri/2015/11/05/directed-saveset-recovery-command-line>

How to check Avamar node capacity- MSG_ERR_DISKFULL

Last GC: finished Wed Aug 25 01:01:04 2010 after 00m 50s >> recovered 0.00 KB (MSG_ERR_DISKFULL)

The total grid utilization is currently at 88% and I also saw some Unacknowledged Events with the following information:

Code: 4202 Message: failed garbage collection with error MSG_ERR_DISKFULL

This error is a direct result of the garbage collect run limit being reached or exceeded due to excessive checkpoint overhead. To verify and check all of the node capacities use the following commands; also if this is a single node you will not have to use the mapall command.

su – admin

ssh-agent bash

ssh-add ~admin/.ssh/admin_key


mapall –noerror ‘df -h’

This should give you the filesystem for each node including the sizes, used, and space available. Then run:

avmaint nodelist | grep percent-full

This output gives you a true reading of the OS capacity utilization.  On a grid where data nodes use a file pool, the Linux "df" command is not meaningful because the stripes are pre-allocated in the file pool, and many of the stripes might not be in use.

Data Domain Data Invulnerability Architecture Lightboard Video

Deduplication with Data Domain Lightboard Video

Saveset Recover to restore NDMP data with following command

Saveset Recover to restore NDMP data with following command

  nsrndmp_recover  -s <networker_server_name> -c <client_name>  -S <ssid> -v off  -m <hostname::/path_to_recover_to> <path_to be_recovered>

  Where:     -s <networker_server_name> is the hostname of the NetWorker server,

                   -c <client_name> is the client hostname (NDMP server: filer/datamover ) that this data originated from

                 -m option uses for new destination either on the same NDMP server but different directory, or the different NDMP server

                    <hostname::/path_to_recover_to> hostname of the NDMP server (filer/datamover) you are recovering to followed by 2 colons and

                               the full path starting with the mountpoint down to the directory you would like to recover this data to

                   The directory in path-to-recover-to MUST be existence on the host.

                 <path_to_be_recovered> is the full path name starting at the mountpoint down to the directory you would like to restore.

−c client Client is the name of the machine that saved the files. 

−F This option specifies that a file level recovery is going to be performed. This option should only be specified by nwrecover(8) or recover(8). 

−m mount point The mount point of the raw device specified by the -r option. The filesystem will be unmounted for the recover operation and mounted after the operation is complete. 

−r raw device Specifies the pathname of the raw device the data is to be recovered to. This option is mandatory for destructive recovers. 

−s server Selects which NetWorker server to use. 

−S ssid This mandatory option is used to specify save set recover mode. This mode can be used to implement fast batch file recovery without requiring the NetWorker file index entries. Ssid specifies the save set id for the save set to be recovered. NDMP generated save sets cannot be cloned, so no cloneid applies as it does for the standard recover(8) command.

EMC Networker Recovery Command Line

·         Run  the below commands from backup server where client resides.

recover -c "source client name" -R "destination client name" -iR

y - overwrite the file, continue to prompt if more duplicates are found

Y - overwrite the file, do not continue to prompt

n - do not overwrite, continue to prompt

N - do not overwrite the file, do not continue to prompt

r - rename recovered file, continue to prompt

R - rename recovered file, do not continue to prompt

·         If your source and destination is same e.g abc.com

recover -c abc.com -R abc.com -iR

·         If your source and destination diffrent e.g source : abc.com, Destination: xyz.com ( but here you should check server file entry as well as remote host entry)

recover -c abc.com -R xyz.com -iR

·         then go to required save set path with cd command (e.g c:\data\vd\path1)

recover -c abc.com -R abc.com -iR

·         you will get the prompt

recover>cd c

recover>cd data

recover>cd vd

recover>cd path1

·         you can directly go to actual path cd "c:\data\vd\path1"

check the version if you want to browse the old version.

recover>version

·         select version which you want. (e.g 08/30/2015)

recover>changetime 08/30/2015

·         select which file you want to restore or if you restore all files.

recover> add *

·         if you want to restore on original location run command recover

recover> recover

·         if you wan to restore other location

recover> relocate

6479:recover: <return> will recover files into their original location

New destination directory:c:\data\vd\restored

recover> recover

Basic trouble shooting steps

Basic trouble shooting steps:

We have assumed below details for backup server and client name:

abcbackupserver.com=  Backup Server
xyzclient.com =            Client name


On Client:

• Ensure networker client package is installed:

• Ensure networker services are running on client:

• Networker requires that both forward and reverse FQDN resolution is working fine.  Nslookup should be checked from both backup server and client (Both reverse and forward lookup):

         nslookup  abcbackupserver.com
         nslookup  "IP address" {Reverse Lookup}

• Check and update the hosts file entries on the client and backup server if you have DNS issue.

        Unix/Linux : /etc/hosts
        Windows : C:\Windows\System32\drivers\etc

• You should check if your client/backup server can contact each other.

From client :
tracert  or traceroute  abcbackupserver.com


From Backup server:

• ping -a  xyzclient.com
• rpcinfo -p xyzclient.com

    program vers proto   port  service
    100000    2   tcp   7938  portmapper
    100000    2   udp   7938  portmapper
    390436    1   tcp   9842
    390435    1   tcp   9164
    390113    1   tcp   7937  nsrexecd

• Networker requires that both forward and reverse FQDN resolution is working fine.  Nslookup should be checked from both backup server and client (Both reverse and forward lookup):

        nslookup  xyzclient.com
        nslookup  "IP address" {Reverse Lookup}

• If networker client services are running fine even though you are getting failed error like nothing to save or not properly configured, then you should check nslookup as well as below command and check for any canonical name or any aliases name for failed clients. If found, they should be added to the Aliases entry.

        nsradmin -s  xyzclient.com  -p 390113

bash-4.1$ nsradmin -s xyzclient.com  -p 390113
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> p
                        type: NSRLA;
                        name: xyzclient.com ;

• Here you will also get the any virtual or cluster configuration IP associated with failed client in IP address section. If you observed different IP’s, nslookup them and add those in Remote Access entry.

        IP address: x.x.x.x, y.y.y.y, z.z.z.z

• If you are getting connection refused or backup server not present in client server file. Also check your backup server's entry should present in client server file which is located

       Unix: /nsr/res/servers
       Windows: C:\\installation directory\\Legato\\nsr\\res\\ servers

• You should check if your client/backup server can contact each other.

From Backup Server :

• tracert  or traceroute  xyzclient.com  

• If you are getting connection refused or Time out error make sure below port range should open Bi-Directional

• Need to allow bi-directional TCP traffic on ports 7937-9936 to backup data from the Client to the Backup Server

• Need to allow bi-directional TCP traffic on ports 7937-9936 to backup data from the Client to the Storage Node