Amanda-Users

Re: problems getting vxdump to work with amanda...

2002-09-17 01:34:27
Subject: Re: problems getting vxdump to work with amanda...
From: "Luke Miller" <millerlu AT integraonline DOT com>
To: <amanda-users AT amanda DOT org>
Date: Mon, 16 Sep 2002 22:17:04 -0700
> Is /fsapvol1SnapVol listed in /etc/vfstab?  If not, I'll wager that's the
> problem.  Amanda checks the filesystem type in /etc/[v]fstab to determine
> which dump program to use on systems supporting multiple filesystem types,
> falling back on the dump program for the native filesystem type - ufsdump
> in this case - if there's no entry.

I added it to /etc/vfstab.  It still doesn't seam to be happy though.

when I run "getfsent /fsapvol1SnapVol/" it says it is vxfs:

fstype of `/fsapvol1SnapVol/': xvfs

Here is the sendsize debug file from the client:

sendsize: debug 1 pid 16880 ruid 105 euid 105: start at Mon Sep 16 22:00:51
2002
sendsize: version 2.4.3b4
sendsize[16882]: time 0.003: calculating for amname '/fsapvol1SnapVol',
dirname '/fsapvol1SnapVol', spindle -1
sendsize[16882]: time 0.004: getting size via dump for /fsapvol1SnapVol
level 0
sendsize[16882]: time 0.006: running "/usr/sbin/ufsdump 0Ssf 1048576 -
/dev/vx/dsk/datadg1/datavol1:SnapVol"
sendsize[16880]: time 0.010: waiting for any estimate child
sendsize[16882]: time 0.010: running /opt/amanda/libexec/killpgrp
sendsize[16882]: time 0.083:   DUMP: Cannot open dump device
`/dev/vx/dsk/datadg1/datavol1:SnapVol': No such file or directory
sendsize[16882]: time 0.084: .....
sendsize[16882]: estimate time for /fsapvol1SnapVol level 0: 0.077
sendsize[16882]: no size line match in /usr/sbin/ufsdump output for
"/fsapvol1SnapVol"
sendsize[16882]: .....
sendsize[16882]: estimate size for /fsapvol1SnapVol level 0: -1 KB
sendsize[16882]: time 0.084: asking killpgrp to terminate
sendsize[16882]: time 1.082: done with amname '/fsapvol1SnapVol', dirname
'/fsapvol1SnapVol',
spindle -1
sendsize[16880]: time 1.084: child 16882 terminated normally
sendsize: time 1.084: pid 16880 finish time Mon Sep 16 22:00:52 2002

It's not able to find the device because
/dev/vx/dsk/datadg1/datavol1:SnapVol doesn't exist.
The actual device is /dev/vx/dsk/datadg1/datavol1.  I an using Veritas's
checkpoint to create
a point in time copy (like a snapshot) of the disk.  The :SnapVol is telling
it the name of this
checkpoint.  Also, it looks like it is still trying to use ufsdump.

Does anyone have any ideas?  Does anyone have this working with checkpoints
like this?

Any help would be appreciated.

Thanks,

Luke Miller
millerlu AT integraonline DOT com



<Prev in Thread] Current Thread [Next in Thread>