Kenneth,
That's pretty interesting, your saving the file index literally and not
through the savegrp -O command. For a restore then (saveset recover),
or browsable recover there should appear versions of the
\program files\nsr\index saveset.
Seems like a good saveset to have around for DR.. the \program
files\nsr\index\backupserver will be no good though because it will be
written to during the save?
For disaster recovering then one could do a :
mmrecov (with latest bootstrap)
nsrck -L 7 -t latest bootstrap -c backup server (if one has the index
savest..so one can browse)
browse and recover the \program files\nsr\index directory minus the backup
server itself. The backup server index in this saveset is not good.
So you'll need at least the backup server index saved via savegroup -0.
Robert Maiello
Thomson Healthcare
On Fri, 19 Sep 2003 14:52:17 +0200, Kenneth Larsen
<Kenneth.Larsen AT STERIA DOT DK> wrote:
>Run a script to backup the indexes seperatly after your normal backup.
>this way you can restore the indexes to the recover server and do file
>restores
>I use the perl script below to save my indexes seperatly and networker
>will never know the difference.
>The script is made on windows, but should be easy to convert til other
>platforms that can run perl.
>
>#!c:/perl/bin/perl.exe
>system"savegrp \-I \Incremental";
>opendir(INDEX,"x:/program files/nsr/index") || die |"Cannot read index
>dir\n";
>while ($client_name = readdir(INDEX)) {
> if ($client_name eq ".") {next;}
> if ($client_name eq "..") {next;}
> print "***** Saving index for client $client_name\n";
> system"save \-i -b \"INSERT POOL HEREl\" \-l Full -y \"3 months\"
>-w \"3 months\" \-s SERVER \"x:/program files/nsr/index/$client_name\" >>
>e:/logs/saveindx.txt 2>&1";
>} # end of while
>
>I am not sure purging the indexes for these DR media can be done easily,
>but you could try to delete the DR media and see what impact it has on
>your indexes.
>
>Or you could change your normal schedule to run more full backups, Yeah I
>know it will cost more tapes, and then clone them for DR purposes.
>
>
>
>**************************************************
>Med venlig hilsen / Regards
>Kenneth Larsen
>Steria
>Tonsbakken 16-18
>2740 Skovlunde
>kel AT steria DOT dk - 44506261 - 26306261
>**************************************************
>
>
>
>
>Monit Kapoor <mkapoor AT CADENCE DOT COM>
>Sent by: Legato NetWorker discussion <NETWORKER AT LISTMAIL.TEMPLE DOT EDU>
>19-09-2003 07:27
>Please respond to Monit Kapoor
>
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> cc:
> Subject: [Networker] Question on Index Backup and Expiry
>
>
>Hello everyone,
>
>I need advice on the following ?
>
>I have a couple of critical client's ( approx 100 ) on my backup server
>which are
>backed full once a Month and incr other days, with Saturday and Sunday
>as skip.
>Now as part of the DR readiness program, i am supposed to perform a
> Full backup each
>weekend for these systems on to a seperate Tape pool.Here's how i have
>setup:
>
>1. I run the weekend full backups without index saves.The Bootstrap is
>also backed to this Tape
> pool to assist in recovery at remote site.However indexes are not
>backed because if i
> create indexes for each weekend run, then i end up screwing my
>regular incr
> backups as on monday they'll end up using each Sunday's (level 0)
>indexes for finding and backing
> changed files.
>
>Now Since I dont create any indexes for this DR run , i am unable to
>perofrm file-by-file browsing
>for recoveries without having to scan all tapes.
>
>What i need help on:
>
>1. Is there any way i could create these Indexes for Weekend Backup and
>backup this run's indexes
> to this DR tape pool only ?
>
>2. Once this activity has been done ,can i purge the local disk index
>by defining a very short expiry period
> ( 0 or 1 day, i am not sure ) befor next run for these clients ?
>
>Appreciate any assistance from you folks.
>
>Rgds,
>
>Monit
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>
>--
>Note: To sign off this list, send a "signoff networker" command via email
>to listserv AT listmail.temple DOT edu or visit the list's Web site at
>http://listmail.temple.edu/archives/networker.html where you can
>also view and post messages to the list.
>=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
