On Thu, Jan 19, 2017 at 12:36:24PM -0500, Jean-Francois Malouin wrote:
> * Jean-Louis Martineau [20170119 10:29]:
> > On 19/01/17 09:49 AM, Jean-Francois Malouin wrote:
> > > Hi,,
> ...
> > >
> > >
> > > Question: are they any drawbacks, performance, etc, when setting
>
On 19/01/17 12:36 PM, Jean-Francois Malouin wrote:
> * Jean-Louis Martineau [20170119 10:29]:
>> On 19/01/17 09:49 AM, Jean-Francois Malouin wrote:
>>> Hi,,
> ...
>>>
>>> Question: are they any drawbacks, performance, etc, when setting
>>> property "ATIME-PRESERVE" "NO"
* Jean-Louis Martineau [20170119 10:29]:
> On 19/01/17 09:49 AM, Jean-Francois Malouin wrote:
> > Hi,,
...
> >
> >
> > Question: are they any drawbacks, performance, etc, when setting
> > property "ATIME-PRESERVE" "NO" ?
> The atime of each file/dir tar read will be
On 19/01/17 09:49 AM, Jean-Francois Malouin wrote:
> Hi,,
>
> I've got this FreeBSD 11.0 box (virtual at the moment but will become
> real metal soon) for which I've installed an Amanda client (v3.3.6) and
> while testing it, tar (GNU tar) 1.29 complains when the Amanda run is
> started with
Hi Guys,
I think i found out the culprit to this issue. The main problem of the
GNUTAR to be in hanging state was due to the cancellation of the amdump
process during its execution. This happenned when the amdump (running)
process is being cancelled and were being rerun at a certain point of
Hi Anthony,
I have been having issues of gnutar hanging also. In my case I think
is has to do with hardware issues with the external Western Digital
1TB drive to which I do the backups.
I usually end up having to kill the process on the client, reboot the
server and make sure that the HD
amanda version?
tar version?
Any other amanda process running?
Send the complete debug files:
sendbackup.*.debug and amandad.*.debug from the client
dumper.*.debug from the server.
anthonyh wrote:
Hi guys,
Any solution to the GNUTAR hanging issue yet? I'm having the same problem as
the tar
Chris,
Was there ever any resolution to your problem? I'm having the same
problem with amanda 2.5.1p3 and GNU tar 1.16 hanging on one of my
Solaris 8 servers. The funny thing is that it only hangs when tarring
up one of the disks...my root filesystem. 5 other disks on the same
server get
sendbackup:
sendbackup: debug 1 pid 28355 ruid 2 euid 2: start at Thu Mar 29
07:15:09 2007
sendbackup: version 2.5.1p3
Could not open conf file /etc/amanda/amanda-client.conf: No such file
or directory
Could not open conf file /etc/amanda/test/amanda-client.conf: No such
file or directory
The 'Illegel seek' is not a problem.
The sendsize is working correctly, the problem is with sendbackup
Could you post the sendbackup and amandad debug files?
Jean-Louis
Chris Cameron wrote:
I have Amanda 2.5.1p3 running on Solaris 8 for the server, and the
client is the same version running
On Sat, Jan 14, 2006 at 03:04:26PM -0500, Jon LaBadie wrote:
The contents of the file must always be specified as relative to the
head directory of the DLE.
Since you guys are currently working hard to get 2.5.0 out, it might be
a good time to put this sentence into the amanda.conf manpage?
Josef Wolf wrote:
On Sat, Jan 14, 2006 at 03:04:26PM -0500, Jon LaBadie wrote:
The contents of the file must always be specified as relative to the
head directory of the DLE.
Since you guys are currently working hard to get 2.5.0 out, it might be
a good time to put this sentence into the
On Sat, Jan 14, 2006 at 03:04:26PM -0500, Jon LaBadie wrote:
In the above case the DLE in question was the root-directory. In
filesystem semantics /media and ./media is aequivalent as long as
you are cd'd into / (as it was in this case).
Not that it explains any of Josef's problems, but
On Sun, Jan 15, 2006 at 03:55:33PM +0100, Josef Wolf wrote:
On Sat, Jan 14, 2006 at 03:04:26PM -0500, Jon LaBadie wrote:
In the above case the DLE in question was the root-directory. In
filesystem semantics /media and ./media is aequivalent as long as
you are cd'd into / (as it was in
On Fri, Jan 13, 2006 at 10:44:47AM -0500, Gene Heskett wrote:
and put /media into /.amanda.exclude on that host, but this
You need to put ./media into the exclude file.
Huh? How comes that this makes a difference on the root-filesystem?
Perhaps the reason for that syntax needs to be
On Sat, Jan 14, 2006 at 12:31:38PM +0100, Josef Wolf wrote:
On Fri, Jan 13, 2006 at 10:44:47AM -0500, Gene Heskett wrote:
and put /media into /.amanda.exclude on that host, but this
You need to put ./media into the exclude file.
Huh? How comes that this makes a difference on the
Josef Wolf wrote:
Hello!
I get from gnutar the following error messages:
? gtar: ./media/floppy: Cannot savedir: No medium found
? gtar: ./media/floppy: Warning: Cannot savedir: No medium found
[...]
and put /media into /.amanda.exclude on that host, but this doesn't seem to
help.
You
On Fri, Jan 13, 2006 at 10:36:17AM +0100, Alexander Jolk wrote:
I get from gnutar the following error messages:
? gtar: ./media/floppy: Cannot savedir: No medium found
? gtar: ./media/floppy: Warning: Cannot savedir: No medium found
[...]
and put /media into /.amanda.exclude on that
Josef Wolf schrieb:
and put /media into /.amanda.exclude on that host, but this doesn't
seem to help.
You need to put ./media into the exclude file.
Huh? How comes that this makes a difference on the root-filesystem? Anyway,
I'll try it (but I will have the result not before tomorrow).
On Fri, Jan 13, 2006 at 07:47:27AM +0100, Josef Wolf wrote:
Hello!
I get from gnutar the following error messages:
? gtar: ./media/floppy: Cannot savedir: No medium found
? gtar: ./media/floppy: Warning: Cannot savedir: No medium found
| gtar: ./tmp/.X11-unix/X0: socket ignored
|
Josef Wolf wrote:
I get from gnutar the following error messages:
? gtar: ./media/floppy: Cannot savedir: No medium found
? gtar: ./media/floppy: Warning: Cannot savedir: No medium found
...
The /media directory is handled by an automounter, hence the error message.
Strange it gives
On Fri, Jan 13, 2006 at 03:58:16PM +0100, Paul Bijnens wrote:
? gtar: ./media/floppy: Cannot savedir: No medium found
? gtar: ./media/floppy: Warning: Cannot savedir: No medium found
The /media directory is handled by an automounter, hence the error message.
Strange it gives any error!
On Fri, Jan 13, 2006 at 09:52:45AM -0500, Jon LaBadie wrote:
RE the last paragraph; yes, amanda's treatment of the error messages
is configurable. You can add regex messages in sendbackup-gnutar.c.
Oh. Sorry, I should have said runtime configurable. Having to recompile
is not really
On Fri, Jan 13, 2006 at 04:11:40PM +0100, Josef Wolf wrote:
On Fri, Jan 13, 2006 at 09:52:45AM -0500, Jon LaBadie wrote:
Are you sure the dump was discarded? Or are you assuming that based
on the above messages?
The dump was neither in the holding disk nor on the tape. And amdump's
On Friday 13 January 2006 08:38, Josef Wolf wrote:
On Fri, Jan 13, 2006 at 10:36:17AM +0100, Alexander Jolk wrote:
I get from gnutar the following error messages:
? gtar: ./media/floppy: Cannot savedir: No medium found
? gtar: ./media/floppy: Warning: Cannot savedir: No medium found
I've had no time to work on this lately. I will get back to it soon.
On Wed, Jun 15, 2005 at 05:39:54PM +0200, Paul Bijnens wrote:
Paul Bijnens wrote on 2 June 2005:
OK, I'll jump on this.
Any progress on this problem?
Can you reproduce the problem with a small setup, that I could
Paul Bijnens wrote on 2 June 2005:
OK, I'll jump on this.
Any progress on this problem?
Can you reproduce the problem with a small setup, that I could
duplicate here?
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM
On Thursday 02 June 2005 23:47, Joe Rhett wrote:
Okay, so if it isn't a documentation problem then what do we test
now? A test lab just demonstrated what I already knew.
On Thu, Jun 02, 2005 at 11:16:18PM +0200, Paul Bijnens wrote:
Joe Rhett wrote:
In the meantime, can you confirm exclude
Joe Rhett wrote:
Okay, so if it isn't a documentation problem then what do we test now? A
test lab just demonstrated what I already knew.
You know it, but we don't. And we both would like to know why.
Then I would like to have the config of that test:
amanda.conf, disklist, the contents of
On Thursday 02 June 2005 15:50, Joe Rhett wrote:
On Thu, Jun 02, 2005 at 08:02:21AM -0400, Gene Heskett wrote:
And as I noted before, and someone tried to explain away, it
appears that the command line invocation for the exclude list
is wrong (missing an equals)
Okay, so if it isn't a documentation problem then what do we test now? A
test lab just demonstrated what I already knew.
On Thu, Jun 02, 2005 at 11:16:18PM +0200, Paul Bijnens wrote:
Joe Rhett wrote:
In the meantime, can you confirm exclude file versus exclude list ?
Someone else reported
Gene Heskett wrote:
On Thursday 02 June 2005 17:16, Paul Bijnens wrote:
The documentation is correct:
exclude file ./some*thing
this excludes all the files matching name some*thing
exclude list /some/file
/some/file on the client contains a list of patterns
to be excluded
I'd argue that
On Friday 03 June 2005 06:23, Paul Bijnens wrote:
Gene Heskett wrote:
On Thursday 02 June 2005 17:16, Paul Bijnens wrote:
The documentation is correct:
exclude file ./some*thing
this excludes all the files matching name some*thing
exclude list /some/file
/some/file on the client contains a
Joe Rhett wrote:
These systems I can test with to my heart's content, unlike those Windows
boxes, so tell me what you need to know.
OK, I'll jump on this.
I can assure you there is at least one configuration in the world where
the excludes do work.
First some general info needed:
Amanda
On Wed, Jun 01, 2005 at 10:11:07PM -0700, Joe Rhett wrote:
On Wed, Jun 01, 2005 at 11:27:11PM -0400, Jon LaBadie wrote:
On Wed, Jun 01, 2005 at 07:25:44PM -0700, Joe Rhett wrote:
Okay, last year I had observed that perfectly valid gnutar exclude lists
were being ignored by amanda on
On Thursday 02 June 2005 01:11, Joe Rhett wrote:
On Wed, Jun 01, 2005 at 11:27:11PM -0400, Jon LaBadie wrote:
On Wed, Jun 01, 2005 at 07:25:44PM -0700, Joe Rhett wrote:
Okay, last year I had observed that perfectly valid gnutar
exclude lists were being ignored by amanda on Windows machines.
On Wed, Jun 01, 2005 at 10:11:07PM -0700, Joe Rhett wrote:
That's fine, I was trying everything possible. Right now with those regexs
I'm backing up 60gb a night from that system. Wouldn't that suggest
something is wrong? I started with just the first regex and added others
when it
On Thu, Jun 02, 2005 at 08:02:21AM -0400, Gene Heskett wrote:
And as I noted before, and someone tried to explain away, it
appears that the command line invocation for the exclude list is
wrong (missing an equals) runtar.20050601020202.debug:
running: /bin/tar: gtar --create --file -
Thanks for the advice on doing that. I had such an environment set up last
year, and was able to replicate it at will on the Windows boxes. I'll set
it up again for the linux systems. Working this out on Windows stalled
because I was reluctant to toy with these production systems. Windows
Joe Rhett wrote:
In the meantime, can you confirm exclude file versus exclude list ?
Someone else reported a different syntax that conflicts with the man page,
but actually makes more sense to the naked eye. This may be a
documentation problem.
The documentation is correct:
exclude file
On Wed, Jun 01, 2005 at 07:25:44PM -0700, Joe Rhett wrote:
Okay, last year I had observed that perfectly valid gnutar exclude lists
were being ignored by amanda on Windows machines. The best answer anyone
could give me was to build my own tar program that does the excludes, and
replace
On Wed, Jun 01, 2005 at 11:27:11PM -0400, Jon LaBadie wrote:
On Wed, Jun 01, 2005 at 07:25:44PM -0700, Joe Rhett wrote:
Okay, last year I had observed that perfectly valid gnutar exclude lists
were being ignored by amanda on Windows machines. The best answer anyone
could give me was to
Many thanks for that. it's all up and running now.
Kee
Paul Bijnens wrote:
Kee Gohil wrote:
Bear with me on this. I've inherited a system to look after and I'm
new to Amanda.
I'm using gnutar to backup a ~50Gb filesystem. Unfortunately it won't
backup due to..
/home lev 0 FAILED [dump
Kee Gohil wrote:
Bear with me on this. I've inherited a system to look after and I'm
new to Amanda.
I'm using gnutar to backup a ~50Gb filesystem. Unfortunately it won't
backup due to..
/home lev 0 FAILED [dump larger than tape, but cannot incremental dump
new disk]
A new disk. OK.
I have
* Joshua Baker-LePain [EMAIL PROTECTED] [20040730 11:20]:
On Fri, 30 Jul 2004 at 10:50am, Jean-Francois Malouin wrote
I find myself forced to use ACLs for a finer-grained permissions setup
of a few filesystems (Irix CXFS) and I wonder if any of you had done a
similar thing. The irix tar
Michael D Schleif wrote:
Does Amanda/GNUTAR _follow_ all mount points and symbolic links in a
DLE?
Everytime that I setup Amanda clients, I get confused on these issues.
If this is covered in the FAQ-O-Matic, then I do not see it. If it has
been covered on the mailing list countless times, then
On Mon, Jul 12, 2004 at 03:13:24PM -0500, Michael D Schleif wrote:
Does Amanda/GNUTAR _follow_ all mount points and symbolic links in a
DLE?
Everytime that I setup Amanda clients, I get confused on these issues.
If this is covered in the FAQ-O-Matic, then I do not see it. If it has
been
Hello,
I ran ./configure using the --with-gnutar option and it's working fine now.
Thanks once again.
Regards,
Pipoli
***
amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin
amandad:libexecdir=/usr/local/libexec
mandir=/usr/local/man
amandad:
Rodrigo Pipoli wrote:
I installed, then, this package, also found on sunfreeware.com:
tar-1.13.94-sol26-sparc-local
That is still a little too experimental. In tar 1.13.92 there
were some incompatibilities that made it impossible to work together
with amanda. They could have been resolved in
***
amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin
amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man
amandad:CONFIG_DIR=/usr/local/etc/amanda
DEV_PREFIX=/dev/dsk/
amandad:RDEV_PREFIX=/dev/rdsk/ DUMP=/usr/sbin/ufsdump
amandad:
Christian,
I just did this on my systems, well worth it.
I compiled with, I should say, I ran ./configure --with-gnutar=
and I specified /usr/local/bin/gnutar
I've either copied the actual gnutar to that location from wherever
it happened to be (/usr/freeware/bin/tar on IRIX) or made a link.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok I found the problem. gtar installes wasn't for
the sun version 2.7 . Now it is ok with amcheck.
Christian Molière wrote:
| Hello,
|
|
| I have this error message when I run amcheck config :
|
| GNUTAR program not available
|
| I compiled and
Allen Liu --- work wrote:
I installed gnutar 1.13.25 which generate :
/usr/local/bin/tar
When I configure amanda 2.4.4p2, it could not find gnutar :
./configure --with-user=amanda --with-group=sys --prefix=/myapp/am1
...
checking for grep... /usr/bin/grep
checking for gtar... no
checking
--On Tuesday, March 02, 2004 13:34:19 -0500 Allen Liu --- work [EMAIL PROTECTED]
wrote:
I installed gnutar 1.13.25 which generate :
/usr/local/bin/tar
When I configure amanda 2.4.4p2, it could not find gnutar :
./configure --with-user=amanda --with-group=sys --prefix=/myapp/am1
- Original Message -
From: Frank Smith [EMAIL PROTECTED]
To: Allen Liu --- work [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, March 02, 2004 1:59 PM
Subject: Re: gnutar in configure
--On Tuesday, March 02, 2004 13:34:19 -0500 Allen Liu --- work
[EMAIL PROTECTED] wrote:
I
--On Tuesday, March 02, 2004 14:09:06 -0500 Allen Liu --- work [EMAIL PROTECTED]
wrote:
- how to make ./configure recognize gnutar ?
Run configure with --with-gnutar=/path/to/your/gnutar
I installed tar-1.13.25 . There is no such thing 'gnutar' generated. It only
generated 'tar' and
If you're backing up more than one architecture, I find that it's nice
to set things up so that you can have the same path to gnutar on all of
the architectures. That way, you can run amrecover on any machine and
it will find a valid path to gnutar. Normally, I just create a symbolic
link to
On Tue, 2 Mar 2004 at 3:48pm, Jonathan Dill wrote
On another note, maybe things have changed, but I once found that gnutar
incremental backups sucked performance-wise, would make machines pretty
much unusable during estimates and dumps. Normally, this would not
matter, but you're talking
On Wednesday 07 January 2004 12:09, [EMAIL PROTECTED] wrote:
What are the files in the gnutar-lists/ dir maintained on the amanda
clients?
That should be specified in your amanda.conf.
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.22% setiathome rank, not too shabby for
[EMAIL PROTECTED] wrote:
These are the Amanda processes on the client side of a second DLE that
gives the same illusion of hanging forever:
UID PID PPID CSTIME TTY TIME COMMAND
amanda 3520 1 0 00:36:45 ? 0:02
/opt/amanda/libexec/sendbackup
amanda 3526
To: [EMAIL PROTECTED]
From: Dan L. Ostrom [EMAIL PROTECTED]
Subject: Re: gnutar version -- exactly 1.13.25 or just 1.13.25 and
above?
Cc: Paul Bijnens [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Gene,
Thanks, our version of tar here is 1.13. Looking
Dan L. Ostrom wrote:
sendsize[27262]: time 0.090: runtar: error [must be invoked by root]
The program runtar (and some others) need to have the suid-bit set
and be owned by root.
$ ls -l runtar
-rwsr-x---1 root bin 50980 Oct 9 15:13 runtar
Did you do make install as root?
Are the
-0500
To: [EMAIL PROTECTED]
From: Dan L. Ostrom [EMAIL PROTECTED]
Subject: Re: gnutar version -- exactly 1.13.25 or just 1.13.25 and
above?
Cc: Paul Bijnens [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Gene,
Thanks, our version of tar here
Ok, so it looks like my version of gnutar (1.13.90) might have some pbs,
and it keeps locking up while trying to build the index of some of the
larger DLEs of one of my dumpsets.
So while it's sitting there, locked up, does anyone have any ideas for
what I can try so that it gives up on this
Windows Eudora Pro Version 4.2.0.58
Date: Wed, 17 Dec 2003 10:54:35 -0500
To: [EMAIL PROTECTED]
From: Dan L. Ostrom [EMAIL PROTECTED]
Subject: Re: Fwd: Re: gnutar version -- exactly 1.13.25 or just 1.13.25
and above?
Cc: Dan L. Ostrom [EMAIL PROTECTED]
Gene,
At 08:13 AM 12/17/2003, Gene Heskett
[EMAIL PROTECTED] wrote:
Ok, so it looks like my version of gnutar (1.13.90) might have some pbs,
and it keeps locking up while trying to build the index of some of the
larger DLEs of one of my dumpsets.
I'm still not convinced of that fact.
We only know that the index was still being build.
On Tuesday 16 December 2003 13:11, [EMAIL PROTECTED] wrote:
Jon LaBadie writes:
On Fri, Nov 14, 2003 at 07:15:07PM +0100, Zoltan Kato wrote:
/home is not NFS mounted and the directories are not transient
(they
are
the actual home dirs of individual users). runtar is seduid
root. I
In fact, when I tried to build 1.13.25 a couple of weeks ago, I kept
hitting a build error:
gmake[2]: Entering directory `/src/gnu/tar-1.13.25/lib'
source='xstrtoimax.c' object='xstrtoimax.o' libtool=no \
depfile='.deps/xstrtoimax.Po' tmpdepfile='.deps/xstrtoimax.TPo' \
depmode=gcc /bin/sh
BTW, etimeout is set to 7200 seconds, which has long since
elapsed.
Correction -- I meant to say that it's _dtimeout_ that's set to 7200
seconds:
etimeout10800 # 3h estimate timeout per f/s; default
is 300s.
dtimeout7200# 2h amdump
[Sorry to keep replying to my own posts, but things keep occurring to me
after I've sent the last one! :-]
But I'm puzzled as to why, after 15+ hours of working on the
same DLE, the dump hasn't timed out??
These are the Amanda processes on the client side of a second DLE that
gives the same
[EMAIL PROTECTED] wrote:
Question: Is it to be understood that versions of gnutar _greater_ than
1.13.25 are also incompatible? Or is it implied that those are also
valid acceptable for use with Amanda?
I ask because I'm seeing the same problem as is Mr. Kato, only I'm on an
HP-UX server,
[EMAIL PROTECTED] wrote:
The fact that it's doing a 'tar -tf -', though, in conjunction with the
errors from amstatus when I finally killed it, indicated that it was
still in the estimate stage:
FAILURE AND STRANGE DUMP SUMMARY:
s3sme /var/opt/ignite/recovery RESULTS MISSING
s3sme
On Tue, Dec 16, 2003 at 01:24:56PM -0500, Gene Heskett wrote:
On Tuesday 16 December 2003 13:11, [EMAIL PROTECTED] wrote:
Jon LaBadie writes:
... , is not a suitable version for use with amanda.
It is only 1.13 and what is needed is 1.13.25.
Question: Is it to be understood that
[EMAIL PROTECTED] writes:
That is 10800 seconds for each DLE on that host. If you have 5 DLE's
on that host, the timeout would become effective after
5*10800 seconds.
How many DLE's do have for that host?
Ohhh! I interpreted that to mean that it would wait n seconds with
each DLE, not
On Tuesday 16 December 2003 17:38, Paul Bijnens wrote:
[EMAIL PROTECTED] wrote:
Question: Is it to be understood that versions of gnutar
_greater_ than 1.13.25 are also incompatible? Or is it implied
that those are also valid acceptable for use with Amanda?
I ask because I'm seeing the
Gene,
Thanks, our version of tar here is 1.13. Looking into upgrading
it.
I am currently running amanda-2.4.4p1. I'll check into the
patches available.
I'll post to the group the success/failure of all of this.
At 07:23 PM 12/16/2003, Gene Heskett wrote:
On Tuesday 16
On Tue, Dec 16, 2003 at 05:51:51PM -0500, Jon LaBadie wrote:
** there still are no [gtar] point releases listed from 1.13.25 - 1.13.89 :))
yet 1.13.90 was followed five weeks later with 1.13.91 and a week
after that 1.13.92.
I've seen this before. It seems to be a new(ish)
Dana Bourgeois wrote:
I am running all of these for the first time. Amanda is scheduling 35G (one
tape) but only about 3G is actually getting written for one reason or
another (some is compression, some is weird tar errors). At this rate it
Is the compression problem because amanda actually
--On Saturday, November 08, 2003 12:43:12 -0800 Dana Bourgeois [EMAIL PROTECTED]
wrote:
I am building a new Amanda server and have to use GNUTAR to split up some
very large DLEs. The result is only 128G but 62 DLEs. This is not my
question.
I am running all of these for the first time.
On Fri, Jan 24, 2003 at 01:20:04PM +0100, Paul Bijnens wrote:
Simon Young wrote:
The question is, should I be refering to paths rather than devices when
using tar? Like this:
henry / root-tar
henry /usruser-tar
Yes. You may even use path for if you use dump
On Friday 24 January 2003 06:00, Simon Young wrote:
Hi,
I'm using tar for backup, but my DLEs refer to device names. For
example,
henry /dev/sda1 root-tar
henry /dev/sda2 user-tar
I'm also trying to use exclude lists, but these don't seem to be
working as I would expect them to
--On Friday, January 24, 2003 08:45:24 -0500 Gene Heskett [EMAIL PROTECTED] wrote:
On Friday 24 January 2003 06:00, Simon Young wrote:
Hi,
I'm using tar for backup, but my DLEs refer to device names. For
example,
henry /dev/sda1 root-tar
henry /dev/sda2 user-tar
I'm also
On Friday 24 January 2003 10:34, Frank Smith wrote:
[...]
If both the above examples are the same system (i.e. / is
/dev/sda1 and /usr is /sda2), then using / for a DLE won't
include /usr. Dump limits itself to a single filesystem, and
gnutar is called with the --one-file-system option so it
On Sun, Jan 05, 2003 at 01:02:22PM -0800, Will Lowe wrote:
Note carefully that Jon says like. The include keyword does *not*
do patterns. You must explicitly list each item to be included.
That's ok, provided I can list directories ... something like this:
./var/spool/mail
Is there a way to specify a file of patterns to include rather than to
exclude with the GNUTAR type? Here's the scenario:
In 2.4.3, check man amanda for include, much like exclude.
Note carefully that Jon says like. The include keyword does *not*
do patterns. You must explicitly list each
Note carefully that Jon says like. The include keyword does *not*
do patterns. You must explicitly list each item to be included.
That's ok, provided I can list directories ... something like this:
./var/spool/mail
./usr/local
./etc
./var/log/samba
... and just catch those directories and
On Sun, Jan 05, 2003 at 03:04:21PM -0500, John R. Jackson wrote:
Is there a way to specify a file of patterns to include rather than to
exclude with the GNUTAR type? Here's the scenario:
In 2.4.3, check man amanda for include, much like exclude.
Note carefully that Jon says like. The
At 2003-01-02T15:26:06Z, Joshua Baker-LePain [EMAIL PROTECTED] writes:
Amanda uses a suid wrapper to run tar as root when making backups.
I guess my question was triggered by error messages like:
root@kanga:~# su operator -c amcheck -c Daily
Amanda Backup Client Hosts Check
Hi,
Kirk Strauser schrieb:
I'm using Amanda on a mixed network of Linux and FreeBSD machines. The
default installation of Amanda on FreeBSD defines --with-user=operator and
--with-group=operator . It occurs to me that I have many files that aren't
world-readable. Can tar backup these files?
On Wed, Jan 01, 2003 at 11:58:27AM -0600, Kirk Strauser wrote:
I'm using Amanda on a mixed network of Linux and FreeBSD machines. The
default installation of Amanda on FreeBSD defines --with-user=operator and
--with-group=operator . It occurs to me that I have many files that aren't
On Wednesday 01 January 2003 12:58, Kirk Strauser wrote:
I'm using Amanda on a mixed network of Linux and FreeBSD machines.
The default installation of Amanda on FreeBSD defines
--with-user=operator and --with-group=operator . It occurs to me
that I have many files that aren't world-readable.
On 1 Jan 2003 at 11:58am, Kirk Strauser wrote
I'm using Amanda on a mixed network of Linux and FreeBSD machines. The
default installation of Amanda on FreeBSD defines --with-user=operator and
--with-group=operator . It occurs to me that I have many files that aren't
world-readable. Can tar
Hi
this is very strange,
i have a few servers under linux using ext3 and gnutar with amanda
doing fine level1 and 2's.
I guess you may have a process on your server touching all your files once
a day, making tar thinking they where changed and for that taking them
into your level one backups.
Any
On Wed, Nov 27, 2002 at 10:54:42AM +0100, Helas, Stephan wrote:
Christoph Scheeder wrote:
Hi
this is very strange,
i have a few servers under linux using ext3 and gnutar with amanda
doing fine level1 and 2's.
I guess you may have a process on your server touching all your files
once a
On Tuesday 26 November 2002 20:23, Ivan Zaigralin wrote:
calcsize: gnutar not available on this system
calcsize: gnutar not available on this system
calcsize: gnutar not available on this system
calcsize: gnutar not available on this system
I tried to look this up in the provided
--On Tuesday, November 26, 2002 21:55:43 + Niall O Broin [EMAIL PROTECTED] wrote:
On Tuesday 26 November 2002 20:23, Ivan Zaigralin wrote:
calcsize: gnutar not available on this system
calcsize: gnutar not available on this system
calcsize: gnutar not available on this system
calcsize:
On Tue, Nov 26, 2002 at 12:23:56PM -0800, Ivan Zaigralin wrote:
Dear amanda wizards;
I've just installed the amanda client on a Solaris 9 machine,
and tried to set up the backup of the partitions. However,
that just doesn't happen. The server writes in the report:
FAILURE AND STRANGE
On Tue, Nov 26, 2002 at 09:55:43PM +, Niall O Broin wrote:
On Tuesday 26 November 2002 20:23, Ivan Zaigralin wrote:
calcsize: gnutar not available on this system
calcsize: gnutar not available on this system
calcsize: gnutar not available on this system
calcsize: gnutar not
At 07:11 9/4/2002 -0400, Gene Heskett wrote:
On Wednesday 04 September 2002 01:52, Per olof Ljungmark wrote:
Hi all,
Got a working amanda 2.4.3b2 installation running on a FreeBSD 4.6
server. AFAICS everything is OK except for one thing, backing up
RedHat 6.2 systems with gnutar. The only
On Fri, Sep 06, 2002 at 10:55:35AM +0200, Per olof Ljungmark wrote:
At 07:11 9/4/2002 -0400, Gene Heskett wrote:
On Wednesday 04 September 2002 01:52, Per olof Ljungmark wrote:
Hi all,
Got a working amanda 2.4.3b2 installation running on a FreeBSD 4.6
server. AFAICS everything is OK except
1 - 100 of 142 matches
Mail list logo