Rodrigo Filgueira wrote:
I've defined three diferent configs, Monthly, Weekly and Daily. W and D
are working without a problem, but Monthly is generally done some day
between Monday and Friday.
Two things to watch out for:
1. I believe amanda _really_ doesn't like running more than
once
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I am located in China and, as far as I can tell, the amanda web site
(http://www.amanda.org/) is not accessible from here.
I am trying to get amanda running on a rh9 host, primarily using
http://www.harkness.co.uk/services/backup.html as my guide.
Max Waterman wrote:
When I get to this part :
su amanda -c /usr/sbin/amdump DailySet1
it seems to return quite quickly without any messages at all.
The normal way is to run amcheck first, fix everything
it complains about, before proceeding with a real amdump.
The error messages of amcheck are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Bijnens wrote:
| Max Waterman wrote:
|
| When I get to this part :
|
| su amanda -c /usr/sbin/amdump DailySet1
|
| it seems to return quite quickly without any messages at all.
|
|
|
| The normal way is to run amcheck first, fix everything
| it
hi,
I'm having 2 configuration of amanda :
- a DailySet crontab: monday-friday
- a WeeklySet crontab: saturday
since now I always used the same holding disk for both configurations
but what if the WeeklySet and the DailySet work at the same time...
could amanda deal with this or not ?
Phil Homewood wrote:
1. I believe amanda _really_ doesn't like running more than
once per day. At least in a single config. Having multiple
configs _might_ avoid her objections there though.
I've heard that a few times before, but I still don't quite understand
what the problems are
Max Waterman wrote:
Could it be that it's actually working, but doesn't give an output that
I am expecting - ie a list of files, or something that says 'I backed up
so many files' or even I'm done.
amdump doesn't generally (ever?) give output on stdout -- it
emails it.
BTW, email isn't
Hello,
using Amanda 2.4.4p2, I'd like to do daily full backups, no matter
what happens. I.e.: There are about 20 tapes, and humans (as opposed
to Amanda) are responsible for the correct tape beeing loaded before
each amdump run. If one forgets to change tapes the next run should
overwrite the
Alexander Jolk wrote:
Phil Homewood wrote:
1. I believe amanda _really_ doesn't like running more than
once per day. At least in a single config. Having multiple
configs _might_ avoid her objections there though.
I've heard that a few times before, but I still don't quite understand
what the
(Sorry, hit the send button by accident)
Alexander Jolk wrote:
Phil Homewood wrote:
1. I believe amanda _really_ doesn't like running more than
once per day. At least in a single config. Having multiple
configs _might_ avoid her objections there though.
I've heard that a few times before, but
Jukka Salmi wrote:
To achieve this I set dumpcycle and runspercycle to 0, and tapecycle
and runtapes to 1.
This seems to work so far, except for the planner being discontent:
NOTES:
planner: tapecycle (1) = runspercycle (1)
If I try this in amanda 2.4.4p3, then planner does not warn.
Have you
On Wed, 23 Jun 2004 at 10:38am, BRINER Cedric wrote
I'm having 2 configuration of amanda :
- a DailySet crontab: monday-friday
- a WeeklySet crontab: saturday
since now I always used the same holding disk for both configurations
but what if the WeeklySet and the DailySet
Joshua Baker-LePain wrote:
On Wed, 23 Jun 2004 at 10:38am, BRINER Cedric wrote
I'm having 2 configuration of amanda :
- a DailySet crontab: monday-friday
- a WeeklySet crontab: saturday
since now I always used the same holding disk for both configurations
but what if the WeeklySet and
Paul Bijnens -- amanda-users (2004-06-23 13:14:45 +0200):
Jukka Salmi wrote:
To achieve this I set dumpcycle and runspercycle to 0, and tapecycle
and runtapes to 1.
This seems to work so far, except for the planner being discontent:
NOTES:
planner: tapecycle (1) = runspercycle (1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Phil Homewood wrote:
| amdump doesn't generally (ever?) give output on stdout -- it
| emails it.
|
|
|BTW, email isn't configured on the host machine - perhaps it is telling
|me it is working, but I can't read what it says.
|
|
| That could well be the
Jukka Salmi wrote:
Paul Bijnens -- amanda-users (2004-06-23 13:14:45 +0200):
Jukka Salmi wrote:
To achieve this I set dumpcycle and runspercycle to 0, and tapecycle
and runtapes to 1.
This seems to work so far, except for the planner being discontent:
NOTES:
planner: tapecycle (1) = runspercycle
Max Waterman wrote:
Phil Homewood wrote:
| amdump doesn't generally (ever?) give output on stdout -- it
| emails it.
You can generate the email by hand and safe it in a file instead:
cd ~amanda/DailySet1
amreport DailySet1 -l log.X.X -f save-mail-file
At least if you have file named
Paul Bijnens -- amanda-users (2004-06-23 14:53:04 +0200):
In that case, yes, just ignore the note.
OK, I'll try that... But hmm, why does one get warned if
tapecycle = runspercycle? How could that be a problem?
Oops. I was wrong. The note is there indeed.
(why didn't I see that this
Jukka Salmi wrote:
OK, I'll try that... But hmm, why does one get warned if
tapecycle = runspercycle? How could that be a problem?
Because in a sane backup scheme you avoid to overwrite the last
good backup.
Actually, that is what's happening in your case when you don't
change the tape, and
Hello.
I've been running an Amanda Server (2.4.4p2) on Debian to backup 13 clients
(Debian machines as well).
I came to a challenge where I need to backup a Solaris 2.6 (sparc).
The amanda-client found on sunfreeware.com was installed properly:
amanda-2.4.1p1-sol26-sparc-local.gz
The problem
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:
Hi,
I'm running Amanda on a heterogeneous network. Server is a Linux box.
Some of the clients are Windows machines, and we're running Samba.
Mostly works OK, except that sometimes the Windows machines have errors
that look like the following:
? Call timed out: server did not respond after
Harlan Harris wrote:
I'm running Amanda on a heterogeneous network. Server is a Linux box.
Some of the clients are Windows machines, and we're running Samba.
Mostly works OK, except that sometimes the Windows machines have errors
that look like the following:
? Call timed out: server did not
Greetings all;
I'm back from a week out in Nebraska, getting a son married off. I
hope that you didn't get too many bounces as my mailbox was full when
I got X running again, which had died due to my changing the default
prompt in bash, which in turn screwed up the X startup, it would get
to
--On Wednesday, June 23, 2004 13:56:27 -0400 Gene Heskett [EMAIL PROTECTED] wrote:
Greetings all;
I'm back from a week out in Nebraska, getting a son married off. I
hope that you didn't get too many bounces as my mailbox was full when
I got X running again, which had died due to my
I have the exact opposite problem. I have some error indications that I'd like to
ignore, as they consistently happen and don't mean that there's a problem, if I
understand them correctly. Here's two examples:
/-- admin //db/f$ lev 0 STRANGE
sendbackup: start [admin://db/f$ level 0]
On Wednesday 23 June 2004 14:30, Frank Smith wrote:
--On Wednesday, June 23, 2004 13:56:27 -0400 Gene Heskett
[EMAIL PROTECTED] wrote:
Greetings all;
I'm back from a week out in Nebraska, getting a son married off.
I hope that you didn't get too many bounces as my mailbox was full
when I
28 matches
Mail list logo
