Jean-Louis Martineau schrieb:
It's important to do the dump direct to tape at the end if you have a
small holding disk, Amanda was designed for this case.
But hard disk are now cheap, what you propose is a good idea.
Patch is welcome.
Maybe we should show this to the hackers-list ?
S
Dustin J. Mitchell schrieb:
However, the driver always schedules its PORT_WRITE (direct to tape)
dumps *after* its holding-based runs. The idea is that dumping
directly to tape basically monopolizes the entire server
infrastructure, so it's better to get the cooperating dumps out of the
way
It's important to do the dump direct to tape at the end if you have a
small holding disk, Amanda was designed for this case.
But hard disk are now cheap, what you propose is a good idea.
Patch is welcome.
Jean-Louis
Stefan G. Weichinger wrote:
Dustin J. Mitchell schrieb:
However, the
OK, I'll take a swing at this :)
On Wed, Apr 1, 2009 at 3:50 PM, Stefan G. Weichinger s...@amanda.org wrote:
I want to avoid to copy ~60 GB from disk to holdingdisk internally at
every amdump, so I decided to set them to holdingdisk no -- write the
to tape directly.
taperalgo first, btw
The
At a client I have two DLEs which are local directories on the amanda
tapeserver. There is new data dumped there every day during the day.
I want to avoid to copy ~60 GB from disk to holdingdisk internally at
every amdump, so I decided to set them to holdingdisk no -- write the
to tape directly.
