Hello
We have recently converted our filesystems over to AdvFS as part
of a change required to allow us to access large filesystems
(greater than 32GBytes). We are now trying to use VDUMP to backup
the filesystems. However, VDUMP (unlike DUMP) does not wait for our
4mm autoloader to change tapes. Instead, VDUMP prompts the user manually
to change the tapes. For background scripts, the process simply aborts
at this point.
We are looking for any help available on how to make VDUMP wait
for the autoloader to change tapes. Our filesystems are over 20GBytes
in size and are still growing. As such, it is normal for the backup
job to use 4 or more tapes.
Has anyone tackled this problem with VDUMP?
Here is an example of our backup script which we run in the
background from the crontab:
/sbin/vdump -b 60 -0uCNf /dev/rmt0h /
/sbin/vdump -b 60 -0uCNf /dev/rmt0h /usr
/sbin/vdump -b 60 -0uCNf /dev/rmt0h /usr/local
/sbin/vdump -b 60 -0uCNf /dev/rmt0h /share
/sbin/vdump -b 60 -0uCNf /dev/rmt0h /local
/sbin/vdump -b 60 -0uCNf /dev/rmt0h /stis0
The last entry is the large filesystems (/stis0). We get the following
error when running the backup:
.
:
vdump: Dumped 11187 of 24498 files; 45.7% completed
vdump: out of space and unable to prompt input for new tape;
[25] Not a typewriter
Thanks for any help...we will summarize,
Keith Feggans (HST/STIS Project at GSFC)
Received on Wed Sep 17 1997 - 14:12:34 NZST