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?
