Keith Sudbury wrote:
> John Drescher wrote:
>   
>> On Fri, Aug 1, 2008 at 9:36 AM, Keith Sudbury <keith AT netzensolutions DOT 
>> com> wrote:
>>   
>>     
>>> John Drescher wrote:
>>>     
>>>       
>>>> On Fri, Aug 1, 2008 at 8:32 AM, Keith Sudbury <keith AT netzensolutions 
>>>> DOT com> wrote:
>>>>
>>>>       
>>>>         
>>>>> Hi,
>>>>>
>>>>> I have an LTO-3 drive on my server and currently my backups re only
>>>>> about 100GB, and I could (and currently am fitting multiple backups on
>>>>> one tape). I am obviously changing the tape each day etc (its not the
>>>>> same tape) I have a different tape for mon - thursday and friday1
>>>>> friday2 etc
>>>>>
>>>>> But I am wondering if I should be using *Use Volume Once = Yes *which
>>>>> would then mark the tape FULL after it has used it once. If I don't do
>>>>> this I will eventually get to a day when only half a backup fits on the
>>>>> end?
>>>>> *
>>>>> *Or is it fine to leave more than one backup on a tape?
>>>>>
>>>>>
>>>>>         
>>>>>           
>>>> It is fine. I have had > 30 backups on a single LTO2 tape.
>>>>
>>>>
>>>>       
>>>>         
>>>>> I am ejecting my tapes with "umount LTO-3" is this ok? or should I be
>>>>> using "release LTO-3" and then doing umount?
>>>>>
>>>>>
>>>>>         
>>>>>           
>>>> Release is better because it does not remove the drive from bacula's
>>>> control so that if you reinsert the tape you will not need to mount
>>>> it. If you umount a tape bacula will not have control of the tape
>>>> drive until you issue a mount command inside of bacula.
>>>>
>>>>
>>>>       
>>>>         
>>> So a "mt eject" should work after I have done a   'release LTO-3' | bconsole
>>>
>>> And its fine to put in a different tape, so for example release mondays
>>> tape do a mt eject then put in tuesdays tape...
>>>
>>>     
>>>       
>> No need to eject. Release will eject the tape but the bacula will
>> automatically mount the next tape instead of requiring the user to
>> issue a mount in bacula. I hope I am not too confusing...
>>   
>>     
> Cool, I understand now! So i can just add: echo 'release LTO-3' | bconsole
>
> To an Admin job and set the priority higher and this will spit out the 
> tape, and when a user puts in a new tape and the next job comes around 
> bacula will be able to use the tape in the drive.
>
> Keith
>
>
>   
Infact, can I just run two RunAfterJobs like this:


 Job {
  Name = "BackupCatalog"
  JobDefs = "DefaultJob"
  Level = Full
  FileSet="Catalog"
  Schedule = "WeeklyCycleAfterBackup"
  # This creates an ASCII copy of the catalog
  RunBeforeJob = "/usr/libexec/bacula/make_catalog_backup bacula bacula"
  # This deletes the copy of the catalog
  RunAfterJob  = "/usr/libexec/bacula/delete_catalog_backup"
  RunAfterJob  = "echo 'release LTO-3' | bconsole"
  Write Bootstrap = "/var/spool/bacula/BackupCatalog.bsr"
  Priority = 11                   # run after main backup
}

Then I can just add it to my catalog job which runs after all the other 
jobs.

Keith


-- 
Keith Sudbury
Netzen Solution Ltd
Suite 5, Piccadilly House, London Rd, Bath, BA1 6PL, UK
Mobile: +44 (0)7921464106
Tel: +44 (0)1225 588 588
Fax: +44 (0)1225 580 061


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users