RE: Backup question

Actually, HBOC has made significant changes in the past few years resulting in
only a small downtime window. But, there will always be people who will want
100 percent availability - no matter the cost - as long as somebody else pays
for it.

John McKee

Quoting Pete Massiello <pmassiello-ml@xxxxxxxxxxxx>:

Have you looked at Save While Active to reduce the window, or a High
Availability product and do target side backups on the 2nd machine
(expensive, but what is the cost of not being available for your users).

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Tuesday, August 26, 2008 12:02 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Backup question

The reason it is sometimes an issue is that there are people who want
the system
to be available all the time, or at least know when it was not for planned
maintenance. When the system is unavailable, manual processes are used.
And,
the manual processes effect other systems that would normally get data via
interfaces.

John McKee

Quoting Jim Franz <franz400@xxxxxxxxxxxx>:

a further note:
<quote>
When using this command, it is important to use the device on the
system that is defined as the initial program load (IPL) device...

also, what did you mean by this:

One reason to ask is that the BBACKUP command logs start and stop time of
each step - which is sometimes an issue.

What issue?

Jim Franz



----- Original Message -----
From: "Jim Franz" <franz400@xxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, August 26, 2008 11:17 AM
Subject: Re: Backup question

This is from the V5R4 Help text for Save 21:

Runs the following commands:
ENDSBS SBS(*ALL) OPTION(*IMMED)
SAVSYS
SAVLIB LIB(*NONSYS) ACCPTH(*YES)
SAVDLO DLO(*ALL) FLR(*ANY)
SAV OBJ(('/*') ('/QSYS.LIB' *OMIT)
('/QDLS' *OMIT)) UPDHST(*YES)
STRSBS SBSD(controlling-subsystem)


The SAVSYS help text notes this:
The Save System (SAVSYS) command saves a copy of the Licensed
Internal Code and the QSYS library in a format compatible with the
installation of the operating system. It does not save objects from
any other library. In addition, it saves security and configuration
objects that can also be saved using the Save Security Data
(SAVSECDTA) and Save Configuration (SAVCFG) commands.

hth
Jim Franz


----- Original Message -----
From: "John McKee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, August 26, 2008 10:00 AM
Subject: Backup question

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

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