Onbar logical restore fails

Hello, After setting up a new 9.40.FC4 informix server and configuring onbar with TSM I tested backup and restore. Backup of both dbspaces and logical logs turned out to go fine. I performed a level 0 backup and forced a log switch to test logical log backup. All OK. Then I created a database and waited a few minutes to perform a point in time restore to a point in time prior to creating the database. The created database should then not be present after the restore. The physical restore went fine, however when performing the subsequent logical restore I encountered problems causing the Logical restore to suspend (message in message log, see below). In addition the following message was shown to me: $ onbar -r -t "2007-07-05 15:00:00"You cannot switch logs while Dynamic Server is in fast recovery. IDS then showed the following status: IBM Informix Dynamic Server Version 9.40.FC4 -- Fast Recovery (CKPT REQ) -- Up 00:13:54 -- 613152 KbytesBlocked:CKPT The message log (as shown below) suggested to me that this situation appeared when performing a logical recovery of logfile 10. To get the system running again I tried to restore up to log 9 (onbar -r -n 9). This turned out to work fine and the system came on-line again. I cannot seem to find the reason why the point in time restore failed. Since we also use this mechanism on our production system I want to be sure we don't run into these problems when we need to perform a restore on our production systems. Therefor, has anyone experienced this problem before? And is there something I am doing wrong/missing? How can I prevent this situation to occur? Thanks for your help. Regards, Bart ---------------------- From the message log: 15:05:36 Restartable Restore has been ENABLED 15:05:36 Recovery Mode 15:05:38 Physical Restore of rootdbs started. 15:05:39 Checkpoint Completed: duration was 0 seconds. 15:05:39 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54675 15:05:39 Maximum server connections 0 15:05:40 Physical Restore of rootdbs Completed. 15:05:40 Checkpoint Completed: duration was 0 seconds. 15:05:40 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54682 15:05:40 Maximum server connections 0 15:05:40 Physical Restore of llogdbs started. 15:05:40 Physical Restore of datadbs started. 15:05:40 Physical Restore of newtraindbs started. 15:05:40 Physical Restore of objectdbs started. 15:05:41 Physical Restore of plogdbs started. 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54696 15:05:45 Maximum server connections 0 15:05:45 Physical Restore of llogdbs Completed. 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54791 15:05:45 Maximum server connections 0 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54799 15:05:45 Maximum server connections 0 15:05:46 Physical Restore of datadbs Completed. 15:05:46 Checkpoint Completed: duration was 0 seconds. 15:05:46 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54886 15:05:46 Maximum server connections 0 15:05:46 Checkpoint Completed: duration was 0 seconds. 15:05:46 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54894 15:05:46 Maximum server connections 0 15:05:47 Physical Restore of objectdbs Completed. 15:05:47 Checkpoint Completed: duration was 0 seconds. 15:05:47 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54929 15:05:47 Maximum server connections 0 15:05:47 Checkpoint Completed: duration was 0 seconds. 15:05:47 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54937 15:05:47 Maximum server connections 0 15:05:48 Physical Restore of newtraindbs Completed. 15:05:48 Checkpoint Completed: duration was 0 seconds. 15:05:48 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54943 15:05:48 Maximum server connections 0 15:05:48 Checkpoint Completed: duration was 0 seconds. 15:05:48 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54951 15:05:48 Maximum server connections 0 15:05:49 Physical Restore of plogdbs Completed. 15:05:49 Checkpoint Completed: duration was 0 seconds. 15:05:49 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54957 15:05:49 Maximum server connections 0 15:05:49 Logical Recovery Started. 15:05:49 10 recovery worker threads will be started. 15:05:49 Checkpoint Completed: duration was 0 seconds. 15:05:49 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54980 15:05:49 Maximum server connections 0 15:05:49 Start Logical Recovery - Start Log 9, End Log ? 15:05:49 Starting Log Position - 9 0x6050 15:05:49 Clearing the physical and logical logs has started 15:09:24 Cleared 2050 MB of the physical and logical logs in 215 seconds 15:09:24 Checkpoint Completed: duration was 0 seconds. 15:09:24 Checkpoint loguniq 9, logpos 0xa018, timestamp: 55012 15:09:24 Maximum server connections 0 15:09:25 Checkpoint Completed: duration was 1 seconds. 15:09:25 Checkpoint loguniq 9, logpos 0xb018, timestamp: 55017 15:09:25 Maximum server connections 0 15:09:25 Checkpoint Completed: duration was 0 seconds. 15:09:25 Checkpoint loguniq 9, logpos 0xc018, timestamp: 55022 15:09:25 Maximum server connections 0 15:09:26 Checkpoint Completed: duration was 0 seconds. 15:09:26 Checkpoint loguniq 10, logpos 0x20cc, timestamp: 55097 15:09:26 Maximum server connections 0 15:09:26 Checkpoint Completed: duration was 0 seconds. 15:09:26 Checkpoint loguniq 10, logpos 0x3064, timestamp: 55102 15:09:26 Maximum server connections 0 15:09:26 Suspending Logical Restore ---------------------- Logical logs prior to performing restore: $ onstat -l IBM Informix Dynamic Server Version 9.40.FC4 -- Fast Recovery (CKPT REQ) -- Up 00:13:54 -- 613152 KbytesBlocked:CKPT Physical Logging Buffer bufused bufsize numpages numwrits pages/io P-1 11 16 122 8 15.25 phybegin physize phypos phyused %used 2:53 24947 185 107 0.43 Logical Logging Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io L-1 0 16 0 0 0 0.0 0.0 Subsystem numrecs Log Space used address number flags uniqid begin size used %used 70000003036bc20 4 F------ 0 3:53 25000 0 0.00 70000003036bc78 5 F------ 0 3:25053 25000 0 0.00 70000003036bcd0 6 U-B---- 9 3:50053 25000 26 0.10 70000003036bd28 7 U---C-L 10 3:75053 25000 179 0.72 70000003036bd80 8 A------ 0 3:100053 25000 0 0.00 70000003036bdd8 9 A------ 0 3:125053 25000 0 0.00 70000003036be30 10 A------ 0 3:150053 25000 0 0.00 70000003036be88 11 A------ 0 3:175053 25000 0 0.00 70000003036bee0 12 A------ 0 3:200053 25000 0 0.00 70000003036bf38 13 A------ 0 3:225053 25000 0 0.00 70000003036bf90 14 A------ 0 3:250053 25000 0 0.00 700000030357450 15 A------ 0 3:275053 25000 0 0.00 7000000303574a8 16 A------ 0 3:300053 25000 0 0.00 700000030357500 17 A------ 0 3:325053 25000 0 0.00 700000030357558 18 A------ 0 3:350053 25000 0 0.00 7000000303575b0 19 A------ 0 3:375053 25000 0 0.00 700000030357608 20 A------ 0 3:400053 25000 0 0.00 700000030357660 21

Hi Bart, I tested the scenario, as mentioned by you, with IDS 9.40 FC9. The entire scenario, with and without 'point in time restore', works fine without any error msgs being thrown. Since, IDS 9.40 FC4 is a pretty old version when compared to IDS 9.40 FC9, I tested your problem with FC9 only. Thanks, Prasanna Alur Mathada Informix -Interoperability India Software Lab, IBM Software Group ------------------------------------------- Ph : Extn : 91-80-4105-6327 "BART GROOT" <bart.groot@corusgroup.com> Sent by: ids-bounces@iiug.org 09/07/2007 15:15 Please respond to ids@iiug.org To ids@iiug.org cc Subject Onbar logical restore fails [9532] Hello, After setting up a new 9.40.FC4 informix server and configuring onbar with TSM I tested backup and restore. Backup of both dbspaces and logical logs turned out to go fine. I performed a level 0 backup and forced a log switch to test logical log backup. All OK. Then I created a database and waited a few minutes to perform a point in time restore to a point in time prior to creating the database. The created database should then not be present after the restore. The physical restore went fine, however when performing the subsequent logical restore I encountered problems causing the Logical restore to suspend (message in message log, see below). In addition the following message was shown to me: $ onbar -r -t "2007-07-05 15:00:00"You cannot switch logs while Dynamic Server is in fast recovery. IDS then showed the following status: IBM Informix Dynamic Server Version 9.40.FC4 -- Fast Recovery (CKPT REQ) -- Up 00:13:54 -- 613152 KbytesBlocked:CKPT The message log (as shown below) suggested to me that this situation appeared when performing a logical recovery of logfile 10. To get the system running again I tried to restore up to log 9 (onbar -r -n 9). This turned out to work fine and the system came on-line again. I cannot seem to find the reason why the point in time restore failed. Since we also use this mechanism on our production system I want to be sure we don't run into these problems when we need to perform a restore on our production systems. Therefor, has anyone experienced this problem before? And is there something I am doing wrong/missing? How can I prevent this situation to occur? Thanks for your help. Regards, Bart ---------------------- >From the message log: 15:05:36 Restartable Restore has been ENABLED 15:05:36 Recovery Mode 15:05:38 Physical Restore of rootdbs started. 15:05:39 Checkpoint Completed: duration was 0 seconds. 15:05:39 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54675 15:05:39 Maximum server connections 0 15:05:40 Physical Restore of rootdbs Completed. 15:05:40 Checkpoint Completed: duration was 0 seconds. 15:05:40 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54682 15:05:40 Maximum server connections 0 15:05:40 Physical Restore of llogdbs started. 15:05:40 Physical Restore of datadbs started. 15:05:40 Physical Restore of newtraindbs started. 15:05:40 Physical Restore of objectdbs started. 15:05:41 Physical Restore of plogdbs started. 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54696 15:05:45 Maximum server connections 0 15:05:45 Physical Restore of llogdbs Completed. 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54791 15:05:45 Maximum server connections 0 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54799 15:05:45 Maximum server connections 0 15:05:46 Physical Restore of datadbs Completed. 15:05:46 Checkpoint Completed: duration was 0 seconds. 15:05:46 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54886 15:05:46 Maximum server connections 0 15:05:46 Checkpoint Completed: duration was 0 seconds. 15:05:46 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54894 15:05:46 Maximum server connections 0 15:05:47 Physical Restore of objectdbs Completed. 15:05:47 Checkpoint Completed: duration was 0 seconds. 15:05:47 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54929 15:05:47 Maximum server connections 0 15:05:47 Checkpoint Completed: duration was 0 seconds. 15:05:47 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54937 15:05:47 Maximum server connections 0 15:05:48 Physical Restore of newtraindbs Completed. 15:05:48 Checkpoint Completed: duration was 0 seconds. 15:05:48 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54943 15:05:48 Maximum server connections 0 15:05:48 Checkpoint Completed: duration was 0 seconds. 15:05:48 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54951 15:05:48 Maximum server connections 0 15:05:49 Physical Restore of plogdbs Completed. 15:05:49 Checkpoint Completed: duration was 0 seconds. 15:05:49 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54957 15:05:49 Maximum server connections 0 15:05:49 Logical Recovery Started. 15:05:49 10 recovery worker threads will be started. 15:05:49 Checkpoint Completed: duration was 0 seconds. 15:05:49 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54980 15:05:49 Maximum server connections 0 15:05:49 Start Logical Recovery - Start Log 9, End Log ? 15:05:49 Starting Log Position - 9 0x6050 15:05:49 Clearing the physical and logical logs has started 15:09:24 Cleared 2050 MB of the physical and logical logs in 215 seconds 15:09:24 Checkpoint Completed: duration was 0 seconds. 15:09:24 Checkpoint loguniq 9, logpos 0xa018, timestamp: 55012 15:09:24 Maximum server connections 0 15:09:25 Checkpoint Completed: duration was 1 seconds. 15:09:25 Checkpoint loguniq 9, logpos 0xb018, timestamp: 55017 15:09:25 Maximum server connections 0 15:09:25 Checkpoint Completed: duration was 0 seconds. 15:09:25 Checkpoint loguniq 9, logpos 0xc018, timestamp: 55022 15:09:25 Maximum server connections 0 15:09:26 Checkpoint Completed: duration was 0 seconds. 15:09:26 Checkpoint loguniq 10, logpos 0x20cc, timestamp: 55097 15:09:26 Maximum server connections 0 15:09:26 Checkpoint Completed: duration was 0 seconds. 15:09:26 Checkpoint loguniq 10, logpos 0x3064, timestamp: 55102 15:09:26 Maximum server connections 0 15:09:26 Suspending Logical Restore ---------------------- Logical logs prior to performing restore: $ onstat -l IBM Informix Dynamic Server Version 9.40.FC4 -- Fast Recovery (CKPT REQ) -- Up 00:13:54 -- 613152 KbytesBlocked:CKPT Physical Logging Buffer bufused bufsize numpages numwrits pages/io P-1 11 16 122 8 15.25 phybegin physize phypos phyused %used 2:53 24947 185 107 0.43 Logical Logging Buffer bufused bufsize numrecs numpages numwrits recs/pages pages/io L-1 0 16 0 0 0 0.0 0.0 Subsystem numrecs Log Space used address number flags uniqid begin size used %used 70000003036bc20 4 F------ 0 3:53 25000 0 0.00 70000003036bc78 5

Hi Bart, onbar -r -t "2007-07-05 15:00:00" is for a complete restore (physical and logical, IDS offline) Once the pysical restore is done (IDS is in fast recovery mode, with SH= M initialised) and you can use onbar -r -l -t "2007-07-05 15:00:00" or simply onbar -r -l depending on the command you used for physical restore. HTH = = Mit freundlichen Gr=FC=DFen / Best = Regards = = = Martina Lang (Embedded image moved to file: = SWG Client Support - Information pic28596.jpg) = Management Software = DB2 UDB LUW Advanced Support = Phone: +49 89 4504 1477 Internal: = 145 - 1477 = Martina.Lang@de.ibm.com = = = = IBM Deutschland GmbH = Chairman of the Supervisory Board: = Hans Ulrich M=E4rki = Board of Management: Martin Jetter = (Chairman), Rudolf Bauer, = Christian Diedrich, Christoph = Grandpierre, Matthias Hartmann, = Thomas Fell, Michael Diemer = Corporate Seat: Stuttgart, = Reg.-Gericht: Amtsgericht = Stuttgart, HRB 14562 WEEE-Reg.-Nr. = DE 99369940 = = = "Prasanna A = Mathada" = <amprasanna@in.ib = To m.com> ids@iiug.org = Sent by: = cc ids-bounces@iiug. = org Subj= ect Fw: Onbar logical restore fails = [9545] = 13-07-07 14:27 = = = Please respond to = ids@iiug.org = = = Hi Bart, I tested the scenario, as mentioned by you, with IDS 9.40 FC9. The entire scenario, with and without 'point in time restore', works fine without any error msgs being thrown. Since, IDS 9.40 FC4 is a pretty old version when compared to IDS 9.40 FC9, I tested your problem with FC9 only. Thanks, Prasanna Alur Mathada Informix -Interoperability India Software Lab, IBM Software Group ------------------------------------------- Ph : Extn : 91-80-4105-6327 "BART GROOT" <bart.groot@corusgroup.com> Sent by: ids-bounces@iiug.org 09/07/2007 15:15 Please respond to ids@iiug.org To ids@iiug.org cc Subject Onbar logical restore fails [9532] Hello, After setting up a new 9.40.FC4 informix server and configuring onbar w= ith TSM I tested backup and restore. Backup of both dbspaces and logical logs turned out to go fine. I performed a level 0 backup and forced a log switch to= test logical log backup. All OK. Then I created a database and waited a few minutes to perform a point in time restore to a point in time prior to creating= the database. The created database should then not be present after the restore. The physical restore went fine, however when performing the subsequent logical restore I encountered problems causing the Logical restore to suspend (message in message log, see below). In addition the following message was shown= to me: $ onbar -r -t "2007-07-05 15:00:00"You cannot switch logs while Dynamic Server is in fast recovery. IDS then showed the following status: IBM Informix Dynamic Server Version 9.40.FC4 -- Fast Recovery (CKPT REQ= ) -- Up 00:13:54 -- 613152 KbytesBlocked:CKPT The message log (as shown below) suggested to me that this situation appeared when performing a logical recovery of logfile 10. To get the system running again I tried to restore up to log 9 (onbar -= r -n 9). This turned out to work fine and the system came on-line again. I cannot seem to find the reason why the point in time restore failed. Since we also use this mechanism on our production system I want to be sure w= e don't run into these problems when we need to perform a restore on our production systems. Therefor, has anyone experienced this problem before? And is there something I am doing wrong/missing? How can I prevent this situation to occur? Thanks for your help. Regards, Bart ---------------------- >From the message log: 15:05:36 Restartable Restore has been ENABLED 15:05:36 Recovery Mode 15:05:38 Physical Restore of rootdbs started. 15:05:39 Checkpoint Completed: duration was 0 seconds. 15:05:39 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54675 15:05:39 Maximum server connections 0 15:05:40 Physical Restore of rootdbs Completed. 15:05:40 Checkpoint Completed: duration was 0 seconds. 15:05:40 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54682 15:05:40 Maximum server connections 0 15:05:40 Physical Restore of llogdbs started. 15:05:40 Physical Restore of datadbs started. 15:05:40 Physical Restore of newtraindbs started. 15:05:40 Physical Restore of objectdbs started. 15:05:41 Physical Restore of plogdbs started. 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54696 15:05:45 Maximum server connections 0 15:05:45 Physical Restore of llogdbs Completed. 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54791 15:05:45 Maximum server connections 0 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54799 15:05:45 Maximum server connections 0 15:05:46 Physical Restore of datadbs Completed. 15:05:46 Checkpoint Completed: duration was 0 seconds. 15:05:46 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54886 15:05:46 Maximum server connections 0 15:05:46 Checkpoint Completed: duration was 0 seconds. 15:05:46 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54894 15:05:46 Maximum server connections 0 15:05:47 Physical Restore of objectdbs Completed. 15:05:47 Checkpoint Completed: duration was 0 seconds. 15:05:47 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54929 15:05:47 Maximum server connections 0 15:05:47 Checkpoint Completed: duration was 0 seconds. 15:05:47 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54937 15:05:47 Maximum server connections 0 15:05:48 Physical Restore of newtraindbs Completed. 15:05:48 Checkpoint Completed: duration was 0 seconds. 15:05:48 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54943 15:05:48 Maximum server connections 0 15:05:48 Checkpoint Completed: duration was 0 seconds. 15:05:48 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54951 15:05:48 Maximum server connections 0 15:05:49 Physical Restore of plogdbs Completed. 15:05:49 Checkpoint Completed: duration was 0 seconds. 15:05:49 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54957 15:05:49 Maximum server connections 0 15:05:49 Logical Recovery Started. 15:05:49 10 recovery worker threads will be started. 15:05:49 Checkpoint Completed: duration was 0 seconds. 15:05:49 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54980 15:05:49 Maximum server connections 0 15:05:49 Start Logical Recovery - Start Log 9,

Hi Bart, A add on to the previous mail. Probably, you might need to correct your command for the point in time restore. When you try to execute the command onbar -r -t " ", then, it tries to restore both spaces and logs,beginning with spaces first. Since you have explicitly restored the spaces already, probably, thats causing an error msg to be thrown. try executing, onbar -r -l -t " ", since, -l defines the restore operation only forlogs and -t refers to the point in time restore !! FYI : onbar -r -p, restores spaces only and does not restore logs. onbar -r -l, restores logs only and does not restore spaces. Thanks, Prasanna -----Original Message----- From: Prasanna A Mathada <amprasanna@in.ibm.com> To: ids@iiug.org Sent: Fri, Jul 13 8:29 AM Subject: Fw: Onbar logical restore fails [9545] Hi Bart, I tested the scenario, as mentioned by you, with IDS 9.40 FC9. The entire scenario, with and without 'point in time restore', works fine without any error msgs being thrown. Since, IDS 9.40 FC4 is a pretty old version when compared to IDS 9.40 FC9, I tested your problem with FC9 only. Thanks, Prasanna Alur Mathada Informix -Interoperability India Software Lab, IBM Software Group ------------------------------------------- Ph : Extn : 91-80-4105-6327 "BART GROOT" <bart.groot@corusgroup.com> Sent by: ids-bounces@iiug.org 09/07/2007 15:15 Please respond to ids@iiug.org To ids@iiug.org cc Subject Onbar logical restore fails [9532] Hello, After setting up a new 9.40.FC4 informix server and configuring onbar with TSM I tested backup and restore. Backup of both dbspaces and logical logs turned out to go fine. I performed a level 0 backup and forced a log switch to test logical log backup. All OK. Then I created a database and waited a few minutes to perform a point in time restore to a point in time prior to creating the database. The created database should then not be present after the restore. The physical restore went fine, however when performing the subsequent logical restore I encountered problems causing the Logical restore to suspend (message in message log, see below). In addition the following message was shown to me: $ onbar -r -t "2007-07-05 15:00:00"You cannot switch logs while Dynamic Server is in fast recovery. IDS then showed the following status: IBM Informix Dynamic Server Version 9.40.FC4 -- Fast Recovery (CKPT REQ) -- Up 00:13:54 -- 613152 KbytesBlocked:CKPT The message log (as shown below) suggested to me that this situation appeared when performing a logical recovery of logfile 10. To get the system running again I tried to restore up to log 9 (onbar -r -n 9). This turned out to work fine and the system came on-line again. I cannot seem to find the reason why the point in time restore failed. Since we also use this mechanism on our production system I want to be sure we don't run into these problems when we need to perform a restore on our production systems. Therefor, has anyone experienced this problem before? And is there something I am doing wrong/missing? How can I prevent this situation to occur? Thanks for your help. Regards, Bart ---------------------- >From the message log: 15:05:36 Restartable Restore has been ENABLED 15:05:36 Recovery Mode 15:05:38 Physical Restore of rootdbs started. 15:05:39 Checkpoint Completed: duration was 0 seconds. 15:05:39 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54675 15:05:39 Maximum server connections 0 15:05:40 Physical Restore of rootdbs Completed. 15:05:40 Checkpoint Completed: duration was 0 seconds. 15:05:40 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54682 15:05:40 Maximum server connections 0 15:05:40 Physical Restore of llogdbs started. 15:05:40 Physical Restore of datadbs started. 15:05:40 Physical Restore of newtraindbs started. 15:05:40 Physical Restore of objectdbs started. 15:05:41 Physical Restore of plogdbs started. 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54696 15:05:45 Maximum server connections 0 15:05:45 Physical Restore of llogdbs Completed. 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54791 15:05:45 Maximum server connections 0 15:05:45 Checkpoint Completed: duration was 0 seconds. 15:05:45 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54799 15:05:45 Maximum server connections 0 15:05:46 Physical Restore of datadbs Completed. 15:05:46 Checkpoint Completed: duration was 0 seconds. 15:05:46 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54886 15:05:46 Maximum server connections 0 15:05:46 Checkpoint Completed: duration was 0 seconds. 15:05:46 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54894 15:05:46 Maximum server connections 0 15:05:47 Physical Restore of objectdbs Completed. 15:05:47 Checkpoint Completed: duration was 0 seconds. 15:05:47 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54929 15:05:47 Maximum server connections 0 15:05:47 Checkpoint Completed: duration was 0 seconds. 15:05:47 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54937 15:05:47 Maximum server connections 0 15:05:48 Physical Restore of newtraindbs Completed. 15:05:48 Checkpoint Completed: duration was 0 seconds. 15:05:48 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54943 15:05:48 Maximum server connections 0 15:05:48 Checkpoint Completed: duration was 0 seconds. 15:05:48 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54951 15:05:48 Maximum server connections 0 15:05:49 Physical Restore of plogdbs Completed. 15:05:49 Checkpoint Completed: duration was 0 seconds. 15:05:49 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54957 15:05:49 Maximum server connections 0 15:05:49 Logical Recovery Started. 15:05:49 10 recovery worker threads will be started. 15:05:49 Checkpoint Completed: duration was 0 seconds. 15:05:49 Checkpoint loguniq 9, logpos 0x6050, timestamp: 54980 15:05:49 Maximum server connections 0 15:05:49 Start Logical Recovery - Start Log 9, End Log ? 15:05:49 Starting Log Position - 9 0x6050 15:05:49 Clearing the physical and logical logs has started 15:09:24 Cleared 2050 MB of the physical and logical logs in 215 seconds 15:09:24 Checkpoint Completed: duration was 0 seconds. 15:09:24 Checkpoint loguniq 9, logpos 0xa018, timestamp: 55012 15:09:24 Maximum server connections 0 15:09:25 Checkpoint Completed: duration was 1 seconds. 15:09:25 Checkpoint loguniq 9, logpos 0xb018, timestamp: 55017 15:09:25 Maximum server connections 0 15:09:25 Checkpoint Completed: duration was 0 seconds. 15:09:25 Checkpoint loguniq 9, logpos 0xc018, timestamp: 55022 15:09:25 Maximum server connections 0 15:09:26 Checkpoint Completed: duration was 0 seconds. 15:09:26 Checkpoint loguniq 10, logpos 0x20cc, timestamp: 55097 15:09:

Hi all, Many thanks to all for your suggestions. I suppose I could split up the restore to a physical restore using onbar -r -p and a logical restore using onbar -r -l. However, what I was trying to do was a complete combined restore using onbar -r. This gave the problems in fast recovery as described. If a separate physical and logical restore works, then I suppose a combined restore should also work? Thanks.