On 06/07/11 09:59, Rory Campbell-Lange wrote:
> I've just moved to using the same (Default) pool for all my backup jobs. All
> my
> backup jobs are configured as Backups, and run as full backups. Each backup is
> for a different tape set and no tape sets should have more than one job on
> them.
>
> I have a problem that the last tape in a set is set to 'Append'. Unless I
> change this in the database media table to 'Full', a second job may be written
> to the tape. This is what I've just done.
>
> I've written job 329 after job 315 on the same tape (CLW112L4). See below
>
> Two questions:
>
> * can I wipe the data pertaining to job 329 off tape CLW112L4 ?
> (I assume by using mt commands -- how can I find the block number
> to start writing zeros from?)
Not safely, no. But you could migrate the second job to a different
volume, or delete the job and re-run it to a different volume.
> * how can I stop this "Append" problem happening again?
If you're working on the basis that no tape should ever have more than
one job on it, then simply set "Maximum Volume Jobs = 1" in the Pool.
You will have to update the Pool from the resource, then all the Volumes
from the Pool. Keep in mind, though, that this does mean you will only
ever be able to have one job running at once to that storage device.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
