Forum Discussion

Mohmec's avatar
Mohmec
Level 4
10 years ago

Snapshot consolidation fails for hot add

Hi

We are using virtual master/media and tape targets. Consolidation fails every time when a job is cancelled. Any idea why? I know tape targets are not supported with virtual media server. But we are able to reproduce the same failure each time we cancel the job.

 




 

5 Replies

  • Hello,

    What version of ESX are you running and what is the error?

    Check out this thread and see if it applies. Also look at http://kb.vmware.com/kb/2007245

  • It is not a "fix" but I have had to edit the VM media server that is doing the hotadd and remove the disks of the server that was being backed up. This will then allow the disk consolodation to run.

  • Thank you. We are running ESX 5.5 . We are using hot add and the error occurs when we cancel the job. Here is the error:

    - vmwareLogger: WaitForTaskCompleteEx: Unable to access file  since it is locked <232>
    8/29/2014 12:28:22 PM - Info bpbrm(pid=3100) INF - vmwareLogger: WaitForTaskCompleteEx: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE      
    8/29/2014 12:28:22 PM - Info bpbrm(pid=3100) INF - vmwareLogger: ConsolidateVMDisks: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE      
    8/29/2014 12:28:22 PM - Info bpbrm(pid=3100) INF - vmwareLogger: ConsolidateVMDisksAPI: SYM_VMC_ERROR:  TASK_REACHED_ERROR_STATE      
    8/29/2014 12:28:22 PM - Critical bpbrm(pid=3100) from client matlktda1apd015.nam.pwcinternal.com: VMware_thaw: VMware delete snapshot failed: SYM_VMC_TASK_REACHED_ERROR_STATE    
    8/29/2014 12:28:24 PM - Info bpfis(pid=4380) done. status: 0          
    8/29/2014 12:28:24 PM - end Application Snapshot, Delete Snapshot; elapsed time: 0:00:22
    8/29/2014 12:28:24 PM - Info bpfis(pid=4380) done. status: 0: the requested operation was successfully completed    
    8/29/2014 12:28:24 PM - end writing
    Status 0
    8/29/2014 12:28:24 PM - end operation
    Status 150
    8/29/2014 12:28:24 PM - end operation
    termination requested by administrator(150)

     

  • Thank you Marianne.

    We updated the VM tools. We are at 7.6.0.3. TECH181118 was referred to Symantec support and they confirmed this was fixed in 7.6.x.