At the end of your onstat -d command you will see something like this: .... 50903564 59 50 2 32000 26969 PO- /dev/lrmdata01 5090365c 60 51 2 48000 46337 PO- /dev/lvsdata01 50903754 61 52 2 500000 491359 PO- /dev/lpshistory 5090384c 62 53 2 64000 63397 PO- /dev/lpsdata20 50903944 63 54 2 64000 63397 PO- /dev/lpsdata18 63 active, 2047 maximum
The important thing is the "63 active" must be the same on both boxes. If not, the restore will bomb. the "63 active" must be the same as that is the number of chunks in thedbspaces associated with the instance and these are supported by devices (as noted in the last column) which must be the same on both boxes.... Also your offset between dbspaces must be the same...Sounds like you are almost there except that your instances are somehow different. Jason Morgan <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/21/2002 10:14:43 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: On-Bar restore error. Hi George, Thanks for replying. I am actually a Sys Admin working in conjuction with a DBA. We are actually trying to restore a backup taken from another server to a new instance on another server. The source server is an RS/6000 running ADSM API 3.1.06 and ADSM 3.1 . The target server is RS/6000 AIX 4.2.1 TSM 4.1 and API 3.1.20.8 One question that the DBA mentioned was whether the DbSpace number ( Column 2 ) in the onstat -d report has any relevance. This is the only difference he can see at the moment. As part of the testing, we successfully manage to perform a full back up / restore of an empty instance. This suggest that API /TSM is correctly configured. Many thanks. Jason George Lesho <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 21/01/2002 15:37:53 Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: On-Bar restore error. You didn't mention whether you were trying to restore a backup of the Informix instance to itself or the backup was coming from another server. If you are trying to restore a backup taken on a server to that server, I don't know if you are the sys admin or dba of that server as well as the storage admin. If you are only the storage admin, the 33rd dbspace may have been modified by adding a device (chunk). You also didn't mention the platform type but if it is a UNIX box, go to the /dev dir and see if a device has been added (check file date/time) since the backup was made. If a device has been added to support a new chunk for the dbspace 33, then you will need to rebuilt the instance to be the same as when the backup was made. If the backup was made on another machine / instance, check the devices on the donating machine to see if the number of chunks is consistant with the machine to be backed up to... use onstat -d as the instance owner... George Lesho AFC Enterprises Storage/System Admin Jason Morgan <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/21/2002 08:42:56 AM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: George Lesho/Partners/AFC) Fax to: Subject: On-Bar restore error. All, I have the following error when trying to restore an Informix using On-Bar Out-of-sequence errors. 32 DBSpaces restore ok but the process fails on the 33rd DbSpace. Regards Jason
