On 01/25/2015 10:27 PM, Jason L Tibbitts III wrote:
My amanda server has a really large holding disk, because disk is cheap
and because lots of disk striping generally equals better write
performance.
The usual restore operation I have to do is pulling things off of last
night's backup, which
Hi list,
I compiled amanda 3.3.7 from source which completed successfully.
However, each time I run a command which utilizes libUtil.so, e.g.
amlabel or amcheck I get the following error message:
/usr/bin/perl: symbol lookup error:
/usr/local/share/perl/5.14.2/auto/Amanda/Util/libUtil.so:
Dear Jean-Louis,
that helped, thank you very much!
Best
Jens
On Mon Jan 26 2015 16:14:52 GMT+0100
martin...@zmanda.com (Jean-Louis Martineau) wrote:
Jens,
Try the attached patch.
Jean-Louis
On 01/26/2015 10:00 AM, Jens Berg wrote:
Hi list,
I compiled amanda 3.3.7 from source which
Jens,
Try the attached patch.
Jean-Louis
On 01/26/2015 10:00 AM, Jens Berg wrote:
Hi list,
I compiled amanda 3.3.7 from source which completed successfully.
However, each time I run a command which utilizes libUtil.so, e.g.
amlabel or amcheck I get the following error message:
/usr/bin/perl:
I wonder if one could somehow use the AMVAULT command to do this?
It serves to make a COPY of a dump tape (as I understand it).
At the very least, you could have a cron job copy the tape back *off* of
the
tape, onto a spare corner of the holding disk that you had labeled as
JM == Jean-Louis Martineau martin...@zmanda.com writes:
JM The main problem is that if you leave the dump in the holding disk,
JM amanda will automatically re-flush (autoflush) them on the next run.
JM There is no way to store the information about dump that are already
JM flushed and dump that
