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
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 runtar.
Well now I've enabled my first gnutar linux clients, and
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
I've been told that Amanada supports both windows and linux clients, but I have a few
questions about this.
1. will it back up both clients in the same tape set?
2. Does it support backing up the data over multiple tapes?
3. Where do I find the clients for windoze 95, nt
4. Does it support
19 matches
Mail list logo
