I'm new in amanda world so have a question:
If i do incremental backup. For example if in very big file changed
only few bytes, what amanda do? Send all file, or only changed part of
file?
ruslan usifov wrote:
I'm new in amanda world so have a question:
If i do incremental backup. For example if in very big file changed
only few bytes, what amanda do? Send all file, or only changed part of
file?
Amanda is file level backup, the complete file will be sent.
Jean-Louis
Hi list,i've been using amanda for many years now (stuck at version 2.5.2p1-4). She has been recovering my/our files very reliably for a long time - thanks a lot for that great piece of software! But by the time files and file systems are getting bigger (14TB of data on the main backup server
Just a follow up on this issue, which isnt makeing
sense to me at all.
I shut down the amanda client via xinetd, and ran
the backups and the backups worked perfectly. It went over
the client with the report mentioning that the client
was not responsive.
However, I had someone (by
On Fri, 15 Apr 2011 13:11:21 + (GMT)
Kai Zimmer k...@zimmer.net wrote:
Hi list,
i've been using amanda for many years now (stuck at version
2.5.2p1-4). She has been recovering my/our files very reliably for a
long time - thanks a lot for that great piece of software! But by the
time
Kai,
Amanda never required splitting DLEs into 20 Gig pieces, my
'guess' as to why your site did so is that you either had
very limited amanda work area or a very limited backup/tape device.
Amanda for did have a restriction that a DLE could not span
an output tape, but that has been lifted
On Friday, April 15, 2011 10:17:50 AM Tim Johnson did opine:
Just a follow up on this issue, which isnt makeing
sense to me at all.
I shut down the amanda client via xinetd, and ran
the backups and the backups worked perfectly. It went over
the client with the report mentioning that
Anything new about this bug?
--
Marc Muehlfeld (IT-Leiter)
Zentrum fuer Humangenetik und Laboratoriumsmedizin Dr. Klein und Dr. Rost
Lochhamer Str. 29 - D-82152 Martinsried
Telefon: +49(0)89/895578-0 - Fax: +49(0)89/895578-780
http://www.medizinische-genetik.de
I have already tried changing the etimeout, as stated before the
timeouts are :
etimeout 8000 (changed from 5000 and the origanal -600)
( the long wait is due to a few of the machines being very old 800 MHz)
dtimeout 2800
ctimeout 60
I believe I tried using a -5000 seconds and see if it
On Friday, April 15, 2011 12:39:19 PM Tim Johnson did opine:
I have already tried changing the etimeout, as stated before the
timeouts are :
etimeout 8000 (changed from 5000 and the origanal -600)
( the long wait is due to a few of the machines being very old 800 MHz)
dtimeout 2800
Marc,
Can you try the attached patch?
Jean-Louis
Marc Muehlfeld wrote:
Anything new about this bug?
diff --git a/perl/Amanda/Changer.pm b/perl/Amanda/Changer.pm
index a6857a5..5bc63c6 100644
--- a/perl/Amanda/Changer.pm
+++ b/perl/Amanda/Changer.pm
@@ -185,6 +185,7 @@ has one of the
Not sure I understand, this really doesnt effect
what the problem actually is with the server not
responding after 10-12 hours to several days (when I
was on vacation) waiting for a down client that will
not send an estimate. Even after changing to different
timeout
Sorry, no mal intent
Greetings, all.
Attempting to perform a make of amanda-client on a FreeBSD 8.1 system,
to update from 2.5.1p2, I receive the following error:
checking for perl version greater than or equal to 5.6.0...
Segmentation fault (core dumped)
However, a real quick (perl -v) check reveals that
On Friday, April 15, 2011 03:07:03 PM Tim Johnson did opine:
Not sure I understand, this really doesnt effect
what the problem actually is with the server not
responding after 10-12 hours to several days (when I
was on vacation) waiting for a down client that will
not send an estimate.
14 matches
Mail list logo
