Hi,
thanks for the answer.
I expected something like this, but unfortunatelly the image is not split
into multiple chunks on the holding disk and also with amrestore I get the
same message. Amdump runs without error and creates only one image per
partition. Even worse I do have the same entry in the disklist file
(always-full) for different partitions on the same host. I'm able to restore
all other partitions on that host. When I run amdump again I get the same
result restoring that host but sometimes with a different partition.
Help please, I've got a bad feeling, when I should rely on this......
Wolfgang
>I'm trying to restore from the holding disk, after I mounted the directory
>from the backup server. I use the following command:
>
>dd if=/a/20010515/volvo._dev_dsk-c0t0d0s7.0 bs=32k skip=1 | ufsrestore -ifv
-
>
>After entering the command, the ufsrestore runs fine for a while. Then I
get
>the following message:
>
>42267+0 records in
>42267+0 records out
>changing volumes on pipe input
>abort? [yn]
That means ufsrestore did not get the end of image markers it
expected.
Is your image split into multiple chunks in the holding disk? If so,
or even if not, you might want to use amrestore rather than dd to pipe
into ufsrestore:
amrestore -p /a/20010515/volvo._dev_dsk-c0t0d0s7.0 volvo | ufsrestore ...
Amrestore knows about multiple holding disk chunks and will go from one
to the other. Using dd to do that will be more "challenging" :-).
>Wolfgang
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
