On Tue, 2003-11-04 at 07:08, [EMAIL PROTECTED] wrote:
> Hi
>
> I would like to know if anyone had any knowledge on how to preserve
> ACL while extracting files of the tape.
>
> Cheers
You can do this:
getfacl -R dir > acls.txt
now backup
to restore:
restore
setfacl --restore=acls.txt
Basical
On Thu, 2003-09-04 at 10:46, Ripley, Scott wrote:
> >By "non-working" do you mean ldd says they are not found?
>
> >If that is the case I think amandad will start, look for all its
> >libraries in the "dlopen" routine before "main" and terminate
> >when it can't locate every library it "requires".
On Thu, 2003-08-28 at 14:28, Kurt Yoder wrote:
> So I'm trying to get amverify to verify "nttar" and "gtar" backups.
> I've looked at this part of the amverify script from amanda 2.4.2p2:
>
> if [ X"$1" = X"program" -a X"$2" != X"" ]; then
> if [ X"$TAR" != X"" -a X"$2" = X"$TAR" ]; then
>
Some tars are returning with an error (sort of).
---
? gtar: ./dsmith/.xsession-errors: file changed as we read it
| Total bytes written: 163194880
? gtar: Error exit delayed from previous errors
sendbackup: error [/opt/gnome/bin/gtar returned 2]
---
Also:
? gtar: ./net/freeware: Cannot savedir
One of my filesystems failed with the following error:
/-- arsd /net/data3 lev 0 FAILED [/tmpbin/tar returned 2]
sendbackup: start [arsd:/net/data3 level 0]
sendbackup: info BACKUP=/tmpbin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/tmpbin/tar -f... -
sendbackup: info COMPRES
I think I may just reinstall on this system. It is working fine on 2
other systems, just not on this one.
FAILURE AND STRANGE DUMP SUMMARY:
arsd /net/gnome lev 0 FAILED [Request to arsd timed out.]
arsd /net/user1 lev 0 FAILED [Request to arsd timed out.]
arsd /net/pdrs2
On Thu, 14 Jun 2001, John R. Jackson wrote:
> > I mean, /net/useruv is 268842m ...
> >
> >> Whoa, there. This implies you're trying to back up an NFS mounted
> >> area..
> >> That, in general, is a bad idea.
> >
> >Well, actually, no. It is one of the nfs mounts, but this is the original
> >mou
> > I mean, /net/useruv is 268842m ...
> Whoa, there. This implies you're trying to back up an NFS mounted
> area..
> That, in general, is a bad idea.
Well, actually, no. It is one of the nfs mounts, but this is the original
mount point, not the nfs mount itself. I mean, this is the system it
The best way I can think of doing this (I'm far from an expert with
amanda, but I'm learning) is set up one cron with your normal
configuration, then setup another configuration that is set to do full
dumps always, and have another cron run that on the weekend.
That seems to be the easiest way to
I did my first backup last night, and tried a recovery of a couple files
today, but it didn't seem to work.
It only seemed to write like around 40 blocks or so, maybe (of 32k each).
Well, the dd (for testing) came up like this:
mt rewind
dd if=/dev/rmt/1hn bs=32k count=1 > header.dat # tape la
10 matches
Mail list logo