Start a Conversation

Unsolved

This post is more than 5 years old

N

2900

August 5th, 2015 16:00

Problem with nwrecover on Linux?

I have just set up a new Networker server using Red Hat 6 and Networker 8.2. The backups are running fine for 2 weeks now on over 200 clients...

I wanted to test a recovery from tape to the server and typed "nwrecover" and got the response : Command not found. I searched the system and could not find that command, but all the other nsr and nw commands seem to be in place correctly...

Any suggestions???

2.4K Posts

August 5th, 2015 20:00

You are lucky - you obviously did not need to recover something for a while.

nwrecover is history - I think it has been deleted in the final releases of NW 7.6 ... some years ago.

You can of course use the command line or the NetWorker User GUI (Windows) which now also supports UNIX/Linux clients and run a directed recovery from here.

.

4 Operator

 • 

1.3K Posts

August 6th, 2015 00:00

Tom Conway ,

As Bingo already said nwrecover is history. You Can us the CLI command "recover" instead. Refer tothe NetWorker Command reference guide rOr if you are really lazy you can go to this link http:// www. ipnom. com/Legato-NetWorker-Commands/recover. html

2.4K Posts

August 6th, 2015 00:00

Sorry Nicolino,

you are talking about a different subject ... or it belongs to the wrong post.

August 6th, 2015 00:00

Hi,

in order to rebuild networker backup server & indexes you have to use new "nsrdr" command.

Nsrdr command is nwrecover + nsrck -L7

I suggest/recommend  you to test the backup server bootstrap recvovery in a separate dummy server:  this server must have the same hostname of original backup server and the ability to configure a device mounting volume containing bootstrap backup

In general ,if possible, I suggest to use a dedicated AFTD on backup server for index & bootstrap backup

regards,

-Nicola

August 6th, 2015 01:00

sorry !! I've read wrong ..mmrecover / nwrecover

sorry again

bye

-Nicola

8 Posts

November 4th, 2015 10:00

Hello,

There is no recovery GUI any more is that correct?  Customers are suppose to use a command line recover, are you freaking kidding me. Why would anyone think that is a good idea, I'm the admin and I don't even think that is a good idea.  The GUI was easy and straight forward recovery solution, why get rid of it?

The network has been mostly Windows up to this point now we are adding Linux workstations to the mix and then there is this, wow.

Joe

2 Intern

 • 

14.3K Posts

November 5th, 2015 15:00

In recent NW8 and NW9, you use NMC to run restore.  You can also run it from CLI.  I'm quite sure those Linux folks will prefer CLI.

2 Intern

 • 

147 Posts

November 10th, 2015 02:00

·         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: will recover files into their original location

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

recover> recover

No Events found!

Top