tory
would not be backed up (due to the amanda-excludes entry)
nor that I might moronically delete the QD/.bin contents.
As I redevelop the scripts, I'll put them in a relocated
bin directory. But I just wonder if there was some way
to address this in an amanda-excludes file. I doubt it.
Jon
--
Jon
Am 26.11.19 um 12:39 schrieb Stefan G. Weichinger:
>
> Does someone have a working example for an exclude list in combo with
> the amsamba application?
ah, and now it works .. as so often after asking for help ;-)
sorry for the noise
Does someone have a working example for an exclude list in combo with
the amsamba application?
On Saturday 07 September 2019 12:44:00 Gene Heskett wrote:
> On Saturday 07 September 2019 12:05:45 Nathan Stratton Treadway wrote:
> > On Sat, Sep 07, 2019 at 04:31:04 -0400, Gene Heskett wrote:
> > > i interchanged the order, so /boot was first and removed those
> > > dle's that weren't
On Sat, Sep 07, 2019 at 12:44:00 -0400, Gene Heskett wrote:
> On Saturday 07 September 2019 12:05:45 Nathan Stratton Treadway wrote:
>
> > On Sat, Sep 07, 2019 at 04:31:04 -0400, Gene Heskett wrote:
> > > i interchanged the order, so /boot was first and removed those dle's
> > > that weren't
On Saturday 07 September 2019 12:05:45 Nathan Stratton Treadway wrote:
> On Sat, Sep 07, 2019 at 04:31:04 -0400, Gene Heskett wrote:
> > i interchanged the order, so /boot was first and removed those dle's
> > that weren't mounted. Same story, dead the second amanda touched it.
>
> (Note that the
On Sat, Sep 07, 2019 at 04:31:04 -0400, Gene Heskett wrote:
> i interchanged the order, so /boot was first and removed those dle's that
> weren't mounted. Same story, dead the second amanda touched it.
(Note that the order the DLEs are listed in the disklist doesn't
control the order they are
On Friday 06 September 2019 16:37:48 Gene Heskett wrote:
> On Friday 06 September 2019 14:26:25 Nathan Stratton Treadway wrote:
> > On Fri, Sep 06, 2019 at 13:07:55 -0400, Gene Heskett wrote:
> > > Humm, so why does amanda crash the debian version of buster, but
> > > not the raspian's (jessie,
On Friday 06 September 2019 14:26:25 Nathan Stratton Treadway wrote:
> On Fri, Sep 06, 2019 at 13:07:55 -0400, Gene Heskett wrote:
> > Humm, so why does amanda crash the debian version of buster, but not
> > the raspian's (jessie, stretch) that preceded it? And crashed the
> > armbian on a
On Fri, Sep 06, 2019 at 13:07:55 -0400, Gene Heskett wrote:
> Humm, so why does amanda crash the debian version of buster, but not the
> raspian's (jessie, stretch) that preceded it? And crashed the armbian on
> a rock64, supposedly stretch based? Gotta be something different,
I would be very
On Friday 06 September 2019 12:12:57 Nathan Stratton Treadway wrote:
> On Fri, Sep 06, 2019 at 09:54:34 -0400, Gene Heskett wrote:
> > With the usr merge, and I'm reading its not just debian but RH too,
> > /bin becomes a link to usr/bin, and likewise /sbin becomes a link to
> > usr/sbin. And
On Fri, Sep 06, 2019 at 09:54:34 -0400, Gene Heskett wrote:
> With the usr merge, and I'm reading its not just debian but RH too, /bin
> becomes a link to usr/bin, and likewise /sbin becomes a link to
> usr/sbin. And /bib becomes a link to /usr/lib...
>
> But thats going to trigger on /usr/bin
as related to Amanda
> > > starting up on the client side, that's definitely not related to
> > > the "new reject msg" issue, so it's probably best to start a new
> > > thread for the crash issue...)
> > >
> > > Nathan
> >
> > It was running j
Hello all;
Locally built 3.3.7 on the server, distro clients for wheezy on the x86
boxes, a whatever is on jessie-8.6 or so on the raspi client.
I am bringing up another machine on my home network, and it is ignoreing
the excludes list that is in its custom dumptype. So it appears that I
am
Hello,
Since I have a large filesystem that is larger than my 40GB tapes, I
use the gnutar exclude lists features to back this up. Since the
method is somewhat error-prone to forgetting things/excluding too
much, I was wondering if anyone had a script to show me all of the
files on my filesystem
(anywhere on my server) has been accidentally left out.
Any suggestions for how I can do my configuration better that might
prevent some of these issues would be appreciated as well.
Add a DLE for largedir/ that excludes largedir/A largedir/B etc. As
long as you do what you think you're
On Thu, Oct 14, 2004 at 09:27:17AM -0700, Paul Schmidt wrote:
Hello,
Since I have a large filesystem that is larger than my 40GB tapes, I
use the gnutar exclude lists features to back this up. Since the
method is somewhat error-prone to forgetting things/excluding too
much, I was wondering
Greetings;
I just setup an exclude file to skip that 2.2 gig subdir of /amanda,
the one with all the daily copies of the archived indices etc in it.
But now the other client is complaining it cannot find the exclude
file!
---
[EMAIL PROTECTED] amanda]$ amcheck DailySet1
Amanda Tape Server Host
Hi, Gene Heskett,
on Freitag, 23. Jänner 2004 at 23:40 you wrote to amanda-users:
GH Greetings;
GH I just setup an exclude file to skip that 2.2 gig subdir of /amanda,
GH the one with all the daily copies of the archived indices etc in it.
GH But now the other client is complaining it cannot
On Fri, Jan 23, 2004 at 05:40:16PM -0500, Gene Heskett ([EMAIL PROTECTED]) wrote:
Greetings;
I just setup an exclude file to skip that 2.2 gig subdir of /amanda,
the one with all the daily copies of the archived indices etc in it.
But now the other client is complaining it cannot find the
On Friday 23 January 2004 21:26, Jobst Schmalenbach wrote:
On Fri, Jan 23, 2004 at 05:40:16PM -0500, Gene Heskett
([EMAIL PROTECTED]) wrote:
Greetings;
I just setup an exclude file to skip that 2.2 gig subdir of
/amanda, the one with all the daily copies of the archived indices
etc in it.
Hello, amanda-users,
welcome back to another round of discussing Samba-excludes ...
I set up an AMANDA server these days. Its job is to backup one
Windows-Server. This Win-box shares one big directory which contains
several directories which should not be backed up due to their size
and the fact
.
I've been working on an smbclient wrapper to allow
multiple pattern excludes but that got me wondering
about the include feature.
Though I've not looked at the code, it seems like enabling
the include feature would require nearly the same changes
that went into adding exclude. Is there any reason
Jon LaBadie wrote:
Though I've not looked at the code, it seems like enabling
the include feature would require nearly the same changes
that went into adding exclude. Is there any reason,
aside for lack of interest in the past, that the include
feature was not added?
I wouldn't know about the
- Original Message -
From: David Barcelo [EMAIL PROTECTED]
I can't get amanda to exclude files. I am defining them on the server
and not the client. I have the following entries under my global
dumptype definition in amanda.conf:
define dumptype global {
comment Global
Does Amanda 2.4.1p1 support excludes?
Can I use excludes with dump, or only gnutar?
--
David Olbersen
iGuard Engineer
11415 West Bernardo Court
San Diego, CA 92127
1-858-676-2277 x2152
On Tue, May 27, 2003 at 10:13:03PM -0400, Luc Lalonde wrote:
Hello Folks,
Would there be a way to force excludes from the client side? I want to
enforce an exclude list regardless of wether the exclude directive states on
the server amanda.conf file.
One way I thought of doing
Hello Folks,
Would there be a way to force excludes from the client side? I want to
enforce an exclude list regardless of wether the exclude directive states on
the server amanda.conf file.
One way I thought of doing this is by writting a shell wrapper for tar on the
client and using
: Tuesday, December 04, 2001 3:06 PM
To: Stephen Carville
Cc: Amanda Users
Subject: Re: Excludes not working
On Tue, 4 Dec 2001 at 10:10am, Stephen Carville wrote
I have an exclude list that looks like:
/proc
/devices
/tmp
/temp
/var/lock
/var/spool/postfix/private
/spool/postfix/private
: Octavian Popescu [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 17, 2002 2:15 PM
To: [EMAIL PROTECTED]
Subject: amanda excludes
Hello,
It seems that amanda doesn't want to exclude the folders mentioned in the
exclude list file.
Basically, I have included an entry in the diskfile - exclude list
On Mon, 17 Dec 2001 at 2:18pm, Jon LaBadie wrote
The strange report is what I'm trying to eliminate. For example:
/-- butch //winnie/E lev 1 STRANGE
sendbackup: start [butch://winnie/E level 1]
sendbackup: info BACKUP=/opt/samba/bin/smbclient
sendbackup: info
$ -U backup -E -W HOST -d0 -TXqcg - ./Directory1
./Directory2
Given that this smbclient syntax when run manually on the command line
works and has the desired effect in that it excludes both files, this I
thought would be the answer to my problem.
However, when two files are specified
On Tue, 4 Dec 2001 at 10:10am, Stephen Carville wrote
I have an exclude list that looks like:
/proc
/devices
/tmp
/temp
/var/lock
/var/spool/postfix/private
/spool/postfix/private
/var/tmp
/lost+found
*..LCK
But amrecover tells me that amanda is still backing up these
Indicates
Hello,
It seems that amanda doesn't want to exclude the folders mentioned in the
exclude list file.
Basically, I have included an entry in the diskfile - exclude list
'/excluded'
On the test client, I have created the /excluded file, with read permissions
for the amanda user, and which contains
$ -U backup -E -W HOST -d0 -TXqcg - ./Directory1
./Directory2
Given that this smbclient syntax when run manually on the command line
works and has the desired effect in that it excludes both files, this I
thought would be the answer to my problem.
However, when two files are specified
On Wednesday 09 January 2002 09:45, Donhost Support wrote:
Amanda with smbclient can't use excludes like Linux does.
This is being
addressed in the next several releases of Amanda. If you read
the amanda.conf
in your amanda directory, you'll notice that it points out
that exclude
of the amandad*debug you sent (I think -- I've not been paying close
attention to this thread), the multiple excludes created a malformed
packet. This is probably due to AMANDA only expecting one argument there,
since multiple excludes (non samba of course) belong in an exclude list.
Or am I
On Wed, 9 Jan 2002 at 4:32pm, Donhost Support wrote
I don't know what the docs say, or what the case was in previous
versions, but using amanda-2.4.2p2 one can exclude as many files as
required by listing them on the command line one by one, each one
I thought that this was exactly
On Wed, 9 Jan 2002 at 4:53pm, Donhost Support wrote
In terms of getting amanda to do this, well, you've got the
source. ;)
I guess so, just thought there might be a way round this.
As I said, I think the difficulty is differntiating between GNUTAR/tar and
GNUTAR/smbclient. You may
A while back I asked:
I'm using an exclude list with some tar backups on unix.
Now I'm trying to use samba for windoze backups, but I'm
unable to exclude anything from those shares..
Is it feasible?
Different syntax?
and got one reply:
Yes.
On Mon, 17 Dec 2001 at 2:18pm, Jon LaBadie wrote
The strange report is what I'm trying to eliminate. For example:
/-- butch //winnie/E lev 1 STRANGE
sendbackup: start [butch://winnie/E level 1]
sendbackup: info BACKUP=/opt/samba/bin/smbclient
sendbackup: info
I think you must add a dot before each exclude list entry and you must
use shell wildcards:
./proc/*
./devices/*
Those are relative to the partition roots, not necessarily to the
filesystem root.
Moritz
Du schriebst am Dienstag, 4. Dezember 2001:
I have an exclude list that looks like:
Joshua Baker-LePain wrote:
On Tue, 4 Dec 2001 at 10:10am, Stephen Carville wrote
I have an exclude list that looks like:
/proc
/devices
/tmp
/temp
/var/lock
/var/spool/postfix/private
/spool/postfix/private
/var/tmp
/lost+found
*..LCK
But amrecover tells me that
Putting a dot (.) in front of the directory names did the trick.
Thanks to everyone who answered.
On Tue, 4 Dec 2001, Stephen Carville wrote:
--
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
[EMAIL PROTECTED]
Redhat 7.0 w/tar 1.13.17
Solaris 8 w/tar 1.13.19
amanda 2.4.2p2
I have an exclude list that looks like:
/proc
/devices
/tmp
/temp
/var/lock
/var/spool/postfix/private
/spool/postfix/private
/var/tmp
/lost+found
*..LCK
But amrecover tells me that amanda is still backing up these
directories.
On Tue, 4 Dec 2001 at 10:10am, Stephen Carville wrote
I have an exclude list that looks like:
/proc
/devices
/tmp
/temp
/var/lock
/var/spool/postfix/private
/spool/postfix/private
/var/tmp
/lost+found
*..LCK
But amrecover tells me that amanda is still backing up these
Indicates
Hello,
Since GNUTAR must be used as your dump program you can test with tar local
on the machine, or check out the exclude doc. It is only available via
cvs currently.
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/amanda/amanda/docs/EXCLUDE
Remember that all patterns are relative to your
On Fri, Nov 30, 2001 at 07:38:15AM -0600, Albert Hopkins wrote:
$ gtar -c -v -X exclude-file -f /dev/null /path
on the amanda client
On Fri, 2001-11-30 at 04:33, Stephen Carville wrote:
Is there any way to test the patters in the exclude list for a
disklist entry?
End of included
Thanks for the link!
I'd like to humbly suggest to whoever maintains www.amanda.org, and might be
reading this list that
a link to:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/amanda/amanda/docs/ be located
somewhere on the index page. I have had amanda for over a year, but was not
aware of
$ gtar -c -v -X exclude-file -f /dev/null /path
on the amanda client
On Fri, 2001-11-30 at 04:33, Stephen Carville wrote:
Is there any way to test the patters in the exclude list for a
disklist entry?
--
-- Stephen Carville
UNIX and Network Administrator
Ace Flood USA
310-342-3602
50 matches
Mail list logo
