> > File = c:/ > Plugin = "systemstate:/@SYSTEMSTATE/" > Plugin = "vssexchange:/@VSSEXCHANGE/" (doesn't exist yet) > File = e:/ > Plugin = "vssmssql:/@VSSMSSQL/" (also doesn't exist yet) > File = d:/ > Plugin = "vssoracle:/@VSSORACLE/" (I assume oracle uses VSS) > > Then we'd have to take care to write the normal backup stuff direct to the > media (or spool it as per the config), but write the plugin data to the > temporary spool. I assume that is possible. Otherwise we just tell the user > not to do that, put the file backups first then the plugins. > > So no showstoppers so far... >
Something just occurred to me after I hit send (how often does that happen!) - all the VSS stuff has to be backed up in the same way and together whether it is system state, Exchange, or MSSQL. Exchange can be up to 75GB under Exchange 2003, probably much bigger under 2007/2010. MSSQL is pretty much open ended in terms of size. I think we'd run the risk of running out of spool space. IMHO, writing to the catalog is a much more elegant solution. James ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
