>
> And, actually, we did not yet see how many times this DLE
> was dumped with level 0.
>
> Can you post the output of "amadmin config balance" and
> "amoverview config" (or mail it to me if it contains
> too much private information).
>
>
[EMAIL PROTECTED] root]# amadmin IS balance
due-da
Thomas Widhalm schrieb:
> [EMAIL PROTECTED] root]# amadmin IS balance
>
> due-date #fsorig KB out KB balance
> --
> 3/16 Thu0 0 0 ---
> 3/17 Fri0 0 0 ---
> 3/18 Sat0 0
Hi all:
Env - Fedora Core 4
Amanda Version: amanda-2.4.5p1
I'm using a test platform that consist of an intranet server (VEGA)
and my test pc (SSPC020) *both running FC4. The intranet server is the
master host, using the vtapes configuration as set out in Chapt
13:File
On 2006-03-16 09:12, Thomas Widhalm wrote:
And, actually, we did not yet see how many times this DLE
was dumped with level 0.
Can you post the output of "amadmin config balance" and
"amoverview config" (or mail it to me if it contains
too much private information).
[EMAIL PROTECTED] root]# a
On Thu, 2006-03-16 at 10:32 +0100, Paul Bijnens wrote:
> On 2006-03-16 09:12, Thomas Widhalm wrote:
> >> And, actually, we did not yet see how many times this DLE
> >> was dumped with level 0.
> >>
> >> Can you post the output of "amadmin config balance" and
> >> "amoverview config" (or mail it to
On 2006-03-15 18:05, Thomas Widhalm wrote:
||
|| inparallel 1
Only now my eye fell on this one here.
This is not about balancing your level 0 dumps, but with
"inparallel 1", you are not using any possibility
to do things in parallel, a very useful feature in Amanda.
From my archive run in the
Jon LaBadie wrote:
Is your root FS used for other, non-file storage, things as well?
no
For example, have you allocated some swap space there.
Swapping is only to swap partitions.
Is that
the file system that also is used for making pipes. Are some
files opened and immediately removed b
On 2006-03-16 12:02, listrcv wrote:
planner: prometheus /home 20060315 0 [dump larger than tape, 101387063
KB, full dump delayed]
Backups should automatically spread across multiple tapes in case they
don't fit onto one tape. That's why we are using a tape changer.
In 2.4.X a single dump
Hi,
how do I split partitions to get smaller dumps? I have two partitions
that are too large to be backed up to one tape as a whole. Backups are
to a tape changer, so once a tape is full, amanda should automtically
change to the next tape and continue the backup run.
As far as I've been rea
Hi,
As far as I've been reading here and in the docs, I would have to set up
dumptypes using tar and exclude lists. I would somehow backup
/home/[a-c]*, /home/[d-f]* and so on.
But that doesn't seem to be a good solution. I would have to create 10
different dumptypes and 10 exclude lists to
Paul Bijnens wrote:
On 2006-03-16 12:02, listrcv wrote:
planner: prometheus /home 20060315 0 [dump larger than tape,
101387063 KB, full dump delayed]
Backups should automatically spread across multiple tapes in case they
don't fit onto one tape. That's why we are using a tape changer.
Alexander Jolk wrote:
Don't forget that you can define exclude patterns inline in your
disklist file:
srv1/homes/acomp-user-tar 1
srv1/homes/bcomp-user-tar 1
srv1/homes/ccomp-user-tar 1
[...etc...]
srv1/homes/zcomp-user-tar 1
srv1/homes {
comp-user-tar
On 2006-03-16 13:48, listrcv wrote:
prometheus:/tmp/xxx# tar -cf test.tar -T include .
When using -T you should not specify a list of things
to backup on the command line as well, i.e. omit the final dot.
Maybe I just have to try it out ... :/
Yes, indeed!
--
Paul Bijnens, xplanation Te
Alexander Jolk wrote:
srv1/homes/zcomp-user-tar 1
srv1/homes {
comp-user-tar
exclude append "./[a-z]"
} 1
No need to define a proper dumptype for every exclusion under the sun.
Do you think this one will work?
# the backup of home is getting larger when compressed
pr
On Thursday 16 March 2006 04:32, Paul Bijnens wrote:
[...]
>The "reserve 30" will Amanda force in doing only 60% of free
> holdingdisk for level 0, and the rest for incrementals.
>
>Note that those 30% is calculated each run again, based on the current
>available space in the holdingdisk: if you st
On 2006-03-16 14:12, listrcv wrote:
Alexander Jolk wrote:
srv1/homes/zcomp-user-tar 1
srv1/homes {
comp-user-tar
exclude append "./[a-z]"
} 1
No need to define a proper dumptype for every exclusion under the sun.
Do you think this one will work?
No, several errors!
On Thursday 16 March 2006 04:23, Peter Farrell wrote:
>Hi all:
>
>Env - Fedora Core 4
>Amanda Version: amanda-2.4.5p1
>
>I'm using a test platform that consist of an intranet server (VEGA)
>and my test pc (SSPC020) *both running FC4. The intranet server is the
>master ho
Paul Bijnens wrote:
On 2006-03-16 13:48, listrcv wrote:
prometheus:/tmp/xxx# tar -cf test.tar -T include .
When using -T you should not specify a list of things
to backup on the command line as well, i.e. omit the final dot.
Oh! :)
Maybe I just have to try it out ... :/
Yes, indeed!
Paul Bijnens wrote:
Try this:
prometheus /home/ALL_a /home {
tar-dfault-no-x
include "./a*"
} 1
prometheus /home/ALL_b /home {
tar-dfault-no-x
include "./b*"
On 2006-03-16 14:55, listrcv wrote:
[EMAIL PROTECTED]:~$ man amanda.conf
No manual entry for amanda.conf
The whole doc is online too:
http://wiki.zmanda.com/index.php/Amanda#DISKLIST_FILE
--
Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511
Technologielaan 21 bus 2, B
Paul Bijnens wrote:
The whole doc is online too:
http://wiki.zmanda.com/index.php/Amanda#DISKLIST_FILE
That's great :) I've been looking on amanda.org and was even thinking
they should better have a wiki ... :)
GH
On Thu, Mar 16, 2006 at 10:43:30AM +0100, Thomas Widhalm wrote:
> On Thu, 2006-03-16 at 10:32 +0100, Paul Bijnens wrote:
> > On 2006-03-16 09:12, Thomas Widhalm wrote:
> > >
> > > [EMAIL PROTECTED] root]# amadmin IS balance
> > >
> > > due-date #fsorig KB out KB balance
> > >
On Thursday 16 March 2006 08:55, listrcv wrote:
> That is what I was looking for, a description of the disklist format.
> But I'm lacking the manpage:
If you installed amanda with --prefix, then the manpages will also be
installed in that --prefix, which may not be in your manpath.
On my system,
On 2006-03-16 15:37, Ian Turner wrote:
On Thursday 16 March 2006 08:55, listrcv wrote:
That is what I was looking for, a description of the disklist format.
But I'm lacking the manpage:
If you installed amanda with --prefix, then the manpages will also be
installed in that --prefix, which may
On Thu, Mar 16, 2006 at 09:23:47AM +, Peter Farrell wrote:
> Hi all:
>
> Env - Fedora Core 4
> Amanda Version: amanda-2.4.5p1
>
...
> Thanks very much for any input.
> It's fun - but the learning curve feels similar to Nagios at this
> point. (aka 'fiddly' :-)
Peter I'll try to reply to you
On Thu, Mar 16, 2006 at 02:52:06PM +0100, listrcv enlightened us:
> Paul Bijnens wrote:
> >On 2006-03-16 13:48, listrcv wrote:
> >
> >>prometheus:/tmp/xxx# tar -cf test.tar -T include .
> >
> >
> >When using -T you should not specify a list of things
> >to backup on the command line as well, i.e. o
Ian Turner wrote:
If you installed amanda with --prefix, then the manpages will also be
installed in that --prefix, which may not be in your manpath.
It's just a Debian package I installed. Maybe they have an extra package
for some of the manpages, but I rather think they didn't include it in
On Thu, Mar 16, 2006 at 02:55:53PM +0100, listrcv wrote:
>
> >See "man amanda.conf" for the syntax of a disklist entry.
>
> That is what I was looking for, a description of the disklist format.
> But I'm lacking the manpage:
>
>
> [EMAIL PROTECTED]:~$ man amanda.conf
> No manual entry for aman
On 3/15/06, Mitch Collinsworth <[EMAIL PROTECTED]> wrote:
>
> On Wed, 15 Mar 2006, Jean-Louis Martineau wrote:
>
> > That'a not fixed in 2.5.0, that will be done after the dumper-api get
> > implemented.
>
> dumper-api? I thought the story was that's being replaced with
> application-api.
>
> In a
On Thu, 2006-03-16 at 09:27 -0500, Jon LaBadie wrote:
> On Thu, Mar 16, 2006 at 10:43:30AM +0100, Thomas Widhalm wrote:
> > On Thu, 2006-03-16 at 10:32 +0100, Paul Bijnens wrote:
> > > On 2006-03-16 09:12, Thomas Widhalm wrote:
> Should you decide to consolidate, I'd recommend you NOT
> do it all
Thanks you gentlemen all - for your comments and advice.
The advice to RTFM is understood and well taken.
The clarification as to the prepending of my exclude list especially...
My hosts are set up and the backups ran smoothly - all reports minus
"AMANDA MAIL REPORT FOR BogusMonth 0, 0" ran fine.
On Thu, Mar 16, 2006 at 04:41:04PM +, Peter Farrell enlightened us:
> Thanks you gentlemen all - for your comments and advice.
> The advice to RTFM is understood and well taken.
> The clarification as to the prepending of my exclude list especially...
>
> My hosts are set up and the backups ra
On Thu, Mar 16, 2006 at 11:50:26AM -0500, Matt Hyclak enlightened us:
> The clients are trying to contact themselves for the index service. I
> suspect that means you are using distro-provided RPMs and they have
> localhost compiled as the index server.
>
I meant distro-provided packages. No off
*Matt - sorry didn't mean to respond to your personal address.
-pf
On 16/03/06, Peter Farrell <[EMAIL PROTECTED]> wrote:
> Nice one Matt :-)
> I compiled from source... but I'll rebuild it with the option that
> points each client to a predifined index server. Thanks for the tip...
>
> Is this out
On 2006-03-16 18:06, Peter Farrell wrote:
*Matt - sorry didn't mean to respond to your personal address.
-pf
On 16/03/06, Peter Farrell <[EMAIL PROTECTED]> wrote:
Nice one Matt :-)
I compiled from source... but I'll rebuild it with the option that
points each client to a predifined index server
Dave Ewart schrieb:
> On Wednesday, 08.03.2006 at 10:27 -0500, Ian Turner wrote:
>
>> Please
>> try upgrading your tar and check if you still see this behaviour.
>
> OK, you've hit the nail on the head:
>
> Using the existing system tar:
>
> $ tar --version
> tar (GNU tar) 1.14
> And u
On 2006-03-16 18:37, Stefan G. Weichinger wrote:
Dave Ewart schrieb:
On Wednesday, 08.03.2006 at 10:27 -0500, Ian Turner wrote:
Please
try upgrading your tar and check if you still see this behaviour.
OK, you've hit the nail on the head:
Using the existing system tar:
$ tar --version
Paul Bijnens schrieb:
>> Why not implement some check-routine into Amanda that checks for the
>> installed tar-release and gives a WARNING if a well-known problematic
>> release is found?
>
> That would give a lot of false positives.
>
> RedHat for example backports important bugfixes to earlier
Anthony Valentine wrote:
Hello everyone!
I am having an odd issue with amverify and amrecover and am wondering if
anyone can tell me why?
Using 2.5.0b2 (upgraded from 2.4.2), the amdump seems to run fine,
without any errors in the status e-mail, but I am getting some strange
output when run
Anthony Valentine wrote:
Anthony Valentine wrote:
Hello everyone!
I am having an odd issue with amverify and amrecover and am wondering
if anyone can tell me why?
Using 2.5.0b2 (upgraded from 2.4.2), the amdump seems to run fine,
without any errors in the status e-mail, but I am getting some
On Thu, Mar 16, 2006 at 06:10:11PM +0100, Paul Bijnens wrote:
> On 2006-03-16 18:06, Peter Farrell wrote:
> >*Matt - sorry didn't mean to respond to your personal address.
> >-pf
> >
> >On 16/03/06, Peter Farrell <[EMAIL PROTECTED]> wrote:
> >>Nice one Matt :-)
> >>I compiled from source... but I'l
41 matches
Mail list logo