File Server Backup

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 2

Hi all,

I'm hoping someone can help me with this. I've looked through several other posts and FAQ's but am still unable to backup our main File Server.

When trying to back up this particular server, the process takes 4-5 hours and is stuck on 21% the whole time and the process 'Adding '\\Volume.....etc'. Error log is here - 

Failed to back up virtual machine 'DHS-FS1'.
Additional info: 
--------------------
Error code: 32852
Module: 114
LineInfo: c35c04057128fe7f
Fields:  $module : disk_bundle_vs_44421
Message: Failed to back up virtual machine 'DHS-FS1'.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d2e8
Fields:  $module : disk_bundle_vs_44421
Message: Failed to prepare for backing up.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields:  $module : disk_bundle_vs_44421
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: d1ab7fa1e56ec6e7
Fields:  $module : disk_bundle_vs_44421
Message: 
--------------------
Error code: 13
Module: 149
LineInfo: d1ab7fa1e56ec83e
Fields:  $module : disk_bundle_vs_44421
Message: Failed to perform the requested operation.
--------------------
Error code: 236
Module: 16
LineInfo: 7bb42efe3c733241
Fields:  $module : disk_bundle_vs_44421
Message: Internal error: Attempt to access emulated disk for non-initialized object.
--------------------
Error code: 94
Module: 83
LineInfo: 383ffdb092990e23
Fields:  $module : hv_srv_vs_44421
Message: Failed to open virtual disk file 'C:\ClusterStorage\LUN-DHS-FS1\dhs-fs1\DHS-FS1_J.vhdx'.
--------------------
Error code: 212
Module: 83
LineInfo: 383ffdb092990dda
Fields:  $module : hv_srv_vs_44421
Message: Failed to create a multi-volume snapshot where files are located:
C:    \ClusterStorage\LUN-DHS-FS1\DHS-FS1 (virtual machine file location),
C:    \ClusterStorage\LUN-DHS-FS1\DHS-FS1 (virtual machine snapshot file location),
C:    \ClusterStorage\LUN-DHS-FS1\DHS-FS1\DHS-FS1.vhdx (virtual disk file location),
C:    \ClusterStorage\LUN-DHS-FS1\dhs-fs1\DHS-FS1_J.vhdx (virtual disk file location).
--------------------
Error code: 207
Module: 83
LineInfo: 383ffdb092990dcb
Fields:  $module : hv_srv_vs_44421
Message: Failed to mount the volume snapshot.
--------------------
Error code: 33
Module: 7
LineInfo: e24f93d0b8d8c99e
Fields:  $module : hv_srv_vs_44421
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 3fec04e376b8a1af
Fields:  $module : hv_srv_vs_44421
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 9
Module: 0
LineInfo: 2aacb7b2ab852ac
Fields:  code : 2147754767, $module : hv_srv_vs_44421
Message: The shadow copy provider had an unexpected error while trying to process the specified operation.
--------------------

I've tried running the job with different VSS providers and even with it turned off but no luck. I've also moved the server between hosts and still the same issue.

The server is a VM on a Hyper-V host running Server 2012 R2. All other server backups run without issue.

I've raised a ticket with Acronis but they are being incredibly slow in replying to me. It took 4 days to get an initial response!  Ticket ID 02885568

Any help/ideas would be appreciated.
Thanks!

Mon, 01/16/2017 - 11:28
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi John,

The error is related to agent-less VM backup processing through Hyper-V VSS provider on host. From the ticket I can see that you were asked to get the log files: they are required from both the host and from inside the VM - the Windows Event logs (including Hyper-V-specific events) should show the VSS failures and possible reasons for that. The root cause is the VSS failure which should be revealed from these logs.

The workaround for the issue would be to install Agent for Windows inside the VM and perform backup without VSS (since likely VSS is broken inside the VM taking into account the fact that other VMs are backed up fine).

Thank you.

Tue, 01/17/2017 - 12:58
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 2

For reference, it seems that the problem in this instance was linked to the .VHDX's attached to this particular server. To get around this we have had to create a new file server which in our case wasn't such a bad choice as it was pretty slow.

Fri, 02/03/2017 - 15:44