Hello,
Using amanda-2.4.2p2 I got an error from the planner telling me
planner: FATAL error [planner askfor: lev out of range -1..10: 10]
- the maximum dump level is 9, so the message should be
... lev out of range -1..9: 10]
^
- how can this happen? Bug? My
Hello,
Does the netusage parameter in amanda.conf really work ? I am asking this
because I have changed it to 50 kByte/s and still see the backups taking
the same amount of bandwidth on the MRTG graphs of the backup server...
Regards
Marc
hi jerry,
i've been using an ex17 autoloader under various version of solaris (2.6
and 8) for the past 3 years. you WILL need to modify
/kernel/drv/sgen.conf so that the device will be recognized, you
basically need to add the following lines:
device-type-config-list=changer;
name=sgen
On Mon, Oct 07, 2002 at 09:01:09AM +0200, Roman Fietze wrote:
Hello,
Using amanda-2.4.2p2 I got an error from the planner telling me
planner: FATAL error [planner askfor: lev out of range -1..10: 10]
- the maximum dump level is 9, so the message should be
... lev out of range
Frank Smith wrote:
--On Friday, October 04, 2002 18:05:59 +0200 Marcus Huedepohl
[EMAIL PROTECTED] wrote:
2. how do i rename an amanda configuration? let's say from TestSet to
DailySet1?
You could also just create the DailySet1 directory, make a copy
of your disklist and amanda.conf,
On Sunday 06 October 2002 12:27, Gene Heskett wrote:
On Sunday 06 October 2002 11:02, Gene Heskett wrote:
On Sunday 06 October 2002 10:23, Gene Heskett wrote:
This may now be a case of the little boy who cryed wolf.
8-(
I just discoverd that this early 10/05 date also corresonds to my
adding a
ok. My sgen.conf has this basically:
device-type-config-list=
changer (type 0x08)
name=sgen class=scsi target=0 lun=0;
name=sgen class=scsi target=1 lun=0;
name=sgen class=scsi target=2 lun=0;
name=sgen class=scsi target=3 lun=0;
name=sgen class=scsi target=4 lun=0;
ok.
I got it... I changed the sgen.conf so instead of:
changer (type 0x08)
which was already in there, I have:
changer
Thanks a bunch... now I can play with mtx and see how
well it works and continue to read the docs on making
it work with amanda. Just had to
comment all lines in sgen.conf with the exception of
device-type-config-list=changer;
name=sgen class=scsi target=0 lun=0;
then unload the module and run devsfadm again. if devfsadm didn't error
with failed to attach then is should create the device files. i'm
guessing it's not there due to
Greetings.
I'm still confused with the configuration of the tapes, runs, and days.
Basically I want a full backup every night at 8pm. I have 5 tapes, and I
only want the backups on the weeknights. ie. mon-fri. I've configured
the cron to do that much, but I don't understand how to get amanda to
On 7 Oct 2002 at 2:16pm, Thom Paine wrote
Basically I want a full backup every night at 8pm. I have 5 tapes, and I
only want the backups on the weeknights. ie. mon-fri. I've configured
the cron to do that much, but I don't understand how to get amanda to d
oa full backup every night. Do I
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
charset=US-ASCII;
On Mon, 2002-10-07 at 14:32, Joshua Baker-LePain wrote:
Set dumpcycle to 0, and tapecycle to 5. runspercycle doesn't matter, but
you can just set it to 1.
Thanks Joshua.
That worked great.
--
-=/Thom
Red Hat Linux release 8.0 (Psyche) running Linux Kernel 2.4.18-14
Uptime: 2:35pm up
Our amanda has started skipping directories that is has left on the
holding disk when it has run out of tape. The error I get with amflush
daily is
Scanning /var/local/amanda/temp/hold-disk4...
: skipping cruft directory, perhaps you should delete it.
: skipping cruft directory, perhaps
On 7 Oct 2002 at 2:56pm, Thom Paine wrote
How can I exclude /tmp and /var/tmp from being backed up? I would guess
that I wouldn't need the contents of those directories backed up every
night.
That depends. What are your disklist entries? Are you using dump or tar?
What is the output of
On Mon, 2002-10-07 at 15:15, Joshua Baker-LePain wrote:
That depends. What are your disklist entries? Are you using dump or tar?
What is the output of df?
localhost / comp-root-tar
localhost /boot comp-root-tar
[root@mail DailySet1]# df -h
FilesystemSize Used Avail Use%
Hello,
The Amanda core team is pleased to announce the release of Amanda
2.4.3.
It can be dowloaded from http://www.amanda.org/
Here's a list of the changes for release 2.4.3 (from the NEWS file):
Look at the ChangeLog file for more details.
* New runtapes argument to amverify.
* New
On Monday 07 October 2002 15:22, Thom Paine wrote:
On Mon, 2002-10-07 at 15:15, Joshua Baker-LePain wrote:
That depends. What are your disklist entries? Are you using
dump or tar? What is the output of df?
localhost / comp-root-tar
localhost /boot comp-root-tar
Give it the FQDN please,
I have a 140G RAID5 array that I would like to back up to my 20/40 DDS4
Seagate drive.
Without a lot of experience with a drive this large, I've made a 100M
/boot partition, a 2G swap partition (I have 1G of ram), and finally the
rest of the drive ~137G set to /.
I've allocated 20G to /tmp for
Just a recommendation (outside of backup really) but
you should make your 137G LVM controlled so you have
to power to control where it goes. I would make /
like 5 GB or whatever you like, but use the rest of
the space for various filesystems like /home /database
/usr/local and make them LVM
My backups have recently slowed down...
It is very peculiar and just started recently what seems to be out of
the blue. The network clients are backing up at full speed but the file
systems on the dump-host itself have slowed to about one quarter of
their normal speed. I am using dump (as
How do I unsubscribe from this mailing list?
I have observed the same thing on several Linux boxes. It seems
to be a result of the changes made to the virtual memory manager
code in the mid 2.4 kernel series when using multiple processors.
2.4.7 sounds like about the time it started, but I don't remember
exactly. We actually killed
23 matches
Mail list logo
