Skip to main content

Application-aware backup of SBS 2011 (Exchange/AD) - Failed to connect to guest service 'VMware Snapshot Provider'

Thread needs solution

Hi,

I need to apply an application-aware backup plan to my SBS 2011 server VM.

Domain Admin credentials have been added, but when Applying the plan, on Checking' I get this error:

Error

MODULE 548

MESSAGE
Additional info:

------------------------
Error code: 22
Module: 548
LineInfo: 0xA204C517DA36D5C3
Fields: {"$module":"disk_bundle_vsa64_3602"}
Message: Failed to connect to guest service 'VMware Snapshot Provider'.

VMTools is up-to-date and running on the server computer.

 

 

Any ideas?

 

Cheers

 

Neil

0 Users found this helpful

Hi Neil,

There are some requirements for application-aware backups (UAC): http://dl.managed-protection.com/u/backup/help/12/user/en-US/index.html#36264.html

Can you manually take a quiesced snapshot from your VM?

Please also visit https://kb.acronis.com/content/31347 for this particular issue.

I'll have a look later Raphael. I've got more pressing issues - my AB12 ESXi host licences seem to be no longer enough to back up my VMs and I'm being prompted to add more licences!

Time for another thread!

Neil,

since AB12 you need 1 license per host, this has changed when you come from Backup for VMware (vmprotect, license per CPU).

Hi Raphael,

I've sorted it. It was me being stupid. My original plan included the virtual Windows Server machine that was hosting AB12 et al. Now I've made it physical, that machine needs a physical server license. Deselecting that machine from my backup schedule fixed the issue.

I needed to make sure I had a full system backup before I left for the weekend, and overlooked that little fact!

That's what happens when you rush these things :) 

Now on to the Application-aware backup config...

 

Cheers

 

 

Neil

 

 

 

Application-aware backup revisited...

A repair install of VMWare Tools on the SBS fixed the issue. The vSphere client was reporting that VMWare Tools was installed and up to date, but there was no 'VMWare Tools' icon in the system tray, which made me think something wasn't quite right.

All sorted :)

Yeah, often it is just an uncommon application state when a reboot can fix it.

Thanks for reporting back!