Hi Dave -

We are not running anything too special for Y2K.
Technically LM is based in Mass and I have not heard anything about a
required "static backup". What exactly does he mean? Full backup?
"Technically" you have that covered. If you are running backups all along
and you run a incremental on 12/31/99 you should be all set.

You'll be all set anyway. I tested ADSM ten ways to Sunday and had no issues
with data backup or recovery. If the data is bad thats tough cookies. All
you can do is put back their non y2k data.

You wouldn't believe some of the hair brained things management here is
doing and thinking of doing.


I can't wait for this to pass so we can get on with our work.

good luck-
CR
__________________________________________________
Cris Robinson
Sr. Technical Analyst
Enterprise Storage Management / TSM (ADSM)
Liberty Mutual Insurance
Portsmouth, New Hampshire
603.431.8400.54837
mailto:cris.robinson AT libertymutual DOT com

        -----Original Message-----
        From:   Sanders, David [SMTP:DSanders AT INTERNAL.MASSMUTUAL DOT COM]
        Sent:   Tuesday, December 07, 1999 9:48 AM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: archive (gotta get it all)

        Hi Andy!

        Thanks for that response, but it seems like there are an awful lot
of
        "gotchas" this late in the game to meet the "one-time" schedule
requirement
        for the mandated Y2K backups.  I guess that you are saying that
there isn't
        an easy, generic, all-inclusive method?

        I guess I will see how your suggestion works and what it builds.

        Dave Sanders
        Sr. Technical Consultant
        MassMutual / The Blue Chip Company
        1295 State St, E060, Springfield, MA 01111
        413-744-5095





        -----Original Message-----
        From: Andy Raibeck [mailto:storman AT US.IBM DOT COM]
        Sent: Tuesday, December 07, 1999 10:12 AM
        To: ADSM-L AT VM.MARIST DOT EDU
        Subject: Re: archive (gotta get it all)


        Hello Dave,

        Couldn't you run something like this:

           SELECT NODE_NAME,FILESPACE_NAME,FILESPACE_TYPE
                  FROM FILESPACES

        Then create a script to read the output and create
        individual DEFINE SCHEDULE and DEFINE ASSOC commands
        for each node and its filespaces? Example schedule
        definition:

           DEFINE SCHEDULE domain Y2KARCHIVE_nodename
                  DESC="Y2K ARCHIVE"
                  ACTION=ARCHIVE OBJECTS="fs1\ fs2\ fs3\"
                  OPTIONS="-SUBDIR=YES -ARCHMC=Y2KMC"
                  STARTDATE=mm/dd/yyyy
                  STARTTIME=hh:mm PERUNITS=ONETIME

           DEFINE ASSOCIATION domain Y2KARCHIVE_nodename
                  nodename

        The lower-case items would be filled in by the script.
        You could use SELECT NODE_NAME,DOMAIN_NAME FROM NODES
        to identify which nodes belong to which domains (unless
        you have only one domain which makes things easier).

        Some complications: If you have clients (especially UNIX)
        that have a large number of filespaces, you might want to
        create multiple schedules, putting a smaller numer of
        filespaces into each schedule.

        If you have any Windows clients where the filespace names
        are still identified by the drive label (pre-3.1.0.5),
        your script can probably determine this by checking the
        first two characters of the filespace name for the "\\"
        characters. If the first two characters are not
        "\\", then you can use the "{LABEL_NAME}\" notation to
        specify the filespace names in the OBJECTS parameter of
        the schedule; otherwise you can use the "\\machname\c$"
        notation to identify the filespaces.

        There would almost certainly be little "gotchas" like
        this to work out, but it should be do-able.

        Regards,

        Andy

        Andy Raibeck
        IBM Storage Systems Division
        ADSM Client Development
        e-mail: storman AT us.ibm DOT com
        "The only dumb question is the one that goes unasked."

        Well, I wish that I could set the record straight (whatever it is).
But, I
        don't have the knowledge to determine the automated archive process
from
        the
        server schedule!!  Help someone?

        Dave Sanders
        Sr. Technical Consultant
        MassMutual / The Blue Chip Company
        1295 State St, E060, Springfield, MA 01111
        413-744-5095





        -----Original Message-----
        From: Remeta, Mark [mailto:MRemeta AT SELIGMANDATA DOT COM]
        Sent: Tuesday, December 07, 1999 8:29 AM
        To: ADSM-L AT VM.MARIST DOT EDU
        Subject: Re: archive (gotta get it all)


        I believe it processes the server options first, then the options in
the
        DSM.OPT file on the client. With include/exclude processing it
processes
        from the bottom to the top. The first match it stops. Correct me if
I'm
        wrong...

        Mark


        -----Original Message-----
        From: Sanders, David [mailto:DSanders AT INTERNAL.MASSMUTUAL DOT COM]
        Sent: Tuesday, December 07, 1999 8:21 AM
        To: ADSM-L AT VM.MARIST DOT EDU
        Subject: Re: archive (gotta get it all)


        Thanks again Betsy for your followup;

        but I think that I'm confused by your response?  My belief is that
running
        the archive function from the centralized schedule doesn't use the
node's
        option file which is where the include/exclude list would be?  Am I
to
        believe that there would be a common include/exclude list that could
be
        used
        from the server end-of-the-pipe to blanket the archive request with
pick
        and
        choose?  If so,, I'm missing that big time??

        Dave Sanders
        Sr. Technical Consultant
        MassMutual / The Blue Chip Company
        1295 State St, E060, Springfield, MA 01111
        413-744-5095





        -----Original Message-----
        From: Moir,Betsy [mailto:betsy.moir AT ABBOTT DOT COM]
        Sent: Tuesday, December 07, 1999 8:16 AM
        To: ADSM-L AT VM.MARIST DOT EDU
        Subject: Re: archive (gotta get it all)


        Instead of using the domain c: d: parameter or  the objects
parameter in
        the
        schedule, have you tried adding the line INCLUDE *:\...\* at the top
of the
        include/exclude list.  This would cause ADSM to backup everything on
any
        locally attached drive, i.e. if they had only a c: drive it would
only back
        that up, but if it had a c: and a d: drive it would back them both
up.




        ADSM-L AT vm.marist DOT edu on 12/07/99 05:59:10 AM
        Please respond to ADSM-L AT vm.marist DOT edu @ INTERNET
        To: ADSM-L AT vm.marist DOT edu @ INTERNET
        cc:
        Subject: Re: archive (gotta get it all)

        Betsy, thanks for that suggestion.  But, I don't seem to be able to
do this
        from my serve using the automated schedular.  I'm looking to do a
generic
        backup for all platforms with a customized 1-time schedule.  I've
seen
        references that say that to include "all stuff" you may have to
create
        seperate schedules for each platform.  I was willing to do that but,
I
        can't
        even get the Win95 one to "get it all".

        If I use "domain c: d:", that will work fine except for those
workstations
        that don't have a "d" drive.  So it gets marked as failed and then
will try
        to rerun and will redo the c: drive data over again.

        It looks like I will have to go thru the filespaces and have
seperate
        schedules for those that have "c only" drives and another one for "c
& d"?

        BTW: we do realize how much potential data we will be pumping over
the
        network.  It's been raised as an issue and we are trying to
determine how
        we
        can ask our clients to stop processing for the length of time that
we need
        to do their quiesced backup.  Two opposing forces:  the client's
need for
        processing their data as normal (maybe more so before the Y2K
rollover) vs.
        the Insurance Commisioner request.

        Dave Sanders
        Sr. Technical Consultant
        MassMutual / The Blue Chip Company
        1295 State St, E060, Springfield, MA 01111
        413-744-5095





        -----Original Message-----
        From: Moir,Betsy [mailto:betsy.moir AT ABBOTT DOT COM]
        Sent: Monday, December 06, 1999 3:18 PM
        To: ADSM-L AT VM.MARIST DOT EDU
        Subject: archive (gotta get it all)


        I can help you with a couple of these things.

        We do a yearly archive on 10 CADD servers in our company.  They're
NT
        servers
        and our ADSM server is on the VM mainframe.

        Because they're NT servers, we can run the archive as an NT service.
We
        use
        the DSMCUTIL command to create a separate NT service for the yearly
backup.
        We created a separate management class for the yearly archives and
at the
        top
        of all our EXCLUDE  statements in the options file we have an
INCLUDE
        statement which reads:

        INCLUDE *:\...\* CEDCADY

        Keep in mind, though, that depending on how many machines you're
backing
        up,
        this can be a huge amount of data going across your network at a
possibly
        very busy time of year.  If your major concern is not losing data,
I'd make
        the extra effort to get exclude statements in there for anything and
        everything you don't need to archive.

        where CEDCADY is the name of the management class for the yearly
archive.

        If you're not backing up NT servers, then you'd have to initiate
another
        scheduled session with ADSM or use whatever other scheduler you're
using.

        Hope this helps
        ---------------------- Forwarded by Betsy Moir/LAKE/CHMS/ABBOTT on
12/06/99
        02:04 PM ---------------------------


        Michael A Cernak
        12/06/99 01:51 PM
        To: Betsy Moir/LAKE/CHMS/ABBOTT@ABBOTT
        cc:
        Subject: archive (gotta get it all)

        Betsy, do you think our experience with CED archives would help this
guy?
        It
        also sounds like he doesn't comprehend the magnitude of the task due
to
        volume of data.
        ---------------------- Forwarded by Michael A
Cernak/LAKE/CHMS/ABBOTT on
        99-12-06 01:49 PM ---------------------------


        ADSM-L AT vm.marist DOT edu on 99-12-05 06:45:40 AM
        Please respond to ADSM-L AT vm.marist DOT edu @ INTERNET
        To: ADSM-L AT vm.marist DOT edu @ INTERNET
        cc:
        Subject: archive (gotta get it all)

        We have been told that the Insurance Commisioner in our state (MA),
has
        informed us insurance companies that we need to have "static backups
of
        vital records" at the Y2K rollover.

        I'm trying to set up a special scheduled archive run for all
participating
        client nodes (we are mainframe-based server).  I'm wondering if
anyone has
        tried and true "objects" all-inclusive for a scheduled task that
will get
        it
        all (  maybe  *:*   ?)

        I'm wondering what other companies are doing in this regards?

        Dave Sanders
        Sr. Technical Consultant
        MassMutual / The Blue Chip Company
        1295 State St, E060, Springfield, MA 01111
        413-744-5095