RE: Informix/TSM Point In Time Restore

Yes, been there, got the T-shirt. You can only recover to point in time if you restore ALL dbspaces. If you don't back up all dbspaces you can't restore ALL dbspaces. I even had to backup and restore temp dbspaces despite the fact that they are cleared when you restore. The same applies to restroe to log number. Regards Malcolm -----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On Behalf Of ptitchuisse Sent: 14 September 2005 17:28 To: informix-list@iiug.org Subject: Informix/TSM Point In Time Restore Hello, I am using Informix IDS 9.4 and TDP as a backup solution (on an AIX 5.1 server). Our database contains: - rootdbs - ste_tmp as a temporary dbspace - ste_dbs as an intraday application dbspace - ste_e01_dbs as an archive application dbspace - ste_r01_dbs as an archive application dbspace . . . - ste_e07_dbs as an archive application dbspace - ste_r07_dbs as an archive application dbspace Then, we have have 20 tables which are fragmented on the ste_dbs and ste_e*, ste_r* depend on a dbspace_id field in each table. 0 for ste_dbs, 1 for ste_e01_dbs, ste_r01_dbs. During the intraday traffic, messages are created in these table with the dbspace_id field to 0. During the night, we have a process with set this field to [1-7], depend of the current dbspace to use. It allows to move automatically messages fron the intraday ste_dbs to an archive dbspace. In order to implement a point in time recovery, we made the choice to only backup criticals dbspaces and the intraday's one: each archive dbspace are 36Gb chunk and in the case of a crash, it will take ages to restore. Then, we have defined a "onbar -b rootdbs ste_dbs" in the crontab to run it each night after our "archiving process" As described in the "IBM Informix Backup and Restore Guide pg 6-6 and 6-21" if you use the onbar -r -t time command, you must restore all storage spaces to specific time in a cold restore. I try to : - oninit -i to reinitialise the instance - onmode -BC 1 to activate huge chunk - onspaces to recreate only the ste_dbs - onbar -r -p -t "time1" rootdbs ste_dbs to do a physical point in time restore of only the critical and the intraday dbspaces - onbar -r -l -t "time1" to replay the logs and it failed with : Unable to start the logical log restore: A Point-In-Time Logical Restore is only permitted during a Full Restore. DBSpace 'ste_e01_dbs' was not recovered during this restore.. Using the onstat -d command, I was surprised to see my 14 archive dbspaces automatically recreated !!! Is somebody already met this issue and was in the same startegy ? Any help would be much appreciated Regards David sending to informix-list