RE: Informix 7.30 (I know!)

If you are logging (and of course you are, 'cause it's production) and you don't have raw tables or blobs, then try this.

1. Old Box - back up logical logs continuously
2. Old Box - while On-line, level 0 archive
3. New Box - restore level 0 archive
4. New Box - answer 'N' to level 1 restore
5. Old Box - Stop logging - switch tapes and restart logging
6. New Box - answer 'Y' to log restore.
7. New Box - use the first log tape and apply logs
8. Do Steps 5-7 until you are ready to switch over to New Box Then get it down to only 5 minutes from the last log restore, this will make your last log restore very small and the switchover should be a very small downtime. One more tip do not have (m)any open transactions at the point of switchover..

HTH,
Zev Berezin

-----Original Message-----
From: informix-list-bounces@xxxxxxxx [mailto:informix-list-bounces@xxxxxxxx] On Behalf Of navdeep virk
Sent: Tuesday, May 29, 2007 12:59 PM
To: art.kagel@xxxxxxxxx; informix-list@xxxxxxxx
Subject: Informix 7.30 (I know!)

We have a need to migrate the database from a running Production server on
to a Pre Production machine which will eventually replace the Production
Machine. This is a Transaction Processing system so we want the migration to
happen without any downtime.

We plan to take level "0" back from the Old box , restore to the new box and
then apply the delta using scripts( Unload /load) to bring the data in sync..

Is there a way by which after we have taken a level "0" backup , we can then
take another backup of whatever changed after level "0" and apply that to
database using some informix utility.I am not sure if a Level "1" will do
the job as while the Level "1" is being restored we will have a down time.

NSV


_______________________________________________
Informix-list mailing list
Informix-list@xxxxxxxx
http://www.iiug.org/mailman/listinfo/informix-list
.

Relevant Pages

  • Re: Logging - Best Practices
    ... Logging isn't for development, it's for production. ... There should be, generally, one log or set of logs per ... Don't think so much in terms of packages as applications. ...
    (comp.lang.java.programmer)
  • Re: Best Way for restoring AD in a test lab
    ... Well do a backup and restore following most of the procedures outlined. ... Just do a backup on a production dc. ... > DC to the test lab with the same Server Name and this is our DR process. ... >> Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Re: Best Way for restoring AD in a test lab
    ... I promo a machine in production, back it up and demote it. ... protected space and restore it and whah lah I have a system up and running. ... "Directory Services Restore Mode (Windows 2000 domain controllers only)" ... Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Computer / IT Job at APHA
    ... The System Computer Administrator will apply proven analytical and problem-solving skills to identify, diagnose, and resolve malfunctions to achieve system or network recovery. ... Operate computers, system software applications, and peripheral equipment and monitor production printouts, reports, and files to ensure optimal performance and uphold quality standards. ... Maintain turnover logs, problem logs, tape logs, access logs, and user problem report logs. ...
    (rec.equestrian)
  • Database restore, both from same and different server
    ... Production WSS is working, but a web part has a memory leak. ... production to a development server. ... I've had all kinds of problems trying to restore this ...
    (microsoft.public.sharepoint.windowsservices)