Re: GO SAVE-Option 21 -- MIDRANGE-L

Sorry, disregard for option 21. End iTera primary, end backup, take 21, start the backup, start the primary.

no... You use mrrendjob command from the production system which 1) suspends the apply jobs on the backup and 2) sends and executes a command (call a program) to perform the backup to tape or other media from the backup system. The primary continues to run, uninterrupted and the backup, even if it's a save-while-active, takes a true point-in-time backup.

On 09/01/2010 05:17 PM, Rhishabh Srivastava wrote:

I have not worked on itera but i just think that it must follow a general
pattern like other HA products

I think we should end the itera application first on production system and
then on backup . even though the other server is not going for maintainance
but its of no use to keep it running. Then once the downtime is over first
start the itera replication on the backup and then on the primary production
so that

I think it can be stopped from itera menu as i have never used it but one of
my friend told me that it can be. May be someone in midrange knows if they
perform role swap for it .

And if QCTL is the only susbsystem remaining then no need to do ENDSBS *ALL
.Go ahead with the option 21.

Rhishabh Srivastava

On Thu, Sep 2, 2010 at 1:13 AM, Darell Wheeler<darellwheeler@xxxxxxxx>wrote:

Thanks Rhishabh.

This server on which I do option 21,is a DR Server.iTera is installed on
this.

Do I need to specifically end iTera on this Backup Server before taking
option 21.?

Also shud I do endsbs *all *immed and then take option 21 once QCTL is the
only sbs remaining?

Thanks
Darell

--- On Wed, 1/9/10, Rhishabh Srivastava<rhishabh@xxxxxxxxx> wrote:

From: Rhishabh Srivastava<rhishabh@xxxxxxxxx>
Subject: Re: GO SAVE-Option 21
To: "Midrange Systems Technical Discussion"<midrange-l@xxxxxxxxxxxx>
Date: Wednesday, 1 September, 2010, 6:10 PM

Though a full checklist is available for V5R4 (

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzaiu/rzaiurzaiu267.htm
)
but its like not all the steps are important . You may want to refer it at
least once.

Option 21 automatically puts the system in restrcited state , but it is
advisable that one should end the system manually to restrcited state so
that if any issues occures while putting it to restrcited state it can be
delt with .

I have faced issues while putting the system in restrcited state when one
of
the ROBOT subsystem did not end . For which i came to know that we should
end the robot netowrk before starting the save. Hence one should end Domino
, Robot , or any network application normally before ending the server.

If any error occurs you will get your control back and if you want to end
it
use System Request Menu ( Attention Key ) ( option 2 to end the request and
option 6 to check message queue)

And as far as media is concerned , you if the density if ULTRIUM3 then you
should *ULTRIUM3
at the DENSITY parameter

Rhishabh Srivastava

On Wed, Sep 1, 2010 at 10:15 PM, Darell Wheeler<darellwheeler@xxxxxxxx

wrote:

Hi,

I have to take he full system backup using GO SAVE option 21.I have to do
this thru the Primary Console.Can you please let me know he following:

1.Once I am on primary console,do I have to do any other thing
apart from taking option 21.

2.Do I have to specifically take ENDSYS or ENDSBS (*ALL) and then do

option

21?

3.Any other precaution I have to take?Will the system automatically come

up

after option 21 excutes fully?

4.I guess opion 21 will not throw me out of the system as I will be

logged

in to QCTL.

5.I also need to initialize an existing tape of Volume ID DX0091 which

has

been used before on the same system.Is the following INZTAP command

correct:

INZTAP DEV(TAP03) NEWVOL(DX0091) CHECK(*NO) DENSITY(*FMT3590E)

I am not sure about the DENSITY parameter.Is the *FMT3590E correct?he

tape

media type which shows is L3 and Media Class is Ultrium3 and device type

is

3580.

Thanks

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