vRanger

7.5.1: Backup task hanging at 100% of VMDK backup until Timeout reached, aborting

We have a vRanger 7.5.1 job that backs up 13 VMs on two ESXi 6.0U3 hosts.  This job typically runs in 1-1.5 hours.  We have been seeing an issue where a single VM within this job will back up its only VMDK to 100% (as shown in the GUI) and then hang there, never completing the task, until the Timeout of 14 hours is reached at which time vRanger aborts it and cleans up the attached disk, snapshot, etc.  The VM is not necessarily the same VM every night.  The VM then usually backs up the next night successfully.  This does not occur every night but happens often, and always seems to be just one VM at a time.  As you can see in the log below, at 7:14p, it indicates the VMDK backup is complete (the GUI shows 100% at this point) but the task job just hangs there until 10:07a the next morning where it aborts with "Backup task using VDDK HotAdd failed: The operation was cancelled."

 

[2017-07-09 19:00:43.546]: vRanger Backup & Replication - v7.5.1.0
[2017-07-09 19:00:43.546]: Selected Options: Backup powered on machines only. | Update notes with the latest backup results. | Enable Active Block Mapping™ (ABM). | Selected SpaceSavingTech: Differential.
[2017-07-09 19:00:43.546]: Task for virtual machine <VM NAME> was queued.
[2017-07-09 19:06:58.122]: SourceVm:<VM NAME> | Uuid:4208d2f1-bb41-f42b-20f8-fe106869c837 | VC:<vCenter Name>, Host:<Host Name> [ESXi 6.0.0]
[2017-07-09 19:06:58.122]: Beginning backup task for Backup '<Name of Backup>'-<VM Name>
[2017-07-09 19:06:58.122]: Starting task validation.
[2017-07-09 19:06:58.122]: Connection to <vCenter Name> was properly validated.
[2017-07-09 19:06:58.122]: <Host Name> is properly licensed.
[2017-07-09 19:06:58.122]: Test connection to repository <Data Domain Boost volume> starting...
[2017-07-09 19:07:04.309]: Test connection to repository <Data Domain Boost volume> successful!
[2017-07-09 19:07:04.309]: Ending task validation... success!
[2017-07-09 19:07:04.309]: Beginning initialization of backup information.
[2017-07-09 19:07:04.544]: Retrieving the tasks parent information.
[2017-07-09 19:07:04.559]: Retrieving save points for any full backups associated with this job.
[2017-07-09 19:07:04.825]: Verifying content of repository.
[2017-07-09 19:07:20.873]: Finished initialization of backup information successfully.
[2017-07-09 19:07:20.873]: Initialization was sucessful. Backup type to run: Differential
[2017-07-09 19:07:32.982]: Retrieving the VM BIOS configuration completed.
[2017-07-09 19:07:34.701]: Checking mounted disks completed.
[2017-07-09 19:07:36.248]: Creating a snapshot for vRanger completed.
[2017-07-09 19:07:44.170]: Loading virtual machine '<VM Name>' information completed.
[2017-07-09 19:07:49.123]: Local machine is a VMware virtual machine.
[2017-07-09 19:07:49.373]: Backup task will attempt to use Machine-based VDDK HotAdd.
[2017-07-09 19:08:04.843]: Filtering out content of pagefile for disk: [<Volume Name>] <VM Name>/<VM Name>.vmdk
[2017-07-09 19:08:04.843]: Using filter type(s) active map for disk: vix:1:r:<vCenter Name>\:443:0:[<Volume Name>] <VM Name>/<VM Name>.vmdk
[2017-07-09 19:14:27.387]: Backing up disk 'vix:1:r:<vCenter Name>\:443:0:[<Volume Name>] <VM Name>/<VM Name>.vmdk:moref=vm-508897:snapshot-534167:4' completed.
[2017-07-10 10:07:18.680]: Backup task using VDDK HotAdd failed: The operation was cancelled.
[2017-07-10 10:07:31.180]: Check the manual for compatibility issues when attempting Lan-free operations.
[2017-07-10 10:08:02.619]: Removing snapshot for vRanger completed.
[2017-07-10 10:08:04.494]: Updating notes for <VM Name> completed.
[2017-07-10 10:08:04.494]: Updating VM notes completed.
[2017-07-10 10:08:04.947]: Setting VM event completed.
[2017-07-10 10:08:10.228]: Cancel detected; exiting task. (150)

Parents
No Data
Reply
  • Took only 4 months to respond.
    > appliance kind of sucks.

    It took me 4 months because I was trying different variations with different settings for the VA over that time before I scrapped it. Not only did it not fix the problem, it was significantly slower. I've tried numerous times over the years to use the appliance in several different environments, as everyone seems to say that is the way to go, but it's never been fast, significantly slower than backing up VMs "on this vRanger machine". Hence my conclusion that the appliance sucks.
Children
No Data