Disaster Recovery testing and HDR
Posted in 2011
Topics: High Availability & Replication, Server Administration, Platform-Specific Issues
The production Informix instance and the disaster recovery (DR) instance are a
HDR pair. The DR is a read-only secondary. We have a significant disaster test
coming up shortly and I would like to break the HDR link and bring the DR
instance up as a stand-alone read-write server. What are the steps to do this?
Here is what I know and have tested. I switch the production (Primary) to be a
Standard server. Then I shutdown the DR(secondary) and restart it, it comes up
as Read-Only (sec). I would like it to be 'OnLine' like the primary
(production) server and not 'Read-Only'. So do I do 'onmode -d standard' on
the DR instance?
(IDS 11.50.FC5 on HP-UX ia64).
Yes, onmode -d standard. You don't have to shutdown the secondary to do
that. After to restore the replication you will have to restore an archive
from the server you want to keep to the other machine with ontape -r (or the
onbar equivalent) and reestablish replication. Once replication is
reestablished, you can reverse the relationship if needed using the
hdrmkpri.sh and hdrmksec.sh to make a server primary or secondary
respectively.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Tue, Oct 4, 2011 at 9:55 AM, MURALI PAZHAYANNUR <pmurali@ftportfolios.com
> wrote:
> The production Informix instance and the disaster recovery (DR) instance
> are a
> HDR pair. The DR is a read-only secondary. We have a significant disaster
> test
> coming up shortly and I would like to break the HDR link and bring the DR
> instance up as a stand-alone read-write server. What are the steps to do
> this?
>
> Here is what I know and have tested. I switch the production (Primary) to
> be a
> Standard server. Then I shutdown the DR(secondary) and restart it, it comes
> up
> as Read-Only (sec). I would like it to be 'OnLine' like the primary
> (production) server and not 'Read-Only'. So do I do 'onmode -d standard' on
> the DR instance?
> (IDS 11.50.FC5 on HP-UX ia64).
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--90e6ba1efb28fb252d04ae7a1341
Does it matter if I do 'ontape -r' or 'ontape -p'. I have always used 'ontape
-p' since I thought 'ontape -r' did physical and logical restore. Please
clarify.
Also, I remember reading somewhere that the scripts you reference were being
deprecated. Should I be still using them?
Ontape -p is correct. I hadn't had my coffee yet ;-(
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Tue, Oct 4, 2011 at 11:45 AM, MURALI PAZHAYANNUR <
pmurali@ftportfolios.com> wrote:
> Does it matter if I do 'ontape -r' or 'ontape -p'. I have always used
> 'ontape
> -p' since I thought 'ontape -r' did physical and logical restore. Please
> clarify.
>
> Also, I remember reading somewhere that the scripts you reference were
> being
> deprecated. Should I be still using them?
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--bcaec52e5fa326b10404ae7b5a77