Il 24/03/2011 16.48, Bruno Friedmann ha scritto:
> On 03/24/2011 02:50 PM, farmershort wrote:
>> Thanks for all the replies folks...
>>
>> I've tried a few things, and I think I may have found the problem... 
>> although I've onyl had time to kick off 2 scheduled jobs since the fix, so 
>> it's not been tested to destruction...
>>
>> The bacula server is called 'viper'. viper is a hyper-v VM sitting on the 
>> host 'elephant. viper is centos, elephant is 2008R2. one the jobs viper is 
>> running is to back up elephants c: drive. there's also a "run client before 
>> job" script which does a system state backup of elephant, before the c: 
>> backup.
>>
>> I think this system state backup was triggering this "saving" (and 
>> rebooting) of certain vm's. of course it didn't upset the elephant backup 
>> job, as it was waiting for the "run before" task to finish.... sadly, the 
>> other job was to back up another 2008R2 server called 'penguin'. The penguin 
>> job didn't do a system state backup before the main backup, so it just kicks 
>> right off into copying files - at which point - viper goes to sleep for a 
>> minute whilst elephant does the system state backup.
>>
>> Does this sound logical to everyone? As I say, the last couple of jobs I've 
>> tried seem to be working ok.
>>
>> Thanks
>>
>> Adam
>>
>
> <joke>
>    never call a 2008R2 penguin :-)
> </joke>
>

LOL

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users