About ComdaIT

ComdaIT · 01-17-2015

Hi all, We have a weekly job to snapshot all of our vm machines (vm center 5.5, build 1750787). We just moved to a new fresh install backup server: Backupexec 2012 SP4 (fully updated). When we ran the job on our previous backup server (Backupexec...

ComdaIT · 10-30-2014

Hi, We use BackupExec 2012 SP4 to backup (with an agent installed) a 2008 r2 server that holds among other things a small sql (CCSSQL). The schedualed backup of the server usually fails with the response code: V-79-57344-34108, An unexpected error...

ComdaIT · 01-24-2015

Hi, sorry for the late reply. I changed a few things within the job hopefuly it will help, but with out any luck. @pkh : this are the error messeges: V-79-57344-38277 - Unable to open a disk of the virtual machine. VixDiskLib_Open() reported...

ComdaIT · 11-13-2014

Hi all, @maurijo : by "worse" I meant it didn't backup at all. eventually as I stated earlier, I did follow the advices here and splitted up the jobs to SQL only and Non-SQL jobs. Although it kept on failing, I decided to change the schedualed time...

ComdaIT · 11-10-2014

@maurijo I did to that, and it didnt change anything. it even made things worse. so I've changed it back to it's defualt state: disabled. Their is plenty of space on the server. all of the list writers are in stable mode with no errors.

ComdaIT · 11-10-2014

***update*** as explained earlier, i've splitted the job in to two sub-jobs. the only sql job succeeds exvery evening, while the other one (file system) fails everytime. I've change the AOFO from automaticaly to Microsoft Shadow Copy, since that...

ComdaIT · 11-04-2014

***update*** I've splited the job as @VJware suggested. yesterday evening the job ran as schedualed: 1. the sub-job Only SQL was succesful 2. the sub-job with only system state and drive C failed. i'll restart the server today maybe it will h...

VOX

User Statistics

User Activity

After moving to BackupExec 2012 SP4 (on a new hardware) VM farm snapshots are failing

V-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes. *********** is a corrupt file. This file cannot verify.

Hi, sorry for the late reply.

Hi all, @maurijo : by "worse"

@maurijo I did to that, and

update as explained

update I've splited