Re: Disaster Recovery test scenario

Nope - after we restore USRPRFs and CFG, we would restore the DISASTER 
library (first library on the nightly backup) and run DISASTER/RESTORE 
(which mirrors our nightly save job except uses RSTLIB rather than SAVLIB) 
using the same file containing the libraries that are backed up on a nightly 
basis (including QUSRSYS and QGPL) . . .

The reason for this is that we have one **huge** data warehouse-type library 
plus many, many historical libraries (which are kept on the system for 
instant-access purposes) that we don't want to waste time restoring from our 
SAVE 21 tape (especially at a recovery center where we're burning contract 
hours for testing . . .)

Steve

<rob@xxxxxxxxx> wrote in message 
news:OFA31BEF53.1EFD423D-ON052570D9.007330F4-052570D9.00733B78@xxxxxxxxxxxx
> What, no RSTLIB *NONSYS step at all?
>
> Rob Berendt
> -- 
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Steve McKay" <mckays@xxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 12/16/2005 03:32 PM
> Please respond to
> Midrange Systems Technical Discussion 
> <midrange-l@xxxxxxxxxxxx>
>
>
> To
> midrange-l@xxxxxxxxxxxx
> cc
>
> Fax to
>
> Subject
> Re: Disaster Recovery test scenario
>
>
>
>
>
>
> I appreciate all of the discussion of journaling and PF/LF restore issues
> but am surprised that no one has commented on the DISASTER library and my
> wish to restore only libraries on the daily backup tape rather than
> libraries on the save 21 tape.
>
> Keep those comments coming  . . .
>
> Steve
>
> <ChadB@xxxxxxxxxxxxxxxxxxxx> wrote in message
> news:OF1003838E.DCD18183-ON852570D8.006F707C-852570D8.006F70D1@xxxxxxxxxxxxxxxxxxxxxx
> .
>
> Without analyzing each step, at a quick glance i'm surprised that I don't
> see any journal oriented recovery steps to get more up to the minute
> recovery results after you restore from your nightly save.  I've never
> worked for someone with a DR site, but i'm thinking that if that expense
> was to be undertaken, you'd probably want to get into some journaling to
> better protect your data.  I can't imagine trying to reproduce a day's
> work
> accurately for even a single department  (heck... even for a user!).
> Journaling gives a lot of bank for the buck...
>
>
>             "Steve McKay"
>             <mckays@xxxxxxxxx
>             om>                                                        To
>             Sent by:
> midrange-l@xxxxxxxxxxxx
>             midrange-l-bounce                                          cc
>             s@xxxxxxxxxxxx
>                                                                   Subject
>                                       Disaster Recovery test scenario
>             12/15/2005 03:06
>             PM
>
>
>             Please respond to
>             Midrange Systems
>                 Technical
>                Discussion
>             <midrange-l@midra
>                 nge.com>
>
>
>
>
>
>
> List -
>
> We will soon do our first-ever disaster recovery test.  I anticipate that
> we
> will be given a 'clean' machine when we walk into the DR site.  Is this an
> accurate series of events?
>
> Restricted State:
> - Load OS/400 and LIC (from save 21 tape)
> - RSTUSRPRF *ALL (from nightly save)
> - RSTCFG *ALL (from nightly save)
> - RSTLIB DISASTER (from nightly save)
>    Note: We have a library called DISASTER which contains a 'restore'
> version of our nightly
>   'save' and a copy of the file containing the names of libraries saved
> in
>
> the nightly save - QGPL
>   and QUSRSYS are included in the file but not all libraries on the
> system.
> - Run DISASTER/RESTORE program to restore libraries from nightly save
> - RSTDLO DLO(*ALL) SAVFLR(*ANY)
> - RST DEV('/QSYS.LIB/your tape drive.DEVD')
>       OBJ(('/*') ('/QSYS.LIB' *OMIT) ('/QDLS' *OMIT))
> - RSTAUT
>
> Questions:
> How do you feel about the idea of having a DISASTER library with a RESTORE
> program?
> What problems would you foresee?
> Will the process work as written above?
>
> Thanks,
>
> Steve
>
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> _____________________________________________________________________________
>
> Scanned by IBM Email Security Management Services powered by MessageLabs.
> For more information please visit http://www.ers.ibm.com
> _____________________________________________________________________________
>
>
> ForwardSourceID:NT000359E6
>
> _____________________________________________________________________________
> Scanned by IBM Email Security Management Services powered by MessageLabs.
> For more information please visit http://www.ers.ibm.com
> _____________________________________________________________________________
>
>
> --------------------------------------------------------------------------------
>
>
>> -- 
>> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>> list
>> To post a message email:
>> MIDRANGE-L@xxxxxxxxxxxx
>> To subscribe, unsubscribe, or change list options,
>> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>> or email: MIDRANGE-L-request@xxxxxxxxxxxx
>> Before posting, please take a moment to review the archives
>> at http://archive.midrange.com/midrange-l.
>>
>>
>
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
> list
> To post a message email: 
> MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>