>Oh well, I'm currently doing a 'gtar -xvf' on the entire image, and there
>is that large number in front of everything, but it seems to be restoring
>files properly. ...
Really? They are not going into a directory with that big number on
the front?
Whatever. If it's working, you win :-).
>However I just noticed that it is restoring files I
>thought were being excluded, so perhaps that's due to this version of
>tar?
That might be the case.
>As for the duplicate partitions, that's not working ...
>and in disklist:
>lou /dev/sd0g comp-user #/export exclude ./logs
>lou /dev/sd0g comp-logs #/export just ./logs
You can't do what you want by listing the disk name (/dev/sd0g).
You need to list the mount point, and then you can put a "/." on the
tail end of one of them. For instance, if /dev/sd0g is mounted on /var,
then you could do:
lou /var comp-user #/export exclude ./logs
lou /var/. comp-logs #/export just ./logs
If you don't do anything special, Amanda will think these are new disks.
You could go into your curinfo directory and rename _dev_sd0g to the
appropriate mount point name ('/' becomes '_'). Ditto for the index area.
>I'll update gtar -- I had previously read not to update, but it sounds
>like gtar+Amanda is now fixed in the current versions. Do I need to
>update Amanda too (I know, loaded question!).
You **always** need to update Amanda :-).
No, you don't really need to. Certainly not to match GNU tar. All the
problems were in GNU tar itself. Amanda had nothing to do with it,
other than trying to use the features.
>-doug
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
