David Boyes schrieb: > > > I think the core of this issue, setting aside implementation details > for > > the moment, reduces to the following question: > > "Is there a way to implement spooling such that Bacula effectively has > a > > circular spool buffer which can be written at the head and read from > the > > tail at the same time?" > > Try using disk volumes as the backup destination using the disk > file-based changer script, and then use migration with a zero retention > time to move the data to tape. Writing to the disk volumes should > commit file data and attributes almost as fast (if not as fast) as > spooling.
Would this work if a job is larger than the available disk storage? I mean, we start having jobs >5-10 TB, but have only 1 TB for spooling. What is the difference if I first spool the data to disk and write it then to tape or doing a backup to disk and then migrate it to tape? Where would I save time for a single job? (I've never use migration, please forgive me my ignorance). I couldn't find anything in the manual about the disk based changer script, but I remember some posts about something like that on the user list. I'll search the list archive. Ralf ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
