d'oh ... I read through docs/INSTALL, saw the 'readable disk devices' and
went braindead and combined 'changer/tape' with 'disk devices' ...
damn, I need a holiday away from computers :(
On Tue, 19 Dec 2000, David Wolfskill wrote:
> >Date: Wed, 20 Dec 2000 00:37:20 -0400 (AST)
> >From: The Her
>Date: Wed, 20 Dec 2000 00:37:20 -0400 (AST)
>From: The Hermit Hacker <[EMAIL PROTECTED]>
>can someone point me at what I'm not seeing here? OS is FreeBSD
>5.0-CURRENT ... everything looks normal to me, I think ...
>%amcheck hub.org
>Amanda Tape Server Host Check
>-
can someone point me at what I'm not seeing here? OS is FreeBSD
5.0-CURRENT ... everything looks normal to me, I think ...
%amcheck hub.org
Amanda Tape Server Host Check
-
Holding disk /usr/local/mp3/amanda: 5348401 KB disk space available, using 5297201 KB
amcheck-
> You are probably right about the first problem, it should be permissions.
> You can check the permissions of the disk device with the command `ls -l
> /dev/hda`. The amanda backup user, or a group the amanda backup user is a
> member of, needs to have read access to this device to back it up.
[
In a message dated: Tue, 19 Dec 2000 15:50:50 MST
George Kelbley said:
>Actually the clouds are beginning to clear, we figured this out earlier
>today,
Doh! I had started to compose this e-mail early this morning but got
distracted and forgot to send it :)
>however we still can't seem to get
Given my results with one particular file system I
don't think I understand dump/run/tape cycle.
My configuration (2.4.2) has these settings:
dumpcycle 1 weeks
runspercycle6
tapecycle 18 tapes
Does this mean that given a level 0 today, the
next leve
Hmm...
> couple of choices to fix this: You could just let it ride, knowing that that
> disk isn't getting backed up, and sometime in the next few tapes, AMANDA
> might have enough space (because other disks backups get bumped to higher
> incremental levels) to do the level 0 backup; OR, you cou
Justin!
> The first one started to occur after rebuilding my Tape Backup Server after
> a Hard Disk Crash. I changed it from a SCSI disk to a IDE disk. Now when
> ever it goes to dump any of the file systems on that system (sol), it gives
> this in the AMDUMP report:
> solhda1 lev 0
You are probably right about the first problem, it should be permissions.
You can check the permissions of the disk device with the command `ls -l
/dev/hda`. The amanda backup user, or a group the amanda backup user is a
member of, needs to have read access to this device to back it up.
For the
I have been receiving 2 different errors lately.
The first one started to occur after rebuilding my Tape Backup Server after
a Hard Disk Crash. I changed it from a SCSI disk to a IDE disk. Now when
ever it goes to dump any of the file systems on that system (sol), it gives
this in the AMDUMP re
Sandra Panesso <[EMAIL PROTECTED]> writes:
> Hi Everybody:
>
> size is 5.3 Gb and my tape doesn't have enough space. Somebody told me
> that I had to do amflush many times until my holding disk cleaned out
> but I have used four tapes ( so I did four times amflush) is it
> normal? or do I have
In a message dated: Tue, 19 Dec 2000 09:10:00 MST
George Kelbley said:
>Thanks, however I'm still confused. The question is how to create the
>/dev/chg device, we have the generic scsi stuff turned on, however our
>makedev script doesn't know how to create a changer device :(. I mean
>our scsi
Hi Everybody:
I know that I did this question before but I still have problems with
amflush. I am trying to amflush my data from my holding disk, the data
size is 5.3 Gb and my tape doesn't have enough space. Somebody told me
that I had to do amflush many times until my holding disk cleaned ou
Hello,
I'm under the impression that the tape type list in Amanda is
very short, especially when thinking of current drives...
Ok, here is one for the popular SLR-6 drives (aka SLR-24).
I didn't test this, it's only from spec (yet).
define tapetype SLR6-24 {
comment "SLR6-24"
length 2
On Tue, Dec 19, 2000 at 07:42:34AM -0800, David Wolfskill wrote:
> But I saw something during the backups from this morning that may be
> related.
That's not related :-)
> eng-backup# amstatus Eng --failed --summ
> Using /var/log/amanda/Eng/amdump from Tue Dec 19 01:53:00 PST 2000
>
> shrimp:/s
>From: "ROD" <[EMAIL PROTECTED]>
>Date: Tue, 19 Dec 2000 15:36:31 -
>I just got around to installing Amanda-2.4.2 stable unfortunately I can't
>get it to build on FreeBSD 4.11. The following error is reported:
>make: don't know how to make amoverview. Stop
>*** Error code 1
>Any help would
ROD-
If I remember the previous discussion properly, Amanda seems to tickle a bug
in the FreeBSD "make" program. You might try again with GNU make (installed
as /usr/local/bin/gmake or available in the ports as devel/gmake).
-Ben
--
Benjamin LewisThank goodness modern
On Tue, Dec 19, 2000 at 10:00:23AM +0100, David Klasinc wrote:
> Banzai!
>
> I upgraded to 2.4.2 and I noticed that if dump won't fit on one disk that
> amdump will go into endless loop trying to do a backup.
Could you try this patch?
Jean-Louis
--
Jean-Louis Martineau email: [EMA
David Wolfskill [EMAIL PROTECTED] UNIX System Administrator
Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823
driver: send-cmd time 15155.688 to dumper0: CONTINUE
/hd/tmp1/20001219/shrimp._shrimp_home.0 1945600 15712
driver: state time 15155.692 free kps: 1180069 space: 23077320 t
I just got around to installing Amanda-2.4.2 stable unfortunately I can't
get it to build on FreeBSD 4.11. The following error is reported:
make: don't know how to make amoverview. Stop
*** Error code 1
Any help would be appreciated
Best regards
Rod
In a message dated: Mon, 18 Dec 2000 18:54:20 EST
Mitch Collinsworth said:
>Well don't let that stop you. Get on amanda-users and ask. Someone
>will know how. I haven't done it on Linux myself yet, but plenty of
>people have.
>
>-Mitch
>
>
>On Mon, 18 Dec 2000, George Kelbley wrote:
>
>> Yeah,
Hi
We set up a new amanda-2.4.2 backup-server, and right now I'm involved in
testing
the backup and recover with the server.
While testing amrecover, some strange behaviour showed up:
I'm unable to see all backed up files while browsing trough the directorys
via amrecover, but viewing the index-f
I always get messages like
? gtar: ./var/spool/postfix/private/bounce: socket ignored
in the daily amanda mail report. Is there a way to tell gtar not to complain
about sockets instead of just excluding them from the backup?
Thanks in advance,
Thomas
--
Dr.-Ing. Thomas Ziegler
Hi!
We're considering swithing to Amanda for backup. We have an Exabyte 480
Tape Library with 4 tape drives, a robot tape-changer and a barcode
reader.
Has anyone got any experience with using Amanda together with a barcode
reader? From the documentation it seems like 'amlabel' is used only to
David Klasinc wrote:
> Banzai!
>
> I upgraded to 2.4.2 and I noticed that if dump won't fit on one disk that
> amdump will go into endless loop trying to do a backup.
>
> If this was already mentioned I apologize for spam. :)
>
> This is a small part of amdump log (it was running like this whole
Banzai!
I upgraded to 2.4.2 and I noticed that if dump won't fit on one disk that
amdump will go into endless loop trying to do a backup.
If this was already mentioned I apologize for spam. :)
This is a small part of amdump log (it was running like this whole night):
driver: result time 3370
26 matches
Mail list logo