On Tue, 19 Jul 2005, Arno Lehmann wrote:
You need to tell bacula which storage device to use. You can do this in the schedule with a job override.
Right - thanks. :)
This might give problems with job promotion, I try to avoid that by starting the affected backups by hand.
Yeah. So, my problem now becomes that promoted incrementals want to use the storage device defined in the job override. The promoted jobs therefore get written to disk (provided I have an appropriate FileStorage volume defined in my "full" pool). Scheduled full backups go to the right device.
I can indeed get around this by running jobs manually, but I'll eventually have 150+ clients across three continents, so that gets tricky. ;)
I suppose I can live with promoted full backups going to disk, given that the scheduled full backups will go to tape. The only thing I don't really like about that is that it increases the likelihood of full backups for often-absent clients never making it to tape.
Perhaps we need something like "Full Backup Storage" and "Incremental Backup Storage" directives so different backup types can be locked to a storage device.
Alternatively, being able to attach a specific storage device to a pool would do the trick.
Thoughts? Adrian Close email: [EMAIL PROTECTED] Hitwise phone: +61 3 8530 2446 Level 7, 580 St Kilda Road fax: +61 3 9529 8907 Melbourne, VIC, 3004, Australia web: http://www.hitwise.com/ ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
