i have downloaded and installed the 60 day eval mainly to test the replication feature.

i have the license provided by vmware and added it during the install/configuration

go into the web client then the vdp and the configuration tab.

this page is supposed to have a vdp advanced tab or link to go somewhere to add hosts to the licensed list.

this installation does not have the advanced tab.

on the configuration confirmed the version and the mode is vdp advanced as listed on the left side of the configuration page

also added the license to license manager in vcenter (appliance 5.5)

i'm stuck, cannot do any backups until i have licensed hosts.

any suggestions??

thanks

Hello!

I have vCenter and ESX 5.1.

I have installed VMware Data Protection 5.5. Then the backup starting i see next error:

An unexpected error occurred with the following error code: 10014. More information may be available in the client logs which can be downloaded from the configuration application

(https://<VDP hostname>:8543/vdp-configure).

error

27.12.2013 13:26:34

VDP: Backup Job

vSphere Data Protection 5.5

What is it mean&

Hello all,

Hi All,

I have a question if VDDK Supports CBT on NFS Datastores?

CBT Feature works fine on VMFS Datastores but not on NFS Datstores...

Please let me know if there are any limitations on NFS Datstores.

Thanks

Armaan

Hi folks.

We have rolled out five VDP appliances to cover around 500VM's over several clusters. I'm not going to lie, VDP has been real pain and I've found it very buggy, but the idea of it working at some point makes me very enthusiastic about getting it to that point. A major issue I am facing at the moment is that while the backups are running relatively OK for most VM's, some of our high IO devices such as Linux Oracle servers, and MSSQL 2008R2 servers are being downed by the backup system.

I had a production MSSQL server freeze for 15 minutes a few days ago while the backups' snapshot was committing itself, this then became responsive again without actually properly going down. This had to be raised as a business affecting incident - so not happy - and yesterday two test Oracle linux boxes freaked out, one rebooted and the other also froze during their backup activities which again wasn't good.

All VMDK's are stored on a NetApp filer accessed through NFS.

I understand these issues are because of either CBT or due to the system using HotAdd which causes the lengthy snapshots. Is this correct? If so - is there a work around to turn off HotAdd for these select VM's, or put them on their own appliance? Or is there another workaround I'm not aware of.

Thanks a lot for any help coming!

I get this error message:

The most recent request has been rejected by the server

when I attempt to connect to VDP. I found this:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2040078

and tried running the command:

ntpq -d IP Address

but no offset values were presented, instead I was at the ntpq> prompt where I am clueless.

HELP me. How do I get my VDP back on track!

Thanks!

I have noticed that I am unable to access both the VDP Configuration Manager or FLR from chrome starting in the last couple weeks.  It looks like the VDP appliance is still using a self-signed certificate signed with the SHA-1 algorithm and I wonder if that is cause.  Has anyone else noticed this?  If so is there a way to reissue the certificate so chrome will accept it?  I have noticed this on both VDP 5.5.8 and 6.

Hello,

as no one runs Linux with GUI installed, I'm trying to figure out if we can come up with some permanent workaround for the File Level Restores on Linux?

I'm thinking we can have a dedicated Linux VM with GUI and a browser installed, added to the VDP backup, which we can then use to do advanced logins from and be able to restore files from other VDP backed up Linux VMs.

If the above works, what about different distors? We use RHEL5.5/ext3, RHEL6/ext4, SLES11/ext3, all using LVM, all 64-bit. Will we have to have one VM of each kind with GUI installed for FLRs?

Thanks.

Hi,

I'm testing with Backup Exec 15 the incremental backup of VMs.

The flags for "ctkEnabled" and "scsi<x>:<x>.ctkEnabled" are both set and "True", the file "*-ctk.vmdk" also exists.

There are no snapshots, the compatibility is ESXi 6.0 (VM Version 11).

The problem is that the full / incremental backups have the same size, so the incremental backups seems not to work.

Would it be possible to check whether this is a problem of VMware ?

thanks

Dirk

Hi All,

My environment is vSphere 6 with 2x VDP Appliances (one for local backup and one as a replication target for a offsite NAS)

Disk Structure:

VDP (local): VDP.vmdk -> On local SAN

                    6x backup storage -> NFS-Onsite NAS

VDP-RT (offsite): VDP-RT -> On local SAN

                              6x backup storage -> NFS-Offiste NAS (roughly 25-30ms latency)

I configured both appliances onsite and replicate (roughly 1.3TB). I then shutdown and remove the replication target from inventory. Dismount the NFS datastore. Move the NAS offsite. Re-mount the datastore, add VDP-RT to inventory .. reconfigured the disks for the VDP-RT and try to boot and it the appliance hangs and this pointin the startup sequence.

I have left it for approx 12 hours with no change.

If i try to re-create the appliance and attach the existing VDP storage to the new appliance the new appliance will get through most of the configuration except hang at VDP: Configuring Import Storage task (stuck at 52%) for still over 12 hours.

I have gone through this process 2-3 times now and am still running into the same issue.

Am i missing something? Surely it cannot be thus hard to move my replication target storage offsite.

Kind Regards

Arun

Hi every one,

I am doing some test with DP 6.0 and the SQL backup, I have been doing some backups but I could not restore any of the backups yet.

Every time is the same error no matter if I do some changes during the restore process.

I can see these lines at the events panel from the vsphere client :

Task: VDP: Restore Job

VDP Restore "VM name" started

VDP server execution error code: 10007 Job name ......

VDP: Restore completed

Could you please tell me where to check if there is another log where I can find more information about this error?

Also, I have done backups and restores for individual VMs and it works fine, until now I have done backups from SQL Application but I could not complete the restore correctly.

Thanks

Hi, We are getting this error message during recatalog. -2241 destination index invalid/damaged

Is it possible to recover from and if so - what should i do?

Using VMware Data Recovery 1.1, backing up to CIFS share and getting this error

1/18/2010 8:55:31 AM: Performing incremental back up of disk "[Lun] VM/VM-DB1-flat.vmdk" using "SCSI Hot-Add"

1/18/2010 8:55:32 AM: Trouble writing to destination volume, error -1020 ( sharing violation)

Integrity checks of the destination complete successfully and I tried rebooting the VDR appliance just in case.

To resolve the issue I removed the share from the VDR, pointed the backups to other destinations and renamed the VMware Data Recovery subfolder in the destination, then re-added the share and pointed the backups, this of course creates a new Backup Store.

Anyone have any ideas why this error is occuring, means I can't backup into this Backup Store any longer.

I've been troubleshooting this error on and off for weeks and haven't seemed to be able to get to the bottom of it.  We have a relatively small ESX 3.5 infrastructure with two hosts and roughly 12 guest VMs connected to an iSCSI SAN.  We're using Backup Exec along with the agent for VMWare to back up all of the virtual servers.  Backups using the VMWare agent are successful 99% of the time for all hosts except one.  This one host will back up successfully 5-7 times in a row, then will fail 10-15 times always with the same error displaying in Backup Exec:

V-79-57344-38220 - Backup of the virtual machine 'CFHCUtil' failed. VMware VCB framework reported the following error

Error: Other error encountered: Snapshot creation failed: Could not quiesce file system.

I believe I'm running the latest version of VMWare Tools which is 3.5.0 build 184236.  I have the following VMWare device drivers enabled/installed within the client:

SCSI Driver

SVGA Driver

Mouse Driver

VMXNet NIC driver

Memory Control Driver

Filesystem Sync Driver

Volume Shadow Copy Services Support

I've reviewed the logs on the ESX host and have cut/pasted the following section which details the events leading up to the failure.  It looks the the snapshot completes successfully, but there appears to be an issue when reporting back to Backup Exec.  If anyone has had any luck resolving this once and for all, I'd love to hear the solution.

Task Created : haTask-16-vim.VirtualMachine.createSnapshot-38159

2010-04-09 05:56:25.426 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 info State Transition (VM_STATE_ON -> VM_STATE_CREATE_SNAPSHOT)

2010-04-09 05:56:25.427 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 info Trying quiesced snapshot via backup agent...

2010-04-09 05:58:00.185 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 info Starting to snapshot VM.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-000001-delta.vmdk" : open successful (21) size = 26843545600, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-000001-delta.vmdk" : open successful (21) size = 5368709120, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-000001-delta.vmdk" : open successful (21) size = 8589934592, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-flat.vmdk" : open successful (21) size = 26843545600, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-flat.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-flat.vmdk" : open successful (21) size = 5368709120, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-flat.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-flat.vmdk" : open successful (21) size = 8589934592, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-flat.vmdk" : closed.

2010-04-09 05:58:02.315 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 info Snapshot guest reported no errors.

2010-04-09 05:58:02.315 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 info Guest snapshot completed for quiesced snapshot via backup agent.

Task Created : haTask-ha-root-pool-vim.ResourcePool.updateConfig-38166

Task Completed : haTask-ha-root-pool-vim.ResourcePool.updateConfig-38166

Task Created : haTask-ha-root-pool-vim.ResourcePool.updateConfig-38167

Task Completed : haTask-ha-root-pool-vim.ResourcePool.updateConfig-38167

2010-04-09 05:58:10.392 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 info Notifying completion of quiesced snapshot via backup agent.

2010-04-09 05:58:10.647 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 error Quiesced snapshot backup agent error: Snapshot operation aborted (3)

2010-04-09 05:58:12.698 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 error Quiesced snapshot backup agent error: Asynchronous operation failed: Start

(5)

2010-04-09 05:58:14.699 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 error An error occurred while creating quiesced snapshot via backup agent.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-000001-delta.vmdk" : open successful (21) size = 26843545600, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-000001-delta.vmdk" : open successful (21) size = 5368709120, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-000001-delta.vmdk" : open successful (21) size = 8589934592, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-flat.vmdk" : open successful (21) size = 26843545600, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-flat.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-flat.vmdk" : open successful (21) size = 5368709120, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-flat.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-flat.vmdk" : open successful (21) size = 8589934592, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-flat.vmdk" : closed.

2010-04-09 05:58:15.329 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 info Removing timedout snapshot...

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-000001-delta.vmdk" : open successful (21) size = 26843545600, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-000001-delta.vmdk" : open successful (21) size = 5368709120, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-000001-delta.vmdk" : open successful (21) size = 8589934592, hd = 0. Type 8

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-000001-delta.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-flat.vmdk" : open successful (21) size = 26843545600, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName-flat.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-flat.vmdk" : open successful (21) size = 5368709120, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_1-flat.vmdk" : closed.

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-flat.vmdk" : open successful (21) size = 8589934592, hd = 0. Type 3

DISKLIB-VMFS : "/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName_2-flat.vmdk" : closed.

2010-04-09 05:58:51.952 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 warning Failed operation

2010-04-09 05:58:51.953 'vm:/vmfs/volumes/4b217231-245bf669-695f-0022640c9c72/ServerName/ServerName.vmx' 22137776 info State Transition (VM_STATE_CREATE_SNAPSHOT -> VM_STATE_ON)

Task Completed : haTask-16-vim.VirtualMachine.createSnapshot-38159

UPDATE : Mistake corrected with red color

Hello,

I use VDR 2.0.0 with ESXi 5 HA cluster created with 3 hosts and FC SAN acting as datastore.

I've tried to backup VM with two vmdks - first 102GB and second 1,6TB. VDR does machine snapshot but strangely two delta files for each disk appear (00001-delta, 00002-delta) rather the only one (?). After that, it starts copying data from second disk then stops at 102GB and hungs up for a two/three minutes. Then for second disk new delta file appears (00003-delta) for a moment and right after VDR remove snapshot. ESX host complains that VM disks need consolidation but it gives an error that <unspecified file> is locked and can't finish it.

Running lsof on the machine hosting that particular VM says that deltas are being used by vpxa-worker process, so finally after killing it, consolidation is possible.

Backing up the VM is all the same wherever it's running - on the same ESXi host as VDR or the other. Another machines, e.g. GNU/Linux with 1,6TB vmdk backs up successfully.

Could somebody have any idea what's going on ?

Any idea highly appreciated.

Best regards

In the VDR logs message "Trouble reading files, error -3956 (operation failed)" appears and in vcbAPI-xx.log it claims that :

2012-07-11T08:16:22.967+02:00 [4C805940 warning 'Default'] The change associated with a property collector field parent is NULL
2012-07-11T08:16:22.968+02:00 [4C805940 info 'Default'] vcbAPI::propCollWrap::doHostSystem: Detected a availability state change for host 192.168.x.1: The state is now available.
2012-07-11T08:16:22.979+02:00 [4C805940 info 'Default'] vcbAPI::propCollWrap::doHostSystem: Detected a availability state change for host 192.168.x.2: The state is now available.
2012-07-11T08:16:22.988+02:00 [4C805940 info 'Default'] vcbAPI::propCollWrap::doHostSystem: Detected a availability state change for host 192.168.x.3: The state is now available.
2012-07-11T08:16:23.030+02:00 [4C805940 info 'blocklist'] Creating snapshot
2012-07-11T08:16:53.394+02:00 [4C805940 info 'blocklist'] Snapshot created, ID: snapshot-3490
2012-07-11T08:16:53.471+02:00 [4C805940 info 'Default'] Establishing NFC connection to host 192.168.x.3 on port 902, service vpxa-nfc
2012-07-11T08:16:53.890+02:00 [4C805940 info 'Default'] VcbAPI::Snapshot::Open: Attempting to access hot-add mode, in parallel mode.
2012-07-11T08:16:53.890+02:00 [4C805940 info 'blocklist'] PrepareForAccess: getting a hot-add instance in parallel mode
2012-07-11T08:16:53.903+02:00 [4C805940 error 'blocklist'] This VM [N3Vim18VirtualMachineStubE:0x61e4810] is not licensed for HotAdd
2012-07-11T08:16:53.903+02:00 [4C805940 info 'Default'] VcbAPI::Snapshot::Open: Exception trying to HotAdd: HotAdd is not licensed
2012-07-11T08:16:53.929+02:00 [4C805940 info 'blocklist'] Will remove all disks belonging to VM "VIRTUAL MACHINE"(vm-3274), Snapshot "snapshot-3490".
2012-07-11T08:16:53.948+02:00 [4C805940 info 'blocklist'] Remove clone disks successful.
2012-07-11T08:17:01.554+02:00 [4C805940 info 'Default'] VcbAPI::Snapshot::GetUnusedFileInfo: Could not obtain file blocks for "pagefile.sys" on one of Partitions of path: "[datastore] VIRTUAL MACHINE/VIRTUAL MACHINE-000002.vmdk", error: 32769
2012-07-11T08:17:01.555+02:00 [4C805940 info 'Default'] VcbAPI::Snapshot::GetUnusedFileInfo: "pagefile.sys" removed from volume "[datastore] VIRTUAL MACHINE/VIRTUAL MACHINE-000002.vmdk"
2012-07-11T08:17:01.748+02:00 [4C805940 info 'Default'] VcbAPI::Snapshot::GetChangeInfo: Processing 1045 changes
2012-07-11T08:17:02.117+02:00 [4C805940 warning 'Default'] VcbAPI::Snapshot::GetChangeInfo: Cannot look for changes past the end of the disk, disk size: 109889715200, offset: 109889715712.
2012-07-11T08:21:30.033+02:00 [4C805940 error 'Default'] vcbAPI::Snapshot::Read: Main read failed for disk [datastore] VIRTUAL MACHINE/VIRTUAL MACHINE_2-disk-000002.vmdk, error: 2338
2012-07-11T08:21:30.041+02:00 [4C805940 error 'Default'] RealPartitionReader: File i/o error ($1)

I'm configuring an environment which uses Veeam for the backups.

In order to make the snapshots used by the backup tool application consistent we implemented pre-freeze scipts.

We notice however that these have a 15 minute hard-limit in their execution time. Stopping some application servers may take quite some more time to achieve.

Is there a way to alter this time-out setting?

I'm using Veeam Backup & Recovery version 6.5 with VMware vSphere ESXi 5.1. The VM storage is local to the ESXi server in a RAID5 SAS array. Veeam is running on a separate physical machine and backing up over a 2 Gbps aggregated link, onto an external USB 2.0 hard drive.

Veeam seems to top out at about 22MB/s when performing a backup operation, and indicates that the bottleneck is the source. This seems too slow given the setup, and I'm wondering if I'm missing something. Can anyone shed any light on my situation?

As you might know, VBR7 was launched late this August and since then many hundreds of customers were posting numerous bug reports on Veeam's forums. I, myself, happen to be their customer and I decided to track the most critical bugs before I migrate my clients to a new version. So, this is my list, please, add what you think are other critical bugs, that I didn't mention.

http://forums.veeam.com/viewtopic.php?f=2&t=17224 - Critical issue and poor handling by support: it is a known issue in the old version of this software and you can see that posts in this thread date back to 2009. One might've expected that they'll deal with this issue in the new version, but, unfortunately, it is still present. Very dissapointing.

As for Veeam tech support, one thing I noticed is that they were flooded so badly with bug reports this August-September that the only answer one could've gotten from them was: "Please, go read about this in the Knowledge Base on our website". I've seen tons of replies like this on their support forums. Not very helpful, obviously, if you have a pressing issue and need a solution right away.

http://forums.veeam.com/viewtopic.php?f=2&t=17872 - Complaints on BS called "WAN accelerator": they've added a new useless gizmo that became a problem in itself causing new complaints. Why add new buggy useless feature?

http://forums.veeam.com/viewtopic.php?f=2&t=17887 - Poor Performance on File verification and againg support send the customer back to User Guide. Yeah, right

http://forums.veeam.com/viewtopic.php?f=2&t=17597 - Random errors are usual thing for a new complex software, but with VBR7 one just gets too many which is frustrating. You get the error, go to their tech support forum and there they say to review the docs again. OOOOOOOOOOk!

http://forums.veeam.com/viewtopic.php?f=2&t=17898 - Dropped support for still quite popular W2K3 x64 (this can be expanded to a problem with upgrade at Customer's site, who wants to backup to tape, etc)

These are the most critical bugs and issues, as I see it.

If you noticed other critical issues, please, comment, add you feedback here or in my blog:

http://vbscs.wordpress.com/2013/09/13/veeam-backup-replication-7-total-disaster/

Hello,

I have 3 clusters running ESXi 5.0 with VCenter 5.0.

I would like to use the VDP 5.1, but for that I need to update the VCenter 5.1.

Know tell me that the VDP 5.1 (2TB) is free?

Someone does not recommend its use?

Tks,

Message was edited by: Brian Atkinson to remove the ALLCAPS from the subject line

I have ESXi 5.1 & ESXi 5.5 hosts, both using custom HP DL360 images (Gen8).  When trying to backup a raw VM with Arcserve 16.5 (patched to latest release & support for ESXi 5.5 etc), i get this error returned from ESXi.

>

1/27/14 15:53:15  [1326.1] SnapshotVM returned -110.

1/27/14 15:53:16  Err_code: -110 SnapshotVM: Exception Raised - Current license or ESXi version prohibits execution of the requested operation.

1/27/14 15:53:16  [1326.1] An unexpected error occurred while creating snapshot for the VM having UUID 564d946e-ea6c-f876-bbf9-xxxxxxxxxx (etc).

The free ESXi license is applied to the ESXi hosts as expected. Is anyone familiar with this error response.. Does anyone know if their is a limitation for backup support for VM with the free ESXi license ?

I have the cbt enabled correctly and are able to do snapshots successfully.

Many Thanks,

Mal