 | |
Copying ingres checkpoints to another server
comp.databases.ingres comp.databases.ingres
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Copying ingres checkpoints to another server -
05-18-2010
, 10:13 AM
#2
| |||
| |||
|
|
I would like to set up DR for our Live ingres installation. We have two identical servers, with identical ingres installations, only different databases on each. I believe this can be accomplished by copying checkpoint and related files from one server to another, into identically named locations, which we have. ... |
not make a huge difference but it would be nice to know.
If you run "infodb databasename" on the database(s) of interest,
you'll see the checkpoint and dump locations listed. You need
*at least* those two. You'll probably want the journal location as
well.
An outline of the general procedure would be:
- create a database on the backup machine with the same name
and owner as the primary. Extend that database to all the same
data and work locations as the primary database. (infodb will
list any extra data and work locations.) If you want to be extra
slick, after creating the database, sql -u'$ingres' +U iidbdb on
the backup and fix the database's db_id in the iidatabase
catalog to match what's on the primary. (This has no effect
in running the database, but keeps ipm a lot happier!)
- copy the checkpoint and dump areas from primary to backup.
Delete the contents of the data area(a) on the backup side
(being careful to make sure you are doing this on the right
machine!!!) Copy the aaaaaaaa.cnf file in the root data
area (infodb again) to the backup. (This is not strictly necessary
but makes some Ingres versions happier, and is good
superstition anyway.)
- rollforwarddb +c -j databasename on the backup
If you want to throw journals into the mix, copy the journal
area and use a +c +j rollforward. There are additional
things you can do, such as issuing a DM1305+DM1314
trace point on the primary to force an archiver cycle, so that the
journals are as up to date as possible. (WIth the most
recent Ingres versions, you can use the incremental
journaling features, which I am unfortunately not all
that familiar with.)
Another thing to keep in mind is that you will probably need
the same Ingres users on the primary as on the backup,
with the same installation privileges, roles, etc. In other
words all of the iidbdb stuff.
I have one of those "I'm forgetting something" feelings, but
if so, surely someone else will chime in to fill the gaps.
Karl
#3
| |||
| |||
|
#4
| |||
| |||
|
#5
| |||
| |||
|
#6
| |||
| |||
|
|
On May 18, 2010, at 11:13 AM, Ingres Forums wrote: I would like to set up DR for our Live ingres installation. We have two identical servers, with identical ingres installations, only different databases on each. I believe this can be accomplished by copying checkpoint and related files from one server to another, into identically named locations, which we have. ... What Ingres version, and what platform? The Ingres version does not make a huge difference but it would be nice to know. If you run "infodb databasename" on the database(s) of interest, you'll see the checkpoint and dump locations listed. You need *at least* those two. You'll probably want the journal location as well. An outline of the general procedure would be: - create a database on the backup machine with the same name and owner as the primary. Extend that database to all the same data and work locations as the primary database. (infodb will list any extra data and work locations.) If you want to be extra slick, after creating the database, sql -u'$ingres' +U iidbdb on the backup and fix the database's db_id in the iidatabase catalog to match what's on the primary. (This has no effect in running the database, but keeps ipm a lot happier!) - copy the checkpoint and dump areas from primary to backup. Delete the contents of the data area(a) on the backup side (being careful to make sure you are doing this on the right machine!!!) Copy the aaaaaaaa.cnf file in the root data area (infodb again) to the backup. (This is not strictly necessary but makes some Ingres versions happier, and is good superstition anyway.) - rollforwarddb +c -j databasename on the backup If you want to throw journals into the mix, copy the journal area and use a +c +j rollforward. There are additional things you can do, such as issuing a DM1305+DM1314 trace point on the primary to force an archiver cycle, so that the journals are as up to date as possible. (WIth the most recent Ingres versions, you can use the incremental journaling features, which I am unfortunately not all that familiar with.) Another thing to keep in mind is that you will probably need the same Ingres users on the primary as on the backup, with the same installation privileges, roles, etc. In other words all of the iidbdb stuff. I have one of those "I'm forgetting something" feelings, but if so, surely someone else will chime in to fill the gaps. Karl _______________________________________________ Info-Ingres mailing list Info-Ingres (AT) kettleriverconsulting (DOT) com http://ext-cando.kettleriverconsulti...fo/info-ingres |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.