Hey everybody, i have tryed to get this software to run on a linux
file-server, i have a DLT7 Autoloader from Tandberg on a Adaptec 2940u2w SCSI
controller.
The problom is, that i cannot load any tapes into the tape device, e.g.
bash-2.04$ chg-scsi -slot 0
DeviceCapabilitiesPage == NULL
bash
Hi,
on my private box at home, I have some drives with more diskspace
than the holding disk is able to hold. I already put some
directories directly into the disklist, but it's not really nice as
it is now, since even the directories can be larger than 6GB (the
holding disk is actually big enough
Hi,
I just recently started using Amanda across a Linux/AIX/Solaris/NT/2000
environment.
We have an arrangement where the Amanda server (Compaq DL380, RAID array,
DLT-8000, RH 7.0, Amanda 2.4.2p2 + the client patch) happily does nightly
backup across all the machines.
What I would like to do is
Brilliant!!
That was all it was, I added "groups = yes" and restarted xinetd and it's
working fine. Many thanks to you and to David for taking the time to help me
out!
Tyrone
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of John R. Jackson
Sent: Monday,
>I have thirty tapes in my tape cycle. I want to be certain to get TWO
>level zero dumps of each file system in this tape cycle. Is this as
>simple as having my dumpcycle equal to "15"? (leaving out extra tapes
>for the moment...)
That's pretty much correct.
Actually, what you want is 15 runs
>I just did a level 0 backup (an erroneous one) Friday night. I've got
>incrementals rarin' to go every night this week. Should I just change
>disklist in both config directories to reflect the mount point and
>amanda will start acting correctly? ...
It depends on what you mean by "correctly".
Hello,
I am suffering a bit from terminology shock. Here's what I want to
know:
I have thirty tapes in my tape cycle. I want to be certain to get TWO
level zero dumps of each file system in this tape cycle. Is this as
simple as having my dumpcycle equal to "15"? (leaving out extra tapes
for
* "John R. Jackson" <[EMAIL PROTECTED]>, 17:39 04/30/2001:
> Short answer -- don't do that. Only do complete file systems with
> ufsdump.
ahhh... that makes sense. So if you don't specify a whole partition,
ufsdump or tar jumps into another mode. Whew!
alright, my final question and I'll leav
>
> >Am I
> >correct, and if so how do I force amanda to do a full on the same day
> >every week?
>
> Why would you want to do that?
>
Here's one example: You're backing up a number of customer servers over
relatively slow WAN connections. A full backup takes 18 hours, and you
don't want to cho
>Below are the two pertinant parts (I think) of an error that is occuring on
>an everyday basis on this server. ...
What version of Amanda? Same version on client and server?
>... There are 11 other servers that are being backed up
>just fine but this one just does not want to work. ...
So w
>Lately I've been having severe problems with amflush. ...
What version of Amanda?
>*** A TAPE ERROR OCCURRED: [[writing file: Bad file descriptor]].
Did you run this in the background (without the -f flag)? Do you have
an amflush.NN file in the amanda.conf directory? What's in it?
If you u
>It went from 3 -> 0 -> 0 -> 3. Did amanda just give up and go to a level
>it believed it could complete?
No. I suspect it "promoted" (moved earlier in the cycle) the two
level 0 attempts because there was room on the tape, it fit within
the balance, etc. But on the fourth day other priorities
> >[the level 0] completly fails.
>
> What incremental level did Amanda do the next day? Did it go back to 1,
> or did it repeat whatever it had been doing before the full?
>
Check this out. I received this in the mail: (my real hostname removed)
Day one:
FAILURE AND STRANGE DUMP SUMMARY:
hos
>Can the image on no-reuse tape be recovered using
>amrecover/restore?
I would have thought so, but haven't tried this.
>amadmin
>does not return stats for the no-reuse tape.
Are you sure it's because the tapes are marked "no-reuse"? I looked at
the code for a few minutes and don't see
>oh, another tidbit of info. ...
Aha! The truth finally comes leaking out ... :-)
>Like I said, my mount point on that slave
>machine is /export, but I've got /export/data in my disklist file.
Short answer -- don't do that. Only do complete file systems with
ufsdump.
>Under that directory e
> >Yes. The partition that's having the problem is nfs mounted, however
> >amanda is calling its daemon on the remote machine to back it up (ie,
> >not thru nfs). At least that's what I'm assuming is happening.
>
> Let me make sure I've got this clear. The host you gave to Amanda has
> the "
>I am using tar. Where is this info about each file backed up saved, in
>the amanda db file?
Amanda has nothing to do with it (well, very little). This is purely
up to the backup program.
For dump, it's stored in /etc/dumpdates. For tar, Amanda tells it to keep
"listed-incremental" files in t
Can the image on no-reuse tape be recovered using
amrecover/restore?
How can I get the stats on a no-reuse tape other than loading the tape in
the tape drive? Which I can do need be.
amadmin
does not return stats for the no-reuse tape.
The stats I am looking for on this tape are:
level 0
>I get an error when I copy over my 2.4.1 configs to 2.4.2 and try to
>run amcheck:
>
> amcheck-server: could not get changer info: cannot open \
> /opt/pkgs/amanda/etc/phg-weekly/changer.conf
>
>I don't reference a `changer.conf' file in any amanda.conf file. I do
>reference chg-zd-mtx, t
On Mon, 30 Apr 2001, John R. Jackson wrote:
> >1) When I run an amflush I notice that the dump are put on tape starting
> >with the smallest and working its way up to the largest last. Why is
> >this?
>
> I suspect the theory is to get as many images safely out to tape as
> quickly as possible.
> So, what's the question? What do you mean by "the configs don't seem to
> be compatible"? As far as I know, 2.4.2 is upward compatible with 2.4.1.
> The only amanda.conf variable I can think of that isn't is a negative
> value for "use" in the holding disk section.
I get an error when I copy
Hello all,
Lately I've been having severe problems with amflush. Using tar 1.13.17,
amdump runs fine, when I forget to change the tape, it backs up to the
holding disk without a problem (the STRANGEness is socket ignored, etc.):
*** A TAPE ERROR OCCURRED: [cannot overwrite active tape daily14].
>ERROR: stats_db: [can not access /dev/sdb1 (/dev/sdb1): Permission denied]
>
>I've created an user called amanda and a group called backup on the client
>and server machines. The amanda user is in the disk group as a secondary
>group on the client machine.
In addition to the good ideas David gav
>1) When I run an amflush I notice that the dump are put on tape starting
>with the smallest and working its way up to the largest last. Why is
>this?
I suspect the theory is to get as many images safely out to tape as
quickly as possible.
Would you prefer it was done some other way? Why?
>2)
> I just recently set up Amanda on a machine here ...
What kind of machine (OS and level)? What version of Amanda?
What does amcheck say?
If this is Linux and Amanda 2.4.2 and it whines about /dev/root, you may
need to upgrade to 2.4.2p2. That fixes some problems with the /etc/fstab
LAB
Hello,
I have three questions about how amanda operates:
1) When I run an amflush I notice that the dump are put on tape starting
with the smallest and working its way up to the largest last. Why is
this?
2) When an incremental runs does it do the incremental based on what was
on the drive at
>Just wanted to share these two tapetypes that was produced by the tapetype
>program for 60 meter and 90 meter DDS1 on a HP35480A 1009 drive. ...
Thanks! Would you mind posting those to the FAQ at www.amanda.org?
>Johan
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
>... I also have tried upgrading amanda to a
>recent version, but the configs don't seem to be compatible going from
>2.4.1p1 to 2.4.2p2 (question in and of itself).
So, what's the question? What do you mean by "the configs don't seem to
be compatible"? As far as I know, 2.4.2 is upward compat
Below are the two pertinant parts (I think) of an error that is occuring on
an everyday basis on this server. Amcheck runs just fine, it just does not
work on this server. There are 11 other servers that are being backed up
just fine but this one just does not want to work. I recently upgraded the
I just recently set up Amanda on a machine
here and had it go through a full system backup. I have
it set up (in the disklist file) to do dumps of every disk
partition on the localhost. It appears to run just fine for
every partition but the root partition. For this one, I get the
follo
30 matches
Mail list logo
