On Mon, Feb 07, 2011 at 01:13:58PM -0500, Josh Fisher wrote:
> On 2/7/2011 10:43 AM, Graham Keeling wrote:
>> It occurs to me that I might prefer to run the 'truncate all' command via
>> a cron job, at some point in the day that bacula doesn't know about.
>>
>> Is there a reason, or reasons, that I should not do this?
>
> The documentation states "Be sure that your storage device is idle when  
> you decide to run this command".

Does anybody know what happens if it is not?

If it just means that the right volume doesn't get truncated, that is not so
bad because I can run the command again later.

If it can cause a volume to be truncated that shouldn't be truncated, then
I wouldn't want to risk it at all.


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users