VMware Cloud Community
vontexx
Enthusiast
Enthusiast
Jump to solution

VDR - Backup of an Windows Server 2003 VM hangs by 59%

Hi, @ all

one of two Windows Server 2003 VM's hangs at 59% during the backup. The DataRecovy Shell show no error. The first two weeks it worked perfect. since 7 days it hangs every time at 59%. All other VMs (Server 2000/2008, Linux etc) work fine. I have tested with a new backupjob, new backup destination, vm off, bur every time it hangs at 59%. I Hope someone can helpd me.

Reply
0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

VDR 1.2 was released yesterday and this issue should be addressed by that release.

  • Data Recovery Backups May Fail To Make Progress At The Start Of The Task

During incremental backup of a virtual machine, Data Recovery would fail to make progress and the backup appliance would show 100% CPU. This condition persisted until the appliance is restarted. Even after restarting the backup appliance, no further progress was made on the incremental backup. This was the result of how the backup appliance used information about the last backup to create a new backup.

View solution in original post

Reply
0 Kudos
5 Replies
fgl
Enthusiast
Enthusiast
Jump to solution

I have experienced this type of problem where VMs hangs at a percentage and you can't even stop/cancel it and you have to force shutdown the VDR appliance everytime to get it out of the system. The only solution that I found that works for me was to go and delete ALL restore points for that VM then reboot the VDR then run a integrity check which takes forever (mine took 26 hours on 230GB) then reboot the VDR again, of course during all this time you have to stop any backup schedule so nothing is running against the datastore otherwise I found it will make things worst. I have had to use this solution 5 times now in the short 3 months of using VDR.

Reply
0 Kudos
vontexx
Enthusiast
Enthusiast
Jump to solution

Thats not a Solution for us, but thx Smiley Wink

The Vm is an converted VMware Workstation VM, but has the Vmware Tools from vSphere. Can this be a reason ?

Reply
0 Kudos
vontexx
Enthusiast
Enthusiast
Jump to solution

With this KB Article: 1012282

http://kb.vmware.com/kb/1008524

i have exported the logs. Only intresting Entrys abput our VM ("Enpirum") is:

2/25/2010 16:52:03.000: 0x0998bab8: DevDelTransaction: DedupeStore_DeleteTransaction(2BC0D788-BE21-4737-A16B-712AFFF4297C/vm-163/2010-02-24 18-00-01-000/SCSI 0:0-flat.vmdk) returned -101

2/25/2010 16:52:03.000: 0x0998bab8: DevDelTransaction: DedupeStore_DeleteTransaction(2BC0D788-BE21-4737-A16B-712AFFF4297C/vm-163/2010-02-24 18-00-01-000/SCSI 0:0.vmdk) returned -101

2/25/2010 16:52:03.000: 0x0998bab8: DevDelTransaction: DedupeStore_DeleteTransaction(2BC0D788-BE21-4737-A16B-712AFFF4297C/vm-163/2010-02-24 18-00-01-000/Empirum.cfg.xml) returned -101

2/25/2010 16:52:03.000: 0x0998bab8: DevDelTransaction: DedupeStore_DeleteTransaction(2BC0D788-BE21-4737-A16B-712AFFF4297C/vm-163/2010-02-24 18-00-01-000/Empirum.nvram) returned -101

2/25/2010 16:52:03.000: 0x0998bab8: DevDelTransaction: DedupeStore_DeleteTransaction(2BC0D788-BE21-4737-A16B-712AFFF4297C/vm-163/2010-02-24 18-00-01-000/Empirum.vmx) returned -101

2/25/2010 16:52:03.000: 0x0998bab8: DevDelTransaction: DedupeStore_DeleteTransaction(2BC0D788-BE21-4737-A16B-712AFFF4297C/vm-163/2010-02-24 18-00-01-000/backup-info.log) returned -101

2/25/2010 16:52:03.000: 0x0998bab8: DevDelTransaction: DedupeStore_DeleteTransaction(2BC0D788-BE21-4737-A16B-712AFFF4297C/vm-163/2010-02-24 18-00-01-000/pre-backup-info.log) returned 0

2/25/2010 16:52:14.000: 0x0998bab8: DDeDupe::ddupMapDedupeResult: mapping DevGetTransStats: DedupeStore_GetTransactionInformation(2BC0D788-BE21-4737-A16B-712AFFF4297C/vm-129/2010-02-22 18-03-22-000/backup-info.log) error code -101 to -1,101

But it comes from the Integritycheck ?!?!

At the Backuptime i only see that the backup is running, but now error entrys, nothing.

Reply
0 Kudos
admin
Immortal
Immortal
Jump to solution

VDR 1.2 was released yesterday and this issue should be addressed by that release.

  • Data Recovery Backups May Fail To Make Progress At The Start Of The Task

During incremental backup of a virtual machine, Data Recovery would fail to make progress and the backup appliance would show 100% CPU. This condition persisted until the appliance is restarted. Even after restarting the backup appliance, no further progress was made on the incremental backup. This was the result of how the backup appliance used information about the last backup to create a new backup.

Reply
0 Kudos
vontexx
Enthusiast
Enthusiast
Jump to solution

With 1.2 the VM backup works fine, nice to see that the bug is fixed.

Reply
0 Kudos