On 7/10/08 8:33 AM, "Kern Sibbald" <kern AT sibbald DOT com> wrote:

>> Why not always write vbackup jobs to a volume in a "special" pool first?
> 
> Well, that is exactly what happens.  It is just called "Next Pool" rather than
> special pool.
> 
> However, the Next Pool cannot be the same as the Pool from which the jobs are
> going to be read.
> 
>> When writing to the volume(s) in the special pool is completed, either
>> the volume(s) could be moved from the special pool to the destination
>> pool specified by the job, or the entire vbackup job could be migrated
>> to the destination pool.
> 
> It sounds like you are more or less re-inventing the Scratch pool, but with a
> slight twist.  It probably would work, but sounds a bit complicated to me.  I
> suspect we would get a lot of support requests :-(
> 
>> The former would be faster, but would likely
>> waste space due to fragmentation if the destination pool was only used
>> for vbackup jobs. However, the destination pool could be the same pool
>> used for normal backups, and remaining volume space would be usable by
>> normal jobs. In either case, all normal pools (except the special pool
>> and the Scratch pool) could then be used for input, including the
>> destination pools of previous vbackup jobs. I would envision putting
>> vbackup jobs into the same pool I put normal full backup jobs.
> 
> For the moment, I don't see any clean solution to this problem unless we
> program logic to implement the concept of a "different" volume or if the user
> does some manual intervention (moving of volumes between pools -- which rules
> writing more vbackups to them).
> 
Could we somehow leverage Spool space so that the vBackup volume could be in
the same pool as the rest of the volumes? I have separate pools for Full,
Diff and Inc. My Full pool only allows 48 hours of write time for a tape,
since I do fulls once a month they do not mix months on a single tape. I
would like my vBackups to end up in the Full pool so I don't have to burden
the client with a Full back-up.

If we use spool space, can we dump all the jobs for vBackup to spool and
then write it to tape? We have two tape drives, so tape to tape would be
nice, but if spool space could help solve the problem, I'm not opposed.

Robert
-- 
Robert LeBlanc
Life Sciences Computer Support
Brigham Young University
leblanc AT byu DOT edu
(801)422-1882


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users