On 2/7/2011 6:53 AM, Dan Langille wrote: > On 2/7/2011 4:11 AM, xunil321 wrote: >> I have a lack of understanding concerning the handling of a disk based file >> volume to >> avoid a disk overflow. > A simple strategy: Max Num Volumes * Max Vol Space = amount of space you > want to use. Why not use that? > > > Let's say there is a 100MB file volume "Volume-1". >> What will be >> happen after the Volume Retention Period when the Recycle and AutoPrune are >> set to >> "Yes" in our Pool setup? >> Will Bacula 5.0.2 clean the 100MB contents of the file "Volume-1" so that it >> will start from >> scratch or do i have to delete/relabel the volume manually for further >> usage? > The answer depends on your Pool configuration directives. > > It is important to read and understand the volume recycling algorithm, > particularly the fact that Bacula will prefer to create a new volume > instead of overwriting a volume: > > http://www.bacula.org/5.0.x-manuals/en/main/main/Automatic_Volume_Recycling.html > > Strictly speaking, you do not *have* to delete/relabel, manually or > otherwise.
Also note that setting ActionOnPurge=Truncate in the pool will only affect new volumes. Existing volumes have to have their ActionOnPurge set to Truncate by manually updating the volume in bconsole. ------------------------------------------------------------------------------ The modern datacenter depends on network connectivity to access resources and provide services. The best practices for maximizing a physical server's connectivity to a physical network are well understood - see how these rules translate into the virtual world? http://p.sf.net/sfu/oracle-sfdevnlfb _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
