On Thu, Jan 19, 2006 at 07:31:08PM -0500, Jean-Louis Martineau wrote:
The Amanda core team is pleased to announce the release of Amanda
2.5.0b2. It is stable and we hope to release 2.5.0 soon. test it and
report it if you find a bug in this release.
I've found one more problem. I reported
On Sat, Jan 14, 2006 at 03:04:26PM -0500, Jon LaBadie wrote:
The contents of the file must always be specified as relative to the
head directory of the DLE.
Since you guys are currently working hard to get 2.5.0 out, it might be
a good time to put this sentence into the amanda.conf manpage?
I am having a problem backing up another host with my amanda server. This is
my first try at backing up another linux machine. These are both debian
machines. The tape server can backup itself just fine. I installed
amanda-common and amanda-client on the client machine. I setup the
amandahosts
Dear All,
Please tell me when it becomes OT or boring.
Gene Heskett wrote:
Not this particular version. But it comes to mind that maybe
there is a
switch or jumper configuration option on the drive that
either locks it
on, or locks the config page in the flash from being changed from
Josef Wolf wrote:
On Sat, Jan 14, 2006 at 03:04:26PM -0500, Jon LaBadie wrote:
The contents of the file must always be specified as relative to the
head directory of the DLE.
Since you guys are currently working hard to get 2.5.0 out, it might be
a good time to put this sentence into the
Gordon J. Mills III wrote:
Stefan, the only problem I have had with the debian packages was
with the
amverifyrun script. It probably depends on the version that you use. There
were some spaces at the end of the fgrep fields which caused it to not find
the tapes used. Once I deleted the extra
Cédric Lucantis wrote:
amanda has little (or no) code dealing with multiple backups on
the same date.
I have read somewhere that this was in project, can anyone tell me more about
this ?
As the REAL amanda-hackers have told me this is a problem that is much
tougher to solve than a bad
On Fri, Feb 03, 2006 at 09:35:25PM +0100, Cédric Lucantis wrote:
If my guess is correct, amanda is working fine. You told it 5
tapes were in rotation but only 3 really are. It will not use
the 3 again until it gets at least a total of 5 available and
used.
Your guess is correct :)
On Sat, Feb 04, 2006 at 07:03:07PM +0100, [EMAIL PROTECTED] wrote:
Matthias Andree gave me some good advice here to use some linux scsi tools
to circumvent the error message of mt, which could not write the mode page
(datcompression off).
As I wrote, I was able to change the compression
Thanks Stefan, I do have iptables running on the client since it is my
firewall machine. It is currently set to allow all connections from the
internal network to the fw though. There is always a chance that I have
mangled something there though :-). I will check out the article you cited
below.
Gordon J. Mills III wrote:
Stefan, the only problem I have had with the debian packages was with
the
amverifyrun script. It probably depends on the version that you use.
There were some spaces at the end of the fgrep fields which caused it
to not find the tapes used. Once I deleted the
Gordon J. Mills III wrote:
Thanks Stefan, I do have iptables running on the client since it is my
firewall machine. It is currently set to allow all connections from the
internal network to the fw though. There is always a chance that I have
mangled something there though :-). I will check out
On 2/4/06, Gordon J. Mills III [EMAIL PROTECTED] wrote:
Gordon J. Mills III wrote:
Stefan, the only problem I have had with the debian packages was with
the
amverifyrun script. It probably depends on the version that you use.
There were some spaces at the end of the fgrep fields which
13 matches
Mail list logo
