Level 0 Restore errors
Posted in 2000
Topics: Backup & Restore, Storage & Space Management
When I am doing a resotre from a level 0 archive to another m/c with
same configuration, I am getting errors after some time. Two Dbspaces
got restored and when the restoration of third one is in progress. There
is no activity in hard disks for a while and process exits showing the
following error messages.
Physical restore failed. Eunction read archive backup failed. code -1
errno - 5
Error reading from network. Abnormal End!!!
At this time, our onstat -D & onstat -d read as below.
Any solution will be highly appreciated.
Thanks
Sampath
Informix Dynamic Server Version 7.30.FC7 -- Fast Recovery (CKPT REQ)
-- Up 00:15:24 -- 155648 Kbytes
Blocked:CKPT
Dbspaces
address number flags fchunk nchunks flags owner
name
2058481c0 1 402 1 1 MP informix
rootdbs
205849488 2 402 2 1 MP informix
logdbs
205849570 3 2005 3 1 NDT informix
tmpdbs1
205849658 4 2005 4 1 NDT informix
tmpdbs2
205849740 5 2005 5 1 NDT informix
tmpdbs3
205849828 6 2005 6 1 NDT informix
tmpdbs4
205849910 7 402 7 1 MP informix
gicdbs
2058499f8 8 202 8 1 MR informix
gicdbs1
205849ae0 9 6 9 1 MD informix
gicdbs2
205849bc8 10 6 10 1 MD informix
gicdbs3
10 active, 2047 maximum
Chunks
address chk/dbs offset page Rd page Wr pathname
2058482a8 1 1 64 0 1096 /dev/rootdbs
205848398 1 1 64 8 1096 /dev/rootmirror
205848768 2 2 64 0 3 /dev/logdbs
205848fd8 2 2 64 0 3 /dev/logmirror
205848858 3 3 64 0 0 /dev/tmpdbs1
205848948 4 4 64 0 0 /dev/tmpdbs2
205848a38 5 5 64 0 0 /dev/tmpdbs3
205848b28 6 6 64 0 0 /dev/tmpdbs4
205848c18 7 7 64 0 323501 /dev/gicdbs
2058490c8 7 7 64 0 323501 /dev/dbsmirror
205848d08 8 8 64 0 239199 /dev/gicdbs1
2058491b8 8 8 64 0 239199 /dev/dbs1mirror
205848df8 9 9 64 0 0 /dev/gicdbs2
2058492a8 9 9 64 0 0 /dev/dbs2mirror
205848ee8 10 10 64 0 0 /dev/gicdbs3
205849398 10 10 64 0 0 /dev/dbs3mirror
10 active, 2047 maximum
Informix Dynamic Server Version 7.30.FC7 -- Fast Recovery (CKPT REQ)
-- Up 00:16:57 -- 155648 Kbytes
Blocked:CKPT
Dbspaces
address number flags fchunk nchunks flags owner
name
2058481c0 1 402 1 1 MP informix
rootdbs
205849488 2 402 2 1 MP informix
logdbs
205849570 3 2005 3 1 NDT informix
tmpdbs1
205849658 4 2005 4 1 NDT informix
tmpdbs2
205849740 5 2005 5 1 NDT informix
tmpdbs3
205849828 6 2005 6 1 NDT informix
tmpdbs4
205849910 7 402 7 1 MP informix
gicdbs
2058499f8 8 202 8 1 MR informix
gicdbs1
205849ae0 9 6 9 1 MD informix
gicdbs2
205849bc8 10 6 10 1 MD informix
gicdbs3
10 active, 2047 maximum
Chunks
address chk/dbs offset size free bpages flags
pathname
2058482a8 1 1 64 225000 217197 PI-
/dev/rootdbs
205848398 1 1 64 225000 0 MI-
/dev/rootmirror
205848768 2 2 64 228436 177183 PI-
/dev/logdbs
205848fd8 2 2 64 228436 0 MI-
/dev/logmirror
205848858 3 3 64 456936 456883 PI-
/dev/tmpdbs1
205848948 4 4 64 456936 456883 PI-
/dev/tmpdbs2
205848a38 5 5 64 456936 456883 PI-
/dev/tmpdbs3
205848b28 6 6 64 456936 456883 PI-
/dev/tmpdbs4
205848c18 7 7 64 999936 672814 PI-
/dev/gicdbs
2058490c8 7 7 64 999936 0 MI-
/dev/dbsmirror
205848d08 8 8 64 999936 562333 PI-
/dev/gicdbs1
2058491b8 8 8 64 999936 0 MI-
/dev/dbs1mirror
205848df8 9 9 64 999936 545101 PI-
/dev/gicdbs2
2058492a8 9 9 64 999936 0 MI-
/dev/dbs2mirror
205848ee8 10 10 64 999936 635054 PI-
/dev/gicdbs3
205849398 10 10 64 999936 0 MI-
/dev/dbs3mirror
10 active, 2047 maximum
Hi Sampath,
Hold the restore for a bit (you do seem to have time on your side!).
Confirm that your Informix versions are identical - not just the major
number, but the entire number - i.e you must have v7.30FC7 on both
machines. If they are, try the following :
1. Copy your production onconfig file to your new machine, changing only
the DBSERVERNAME & DBSERVERALIASES.
2. Using this onconfig file, create an instance on your new machine with
all chunk names and sizes identical to that on production. You will have
to temporarily change some settings in the onconfig file (PHYSDBS,
LOGFILES, DBSPACETEMP) when initializing the instance, but when you are
done, you should have restored all your onconfig settings to those on
production (except DBSERVERNAME & DBSERVERALIASES).
3. Double-check your onstat -d output as being identical except for the
value of "free".
4. Now, bring down the "new" engine and carry out your restore.
If it still fails, call tech support.
Rudy
P.S. Is Hudaibiya behaving?
SAMPATH wrote:
> When I am doing a resotre from a level 0 archive to another m/c with
> same configuration, I am getting errors after some time. Two Dbspaces
> got restored and when the restoration of third one is in progress. There
> is no activity in hard disks for a while and process exits showing the
> following error messages.
>
> Physical restore failed. Eunction read archive backup failed. code -1
> errno - 5
>
> Error reading from network. Abnormal End!!!
>
> At this time, our onstat -D & onstat -d read as below.
>
> Any solution will be highly appreciated.
>
> Thanks
>
> Sampath
Related threads
- IDS 10 table-level restore
- Informix Development Webinar December 11, 2007
- ontape -p/r with changed ROOTPATH
- Migrate from HP PA-RISC to HP ITANIUM by ontape