John,
I have not been through this scenario as you describe but i have had the
power cut to a bank of RVA containing primary DB and LOG volumes.
TSM was able to carry on using the mirror DB and LOG volumes. A message was
displayed saying the primary could not be written top and the miror would be
used. Once the RVA was back up and runing TSM realised that the DB and LOG
volumes were out of synch and resynched them.
If you require any more info drop me a line on the address below.
While i am here has anyone any advice for using mirroring on one ESS 2105
F20?.
Thanks.
Kuli.
Kulbinder Toora
Storage Administrator
Npower
mail to : [EMAIL PROTECTED]
-----Original Message-----
From: John Naylor [mailto:[EMAIL PROTECTED]]
Sent: 21 August 2001 15:13
To: [EMAIL PROTECTED]
Subject: TSM mirroring again
I know this must be a pretty boring subject, but anyone been there ?
This can't be the first time anyone has gone down this road.
Would appreciate your experience
John Naylor
08/16/2001 04:35 PM
Sent by: John Naylor
To: [EMAIL PROTECTED]
cc:
Subject: TSM mirroring
Hi all Tsmers,
I am looking to introduce database/recovery log mirroring into into our
OS390
TSM 3.7.20
environment to cater for cross site disaster recovery.
The thinking is to use our cross site dasd capability to have the primary
database and recovery log volumes written at site1 and the mirror copies
written
at site2 or vice versa.
Then if we lost site1 we would start a new instance of TSM on site2
I will be testing this scenario before going into a live environment, but
from
anyone who
has already been there in a real disaster or disaster test, I have a few
questions.
1) When you come up on site2, does TSM cope ok with the misiing database/log
volumes
2) Are there any gotchas I need to be aware of.
3) Any recommendations for the flavour of mirroring to go with. Are the
defaults
ok?
4) Does mirroring have any significant impact on performance, especially if
you
go with
the non default options
Tia,
John
**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.
Scottish Hydro-Electric and Southern Electric are trading names of
Scottish and Southern Energy Group.
**********************************************************************
================================================================
This incoming e-mail (and any attachments) has been checked at
npower, and has been found to be clean from any
virus infection (using Sophos Sweep 3.48 + patches).
npower Service Desk
(internal telephone 187, external 01384 275454,
or e-mail npower Postmasters [internally]
or [EMAIL PROTECTED] [externally])
================================================================
=====================================================================
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
gpupower.co.uk or [EMAIL PROTECTED]
This outgoing e-mail (and any attachments) has been checked
(using Sophos Sweep 3.48 + patches) before leaving us (UK 08457 353637),
and has been found to be clean from any virus infection.
=====================================================================
