Hi everyone,
pursuant to the below, Compaq's tech support's rather lame answer
is that, well, vdump isn't really for NFS file systems (although if you
do a "man vdump" it says "However, the vdump command is file-
system independent, and you can use it to back up other file systems,
such as UFS and NFS") and they "guess" that it's "probably" a bit
fussier in 4.0E than 4.0B about handling NFS stuff. Anyway they
recommend backing up the AdvFS domains on which the NFS
filesystems are mounted rather than the NFS filesystems themselves,
which is of course a monster pain in our environment which is why
we did it using NFS in the first place. They suggested other iffy
approaches like using rsh and concluded by suggesting we buy
Legato Networker.
This is as I say all a bit lame. Another annoying thing; if we want to
use Compaq's ASE tape services we have to buy the non-Compaq
product Legato NetWorker. So eventually I guess we will end up
forking out for it.
In the meantime, (1) does anyone have any suggestions to add to/
refute Compaq's and (2) I don't suppose anyone can think of a clever
way of making vdump *not* try and change the atimes for files?
Thanks, sorry for short note becoming long rant as usual.
John Speakman
Memorial Sloan-Kettering Cancer Center, NYC
speakman_at_biost.mskcc.org
John Speakman wrote:
> Hi everyone,
>
> since moving from 4.0B to 4.0E we have been seeing the following
> message in our backup logs:
>
> vdump: can't reset atime for <./pathname/.filename>; [22] Invalid argument
>
> where /pathname/filename is the correct path to the file it's backing up.
> It
> happens on ASE mounted NFS volumes only (AdvFS volumes are OK).
> I couldn't swear it happens with every single file on each NFS volume but
> certainly a huge number of them (the reason I noticed is that the volume
> containing our backup logs filled up). Anyway it seems what it's doing is
>
> backing up the file OK (I hope! I will try a restore next) but then trying
> to
> set the archive bit or whatever and failing because (I guess) one of the
> arguments is now no longer valid on NFS volumes. Here's an example
> of the vdump command we use:
>
> vdump -0uN -f /dev/nrmt0h /usr/users
>
> No very exciting arguments there. We backup using the root account
> by the way. Anyone have any idea what's going on?
>
> Thanks in advance; I'll summarize.
>
> John
Received on Sat Aug 21 1999 - 22:46:23 NZST