>Question: Can amanda work as a tape manager for machines that
>share a tape device (or tape library)?
That depends entirely on the underlying OS. All Amanda does is issue
plain file system operations (open, read, write, close) and a few well
defined ioctl's (fsf, rewind, etc). If your OS does
On Dec 14, 2000, "Dave Heafey" <[EMAIL PROTECTED]> wrote:
> that would work if amdump and "command" needed to run on the
> same system. In my configuration, amdump runs on the Amanda
> Server and "command" needs to run on an Amanda client.
In this case, you'd have to configure the client to use
unsubscribe [EMAIL PROTECTED]
Ruksana Siddiqui
office: 03-9246-4848
mobile : 0419-342624
On Dec 13, 2000, Phil Davis <[EMAIL PROTECTED]> wrote:
> I dont have any amandad.debug files anywhere on dhcp or on the main
> backup server is this a config option maybe that I dont have
> running? or is it somewhere besides /var/log/amanda or /var/log or
> /etc/amanda? I have looked there and
>Is there a way to run a "pre-backup" script or command prior to Amanda
>starting the backup?
As others have described, the easiest way is to run a wrapper script
from cron around a command that can reach out to the client and do what's
needed and then run amdump. Mine is in:
ftp://gandalf.cc
> dhcp /dev/ida/c0d0p6 lev 0 FAILED [disk /dev/ida/c0d0p6 offline on dhc
>p?
Did you run amcheck?
What is in /tmp/amanda/sendsize*debug on dhcp?
> Phil
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Oh, well then you could do a little wrapper program.
I am not 100% sure if this would work, but you could try it.
Rename amandad amandad.real, and then make a shell script called
amandad and have it invoke the command and then amandad... You may need to
add a duplicate entry in /etc/inetd.con
Hi Phil,
that would work if amdump and "command" needed to run on the
same system. In my configuration, amdump runs on the Amanda
Server and "command" needs to run on an Amanda client.
Thanks,
Dave
-- Original Message --
From: Phil Davis <[EMAIL PROTECT
Phil et al:
> one of two ways... either run a cron job to execute your Perforce checkpoint
> program on a cron job x mins before the cron job for amanda happens knowing
> that the perforce program takes x mins to complete (and of course some buffering
> wouldn't hurt) and then have the cron job
That alkl seems just fine, as it is on other machines that work just fine
(i.e. inetd.conf) heres the lines from it:
amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped
amanda dgram udp no
This would be fairly easy, all you need to do is modify the cron settings.
one of two ways... either run a cron job to execute your Perforce checkpoint
program on a cron job x mins before the cron job for amanda happens knowing
that the perforce program takes x mins to complete (and of course som
In a message dated: Wed, 13 Dec 2000 23:57:07 PST
Phil Davis said:
>Yeah, I get this:
>brw-rw1 root disk 72, 1 Apr 17 1999 /dev/ida/c0d0p1
[..snip..]
>and heres the line from /etc/group:
>
>disk:x:6:root,backup
>
>so it should be happy... but is isn't :(
Hmm, strange. How
Folks,
I have a source code control system (Perforce) running on a Solaris Amanda
Client (2.4.1p1). Perforce has the ability to "checkpoint" its metadata in
journal files, essentially taking a human-readable snapshot of the metadata
at that particular. I'd like to do this checkpoint and then ba
Yeah, I get this:
[root@dhcp ~]# ls -la /dev/ida/c0d0p*
brw-rw1 root disk 72, 1 Apr 17 1999 /dev/ida/c0d0p1
brw-rw1 root disk 72, 10 Apr 17 1999 /dev/ida/c0d0p10
brw-rw1 root disk 72, 11 Apr 17 1999 /dev/ida/c0d0p11
brw-rw1 root
In a message dated: Wed, 13 Dec 2000 22:55:13 PST
Phil Davis said:
>FAILURE AND STRANGE DUMP SUMMARY:
> dhcp /dev/ida/c0d0p6 lev 0 FAILED [disk /dev/ida/c0d0p6 offline on dhcp?]
> dhcp /dev/ida/c0d0p7 lev 0 FAILED [disk /dev/ida/c0d0p7 offline on dhcp?]
> dhcp /dev/ida/c0d0p5 lev 0 FAILED [dis
Question: Can amanda work as a tape manager for machines that
share a tape device (or tape library)?
If that question is unclear, here is some more information that might
help clarify:
I am assuming that:
1) I can have a 4 tape drive library (a Qualstar TLS-88132) plugged in
to a fibre switch
2
On Tue, 12 Dec 2000, Chris Karakas wrote:
>Sigh...another O'Reilly book I'll have to buy. CVS - no matter how often
>kind members of this list post the cryptic incantations for this temple,
>I _will_ want to know it all when I enter it. I just ask myself why I
>didn't buy all those fine manuals (
Hi,
I have setup a new host for a server, and after much tweaking got amcheck to seem
happy, but then once the run goes I get a really odd error, like so:
FAILURE AND STRANGE DUMP SUMMARY:
dhcp /dev/ida/c0d0p6 lev 0 FAILED [disk /dev/ida/c0d0p6 offline on dhcp?
]
dhcp /dev/ida
On Wed, 13 Dec 2000, Stephen Walton wrote:
>Date: Wed, 13 Dec 2000 10:09:25 -0800 (PST)
>From: Stephen Walton <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: amlabel hangs up
>
>On Tue, 12 Dec 2000, Olaf Seidel wrote:
>
>I had a roughly similar problem. I found that amlabel put the tape
>GNU/Linux dump and Solaris ufsdump (which both use rmt)
That won't work with Amanda. Amanda always runs the dump program
(whatever it is) to stdout and then sends that stream across the network
to a dumper process that either writes it to the holding disk or to
a taper. So the fact that variou
Which version of mtx are you using will depend on which version of
chg-zd-mtx you might need.
The tapetype you can get from the faqomatic, which has all of this.
On Wed, Dec 13, 2000 at 08:09:59AM -0800, Wang Chen wrote:
>
> Hi folks,
>
> Just begin to AMANDA. I installed sst driver in our
>
> I tried that on my configuration, which is Amanda 2.4.1p1 and it uses
> chg-zd-mtx as the changer script.
> spinoza!backup 252# amtape daily reset
> amtape: could not reset changer: /dev/tape
> spinoza!backup 253# amtape daily slot first
> amtape: could not load slot expr:: syntax error
> spinoz
On Wed, Dec 13, 2000 at 02:02:12PM -0500, John R. Jackson wrote:
> >I tried that on my configuration, which is Amanda 2.4.1p1 and it uses
> >chg-zd-mtx as the changer script.
> >...
>
> I think Joe Rhett ([EMAIL PROTECTED]) was working on several mtx/chg-zd-mtx
> issues. He posted this about a m
On Wed, Dec 13, 2000 at 01:18:34PM -0500, John R. Jackson wrote:
:>is it possible to use a remote tape server with Amanda? ...
:
:Using what, rmt?
GNU/Linux dump and Solaris ufsdump (which both use rmt)
Oh well, I'm screwd for now...
-Jon
First, did you configure /kernel/drv/sgen.conf so that it sees the changer
at boot? You probably want/need -
device-type-config-list="changer";
...and uncomment the stuff at the bottom, as documented in the file.
Once the system sees your device ( look in /dev/scsi/changer/... ) you
should downl
>I tried that on my configuration, which is Amanda 2.4.1p1 and it uses
>chg-zd-mtx as the changer script.
>...
I think Joe Rhett ([EMAIL PROTECTED]) was working on several mtx/chg-zd-mtx
issues. He posted this about a month ago:
You'd probably be better off using mtx 1.2.29 and the chg-zd-mtx
"John R. Jackson" wrote:
> >when i run amtape it only reads 4 of the 8 tapes. and sometimes it doesn't
> >even read the labels. I am useing chg-multi.conf ...
>
> Please post your chg-multi.conf file. What version of Amanda are
> you using?
>
> Looking physically at the drive, or by writing your
>is it possible to use a remote tape server with Amanda? ...
Using what, rmt?
In any case, the answer is no, but the support framework for adding
something like rmt will be in the source code within hours (it's actually
already in 2.5 -- the framework, that is, not rmt support specifically).
>
On Tue, 12 Dec 2000, Olaf Seidel wrote:
> I have problems with amlabel. Sometimes, when I label a tape,
> there are no problems and the process takes a minute or so. And
> sometimes (2 out of 6 tapes), Amanda says, that it is writing the
> label to the tape and when the checking label process is
Hi,
is it possible to use a remote tape server with Amanda? If so how,
can't seem to find anything in TFM.
The tape server is working using ufsdump on Solaris boxen and dump on
GNU/Linux systems, but amanda doesn't like specifying the device as
remote (tapedev "netapp:urst1a")
the reason I wan
>when i run amtape it only reads 4 of the 8 tapes. and sometimes it doesn't
>even read the labels. I am useing chg-multi.conf ...
Please post your chg-multi.conf file. What version of Amanda are
you using?
Looking physically at the drive, or by writing your own unique label
on each tape and che
>At the moment, I just use one tape and I am testing the restore function:
>amrestore /dev/st0 localhost '/home$'
You must **always** use the non-rewinding device name, i.e. /dev/nst0.
>Richard Ao
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Hi folks,
Just begin to AMANDA. I installed sst driver in our
Solaris 7 machine and mtx as well. The mtx seems works
fine. Our tape device is EZ17, tape mode is "Mammoth
EXB-8900 8mm ", there is not tapetype defined on
amanda.conf file. Colud anybody mail me a tapetype
entry? I have found chg-z
* Matt McManus ([EMAIL PROTECTED]) [20001213 04:00] thus spake:
>
> I have now got amanda running very happily on my network. I have a query
> about how to turn hardware compression 'off' on my Quantum DLT4000 drive.
> At the moment I use the 'density select'
Matt McManus wrote:
>
> I have now got amanda running very happily on my network. I have a query
> about how to turn hardware compression 'off' on my Quantum DLT4000 drive.
> At the moment I use the 'density select' button on the front of the drive,
> but I understand that I am able to do this wi
"John R. Jackson" wrote:
>
> >Thanks John, I think you are absolutely right to question the dump
> >program. ...
> >It's 0.4b19 version ...
>
> Well, I'd be a lot happier if it was ancient so I could blame it :-).
I've read in this list that there is a Linux dump 0.4b20 out there, so
there mi
Erik van der Meulen wrote:
>
> Funny, if I do something like:
>
> amdump default & mt -f /dev/nst0 eject
>
> The tape ejects first and Amanda gives an error 'no tape found'.
It should be "&&", instead of "&" ;-)
"&" means "do it in the background and continue with next command
immediately",
> richard wrote:
>
> In the 202.85.165.88 /home directory, I have set up different users
> who only themselves can read their directories. So, I have put the
> operator into the root group.
This is more than necessary. Create a group specifically for backups,
say "disk". Then set (amanda is m
richard wrote:
>
> In my amanda.conf file, I use
> dumpcycle 1 days# the number of days in the normal dump cycle
dumpcycle is the period of time for which AMANDA has to guarantee that
for every disk in your disklist, there will be a full backup done in
that period. Setting it to 1 day me
"John R. Jackson" wrote:
>
> So are you saying you just did a cp of the holding disk file to the
> MO disk? If so, then the MO must have a normal Unix file system on it
> and the dd should have worked, assuming the cp worked. I'd start by
> comparing the original and the copy, first by length (
Hi,
yes i meant "&&" instead of "&"..
sorry for the typo
Christoph
Nate Eldredge schrieb:
>
> On Wed, 13 Dec 2000, Erik van der Meulen wrote:
>
> > Funny, if I do something like:
> >
> > amdump default & mt -f /dev/nst0 eject
>
> I think he meant && instead of &. && will execute the seco
Hi,
has anyone an idea what's the problem here?
FAILURE AND STRANGE DUMP SUMMARY:
magazin.xx /home/backup lev 0 FAILED [nak error:amandad busy]
magazin.xx /home lev 0 FAILED [nak error:amandad busy]
[...]
FAILED AND STRANGE DUMP DETAILS:
/-- magazin.xx /home/backup lev 0 FAILED [nak error
I have now got amanda running very happily on my network. I have a query
about how to turn hardware compression 'off' on my Quantum DLT4000 drive.
At the moment I use the 'density select' button on the front of the drive,
but I understand that I am able to do this with the 'tapedev'.
At the mome
On Wed, 13 Dec 2000, Erik van der Meulen wrote:
> Funny, if I do something like:
>
> amdump default & mt -f /dev/nst0 eject
I think he meant && instead of &. && will execute the second command only
if the first succeeds. & will run the first command in the background and
immediately start th
Funny, if I do something like:
amdump default & mt -f /dev/nst0 eject
The tape ejects first and Amanda gives an error 'no tape found'.
I run Debian Linux 2.2
Does this make sense?
--
Erik van der Meulen <[EMAIL PROTECTED]>
Quoting Christoph Scheeder <[EMAIL PROTECTED]>:
> Hi,
> that's al
t 20 Mb in /home
amrestore: 5214: skipping start of tape: date 20001213 label DailySet100
amrestore: 5215: skipping localhost._etc.20001213.1
amrestore: 5216: restoring localhost._home.20001213.1
amrestore: 5217: skipping start of tape: date 20001213 label DailySet100
amrestore: 5218: skipping loca
46 matches
Mail list logo
