× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes. Option 21 saves it all (except spool data...)

Under GO SAVE, option 8 is savsecdata and option 10 is savcfg. But these
are included in options 21 and 22.

Chris Whisonant
Comporium
Senior Mid-Range Systems Administrator
IBM Certified Specialist
(803) 326-7270
mailto:chris.whisonant@comporium.com



                      Rick Rayburn
                      <the400man@hotmai        To:       midrange-l@midrange.com
                      l.com>                   cc:
                      Sent by:                 Subject:  RE: "Go Save" backup 
question
                      CWHISONANT@InfoAv
                      e.Net


                      10/16/2002 03:05
                      PM
                      Please respond to
                      midrange-l






Thanks Andy -

Does the Savsys portion of option #21 INCLUDE savsecdata and savcfg? If
not.
are those commands included ANYWHERE within go save? As a duo?


>From: "Andy Nolen-Parkhouse" <aparkhouse@attbi.com>
>Reply-To: midrange-l@midrange.com
>To: <midrange-l@midrange.com>
>Subject: RE: "Go Save" backup question
>Date: Wed, 16 Oct 2002 09:30:48 -0400
>
>Rick,
>
>Here are the save commands executed by Option 21:
>
>SAVSYS
>SAVLIB LIB(*NONSYS)
>SAVDLO DLO(*ALL) FLR(*ANY)
>SAV DEV('/QSYS.LIB/media-device-name.DEVD') +
>    OBJ(('/*') ('/QSYS.LIB' *OMIT) +
>    ('/QDLS' *OMIT))1 UPDHST(*YES)
>
>Here's Option 42:
>
>SAVLIB LIB(*ALLUSR)
>
>My first reaction to your strategy is that you may have some *nonsys
>stuff in either the DLO or the non-QSYS portions of the IFS.  If this is
>the case, you should look closely at what you do; you may not be saving
>some fairly dynamic user objects.
>
>For disaster recovery purposes you should have (at a minimum) a savsys
>tape which coincides with the application of cumulative PTF's.  This
>will include your security information, user profiles, and configuration
>objects.
>
>Perhaps the most pertinent question for someone in your position to ask
>is "Do you have the opportunity to perform an option 21 save on a
>regular and automated basis?"  If you need to maintain close to 24x7
>availability, then a dedicated save becomes something to be negotiated
>with the user community.  If you have an automated tape library (or if
>your system will fit on one tape) and if you have the ability to
>dedicate your system for the duration of an option 21 save, then do it.
>You can use some programming to schedule the execution and you'll sleep
>better knowing that you have everything on one backup.
>
>Here are some questions that might be helpful in designing a backup
>strategy:
>
>If you were to come into work tomorrow and find the system dark and your
>storage trashed, do you have a plan for what you will do after your
>Customer Engineer repairs the system?  Do you know where the tapes are
>and the proper sequence to load them to bring your entire system back as
>it was before the most recent backup?
>
>Can you backup your entire system without manual changing of tapes?
>
>Can you take the entire system down periodically for a long save?
>
>Do your users use file systems other than QSYS?
>
>What is your reasoning for wanting to keep system stuff segregated from
>application-related data?
>
>You would not necessarily do a complete backup every night, or even
>weekly.  Some of the functions performed by the SAVSYS portion of the
>option 21 save can be done using the SAVSECDTA (Save Security Data) and
>SAVCFG (Save Configuration) commands without dedicating the system.
>These could be incorporated into your nightly saves.
>
>Regards,
>Andy Nolen-Parkhouse
>
>
>
>
> > On Behalf Of Rick Rayburn
> > Subject: "Go Save" backup question
> >
> >
> > Currently, we are using option 42 from the "Go Save" menu to complete
>our
> > *nonsys* backup requirements.
> >
> > What should we use to backup our "system" data...user profiles, object
> > authorities, device configurations, qsys...etc.
> > I've heard option #21 backs "the world up", but we would rather have
>the
> > system stuff segregated on a separate tape from the application -
>related
> > data.
> >
> > Thanks for your time and help.
> >
> > Rick Rayburn
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.


_________________________________________________________________
Surf the Web without missing calls! Get MSN Broadband.
http://resourcecenter.msn.com/access/plans/freeactivation.asp

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.








As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.