On Monday 19 May 2008 06:44:56 Michael Short wrote: > On Sun, May 18, 2008 at 5:38 AM, Thomas Mueller <[EMAIL PROTECTED]> wrote: > > hmm... "move" operation on synthetic backup means, that the last full > > backup will be purged/pruned? so, all diff/inc backup jobs will be > > worthless for a full restore before the new synthetic full backup? For > > my case i have in mind, i would never use such a "move" operation on > > synthetic backup. but there may be other scenarios around. > > I believe this feature would be useful to reclaim disk space occupied > by expired catalog entries.
I don't expect the Consolidation feature to help reclaiming disk space any more than Migration does today -- it could make your disk Volumes recycle faster and thus be reused. Otherwise no space is really reclaimed. Kern > In bandwidth limited environments, it is > almost impossible to perform a reliable full backup of a bacula > client. In these situations, I have used an external drive to collect > the initial full backup and incremental can continue over the network. > Unfortunately, this solution is very resource intensive (requiring > human intervention and a long trip to off site locations) so we avoid > this as much as possible. > > These new features will significantly reduce the cost of maintaining > our current backup solution. > > Sincerely, ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
