Re: [Networker] Bootstrap information Timing Quandry

Are you using the -t date option on your nsrck -L 7 command? Seems to me if
you used the date/time stamp from the bootstrap report, it should not seek
to go beyond that.

>> 11/26/2005 11:38:40 PM   full 1971930720    84       0   000559

nsrck -t "11/26/2005 11:38:40 PM" -L 7 <client>

Might just do what you need.

Conrad Macina
Pfizer, Inc.



On Wed, 30 Nov 2005 16:38:18 -0600, Shawn Cox <shawn.cox AT PCCA DOT COM> wrote:

>Thanks so much,  but i'm still a bit stuck.  I think this is a logic
>problem.  The bootstrap information always contains information that there
>are items on the adv_file devices...  Even if it's just the server itself.
>
>It's circular.  If I backup the bootstrap info to disk, how can it ever know
>it's not on disk anymore...  argh.
>
>It seems almost that I'm going to have to backup my networker server
>directly to tape and skip the adv_disk, or use scanner after the fact to
>tell my recovered server where things really are.  That's what is alluded to
>in the DR docs anyway.
>
>If anyone has any suggestions I'm all ears!  Thanks to all.
>
>--Shawn
>
>
>----- Original Message -----
>From: "Davina Treiber" <DavinaTreiber AT PEEVRO.CO DOT UK>
>To: <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
>Sent: Wednesday, November 30, 2005 2:33 PM
>Subject: Re: [Networker] Bootstrap information Timing Quandry
>
>
>> Shawn Cox wrote:
>>> I'm sort of stuck in between phase here with regards to bootstrap
>>> information pre and post stage.
>>>
>>> Quick scenario:
>>>
>>> All Windows Networker.  v7.1.3
>>>
>>> Networker Server has SCSI attached 24 slot 2 drive LTO2 library and 2
>>> 500GB adv_file devices.
>>>
>>> 25 windows clients.
>>>
>>> 6 groups M-Full, Tu-Full, W-Full, Th-Full, F-Full, AM-Incr
>>> clients 1-5 are in M-Full(S,F,I,I,I,I,S)-9pm
>>> clients 6-10 are in Tu-Full(S,I,F,I,I,I,S)-10pm
>>> clients 11-15 are in W-Full(S,I,I,F,I,I,S)-10:30pm
>>> clients 16-20 are in Th-Full(S,I,I,I,F,I,S)-11:00pm
>>> clients 21-25 are in F-Full(S,I,I,I,I,F,S)-11:30pm
>>> all 25 clients are in AM-incr(I,I,I,I,I,I,I)-5:00am
>>>
>>> Legato Server is client #21
>>>
>>> All backups first go to adv_disk devices.  At 4:00pm each day I stage all
>>> savesets on both adv_file devices to tape.
>>>
>>> I get a bootstrap notification each night that looks something like this:
>>>
>>> .
>>> .
>>> .
>>> 11/26/2005 2:20:33 AM   full 3213368017   242       0   000558
>>> 11/26/2005 11:38:40 PM   full 1971930720    84       0   000559
>>> 11/29/2005 12:12:05 AM   full 596373813      0       0   LANDISK.001
>>> 11/29/2005 12:12:05 AM   full 596373813      0       0   LANDISK.001.RO
>>>
>>> A problem has arisen when trying to restore my backup server and its
>>> indexes over in my test sandbox.  I have mminfo'd and recovered from
>>> 000559 the bootstrap information on the server I intend to restore on.
>>> However, upon attempting to nsrck -L7 <client_name> the server asks for
>>> LANDISK.001 to be mounted.  Can't do that in the test sandbox, nor would
>>> I be able to do it in a DR situation.  At the time of attempting to
>>> nsrck -L7 everything had been staged off of disk to 000559, but the
>>> bootstrap information was from before this happened so the new server
>>> doesn't know this yet.
>>>
>>> So, is there a way to get updated bootstrap information after staging
>>> savesets off of disk? Or am I stuck scannering the remainder of 000559 to
>>> tell the restored server where the indexes really are?
>>> Am I making any logical errors here in my backup process?
>>>
>>
>> Yes you can run mminfo -B to give you a new bootstrap report.
>>
>> 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
>> wit 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
>wit 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
wit 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