Moving data between instances
A user on IDS 9.4 / HP-UX 11.23 copied data between two machines via ontape, but was consolidating onto a single machine and needed a way to replicate between two instances on the same box (static for 10 days, then resynced). Replies suggested ontape's rename option: 'ontape -r -rename -f <chunklist>' with a file mapping old chunk paths/offsets to new ones, noting the target chunks/dbspaces must be the same size and the restore fixes ROOTPATH automatically. Art Kagel also suggested ER, pausing replication during month-end and resyncing after; resync only replays online logical logs, automated in IDS 10.00UC5, but doable manually in 9.4 with scripts (pointing to Madison Pruett's IIUG/IDUG papers M09/M11).
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
I was hoping I could get some advice. We currently
have 2 machines and when we need to replicate the data
we move an ontape from one to the other. All paths
are the same and this works fine. We're moving to one
machine and we still need to figure out a way of
moving the data from one to the other.
We will need the data static for the first 10 days of
the mont and then have it more or less in sync
(doesn't need to be immediate). Anyone have any
suggestions or thoughts on this?
Thanks
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
Hej ! Jag har semester och är åter den 18/7 I am on vacation and will be back on 7/18
IDS 9.4. Let's you do a full restore with renaming of devices. It's
great for creating multiple instances on the same server or where you
can't use the same device names.
Version of IDS? OS?
Bob Roussey
Unix / Informix Administration
Spirit Airlines
Robert.Roussey@SpiritAir.com
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of
Radhe Webster
Sent: Thursday, June 22, 2006 12:04 PM
To: ids@iiug.org
Subject: Moving data between instances [7027]
I was hoping I could get some advice. We currently
have 2 machines and when we need to replicate the data
we move an ontape from one to the other. All paths
are the same and this works fine. We're moving to one
machine and we still need to figure out a way of
moving the data from one to the other.
We will need the data static for the first 10 days of
the mont and then have it more or less in sync
(doesn't need to be immediate). Anyone have any
suggestions or thoughts on this?
Thanks
Any society that would give up a little liberty to gain a little
security will
deserve neither and lose both." - Benjamin Franklin
************************************************************************
*******
Forum Note: Use "Reply" to post a response in the discussion forum.
How do you do that?
IDS 9.4
HP-UX 11.23
--- "Robert Rous...." <Robert.Roussey@SpiritAir.com>
wrote:
>
> IDS 9.4. Let's you do a full restore with renaming
> of devices. It's
> great for creating multiple instances on the same
> server or where you
> can't use the same device names.
>
> Version of IDS? OS?
>
> Bob Roussey
> Unix / Informix Administration
> Spirit Airlines
> Robert.Roussey@SpiritAir.com
>
> -----Original Message-----
> From: ids-bounces@iiug.org
> [mailto:ids-bounces@iiug.org] On Behalf Of
> Radhe Webster
> Sent: Thursday, June 22, 2006 12:04 PM
> To: ids@iiug.org
> Subject: Moving data between instances [7027]
>
> I was hoping I could get some advice. We currently
> have 2 machines and when we need to replicate the
> data
> we move an ontape from one to the other. All paths
> are the same and this works fine. We're moving to
> one
> machine and we still need to figure out a way of
> moving the data from one to the other.
>
> We will need the data static for the first 10 days
> of
> the mont and then have it more or less in sync
> (doesn't need to be immediate). Anyone have any
> suggestions or thoughts on this?
>
> Thanks
>
> Any society that would give up a little liberty to
> gain a little
> security will
> deserve neither and lose both." - Benjamin Franklin
>
>
************************************************************************
>
> *******
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
You can use ontape with rename option:
ontape -r -rename -f <chunklist>
the format of chunklist file, for example, will be:
/informix/data/instance1/rootdbs 0 /informix/data/instance2/rootdbs 0
/informix/data/instance1/dbs1 0 /informix/data/instance2/dbs1 0
/informix/data/instance1/dbs2 0 /informix/data/instance2/dbs2 0
where 0 is the offset.
in your onconfig.instance2, however, your ROOTPATH must be:
/informix/data/instance1/rootdbs
Don't worry, the restore will automatically and properly change this ROOTPATH
for your instance2's onconfig.
Try it. Good luck.
Radhe Webster <radhe2k@yahoo.com> wrote:
I was hoping I could get some advice. We currently
have 2 machines and when we need to replicate the data
we move an ontape from one to the other. All paths
are the same and this works fine. We're moving to one
machine and we still need to figure out a way of
moving the data from one to the other.
We will need the data static for the first 10 days of
the mont and then have it more or less in sync
(doesn't need to be immediate). Anyone have any
suggestions or thoughts on this?
Thanks
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Ok, thanks. The sizes of each dbspace needs to be the
same though correct?
--- Kern Doe <kern_doe@yahoo.com> wrote:
>
> You can use ontape with rename option:
> ontape -r -rename -f <chunklist>>
> the format of chunklist file, for example, will be:
> /informix/data/instance1/rootdbs 0
> /informix/data/instance2/rootdbs 0
> /informix/data/instance1/dbs1 0
> /informix/data/instance2/dbs1 0
> /informix/data/instance1/dbs2 0
> /informix/data/instance2/dbs2 0
>
> where 0 is the offset.
>
> in your onconfig.instance2, however, your ROOTPATH
> must be:
> /informix/data/instance1/rootdbs
>
> Don't worry, the restore will automatically and
> properly change this ROOTPATH
> for your instance2's onconfig.
>
> Try it. Good luck.
>
> Radhe Webster <radhe2k@yahoo.com> wrote:
>
> I was hoping I could get some advice. We currently
> have 2 machines and when we need to replicate the
> data
> we move an ontape from one to the other. All paths
> are the same and this works fine. We're moving to
> one
> machine and we still need to figure out a way of
> moving the data from one to the other.
>
> We will need the data static for the first 10 days
> of
> the mont and then have it more or less in sync
> (doesn't need to be immediate). Anyone have any
> suggestions or thoughts on this?
>
> Thanks
>
> Any society that would give up a little liberty to
> gain a little security will
> deserve neither and lose both." - Benjamin Franklin
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
Correct.
Radhe Webster <radhe2k@yahoo.com> wrote:
Ok, thanks. The sizes of each dbspace needs to be the
same though correct?
--- Kern Doe wrote:
>
> You can use ontape with rename option:
> ontape -r -rename -f>
> the format of chunklist file, for example, will be:
> /informix/data/instance1/rootdbs 0
> /informix/data/instance2/rootdbs 0
> /informix/data/instance1/dbs1 0
> /informix/data/instance2/dbs1 0
> /informix/data/instance1/dbs2 0
> /informix/data/instance2/dbs2 0
>
> where 0 is the offset.
>
> in your onconfig.instance2, however, your ROOTPATH
> must be:
> /informix/data/instance1/rootdbs
>
> Don't worry, the restore will automatically and
> properly change this ROOTPATH
> for your instance2's onconfig.
>
> Try it. Good luck.
>
> Radhe Webster wrote:
>
> I was hoping I could get some advice. We currently
> have 2 machines and when we need to replicate the
> data
> we move an ontape from one to the other. All paths
> are the same and this works fine. We're moving to
> one
> machine and we still need to figure out a way of
> moving the data from one to the other.
>
> We will need the data static for the first 10 days
> of
> the mont and then have it more or less in sync
> (doesn't need to be immediate). Anyone have any
> suggestions or thoughts on this?
>
> Thanks
>
> Any society that would give up a little liberty to
> gain a little security will
> deserve neither and lose both." - Benjamin Franklin
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
One options would be to set up replication of the tables. Stop replication for
the 10 days of EOM processing then reestablish the replication and let it synch
up.
Art S. Kagel
----- Original Message -----
From: Radhe Webster <ids@iiug.org>
At: 6/22 12:08:17
I was hoping I could get some advice. We currently
have 2 machines and when we need to replicate the data
we move an ontape from one to the other. All paths
are the same and this works fine. We're moving to one
machine and we still need to figure out a way of
moving the data from one to the other.
We will need the data static for the first 10 days of
the mont and then have it more or less in sync
(doesn't need to be immediate). Anyone have any
suggestions or thoughts on this?
Thanks
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
I thought about this option and was concerned that we
would have to rely on tape to do this as it would go
past the logs we keep on the system.
Does replication store the transactions in an internal
table and then apply them when the connection has been
re-established?
--- "ART KAGEL, ...." <kagel@bloomberg.net> wrote:
>
> One options would be to set up replication of the
> tables. Stop replication for
> the 10 days of EOM processing then reestablish the
> replication and let it
> synch
> up.
>
> Art S. Kagel
> ----- Original Message -----
> From: Radhe Webster <ids@iiug.org>
> At: 6/22 12:08:17
>
> I was hoping I could get some advice. We currently
> have 2 machines and when we need to replicate the
> data
> we move an ontape from one to the other. All paths
> are the same and this works fine. We're moving to
> one
> machine and we still need to figure out a way of
> moving the data from one to the other.
>
> We will need the data static for the first 10 days
> of
> the mont and then have it more or less in sync
> (doesn't need to be immediate). Anyone have any
> suggestions or thoughts on this?
>
> Thanks
>
> Any society that would give up a little liberty to
> gain a little security will
> deserve neither and lose both." - Benjamin Franklin
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
No, only logical logs that are currently online can be replayed. However, IDS
10.00UC5 can resynch without using the logical logs (and there is a set of
synch/resynch scripts for earlier releases available). I don't remember that
you quoted a version you are using. Check out the posted presentations from the
IIUG/IDUG conference in Tampa. Madison Pruett gave a talk on this subject
there which I attended.
Art S. Kagel
----- Original Message -----
From: Radhe Webster <ids@iiug.org>
At: 6/22 16:46:48
I thought about this option and was concerned that we
would have to rely on tape to do this as it would go
past the logs we keep on the system.
Does replication store the transactions in an internal
table and then apply them when the connection has been
re-established?
--- "ART KAGEL, ...." <kagel@bloomberg.net> wrote:
>
> One options would be to set up replication of the
> tables. Stop replication for
> the 10 days of EOM processing then reestablish the
> replication and let it
> synch
> up.
>
> Art S. Kagel
> ----- Original Message -----
> From: Radhe Webster <ids@iiug.org>
> At: 6/22 12:08:17
>
> I was hoping I could get some advice. We currently
> have 2 machines and when we need to replicate the
> data
> we move an ontape from one to the other. All paths
> are the same and this works fine. We're moving to
> one
> machine and we still need to figure out a way of
> moving the data from one to the other.
>
> We will need the data static for the first 10 days
> of
> the mont and then have it more or less in sync
> (doesn't need to be immediate). Anyone have any
> suggestions or thoughts on this?
>
> Thanks
>
> Any society that would give up a little liberty to
> gain a little security will
> deserve neither and lose both." - Benjamin Franklin
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Unfortunately we're using 9.4 FC7..and can't move up
to 10, because of lack of support from our software
vendor.
--- "ART KAGEL, ...." <kagel@bloomberg.net> wrote:
>
> No, only logical logs that are currently online can
> be replayed. However, IDS
> 10.00UC5 can resynch without using the logical logs
> (and there is a set of
> synch/resynch scripts for earlier releases
> available). I don't remember that
> you quoted a version you are using. Check out the
> posted presentations from
> the
> IIUG/IDUG conference in Tampa. Madison Pruett gave a
> talk on this subject
> there which I attended.
>
> Art S. Kagel
> ----- Original Message -----
> From: Radhe Webster <ids@iiug.org>
> At: 6/22 16:46:48
>
> I thought about this option and was concerned that
> we
> would have to rely on tape to do this as it would go
>
> past the logs we keep on the system.
>
> Does replication store the transactions in an
> internal
> table and then apply them when the connection has
> been
> re-established?
>
> --- "ART KAGEL, ...." <kagel@bloomberg.net> wrote:
>
> >
> > One options would be to set up replication of the
> > tables. Stop replication for
> > the 10 days of EOM processing then reestablish the
>
> > replication and let it
> > synch
> > up.
> >
> > Art S. Kagel
> > ----- Original Message -----
> > From: Radhe Webster <ids@iiug.org>
> > At: 6/22 12:08:17
> >
> > I was hoping I could get some advice. We currently
>
> > have 2 machines and when we need to replicate the
> > data
> > we move an ontape from one to the other. All paths
>
> > are the same and this works fine. We're moving to
> > one
> > machine and we still need to figure out a way of
> > moving the data from one to the other.
> >
> > We will need the data static for the first 10 days
>
> > of
> > the mont and then have it more or less in sync
> > (doesn't need to be immediate). Anyone have any
> > suggestions or thoughts on this?
> >
> > Thanks
> >
> > Any society that would give up a little liberty to
>
> > gain a little security will
> > deserve neither and lose both." - Benjamin
> Franklin
> >
> >
> >
>
>
>
*******************************************************************************
>
> >
> > Forum Note: Use "Reply" to post a response in the
> > discussion forum.
> >
> >
> >
>
>
>
*******************************************************************************
>
> >
> > Forum Note: Use "Reply" to post a response in the
> > discussion forum.
> >
> >
>
> Any society that would give up a little liberty to
> gain a little security will
> deserve neither and lose both." - Benjamin Franklin
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
No problem. IDS 10 just automates the resynch process. In 9.40 you can still
do this, you just have to manually set up the sych. Check out Madison's
presentation (in 2 parts):
www.iiug.org/idug06/M09.pdf and www.iiug.org/idug06/M11.pdf
I forget if he mentions it on the slides, but IB Madison has scripts available
to resynch the replicates in 9.4.
Also get on your software vendor to certify IDS 10.
Art
----- Original Message -----
From: Radhe Webster <ids@iiug.org>
At: 6/22 17:57:13
Unfortunately we're using 9.4 FC7..and can't move up
to 10, because of lack of support from our software
vendor.
--- "ART KAGEL, ...." <kagel@bloomberg.net> wrote:
>
> No, only logical logs that are currently online can
> be replayed. However, IDS
> 10.00UC5 can resynch without using the logical logs
> (and there is a set of
> synch/resynch scripts for earlier releases
> available). I don't remember that
> you quoted a version you are using. Check out the
> posted presentations from
> the
> IIUG/IDUG conference in Tampa. Madison Pruett gave a
> talk on this subject
> there which I attended.
>
> Art S. Kagel
> ----- Original Message -----
> From: Radhe Webster <ids@iiug.org>
> At: 6/22 16:46:48
>
> I thought about this option and was concerned that
> we
> would have to rely on tape to do this as it would go
>
> past the logs we keep on the system.
>
> Does replication store the transactions in an
> internal
> table and then apply them when the connection has
> been
> re-established?
>
> --- "ART KAGEL, ...." <kagel@bloomberg.net> wrote:
>
> >
> > One options would be to set up replication of the
> > tables. Stop replication for
> > the 10 days of EOM processing then reestablish the
>
> > replication and let it
> > synch
> > up.
> >
> > Art S. Kagel
> > ----- Original Message -----
> > From: Radhe Webster <ids@iiug.org>
> > At: 6/22 12:08:17
> >
> > I was hoping I could get some advice. We currently
>
> > have 2 machines and when we need to replicate the
> > data
> > we move an ontape from one to the other. All paths
>
> > are the same and this works fine. We're moving to
> > one
> > machine and we still need to figure out a way of
> > moving the data from one to the other.
> >
> > We will need the data static for the first 10 days
>
> > of
> > the mont and then have it more or less in sync
> > (doesn't need to be immediate). Anyone have any
> > suggestions or thoughts on this?
> >
> > Thanks
> >
> > Any society that would give up a little liberty to
>
> > gain a little security will
> > deserve neither and lose both." - Benjamin
> Franklin
> >
> >
> >
>
>
>
*******************************************************************************
>
> >
> > Forum Note: Use "Reply" to post a response in the
> > discussion forum.
> >
> >
> >
>
>
>
*******************************************************************************
>
> >
> > Forum Note: Use "Reply" to post a response in the
> > discussion forum.
> >
> >
>
> Any society that would give up a little liberty to
> gain a little security will
> deserve neither and lose both." - Benjamin Franklin
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
>
*******************************************************************************
>
> Forum Note: Use "Reply" to post a response in the
> discussion forum.
>
>
Any society that would give up a little liberty to gain a little security will
deserve neither and lose both." - Benjamin Franklin
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.