Clone using LUN Copy
Posted in 2016
Topics: High Availability & Replication, Storage & Space Management, Server Administration, Versions, Editions & End-of-Life
Hi All,
We have IDS - Informix Dynamic Server Version 12.10.FC5W1XZ, configure with
SDS Node. We need to do Clone of the both node to Staging Environment. IBM
Support Executive has configured some LUN Copy Cloning Method, which is not
working Currently. I need some help around.
Overview of the Steps to be taken is as below.
    Shutdown Application and Shutdown
databases on Both node. First it should be on 02 and then 01
    Give Server to Server Team.
    They will take LUN offline and
Delete them and Copy Production LUN and Rename it to Staging LUN
    Server will be handed over to DBA.
    Need to start Database and run
Clean up Script.
    Run Cleanup Script Provided by
IBM Support for cleaning Production related entries from the database.
After Copying all Information from Production LUN to Staing LUN we are not
able to start the database using oninit -vy. IBM Support is not giving proper
support on the same.
What should we do? Is there any way where we can restore the Database using
Chunk Copy to some other Server and Open the Database.
I am very much new to Informix.
Regards
Chintan Bhatt
Chintan:
To be able to clone a server this way, first you have to make sure that all
of the chunk paths on the target system that you are restoring to are the
same as those on the source system. Then you have to have the identical
version of Informix installed there. Finally, you have to have a copy of
the ONCONFIG file and sqlhosts file with critical identifying settings
changed. The ONCONFIG parameters that MUST be changed are:
DBSERVERNAMEDBERVERALIASES
HA_ALIASUpdate any explicit paths in the file that have changed (ex: if you
installed INFORMIXDIR in a different location than on the source).
The following parameters MUST be identical to the ONCONFIG file on the
source system (so it is best to start with a copy):
LOGS
ROOTPATHMIRROR
MIRRORPATH
MIRROROFFSET
PHYSFILE
LOGFILES
DBSPACETEMP
Oh, and the target has to be the same hardware platform and OS. Read the
Backup and Restore Guide (or the Information Center pages) section on "Data
restored in an external restore"
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.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 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 Fri, Dec 9, 2016 at 4:41 AM, CHINTAN BHATT <css.bhatt@gmail.com> wrote:
> Hi All,
>
> We have IDS - Informix Dynamic Server Version 12.10.FC5W1XZ, configure with
> SDS Node. We need to do Clone of the both node to Staging Environment. IBM
> Support Executive has configured some LUN Copy Cloning Method, which is not
> working Currently. I need some help around.
>
> Overview of the Steps to be taken is as below.
>
>     Shutdown Application and
> Shutdown
> databases on Both node. First it should be on 02 and then 01
>     Give Server to Server Team.
>     They will take LUN offline and
> Delete them and Copy Production LUN and Rename it to Staging LUN
>     Server will be handed over to
> DBA.
>     Need to start Database and run
> Clean up Script.
>     Run Cleanup Script Provided by
> IBM Support for cleaning Production related entries from the database.
>
> After Copying all Information from Production LUN to Staing LUN we are not
> able to start the database using oninit -vy. IBM Support is not giving
> proper
> support on the same.
>
> What should we do? Is there any way where we can restore the Database using
> Chunk Copy to some other Server and Open the Database.
>
> I am very much new to Informix.
>
> Regards
> Chintan Bhatt
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--089e0117610fc479370543381692
The PMR you're referring has already a long history with some reports of
$ONCONFIG vs reserved pages differences.
It would be wrong and inefficient to try to provide parallel help here.
Sounds like something in the process is not right or has not been done
right or didn't complete correctly.
The analysis being done by support is you best bet.
Regards.
On Fri, Dec 9, 2016 at 9:41 AM, CHINTAN BHATT <css.bhatt@gmail.com> wrote:
> Hi All,
>
> We have IDS - Informix Dynamic Server Version 12.10.FC5W1XZ, configure with
> SDS Node. We need to do Clone of the both node to Staging Environment. IBM
> Support Executive has configured some LUN Copy Cloning Method, which is not
> working Currently. I need some help around.
>
> Overview of the Steps to be taken is as below.
>
>     Shutdown Application and
> Shutdown
> databases on Both node. First it should be on 02 and then 01
>     Give Server to Server Team.
>     They will take LUN offline and
> Delete them and Copy Production LUN and Rename it to Staging LUN
>     Server will be handed over to
> DBA.
>     Need to start Database and run
> Clean up Script.
>     Run Cleanup Script Provided by
> IBM Support for cleaning Production related entries from the database.
>
> After Copying all Information from Production LUN to Staing LUN we are not
> able to start the database using oninit -vy. IBM Support is not giving
> proper
> support on the same.
>
> What should we do? Is there any way where we can restore the Database using
> Chunk Copy to some other Server and Open the Database.
>
> I am very much new to Informix.
>
> Regards
> Chintan Bhatt
>
>
> ************************************************************
> *******************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
--001a113fbb5ab791c10543387cb1