> On Oct 2, 2020, at 2:26 AM, Stefan G. Weichinger wrote:
>
> (resent with correct subscriber email for the ML)
>
> Am 30.09.20 um 15:21 schrieb Gene Heskett:
>> Sample:
>>
>> HOST lathe ERROR: security file '/etc/amanda-security.conf' do not allow
>> to run '/usr/bin/tar' as root for
On Friday 02 October 2020 08:32:47 Stefan G. Weichinger wrote:
> Am 02.10.20 um 11:57 schrieb Gene Heskett:
> > On Friday 02 October 2020 03:26:01 Stefan G. Weichinger wrote:
> >> (resent with correct subscriber email for the ML)
> >>
> >> Am 30.09.20 um 15:21 schrieb Gene Heskett:
> >>> Sample:
(resent with correct subscriber email for the ML)
Am 30.09.20 um 15:21 schrieb Gene Heskett:
> Sample:
>
> HOST lathe ERROR: security file '/etc/amanda-security.conf' do not allow
> to run '/usr/bin/tar' as root for 'amgtar:gnutar_path'
>
> How do I fix this? Its only been working fine for a
> > Rüdiger
> >
> >
> > Am Mi., 30. Sept. 2020 um 13:11 Uhr schrieb Gene Heskett <
> >
> > ghesk...@shentel.net>:
> > > Greetings all;
> > >
> > > I haven't run amrecover for quite a while, and today it claims no
> > > ho
ings all;
> >
> > I haven't run amrecover for quite a while, and today it claims no
> > host I've named is in the disklist. The disklist is fine, all
> > there.
> >
> > So obviously I didn't scratch this puppies ears recently enough.
> >
> > I did g
Greetings all;
I haven't run amrecover for quite a while, and today it claims no host
I've named is in the disklist. The disklist is fine, all there.
So obviously I didn't scratch this puppies ears recently enough.
I did get the last level0 of the /home/gene for that machine out and
written
On Wednesday 14 November 2018 15:30:11 Debra S Baddorf wrote:
> > On Nov 14, 2018, at 2:18 PM, Gene Heskett
> > wrote:
> >
> > On Wednesday 14 November 2018 15:11:33 Debra S Baddorf wrote:
> >>> On Nov 14, 2018, at 2:04 PM, Gene Heskett
> >>> wrote:
> >>>
> >>> On Wednesday 14 November 2018
On Wed, Nov 14, 2018 at 3:34 PM Debra S Baddorf wrote:
>
> And I’m not certain that amcheck cares, I don’t think it’ll tell you if
> the set is empty.
>
>
It doesn't and it won't.
Kind regards,
Chris
> On Nov 14, 2018, at 2:18 PM, Gene Heskett wrote:
>
> On Wednesday 14 November 2018 15:11:33 Debra S Baddorf wrote:
>
>>> On Nov 14, 2018, at 2:04 PM, Gene Heskett
>>> wrote:
>>>
>>> On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
On Wed, Nov 14, 2018 at 01:06:48PM -0500,
On Wednesday 14 November 2018 15:11:33 Debra S Baddorf wrote:
> > On Nov 14, 2018, at 2:04 PM, Gene Heskett
> > wrote:
> >
> > On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
> >> On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> >>> First a snip/paste of my 3 new del's
On Wednesday 14 November 2018 15:04:25 Gene Heskett wrote:
> On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
> > On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> > > First a snip/paste of my 3 new del's as I try to split a big one
> > > up: line entry
> > > 28 coyote
> On Nov 14, 2018, at 2:04 PM, Gene Heskett wrote:
>
> On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
>
>> On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
>>> First a snip/paste of my 3 new del's as I try to split a big one up:
>>> line entry
>>> 28 coyote
On Wednesday 14 November 2018 14:03:56 Jon LaBadie wrote:
> On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
> > First a snip/paste of my 3 new del's as I try to split a big one up:
> > line entry
> > 28 coyote /home/gene/PublicA/ Publicag {
> > 29 comp-coyote-tar
> > 30 include
ote/PublicAag'
does not exist
it will be created on the next run
NOTE: index dir '/usr/local/var/amanda/Daily/index/coyote/PublicAag' does
not exist
it will be created on the next run
Who knows, might have to adjust the split, but its got to be an
improvement.
Here all this time I thought
On Wed, Nov 14, 2018 at 01:06:48PM -0500, Gene Heskett wrote:
>
> First a snip/paste of my 3 new del's as I try to split a big one up:
> line entry
> 28 coyote /home/gene/PublicA/ Publicag {
> 29comp-coyote-tar
> 30include "./[a-g]*"
> 31exclude "./[h-z]*"
> 32} 1 local
> 33
On Wed, Nov 14, 2018 at 1:10 PM Gene Heskett wrote:
>
> First a snip/paste of my 3 new del's as I try to split a big one up:
> line entry
> 28 coyote /home/gene/PublicA/ Publicag {
> 29 comp-coyote-tar
> 30 include "./[a-g]*"
> 31 exclude "./[h-z]*"
> 32 } 1 local
>
> Try
local
46
Then the amcheck output:
amanda@coyote:/usr/local/etc/amanda/Daily$ /usr/local/sbin/amcheck Daily
"/usr/local/etc/amanda/Daily/disklist", line 34: duplicate disk record,
previous on line 28
"/usr/local/etc/amanda/Daily/disklist", line 34: read of custom dumptype
failed
> On 3 Jun 2018, at 01:12, Nathan Stratton Treadway wrote:
>
> On Sat, Jun 02, 2018 at 13:05:16 +0200, Dirk-Willem van Gulik wrote:
>> On 1 Jun 2018, at 19:14, Chris Nighswonger
>> wrote:
>>>
>>> Based on the example disklist file, it looks like whe
On Sat, Jun 02, 2018 at 13:05:16 +0200, Dirk-Willem van Gulik wrote:
> On 1 Jun 2018, at 19:14, Chris Nighswonger
> wrote:
> >
> > Based on the example disklist file, it looks like when using the multi-line
> > format, you need a leading slash before your diskname en
On 1 Jun 2018, at 19:14, Chris Nighswonger wrote:
>
> Based on the example disklist file, it looks like when using the multi-line
> format, you need a leading slash before your diskname entry:
>
> /tank/jail/webhost091
>
> or some such.
Unfortunately - the disk is a ZFS
Based on the example disklist file, it looks like when using the multi-line
format, you need a leading slash before your diskname entry:
/tank/jail/webhost091
or some such.
Kind regards,
Chris
On Fri, Jun 1, 2018 at 12:09 PM, Dirk-Willem van Gulik wrote:
> I’ve got a bit of an odd
Where did the 091 come from? I don't see it in the first (working) example.
-Chap
On 06/01/18 12:09, Dirk-Willem van Gulik wrote:
> I’ve got a bit of an oddity with the disklist - suspect it is really trivial;
> but am not seeing it.
>
> This works splendidly and
On 1 Jun 2018, at 18:20, J Chapman Flack wrote:
>
> Where did the 091 come from? I don't see it in the first (working) example.
Sorry - that is me badly anonymising on sent. Corrected below.
— corrected --
I’ve got a bit of an oddity with the disklist - suspect it is really trivial;
I’ve got a bit of an oddity with the disklist - suspect it is really trivial;
but am not seeing it.
This works splendidly and as expected:
...
.webweaving.orgtank/jail/webhost
openssl-client-encrypt-best-zfssnapshot-jail
But this (with whitespace reduced
ll see that
each of these items refers to a mount point for a separate filesystem --
otherwise they would't need to be listed separately in the disklist
file)
>
> Part of my disklist is:
>
> ## sbox
> sbox.slsware.net / high-tar 40
> sbox.slsware.net /boot
On 08/05/2017 03:35 AM, Jon LaBadie wrote:
Gnutar writes on the standard error stream both error messages
and informational messages. You are seeing the latter type
for your "/" DLE.
Typically, gnutar is called by amgtar. Amgtar includes lists
of gnutar messages it can ignore and should not
938880 (2.9MiB, 6.6MiB/s)
> sendbackup: size 2870
> sendbackup: end
>
> The directory may be on a different partition, but it's not on a different
> filesystem. They're all on /, and right at the top. They're all RAID 1 too,
> if that makes any difference.
>
> Part of my di
filesystem. They're all on /, and right at the top. They're
all RAID 1 too, if that makes any difference.
Part of my disklist is:
## sbox
sbox.slsware.net/ high-tar 40
sbox.slsware.net/boot high-tar 40
sbox.slsware.net/home high-tar 40
eat...@carbonite.com>
wrote:
> I don't know that it can be done with the amaddclient command but it may
> be faster to just edit the disklist file directly. I believe that is all
> amaddclient is doing: adding entries to the disklist file.
>
> Paul
>
>
>
to
back up. i.e.* $amaddclient --config DailySet1 --client host. example.com
<http://example.com> --diskdev /home --dumptype comp-user-tar*
backing up my home directories is one path, but I would like to add others.
i.e. /etc/, /var/www/htl..etc.. on the same disklist.
Is there a way to do that w
else. I don't really want to formalize it by putting it in the wiki or git or anywhere else. If
someone does find it useful and wants to adapt it, make changes in it, or put it up somewhere, you
are welcome to. Note that changes in the format of disklist will break this.
Of course, the "p
On 03/09/16 23:07, Chris Hoogendyk wrote:
> Does anyone have a perl code snippet to process Amanda's disklist?
[...]
> What I would like to do is have a script on cron that would check the
> size of each DLE and send me an email alert if any one of them goes
> above some threshold. Th
version first.
In addition, recommend consulting man pages for amanda on your
installed system, these will cover your specific version. The website
covers latest. For example, my 3.3.1 install man page for disklist
shows no mention of includefile.
--
Mikalai Krot
Sprachwissenschaftliches
on your installed
system, these will cover your specific version. The website covers
latest. For example, my 3.3.1 install man page for disklist shows no
mention of includefile.
--
Bill Carlson
Anything is possible, given Time and Money.
On 03/10/2016 05:36 AM, Nuno Dias wrote:
Hi
gt;
> > Thanks in advance,
> > Nikolai Krot
> >
> > On 03/09/2016 04:06 PM, Bill Carlson wrote:
> > > Hello,
> > >
> > > What version of amanda are you using?
> > >
> > > Is the combined disklist composed of only unique entrie
Does anyone have a perl code snippet to process Amanda's disklist?
I found http://wiki.zmanda.com/pod/3.1/Amanda/Disklist.html, but it explicitly says that additional
parameters (such as include and exclude) are not reproduced by this package.
Why I am interested in this -- I'm managing four
On Wed, Mar 09, 2016 at 07:30:56PM +0100, Mikalai Krot wrote:
> Hi all,
>
...
> Anyway, the issue is solved. I know that multiple includefile stanzas are
> not possible with amanda-3.3.3 in rhel7.
>
> Thank you for your help,
> Nikolai
Is there a second observation of that defect in 3.3.3?
jl
Hi all,
I have a similar goal in mind. I am backing up mailboxes and want to
avoid manually adding a DLE for any newly added mail account. I rely on
cron more than on my memory.
My intent was also to keep things modular. I would like to have a
dedicated disklist for every possible
to help you but my tests with amanda-3.3.5
show that multiple "includefile" stanzas work, along with or without
inline DLEs.
My "test" uses the command "/opt/amanda/sbin/amadmin disklist"
and checks that its output corresponds to the content of the disklist
and the inclu
Hi,
Not sure if this is going to help you but my tests with amanda-3.3.5
show that multiple "includefile" stanzas work, along with or without
inline DLEs.
My "test" uses the command "/opt/amanda/sbin/amadmin disklist"
and checks that its output corresponds
Hi Debra,
thanks for the suggestion! In the end, this is what I did.
(
cat disklist.manual
generator_of_other_DLEs
) > disklist
Not a big issue, it is the same script as before with a slight
modification. I am happy amanda now works, though knowing the
limitati
anks in advance,
>> Nikolai Krot
>>
>> On 03/09/2016 04:06 PM, Bill Carlson wrote:
>>> Hello,
>>>
>>> What version of amanda are you using?
>>>
>>> Is the combined disklist composed of only unique entries?
>>>
>>>
Carlson wrote:
Hello,
What version of amanda are you using?
Is the combined disklist composed of only unique entries?
Thanks,
--
Bill Carlson
Anything is possible, given Time and Money.
On 03/08/2016 03:48 PM, Mikalai Krot wrote:
Hi list members,
My question is how to combine in a single
, Bill Carlson wrote:
Hello,
What version of amanda are you using?
Is the combined disklist composed of only unique entries?
Thanks,
--
Bill Carlson
Anything is possible, given Time and Money.
On 03/08/2016 03:48 PM, Mikalai Krot wrote:
Hi list members,
My question is how to combine in a single
Hello,
What version of amanda are you using?
Is the combined disklist composed of only unique entries?
Thanks,
--
Bill Carlson
Anything is possible, given Time and Money.
On 03/08/2016 03:48 PM, Mikalai Krot wrote:
Hi list members,
My question is how to combine in a single disklist file
Hi list members,
My question is how to combine in a single disklist file definitions of
DLE and includefile directives. Seems that this is impossible. I tried
the following cases:
### case 1 that worked
disklist contains only DLE entries of the form
server.domain.com /etccomp
Amanda 3.3.4
Hi,
I've got another strange problem. It's probably user-error again, but I
can't figure it out. I added another disklist file to my disklist (see
below), and now amcheck and amdump don't seem to read anything.
amcheck reports 0 hosts checked.
When I run amdump, I get
What's in disklist.picsl-cluster-home?
do 'amadmin CONF disklist' report all Dles?
Jean-Louis
On 09/29/2014 05:23 PM, Michael Stauffer wrote:
Amanda 3.3.4
Hi,
I've got another strange problem. It's probably user-error again, but
I can't figure it out. I added another disklist file to my
For the sake of anyone following this thread in the future, some replies to
my last post:
On Tue, Mar 11, 2014 at 4:12 PM, Michael Stauffer mgsta...@gmail.comwrote:
Thanks Jean-Lous.
In my dumptype I have
program GNUTAR
but I don't know if this always means 'gtar' or if it's
Amanda 3.3.4
Hi,
I'm confused about using glob patterns in disklist. Am I right that if I
use dumptype include and exclude directives, I can use shell globbing?
This is part of my disklist:
cfile.uphs.upenn.edu jet-grosspeople-0-g /jet {
gui-base
#Get everything ^[0-9] and ^[a-zA-Z
expressions with only one slash. The expressions must still
begin with
./, so this effectively only allows expressions like ./[abc]* or
./*.txt.
Jean-Louis
On 03/11/2014 01:53 PM, Michael Stauffer wrote:
Amanda 3.3.4
Hi,
I'm confused about using glob patterns in disklist. Am I
.
Jean-Louis
On 03/11/2014 01:53 PM, Michael Stauffer wrote:
Amanda 3.3.4
Hi,
I'm confused about using glob patterns in disklist. Am I right that if I
use dumptype include and exclude directives, I can use shell globbing?
This is part of my disklist:
cfile.uphs.upenn.edu jet
Thanks, it worked, multiple includes are possible with the append. I
have not tried systematically without append, although I BELIEVE that
in that case only the last include entry is taken into account and
the others silently ignored.
Regards, Charles
p.s. I noticed some strange error messages,
On Mon, Feb 17, 2014 at 12:39:33AM +0100, Charles Stroom wrote:
On Sun, 16 Feb 2014 14:00:01 -0500
Jon LaBadie j...@jgcomp.com wrote:
...
You said that an include implies exclude all else, this clarifies
some behaviour. But I have 1 DLE with multiple includes:
fiume.localnet Vbox
Charles Stroom schreef op 16-02-14 15:29:
include ./*
exclude ./Canon_800IS/*
exclude ./Canon_G2/*
Maybe you need to exclude first?
Met vriendelijke groeten,
AT COMPUTING
Gerrit A. Smit
Beheer Technische Infrastructuur
--
AT Computing Telefoon: +31 24 352 72 22
and have
reformatted my disklist. I have difficulties to understand what will
be, or what will be not included. To take an example, i have a
directory /home/charles/pictures. It contains sub-directories for a
few cameras I have/had and a miscellany of smaller directories and
files. charles
On Sun, Feb 16, 2014 at 03:29:03PM +0100, Charles Stroom wrote:
I am now running my compiled 3.3.5 amanda on opensuse 13.1 and have
reformatted my disklist. I have difficulties to understand what will be, or
what will be not included. To take an example, i have a directory
/home/charles
On Sun, 16 Feb 2014 14:00:01 -0500
Jon LaBadie j...@jgcomp.com wrote:
On Sun, Feb 16, 2014 at 03:29:03PM +0100, Charles Stroom wrote:
I am now running my compiled 3.3.5 amanda on opensuse 13.1 and have
reformatted my disklist. I have difficulties to understand what
will be, or what
On 12/04/13 23:31, Erik P. Olsen wrote:
It looks like you only specify partitions (or entire disk devices) in a disklist
for data to be backed up. How should I specify discrete files to be backed up?
Never mind. Found some info buried in the gigantic manpage for amanda.conf which
I hope I can
It looks like you only specify partitions (or entire disk devices) in a disklist
for data to be backed up. How should I specify discrete files to be backed up?
--
Erik
Concordia parvæ res crescunt discordia maximæ dilabuntur
Hi,
In amanda-3.3.2 if I use includefile directive in disklist, that
directive must be the first thing in the file, and only one includefile
is allowed, this is a feature or a bug?
Cheers,
Nuno
--
Nuno Dias nd...@lip.pt
LIP
On 02/25/2013 06:55 AM, Nuno Dias wrote:
Hi,
In amanda-3.3.2 if I use includefile directive in disklist, that
directive must be the first thing in the file, and only one includefile
is allowed, this is a feature or a bug?
Cheers,
Nuno
It is a bug, the attached patch fix it.
Jean-Louis
this client in disklist, and it was dumped successfully for a couple
of days. Then I decided to temporarily stop dumping this client, and
commented out these entries in disklist.
After that, Amanda sends me mail every morning about RESULTS MISSING
for *one* of these two DLEs:
FAILURE DUMP
Hello!
This may be something that is fixed in most recent version (I'm
running 3.2.2), but I still decided to mention it, since initially I
was quite baffled by the error message.
I recently added a new client to my Amanda setup. I had two DLEs from
this client in disklist
Hi,
Under amanda 3.1.0beta1 with a server multihomed to two networks, when disklist
only contains entries for clients multihomed to networks 1 and 2 - all backups
succeed. When disklist contains any entries connected to only network 2 - all
backups fail. The amanda disklist and amanda
,
Under amanda 3.1.0beta1 with a server multihomed to two networks, when
disklist only contains entries for clients multihomed to networks 1
and 2 - all backups succeed. When disklist contains any entries
connected to only network 2 - all backups fail. The amanda disklist
and amanda-client.conf
On Sat, Feb 6, 2010 at 7:29 AM, Gene Heskett gene.hesk...@verizon.net wrote:
Since putting a fresher psu in it, I am seeing amanda do nothing but level
0's on it now, for 3 nights running. I don't recall it doing that before the
extended outage. I suppose it could be a version miss-match,
Greets all;
My milling machine computer had been offline for about a month, failed PSU.
My disklist norrmally gets the home dir tree where all the emc stuff lives, a
total of 5 entries.
Since putting a fresher psu in it, I am seeing amanda do nothing but level
0's on it now, for 3 nights
In an active amanda system, how do I change a
disk from using dump to tar? I have
/etc/amanda/daily/disklist entries of the
form:
bootmd0 comp-root # dumptypes are per vers X examples
and this should be:
bootmd0 comp-root-tar
Thanks,
rir
Greetings all;
I am attempting to add another machine to my disklist, and I have installed
the amanda-client-2.4.5p1 on that machine, but I can't find where it might be
started, no can I find any configs.
Can I even use that old a client with 2.6.1alpha-20090831 here on this box?
--
Cheers
(Amanda-2.6.0p1)
I've just noticed something peculiar while doing a test restore. While
using amrecover to set a host and a disk, then for two hosts I've got
disklist entries being displayed which don't exist anymore (in fact,
they haven't existed since January 09). When doing a setdisk
On Monday 11 May 2009, Johan Booysen wrote:
(Amanda-2.6.0p1)
I've just noticed something peculiar while doing a test restore. While
using amrecover to set a host and a disk, then for two hosts I've got
disklist entries being displayed which don't exist anymore (in fact,
they haven't existed
Robert,
On Mon, Oct 06, 2008 at 10:16:29AM -0400, McGraw, Robert P wrote:
I want to be able to use a different disklist for different runs. Other than
use shell scripting to mv disklista to disklist is there a way to tell
amanda what disklist to use during a run.
What needs to remain the same
man amanda.conf:
diskfile string
Default: disklist. The file name for the disklist file
holding client hosts, disks and other client dumping
information.
You can use: amdump -odiskfile=disklista
Why do you want to do use different disklist file? You could have one
Can you put variable in disklist file? Like:
set disk=/computer/home/mydir/
host.mydomain ${disk}/backup1 comp-server-tar -1 eth2
Chen
On Wed, Sep 24, 2008 at 11:03 AM, Yu Chen [EMAIL PROTECTED] wrote:
Can you put variable in disklist file? Like:
set disk=/computer/home/mydir/
host.mydomain ${disk}/backup1 comp-server-tar -1 eth2
No -- the configuration syntax does not support that. You would have
to use some
On 23/09/2008 10:35 AM, Nigel Allen wrote:
Greetings
I am trying to restore an accidentally deleted disklist from a level 0
backup using amrecover.
Of course, when I try to start amrecover using amrecover DailySet1 -s
sydsrv08 -t sydsrv08 I get the following:
[EMAIL PROTECTED] tmp
in the disklist.
I'd really rather not have to put FQDN's in the disklist. Can anyone suggest
what I might have configured incorrectly that would be cause this behavior?
--
One of the main causes of the fall of the roman empire was that, lacking
zero, they had no way to indicate successful
in one domain, and I have the short names
in the disklist.
I'd really rather not have to put FQDN's in the disklist. Can anyone suggest
what I might have configured incorrectly that would be cause this behavior?
But do you have all those aliases in each machines /etc/hosts file? ISTR
that's all I had
I'm runing amanda on solaris 9 and fairly recently ran into
a situation where the drive (RAID array) was too large to fit
on a single volume of tape.
We resolved this by dividing the partition into segments and
using gtar for backups.
(for /maildb2/one through /maildb2/five)
wcnotes
Fellow AMANDA users,
In the past, I remember seeing something about AMANDA having trouble
when there are a large number of disklist entries. First, am I
remembering correctly, and second what constitutes a large number
of entries? My current backup plan is to have about 1500-2000 entries
Alan,
Could you send the amandad.timestamps.debug file?
You said all other client works, are they using the same amanda version?
Do they have one or more DLE?
Jean-Louis
Alan Pearson wrote:
Ok,
I've managed to get more info on this.
If I run amdump with the failing entry in the disklist
?
Jean-Louis
Alan Pearson wrote:
Ok,
I've managed to get more info on this.
If I run amdump with the failing entry in the disklist on it's
own, all is fine.
If put another entry from the same machine, the other entry
backups up fine, but the second will fail.
So it sounds like some sort
they have one or more DLE?
Jean-Louis
Alan Pearson wrote:
Ok,
I've managed to get more info on this.
If I run amdump with the failing entry in the disklist on it's
own, all is fine.
If put another entry from the same machine, the other entry
backups up fine, but the second will fail.
So
Ok,
I've managed to get more info on this.
If I run amdump with the failing entry in the disklist on it's own,
all is fine.
If put another entry from the same machine, the other entry backups
up fine, but the second will fail.
So it sounds like some sort of timing issue ?
Here's
Hi List
I'm having a really strange problem with one of my amanda clients
(that also happens to be the server).
It's got 2 disklists (separate filesystems), / and /usr
amcheck reports all ok
estimates come back fine.
/ backs up fine
/usr aborts as soon as it comes time to dump the
shows the following when I do a gtar --version:
tar (GNU tar) 1.15.1
Anything I need to be aware of with this version of GNU tar?
Thanks.
Perhaps I should clarify this message:
I tried to use wildcards both in the exclude and include contexts in
disklist stanzas, both with and without
in the exclude and include contexts in
disklist stanzas, both with and without trailing slashes. I seem to
be running into the same result each time. If I use the include
statement, nothing gets backed up with each stanza I use those wildcards
in. If I use excludes, everything gets backed up
Jean-Louis Martineau wrote:
Hi Ian,
Remove the trailling '/' from your include/exclude.
Jean-Louis
Hello.
Tried using includes again, and still I'm having the same problem. It's
backing up nothing. In fact, one item was still using the exclude
method and it still backed up everything.
looked at the /tmp/amanda/sendbackup.*.exclude files and the
exclusions are getting in as they should.
However, they're not being PARSED as they should be.
For each stanza, it backs up ALL five hundred directories. For the
entire disklist file, it would back up the hierarchy a complete five
in as they should.
However, they're not being PARSED as they should be.
For each stanza, it backs up ALL five hundred directories. For the
entire disklist file, it would back up the hierarchy a complete five
times. Apparently because it can't find the specified pathname
component(s) I'm specifying
Hello,
I am new to AMANDA but I like it very much but I didn't get a good answer from
all the documentation I read already and hope to get answers from the mailing
list now.
I use a Overland PowerLoader with a Ultrium LTO (400GB tape) device which
change the tapes automatically.
The clients
On Mon, 11 Sep 2006 at 4:27pm, Dominik Schips wrote
1. How can I tell AMANDA to start with the big directories first and then the
small directories?
As I have seen AMANDA allways starts with the smallest and then the next
biggest and so on.
'man amanda.conf' and look for the 'dumporder' and
On Mon, 11 Sep 2006 at 11:23am, Jon LaBadie wrote
On Mon, Sep 11, 2006 at 11:08:56AM -0400, Joshua Baker-LePain wrote:
Tape Time (hrs:min) 3:35 3:35 0:00
Tape Size (meg) 374733.9 374733.9 0.0
Tape Used (%) 194.1 194.1 0.0
On Mon, Sep 11, 2006 at 04:27:08PM +0200, Dominik Schips wrote:
Hello,
I am new to AMANDA but I like it very much but I didn't get a good answer
from
all the documentation I read already and hope to get answers from the mailing
list now.
I use a Overland PowerLoader with a Ultrium LTO
On Mon, 11 Sep 2006 at 11:41am, Jon LaBadie wrote
On Mon, Sep 11, 2006 at 11:28:29AM -0400, Joshua Baker-LePain wrote:
On Mon, 11 Sep 2006 at 11:23am, Jon LaBadie wrote
That tape write rate is too slow. Native speed for an LTO3 drive is
rated at ~80MB/s.
I think it is really an LTO2.
The
Hello all,
thank you Joshua, Cyrille and Jon for your very good and fast replies.
With this information I can have a closer look why everythink is so slow.
I'll send a message again if I tried some of your advices.
I try the dumporder as Joshua mentioned and the taperalgo that I found at
: Prefere a dump from the disklist and do several dumpes to
holding disk?
Hello,
I am new to AMANDA but I like it very much but I didn't get a good answer
from
all the documentation I read already and hope to get answers from the
mailing
list now.
I use a Overland PowerLoader
On Monday 11 September 2006 17:32, you wrote:
On 2006-09-11 16:27, Dominik Schips wrote:
Hello,
I am new to AMANDA but I like it very much but I didn't get a good answer
from all the documentation I read already and hope to get answers from
the mailing list now.
I use a Overland
On Mon, Sep 11, 2006 at 07:14:45PM +0200, Dominik Schips wrote:
For your information.
The holding disk is on another harddisk as the data harddisk to back up.
So the holding disk dumps are from a RAID5 (S-ATA) were the backup files
are to another harddisk.
I have to check them with bonnie
1 - 100 of 403 matches
Mail list logo
