Re: Backup - revisited

Pete:
I agree, but I can picture all kinds of places to go wrong:
What if modified SAV not a dedicated system and files in use.
What if modified SAV not all directories except qsys.lib.
How exactly was system restored to a new box?
What is " a bare system " ? Total reinstall or including OS and products?
How was Websphere put back (if used)
Too many unknowns...

Below is original posting:
Our software package is provided by HBOC. They have a number of commands that
are based on IBM commands, with subtle changes. They differentiate them by
prefacing their versions with a 'B'.

Using their commands, a full save of the system was accomplished with BBACKUP.
This command brings up a number of options. Ultimately, a set of user defined
commands is run. In our case, the commands were: SAVSYS, SAVLIB, SAVDLO, and
SAV, with appropriate options.

I was told that IBM pretty much demanded that Go SAVE option 21 be used instead.

According to the command help, the only commands that appear different are that
the controlling subsystem is ended and restarted. That process was performed
by operators when BBACKUP command was used.

Is there something else that is going on that is different from the scripted
backup? One reason to ask is that the BBACKUP command logs start and stop time
of each step - which is sometimes an issue.

Thanks,

John McKee




----- Original Message ----- From: "Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, September 02, 2008 1:17 PM
Subject: RE: Backup - revisited

Yes, I know its data about data, but if I do 4 commands (SAVSYS, SAVSYS
*NONSYS, SAVDLO, and SAV) vs GO SAVE 21, I can't see any meta data. The
SAVLIB command does have meta data, in that it has on the first file in that
data about if it was a *NONSYS, or a *IBM, or *USRLIB. That is how you know
processing library x of y.

If in your note you say its in the IFS, then you would Save those files
during the SAV command.

I think this guy was covering his tracks because he was unsure of himself.

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Tuesday, September 02, 2008 12:26 PM
To: Midrange Systems Technical Discussion
Subject: Re: Backup - revisited

Metadata - data about data...
http://en.wikipedia.org/wiki/Metadata

I found thru google several software packages storing metadata in the ifs,
and often referenced with java and Websphere.
You've listed all the commands but not the exact parms used.
Plus we have no idea how the restore done.
Since it was to a new system, this could get very complex.
Without a detail of both save and restore options, how could we ever
guess what is going on.
To me this sounds more like an issue of the restore... but that is
(dare I say it) an "assumption"..
Jim
----- Original Message ----- From: "Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, September 02, 2008 11:46 AM
Subject: RE: Backup - revisited

I never heard of metadata in the context of a GO SAVE 21

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Tuesday, September 02, 2008 11:13 AM
To: Midrange Systems Technical Discussion
Subject: Backup - revisited

I apologize for not being able to continue the former thread. Don't have
access
to that email.

Just had a rather testy meeting that included the system administrator.

What I learned does not make a lot of sense to me. Hopefully, somebody
can
clarify this for me:

The SA attempted to restore a backup performed via HBOC BBACKUP command to

a
bare system. The SAV commands used were SAVSYS, SAVLIB *NONSYS, SAVDLO,
and
SAV. He said at the end, it failed. HBe spent several weeks in contact
with
IBM and was told that the individual commands did not include metadata,
required to bring the system back.

When I asked him what that data included, he got defensive and hostile. I
did
point out to the group a page from the infocenter indicating exactly what
was
saved by GO SAVE option 21. The SA then volunteered that even using GO
SAVE
21
did not result in a functioning system, again due to missing metadata.

So, can anybody explain what is missing and how to fix it?

John McKee

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