From: Green, Simon (Simon.Green@EU.ALTRIA.COM)
Date: Thu Dec 18 2003 - 10:45:54 EST
Hm.
The idea of an allocation map fits, except neither the backup nor
the restore command makes any explicit use of one! I can't find
anything for that particular message ID, either.
Did you continue with the restore? I don't see how that can do
any harm, provided that you check the restored data afterwards.
Simon Green
Altria ITSC Europe Ltd
AIX-L Archive at https://new-lists.princeton.edu/listserv/aix-l.html
AIX FAQ at http://www.faqs.org/faqs/aix-faq/
N.B. Unsolicited email from vendors will not be appreciated.
Please post all follow-ups to the list.
> -----Original Message-----
> From: Hambleton, John S. [mailto:jhamblet@NMU.EDU]
> Sent: 18 December 2003 14:02
> To: aix-l@Princeton.EDU
> Subject: Re: Restore command error--help
>
>
> At 12:22 PM 12/18/2003 +0100, you wrote:
> >It's not something I'm at all familiar with but I would
> >hazard a guess that it's talking about a physical partition
> >map, created when the data was backed up. Following the
> >disk crash, you're using a different disk, so the map is no
> >longer valid.
> >
> >What sort of backup was it?
> >What's the restore command you're using?
>
> The backup command is:
> backup -0 -u -b 200 -f /dev/rmt1 /m1
> we do a full, level 0 backup of our application
> file system every night
>
> and the restore command is:
> restore -b 200 -rvqf /dev/rmt1
>
> The odd thing is that I have replaced hard drives
> before and restored from backup in the same
> manner, with no errors ever being issued by "restore".
> So, seeing "hole in the map" was disconcerting.
>
> Thanks for the reply, Simon!
> John H
>
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:24 EDT