RE: Back up questions

["Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>]

I am hoping to go to common next year.

-----Original Message-----
From: Paul Nelson [mailto:pnelson@xxxxxxxxxx]
Sent: Thursday, April 03, 2003 2:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: Back up questions


About the tape issue? I doubt it. A lot has come from the school of been
there, done that. :-)) A lot more has come from attending COMMON, and
hearing other people's BTDT stories. I recall that you mentioned that you're
new to the platform. Do whatever you can to get you boss to send you to
COMMON. It's worth the money, cuz you'll come home with knowledge that you
can use immediately to get your ROI.

Paul Nelson
Arbor Solutions, Inc.
708-670-6978 Cell
708-923-7354 Home
pnelson@xxxxxxxxxx

----- Original Message -----
From: "Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, April 03, 2003 1:40 PM
Subject: RE: Back up questions


> Is this all info in the back up manual?
>
> -----Original Message-----
> From: Paul Nelson [mailto:pnelson@xxxxxxxxxx]
> Sent: Thursday, April 03, 2003 1:20 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Back up questions
>
>
> An old time IBM'er once told me that the INZTAP command did an extra
erasure
> function prior to writing the label info, plus there is some extra
> tensioning that takes place. I've had more than a couple of tapes break on
> me at client sites where I've walked in behind this one particular
software
> company's "system setup expert". One of the first things I do for these
> clients is to throw out the software company's backup routine and to set
the
> client up with a backup utility that really works. Sorta helps to follow
the
> rules in the chart about backing up the right stuff. :-))
>
> The IBM'er in question is now retired, but considering I once watched him
> manufacture a jumper for a S/38 circuit board from a paper clip, I pretty
> much have followed his "gospel rules".
>
> Paul Nelson
> Arbor Solutions, Inc.
> 708-670-6978 Cell
> 708-923-7354 Home
> pnelson@xxxxxxxxxx
>
> ----- Original Message -----
> From: <rob@xxxxxxxxx>
> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
> Sent: Thursday, April 03, 2003 9:57 AM
> Subject: Re: Back up questions
>
>
> > Paul,
> >
> > Why does an INZTAP weaken the tape more than writing a backup to it?
> >
> > Rob Berendt
> > --
> > "They that can give up essential liberty to obtain a little temporary
> > safety deserve neither liberty nor safety."
> > Benjamin Franklin
> >
> >
> >
> >
> > "Paul Nelson" <pnelson@xxxxxxxxxx>
> > Sent by: midrange-l-bounces@xxxxxxxxxxxx
> > 04/02/2003 06:18 PM
> > Please respond to Midrange Systems Technical Discussion
> >
> >         To:     "Midrange Systems Technical Discussion"
> > <midrange-l@xxxxxxxxxxxx>
> >         cc:
> >         Fax to:
> >         Subject:        Re: Back up questions
> >
> >
> > If you've got the DASD available, look into having a library containing
a
> > save file named for each library you want to back up. Don't forget the
IFS
> > stuff, the configuration objects and the security data. Save the
libraries
> > and the other objects into those save files, and then you can save this
> > one
> > "backup" library onto tape at your convenience, since you can bring the
> > system back up before the tape activity begins.
> >
> > Also, do NOT reinitialize the tape every day. This will weaken the first
X
> > inches of your tape (been there, done that). Add a reply list entry for
> > the
> > message indicating that the tape has stuff on it. The appropriate
response
> > is I for ignore. The SAVLIB will happily write over what was there from
a
> > previous backup.
> >
> > Paul Nelson
> > Arbor Solutions, Inc.
> > 708-670-6978 Cell
> > 708-923-7354 Home
> > pnelson@xxxxxxxxxx
> > _______________________________________________
> > 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.
>

_______________________________________________
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.