hi,

When I restore all dbspaces it is completing successfully but when I try to restore only one dbspace, it throws me a error!

ex: when I try to restore only rootdbs : the content of bar_act.log file shows ...

2011-03-14 14:11:05 3824 3824 Successfully connected to Storage Manager.
2011-03-14 14:11:07 3824 3824 Begin salvage for log 15.
2011-03-14 14:11:09 3824 3824 Completed salvage of logical log 15 (Storage Manager copy ID: 22 2011003014).
2011-03-14 14:11:09 3824 3824 Successfully connected to Storage Manager.
2011-03-14 14:11:47 3824 3824 Begin cold level 0 restore rootdbs (Storage Manager copy ID: 18 2011003014).
2011-03-14 14:12:07 3824 3824 Completed cold level 0 restore rootdbs.
2011-03-14 14:12:41 3824 3824 Begin cold level 1 restore rootdbs (Storage Manager copy ID: 19 2011003014).
2011-03-14 14:12:45 3824 3824 Completed cold level 1 restore rootdbs.
2011-03-14 14:13:19 3824 3824 Begin cold level 2 restore rootdbs (Storage Manager copy ID: 20 2011003014).
2011-03-14 14:13:23 3824 3824 Completed cold level 2 restore rootdbs.
2011-03-14 14:13:23 3824 3824 Unable to start the logical log restore: rootdbs which is the ROOT DBspace
is being restored and physdbs has not been physically restored.
If the ROOT DBspace or a DBspace containing the physical log or a logical
log file is restored, then the ROOT DBspace and all DBspaces containing
a logical log file or physical log file must be physically restored..
2011-03-14 14:13:23 3824 3824 C:\PROGRA~1\IBM\Informix\11.70\bin\onbar_d complete, returning 131 (0x83)


Can you all please reply me with the solution...

what should I do, to resolve this issue?

That means that you have to restore the rootdbs and all DBSpaces containing the physical log or logical logs.

Can you post "onstat -d" and "onstat -l" please?

thanks informixwili for your response!, but does it mean that I can't restore a single dbspace, everytime I have to select all critical dbspaces for restoration?!

onstat -d and onstat -l says:

onstat -d

IBM Informix Dynamic Server Version 11.70.TC1IE -- On-Line -- Up 00:00:31 -- 7
8208 Kbytes

Dbspaces
address number flags fchunk nchunks pgsize flags owner name
0EE0A820 1 0x40001 1 1 4096 N BA informix rootdbs
0EEC3030 2 0x40001 2 1 4096 N BA informix physdbs
0EEC31A0 3 0x40001 3 1 4096 N BA informix logdbs
0EEC3310 4 0x40001 4 1 4096 N BA informix datadbs
0EEC3480 5 0x48001 5 1 4096 N SBA informix sbspace
0EEC35F0 6 0x42001 6 1 4096 N TBA informix tempdbs
6 active, 2047 maximum

Chunks
address chunk/dbs offset size free bpages flags pathname
0EE0A990 1 1 0 50000 44710 PO-B-D C:\PROGRA~1\IBM\Informix11.70\OL_INF~1\dbspaces\ro otdbs.000
0EEC3760 2 2 0 12544 203 PO-B-D C:\PROGRA~1\IBM\Informix\11.70\OL_INF~1\dbspaces\p logdbs.000
0EEC3940 3 3 0 15360 1483 PO-B-D C:\PROGRA~1\IBM\Informix\11.70\OL_INF~1\dbspaces\l logdbs.000
0EEC3B20 4 4 0 13312 13259 PO-B-D C:\PROGRA~1\IBM\Informix\11.70\OL_INF~1\dbspaces\d atadbs.000
0EEC3D00 5 5 0 8192 7576 7576 POSB-D C:\PROGRA~1\IBM\Informix\11.70\OL_INF~1\dbspaces\s bspace.000
Metadata 563 358 563
0F3B9018 6 6 0 13312 13259 PO-B-D C:\PROGRA~1\IBM\Informix\11.70\OL_INF~1\dbspaces\t empdbs.000
6 active, 32766 maximum

NOTE: The values in the "size" and "free" columns for DBspace chunks are
displayed in terms of "pgsize" of the DBspace to which they belong.


Expanded chunk capacity mode: always




onstat -l

IBM Informix Dynamic Server Version 11.70.TC1IE -- On-Line -- Up 00:00:19 -- 7
8208 Kbytes

Physical Logging
Buffer bufused bufsize numpages numwrits pages/io
P-1 17 32 0 0 0.00
phybegin physize phypos phyused %used
2:53 12288 324 17 0.14

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
0EED6FA0 7 U-B---- 13 3:53 2304 27 1.17
0EE0ADC8 8 U-B---- 14 3:2357 2304 11 0.48
0EE0AE10 9 U-B---- 15 3:4661 2304 13 0.56
0EE0AE58 10 U---C-L 16 3:6965 2304 25 1.09
0EE0AEA0 11 F------ 0 3:9269 2304 0 0.00
0EE0AEE8 12 F------ 0 3:11573 2304 0 0.00
6 active, 6 total


regards,
Pallavi Pathak

I think you can restore a single dbspace like datadbs and sbspace but if you restore the rootdbs you must restore physdbs and logdbs too.

Maybe there is also an conjunction between datadbs and sbspace but I'm not sure.

Thanks sir, the combination of DBspaces do work!

where there is a conjunction between datadbs and sbspace too.

and now in Informix 11.7 there is one more concept of critical_files(CF), now I am trying to restore only critical files, but when I try restoring it, it gives a error stating as

2011-03-14 16:16:47 356 356 Storage space critical_files does not exist.
2011-03-14 16:16:47 356 356 There are no storage spaces/logical logs to backup/restore.

all though while full restore or with the combination of other dbspaces it doesn't give any error of this kind....

and also while backup, all the critical files where successfully backed up!
[Normal] From: OB2BAR@dpi51164.ind.hp.com "ol_informix1170_6" Time: 3/14/2011 4:26:18 PM
Starting OB2BAR Backup: dpi51164.ind.hp.com:/ol_informix1170_6/critical_files/ixbar (dbspace) "Informix"

[Normal] From: OB2BAR@dpi51164.ind.hp.com "ol_informix1170_6" Time: 3/14/2011 4:26:20 PM
Completed OB2BAR Backup: dpi51164.ind.hp.com:/ol_informix1170_6/critical_files/ixbar (dbspace) "Informix"

[Normal] From: OB2BAR@dpi51164.ind.hp.com "ol_informix1170_6" Time: 3/14/2011 4:26:20 PM
Starting OB2BAR Backup: dpi51164.ind.hp.com:/ol_informix1170_6/critical_files/oncfg (dbspace) "Informix"

[Normal] From: OB2BAR@dpi51164.ind.hp.com "ol_informix1170_6" Time: 3/14/2011 4:26:23 PM
Completed OB2BAR Backup: dpi51164.ind.hp.com:/ol_informix1170_6/critical_files/oncfg (dbspace) "Informix"

[Normal] From: OB2BAR@dpi51164.ind.hp.com "ol_informix1170_6" Time: 3/14/2011 4:26:23 PM
Starting OB2BAR Backup: dpi51164.ind.hp.com:/ol_informix1170_6/critical_files/onconfig (dbspace) "Informix"

[Normal] From: OB2BAR@dpi51164.ind.hp.com "ol_informix1170_6" Time: 3/14/2011 4:26:25 PM
Completed OB2BAR Backup: dpi51164.ind.hp.com:/ol_informix1170_6/critical_files/onconfig (dbspace) "Informix"
can you please tell me about the possible things I should do to correct it?!

You cant restore the critical files in that way, I think you only get them back with a full restore.

But they contain just configuration files, in most cases you don't need to restore them.

hi,

as you said i tried it that way(restoring all critical dbspaces and then sbspace, datadbs) , it was working fine!

Now I took backup and tried to restore datadbs and sbspace first, before restoring all critical dbspaces but it gives an error as

2011-03-15 12:14:14 492 492 C:\PROGRA~1\IBM\Informix\11.70\bin\onbar_d -r sbspace datadbs
2011-03-15 12:14:14 492 492 Successfully connected to Storage Manager.
2011-03-15 12:14:49 492 492 Begin cold level 0 restore datadbs (Storage Manager copy ID: 38 2011003015).
2011-03-15 12:14:49 492 492 Unable to write storage space restore data to the database server: restore reserved pages failed .
2011-03-15 12:14:49 492 492 (-43391) Skipped backup/restore of space 'datadbs'.
2011-03-15 12:14:51 492 492 Unable to start the storage space restore: Archive API error: already open.
2011-03-15 12:14:56 492 492 (-43140) Due to the previous error, logical restore will not be attempted.
2011-03-15 12:14:56 492 492 C:\PROGRA~1\IBM\Informix\11.70\bin\onbar_d complete, returning 131 (0x83)


I am not understanding the reason why it says so!, please tell me what it means, or is there ny way to resolve this?

Regards,
Pallavi Pathak

There are problems writing the reserved pages, you can think of it as a kind of header information.

Do you make your restore in the same system you made your backup?

Is the database really down?

Are there other onbar or storage manager processes open?

yes, I have rechecked every thing!

restore is on the same machine where backup is done!

the database is down..

and there is no other onbar and storage process running on the system.....

Please set "BAR_DEBUG" in the onconfig to "9", try again to restore and post the file defined in the onconfig parameter "BAR_DEBUG_LOG".

Don't forget to set "BAR_DEBUG" back to 0!

have attached bar_dbug.log with this post ... please have a look on it!

Yes I found something, you need to start a cold restore with a physically restoring of all critical storage spaces, then the noncritical storage spaces and finally the logical logs.

Its not possible to make it in another way.

Source: Cold restore

I you only want to restore a non critical dbspace you could make a warm restore (the database must be online):
onbar -r -O sbspace datadbs