Re: [Networker] command line recover options?

Yea I did not see that in the posting.


EDWARD COTY

LEAD STORAGE ENGINEER, LCNA, NACP

WORK - 973-533-2098

CELL - 973-296-0918

EDWARD.COTY AT AIG DOT COM


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Goslin, Paul
Sent: Wednesday, June 25, 2008 3:47 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] command line recover options?

The original poster stated that he needed to do this via command line as he has 
to automate this.. So Interactive is not an option...

> -----Original Message-----
> From: EMC NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Coty, Edward
> Sent: Wednesday, June 25, 2008 3:42 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] command line recover options?
>
> Do an interfactive recover.
>
> On the NW server just run recover -s backupservername -c clientserver
>
> The browse time is current. Just Cd to the F Drive. Add * will add all
> sub-directories. Then delete the two directories you do not want to
> recover.
>
> If you are recovering the same drive letter to like. Example F drive
> to F drive then you do not need to relocate the files.
>
> Just type ? At the recover prompt to get some help.
>
>  root@backupserver / # recover -s backupserver -c client
> recover: Current working directory is /
> recover> ?
> Available commands are:
>         add [-q] [filename] - add `filename' to list of files to be
> recovered
>         cd [dir] - change directory to dir
>         changetime [date]  - change the time that you are browsing
>         debug
>         delete [filename] - delete `filename' from the recover list
>         destination - print destination location for recovered files
>         dir [/w] [filename...] - list filename
>         exit - immediately exit program
>         force - overwrite existing files
>         help or `?' - print this list
>         lf [-aAcCdfFgilLqrRsStu1] [filename...] - list filename type
>         list [-c | -l]  - list the files marked for recover
>         ll [-aAcCdfFgilLqrRsStu1] [filename...] - long list filename
>         ls [-aAcCdfFgilLqrRsStu1] [filename...] - list filename
>         noforce - do not overwrite existing files
>         pwd - print current directory
>         quit - immediately exit program
>         recover - recover requested files
>         relocate [dir] - specify new location for recovered files
>         verbose - toggle verbose mode; feedback about what is going on
>         versions [filename] - report on each version of file `filename
>         volumes [filename] - report volumes needed to recover marked
> files `filename' can be either a file or a directory
> recover>
>
>
> EDWARD COTY
>
> LEAD STORAGE ENGINEER, LCNA, NACP
>
> WORK - 973-533-2098
>
> CELL - 973-296-0918
>
> EDWARD.COTY AT AIG DOT COM
>
>
> -----Original Message-----
> From: EMC NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of MIchael Leone
> Sent: Wednesday, June 25, 2008 3:29 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] command line recover options?
>
> "Landwehr, Jerome" <jlandweh AT harris DOT com> wrote on 06/25/2008
> 03:22:34 PM:
>
> > from the man page, it looks like you want this type of command
> >
> > NAME
> >      recover - browse and recover NetWorker files
> >
> > SYNOPSIS
> >      recover [-f] [-n] [-u] [-q] [-i {nNyYrR}]  [-I  input  file]
> >      [-d  destination] [-c client] [-x index-namespace] [-t date]
> >      [ -s server] -a path...
> >
> >
> > so I'd suggest this is what you'd want
> >
> > recover -f -d F: -c OLD -s NWSERVER -a F:
>
> Pretty much what I wrote, then. Good! I was reading it correctly. :-)
>
> >
> >
> > and yes, this will get all subdirectories of the client's F: drive
> >
> >
> > if you wanted to _not_ get some directories, the best you
> could do is
> > specify every path you _do_ want and use the -I option:
> >
> >      -I input file
> >           Takes the paths to recover from the command  line,  and
> >           read  paths  to recover from the named file.  The paths
> >           must be listed one per line.  If no paths are specified
> >           on the command line, then only those paths specified in
> >           the file will be recovered.  To be used in  conjunction
> >           with -a option.
>
> Blech. I have 33 sub-directories, and want only 31. So now I have to
> specify all 31 in a file, instead of something like "-exclude paths".
>
> Thanks for the help.
>
> >
> >
> >
> > cheers
> > Jerry
> >
> >
> > -----Original Message-----
> > From: EMC NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> > On Behalf Of MIchael Leone
> > Sent: Wednesday, June 25, 2008 3:02 PM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: [Networker] command line recover options?
> >
> >
> > NW 7.4.2, on Win2003.
> >
> > I need to do a command line recover (as a scheduled task), and I've
> > always ever used the GUI. What I need if to recover from
> client OLD,
> > drive F:
> > and
> > all sub-directories, to be recovered to the NetWorker
> server, drive F:
> > and
> > all subdirectories.
> >
> > From the NW server, would this do what I want?
> >
> > recover -a -f -s NWSERVER -c OLD F: -d F:
> >
> > Would this restore all the files that were most recently backed up
> > from the client OLD, drive F:, to the NW server, on it's
> drive F:? I'm
> > not seeing (or more likely, not understanding) which option
> to use to
> > tell it that I want the entire contents of F: (i.e, all
> > sub-directories of F:).
> >
> > If I want to exclude 2 specific folders on F: from being restored,
> > where I do that?
> >
> > Thanks. The Command Reference is suspiciously short on examples for
> > this
> >
> > command.
> >
> > --
> > Michael Leone
> > Network Administrator, ISM
> > Philadelphia Housing Authority
> > 2500 Jackson St
> > Philadelphia, PA 19145
> > Tel:  215-684-4180
> > Cell: 215-252-0143
> > <mailto:michael.leone AT pha.phila DOT gov>
> >
> > To sign off this list, send email to
> listserv AT listserv.temple DOT edu and
> > type "signoff networker" in the body of the email. Please write to
> > networker-request AT listserv.temple DOT edu if you have any problems with
> > this list. You can access the archives at
> > http://listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to
> listserv AT listserv.temple DOT edu and type "signoff networker" in the body
> of the email. Please write to networker-request AT listserv.temple DOT edu if
> you have any problems with this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS at
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to
> listserv AT listserv.temple DOT edu and type "signoff networker" in the body
> of the email. Please write to networker-request AT listserv.temple DOT edu if
> you have any problems with this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS at
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or via RSS at 
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER