VSS and VMware ESX

[urs68]

After reading the veem Blog: VSS and VMware ESX: What your VMware backup vendor isn’t telling you

http://www.veeam.com/blog/vss-and-vmwar ... g-you.html

I have tried to do the same with veem Backup & Replication 5.0 (5.0.1.198).
On one ESXi 4.1 (260247) I have installed two Windows Server 2008 (not R2)
I have followed "instructions" of the Blog, but I have exactly the same problem described in the article. It seams that VSS is not "correctly" implanted.
I'm missing something? I have checked backup parameters but everything seems to be correctly setted.

Thanks for you help!

Urs

[Vitaliy S.]

Hello Urs,

Could you please elaborate it? What messages do you receive in the Event log? Have you had a safe boot first and then ordinary one while restoring DC?

Thanks!

[urs68]

No safe boot, just "normal" boot. In the log file I have:

The DFS Replication service failed to contact domain controller to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.

Thanks!

[Gostev]

This functionality works fine, you are definitely missing something...
1. Make sure you have application-aware image processing checkbox selected in the backup job settings.
2. Make sure you are backing up the running DC VM.

If everything is setup correctly, you absolutely have to see DC VM booting into safe mode first upon restore.

If you cannot find the reason why this does not work for you, please contact support directly for further troubleshooting.

Thanks!

[urs68]

"Enable application-aware image processing" is enabled
"Enable guest file system indexing" is disabled

In Advanced option
"Require successful application processing" is selected
"Truncate logs on successful backup only" is selected

The HTML report:
Enabling changed block tracking...
Changed block tracking cannot be enabled: one or more snapshots present.

Removing snapshot
RemoveSnapshot failed, snapshotRef "1664-snapshot-24", timeout "3600000"
File <unspecified filename> was not found
Veeam Backup will attempt to remove snapshot during the next job cycle, but you may consider removing snapshot manually.
Possible causes for snapshot removal failure:
- Network connectivity issue, or vCenter Server is too busy to serve the request
- ESX host was unable to process snapshot removal request in a timely manner
- Snapshot was already removed by another application

The VM had already a manually made snapshot called "fresh install". After the backup appears a snapshot called "Consolidate Helper-0" but I think is generated by the ESX server.

[Gostev]

Hi Urs, we do not provide support over forum, so kindly please contact our support directly with any issues. Thanks!

[urs68]

OK,
thanks

Urs