Ravikiran,
I'm sorry, the /tmp/amanda/server/* files will of course be
on your linux amanda server, rather than your MAC amanda client.
If you can find the logs for the server side of the connection,
please see if they tell you anything useful.
On the client side, double check the .amandahosts
Hello all,
Sorry to post this question, as I have run out of ideas.
I am running a 2.6.1p2-3 server with the same as clients.
Recently a couple of clients are not able to backup their
/ file system. All of the other file systems on them
backup fine (/home /boot). After about 30 minutes
Tim,
That is weird. I've got a couple of Solaris 10/x86 system that
are all ZFS except for the boot partitions which are UFS.
My systems have also recently begun failing on the boot partitions,
even though I'm using server estimates. The ZFS based DLEs are all
backing up just fine.
That is 1 -
I am trying to determine what tape order amanda uses when requesting a reuse
tape.
My amanda.conf is configured to use slots 31-36 for my archive tapes. These
slots contain the following tapes.
Storage Element 31:Full :VolumeTag=A00224L2
Storage Element
Can you post the exact error message you get from amanda?
You said 'broken pipe', where do you get it.
Telling 'tar estimate dying' or 'broken pipe' is useless if you don't
show how/where you get them.
The sendsize debug file looks good, please post the debug file that show
the error you
As for me, I get no errors at all. The only message
I do get is from the amreport which says that the dump
of the file system has failed.
As of right now, I am trying several configs of different
dump type setups to see if it makes a difference. Although
they are the same that have been
Always post which amanda release you are using!
Try chg-robot for your changer.
Jean-Louis
On 07/07/2011 02:21 PM, McGraw, Robert P wrote:
I am trying to determine what tape order amanda uses when requesting a reuse
tape.
My amanda.conf is configured to use slots 31-36 for my archive tapes.
In case this jars any clever thoughts:way back when, I remember
when my size estimates got just big enough that the initial connection
started by the server had timed out. The client had to create a
new connection to send the result . and it didn't have the right permission
to initiate
If you got only 'failed' for the error message, then something is really
broken, I would like to see it, can you post the complete line from the
'FAILURE DUMP SUMMARY' section of the report.
On 07/07/2011 03:22 PM, Tim Johnson wrote:
As for me, I get no errors at all. The only message
I do
Jean-Louis,
On Thu, Jul 07, 2011 at 03:35:58PM -0400, Jean-Louis Martineau wrote:
If you got only 'failed' for the error message, then something is really
broken, I would like to see it, can you post the complete line from the
'FAILURE DUMP SUMMARY' section of the report.
I mispoke, this is
I usually do that just sliped my mind.
My setup is
I am running Amanda-3.2.3 on a Solaris 10 X86 host and I have changer defined
as
define changer c4 {
tpchanger chg-robot:/dev/changer/0
changerfile chg-zd-mtx-state
property tape-device 0=tape:/dev/rmt/0cbn
property
% amadmin archive tape
The next Amanda run should go onto 6 new tapes.
The next 6 new tapes already labelled are: A00221, A00222, A00224, A00225,
A00226, A00223
Ha, they are new tapes, there is no order for new tape, amanda use the
first one.
Put them in the changer in the oreder you want
...
I did installed 2.5.0p2 client with same options that mentioned above
wiki page. Then I started the launch daeomns for bsdudp, For some reason I
am seeinng follwing error in logs on
com.apple.launchd[1] org.amanda.amandad.basdudp getpwnam(amandabackup)
failed
Sent from my Android phone using TouchDown (www.nitrodesk.com)
From: Jean-Louis Martineau
Sent: Thursday, July 07, 2011 9:21:48 PM
To: McGraw, Robert P
Cc: 'amanda-users@amanda.org'
Subject: Re: Tape order
% amadmin archive tape
The next Amanda run should go
14 matches
Mail list logo
