Every day, during the backup window receives about 10 alerts like this.

Backups take longer than 12 hours to finalize

Does anyone have any idea how to solve this?

Sorry for trouble again, not sure if this is correct category, moving this discussion from vCenter to vSphere.

hope get some help from you.

Hi, All

There is one question regarding VMware snapshot technology - CoW or RoW, confusing me for a long time, hope someone can help clarify this.

As we know that the difference between CoW and RoW is the location the changed data is written after a snapshot, like the snapshot space or original data area, for CoW, the changed data will be written to original data area instead of snapshot space after original data to be changed is copied to snapshot space, and for RoW, the changed data will be written to the space stores.

When take a snapshot for VMware, it creates some files, like delta disk files, .vmsd file, for delta disk files, it's a snapshot file and will store the changed data since last snapshot. So from this perspective, the snapshot technology VMware uses should be RoW, right?

However, from VMware guide or KB, we know that it uses CoW technology, as follows:

Understanding virtual machine snapshots in VMware ESXi and ESX (1015180) | VMware KB

The child disk

The child disk, which is created with a snapshot, is a sparse disk. Sparse disks employ the copy-on-write (COW) mechanism, in which the virtual disk contains no data in places, until copied there by a write. This optimization saves storage space. The grain is the unit of measure in which the sparse disk uses the copy-on-write mechanism. Each grain is a block of sectors containing virtual disk data. The default size is 128 sectors or 64 KB.

In addition, can anyone help explain the following snapshot chain regarding how it forms?

thanks

walker

Hello,

This has been an ongoing issue with the last few VDP versions.

I update vSphere to the latest version (in this case 6.5.0 5224529) and then the VMware tools on VDP appliances throws a warning that it is out of date.

I learned the hard way that you cannot simply perform the "Upgrade VMware Tools" automatically... it just uninstalls it and then cannot install the new version.

In the past I would just update to the newest version of VDP (in this case 6.1.4) and the problem would go away.

However, it hasn't gone away...

1. Is this problem really hurting anything? Backups seem to be ok.

2. Is there a KB or something that acknowledges this issue and/or provides a fix?

Thanks!

Hi, Everyone.

Hope you could help me with this issue. Here are the scenario that I have

Scenario: This is newly built vdp server, it doesn't have so much in it. Right now when I go to vsphere data protection->configuration, the status is stuck on Admin. I have tried performing dpnctl stop gsan & start gsan. It automatically switch back to degraded after few seconds. I have manually perform integrity check but the same issue arise.  I have posted below the disk usage on our VDP for reference.

Filesystem      Size  Used Avail Use% Mounted on

/dev/sda2        32G  6.0G   24G  20% /

udev            1.9G  148K  1.9G   1% /dev

tmpfs           1.9G     0  1.9G   0% /dev/shm

/dev/sda1       128M   37M   85M  31% /boot

/dev/sda7       1.5G  184M  1.2G  14% /var

/dev/sda9       138G  4.9G  126G   4% /space

/dev/sdb1       512G   52G  461G  11% /data01

/dev/sdc1       512G   51G  461G  10% /data02

/dev/sdd1       256G   51G  206G  20% /data03

If more information is needed, please let me know and I'll provide those information.

Hello,

Every now and then he gets an email notification saying "The vSphere Data Protection alert is triggered. VDP6: VDP: [008] File level restore services are not running"

I can not find anything in the logs. He just writes that the mechanism of sending the above message has been triggered but in general all of the services work.

The problem is so much weird that messages come at random.

Once it is so that you get a daily message and once there is peace for a week.

I successfully upgraded our two VDP 6.1.8 instances to 6.1.9, but having issues upgrading them to 6.1.10 now.  The ISO mounts, but in the UI under 'Upgrade' it's showing "To upgrade your VDP appliance, place connect a valid upgrade ISO image to the appliance."  The avinstaller.log shows no activity since upgrading to 6.1.9, so I tried restarting the avinstaller service (avinstaller.pl --restart), but when it tries to stop the service it shows a Java "Connection refused" exception.  Anyone know what could be happening or how to debug further?  Thanks.

VDP configuration and installation are normal, but backup error, backup can not continue, although you see            Fail to download VM metadata, try later, but I don't know what the problem is.            The error log is as follows. Ask for help:

--------------------------------------------------------------------------------------------------------

-----  START avvcbimage log 2019-03-07 11:38:09 CST  [7.2.180-167 Linux-x86_64]

--------------------------------------------------------------------------------------------------------

2019-03-07T11:38:09.033-08:00 avvcbimage Info <5008>: Logging to /usr/local/avamarclient/var/test2-1551929879509-3306f8eb7116f7c3e2b9e9e59a4c3a0c591e4e98-1016-vmimagel.log

2019-03-07T11:38:09.033-08:00 avvcbimage Info <5174>: - Reading /root/.avamar

2019-03-07T11:38:09.033-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamar/etc/usersettings.cfg

2019-03-07T11:38:09.034-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimage.cmd

2019-03-07T11:38:09.034-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd

2019-03-07T11:38:09.038-08:00 avvcbimage Info <6673>: CTL listening on port 52565

2019-03-07T11:38:09.040-08:00 avvcbimage Info <10684>: Setting ctl message version to 3 (from 1)

2019-03-07T11:38:09.040-08:00 avvcbimage Info <16136>: Setting ctl max message size to 268435456

2019-03-07T11:38:09.043-08:00 avvcbimage Info <40636>: SSL Certificate Thumbprint: 58:92:C8:7E:11:CE:AB:36:92:8A:60:40:30:CE:D8:CC:53:F1:40:1C

2019-03-07T11:38:09.043-08:00 avvcbimage Info <0000>: job type = 4

2019-03-07T11:38:09.064-08:00 avvcbimage Info <18664>: Login(https://vcsa01.lntmh.com:443/sdk) Datacenter: 'New Core Business'

2019-03-07T11:38:09.064-08:00 avvcbimage Info <19728>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-10244857',  apiVersion:'6.7.1'

2019-03-07T11:38:09.130-08:00 avvcbimage Info <14692>: Login test is OK.

2019-03-07T11:38:09.236-08:00 avvcbimage Info <40726>: VM Config Info: VMX version 4(F), ctk enabled(T), fault tolerant (F), Guest OS Red Hat Enterprise Linux 6 (64-bit), Cloud UUID = NoUUID. version=13

2019-03-07T11:38:09.255-08:00 avvcbimage Info <40727>: VM Guest Info: GuestOS Family = linuxGuest, Guest Full Name = CentOS 4/5 or later (64-bit), Guest OS State = running, Tools Running = guestToolsRunning,  Tools Version Status = guestToolsUnmanaged

2019-03-07T11:38:09.324-08:00 avvcbimage Info <14625>: WorkOrder Disk Info:

   Prior Disk '2000': file(base):'[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmdk', backItUp=1

                snapshot file:'[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmdk'

                prior size(KB):0, current size(KB):367001600, match=0

                prior change block ID:''

                Datastore:'Macrosan_AutoTier_Lun03' Directly Accessible=1

2019-03-07T11:38:09.424-08:00 avvcbimage Info <40637>: Proxy Host Name=esxi29.lntmh.com(6.7.1 build-10302608)

2019-03-07T11:38:09.507-08:00 avvcbimage Info <40638>: VM Host Name=esxi30.lntmh.com(6.7.1 build-10302608)

2019-03-07T11:38:09.507-08:00 avvcbimage Info <19547>: Using Simultaneous Workorders method

2019-03-07T11:38:09.507-08:00 avvcbimage Info <19652>: Updated cache lookup

2019-03-07T11:38:09.507-08:00 avvcbimage Info <19587>: Create cache lock file succeeded

2019-03-07T11:38:09.507-08:00 avvcbimage Info <19588>: usLockFile: /usr/local/avamarclient/bin/var1.lck

2019-03-07T11:38:09.508-08:00 avvcbimage Info <11979>: proxy VM DNS name is: 127.0.0.2,vdp01.lntmh.com,vdp01,192.168.101.126

2019-03-07T11:38:09.508-08:00 avvcbimage Info <18672>: proxy VM Instance name is: vdp01.lntmh.com-proxy-1

2019-03-07T11:38:09.508-08:00 avvcbimage Info <17793>: proxy VM Moref is: vm-5063

2019-03-07T11:38:09.508-08:00 avvcbimage Info <16010>: vCenter 'New Core Business' is vcsa01.lntmh.com

2019-03-07T11:38:09.508-08:00 avvcbimage Info <11981>: VM's host is esxi30.lntmh.com

2019-03-07T11:38:09.508-08:00 avvcbimage Info <11982>: VM's primary storage location is [Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmx

2019-03-07T11:38:09.508-08:00 avvcbimage Info <11983>: VM's vCenter ID is vm-3973

2019-03-07T11:38:09.508-08:00 avvcbimage Info <19658>: change block file: VmImage1_changefilemap.tmp

2019-03-07T11:38:09.541-08:00 avvcbimage Info <11984>: VM's backup account on vdp01.lntmh.com is /vcsa01.lntmh.com/VirtualMachines/ZYLWEB01_UBfzB1oMmAggk1yC18TNtA

2019-03-07T11:38:09.541-08:00 avvcbimage Info <11986>: Changed block tracking is engaged for this VM

2019-03-07T11:38:09.541-08:00 avvcbimage Info <11988>: A reference to a valid prior backup is not available so this will be a full level zero backup.

2019-03-07T11:38:09.610-08:00 avvcbimage Info <19549>: metadata tmp dir: /usr/local/avamarclient/var/vmware/1/temp

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware/1, failed (-1)

2019-03-07T11:38:09.610-08:00 avvcbimage Info <40640>: create tmpDir: /usr/local/avamarclient/var/vmware/1/temp, failed (-1)

2019-03-07T11:38:09.611-08:00 avvcbimage Info <40654>: isExitOK()=0

2019-03-07T11:38:09.611-08:00 avvcbimage Info <17823>: Body- abortrecommended(f)

2019-03-07T11:38:09.613-08:00 avvcbimage Info <19660>: targetlist contains <path backup="true" name="[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmdk" diskCapacity="375809638400" />

2019-03-07T11:38:09.613-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimage.cmd

2019-03-07T11:38:09.613-08:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd

2019-03-07T11:38:09.613-08:00 avvcbimage Info <7084>: target[0]=[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmdk

2019-03-07T11:38:09.613-08:00 avvcbimage Info <40658>: vmparams (vcsa01.lntmh.com)

2019-03-07T11:38:09.613-08:00 avvcbimage Info <40654>: isExitOK()=0

2019-03-07T11:38:09.628-08:00 avvcbimage Info <18664>: Login(https://vcsa01.lntmh.com:443/sdk) Datacenter: 'New Core Business'

2019-03-07T11:38:09.628-08:00 avvcbimage Info <19728>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-10244857',  apiVersion:'6.7.1'

2019-03-07T11:38:09.657-08:00 avvcbimage Info <14692>: Login test is OK.

2019-03-07T11:38:09.746-08:00 avvcbimage Info <18664>: Login(https://vcsa01.lntmh.com:443/sdk) Datacenter: 'New Core Business'

2019-03-07T11:38:09.746-08:00 avvcbimage Info <19728>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-10244857',  apiVersion:'6.7.1'

2019-03-07T11:38:09.772-08:00 avvcbimage Info <14692>: Login test is OK.

2019-03-07T11:38:09.773-08:00 avvcbimage Info <16041>: VDDK:OBJLIB-LIB: Objlib initialized.

2019-03-07T11:38:09.773-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Attempting to locate advanced transport module in "/usr/lib/vmware-vix-disklib".

2019-03-07T11:38:09.966-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Advanced transport plugin /usr/lib/vmware-vix-disklib/lib64/libdiskLibPlugin.so was successfully loaded into vixDiskLib.

2019-03-07T11:38:09.966-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Enabling advanced transport modes.

2019-03-07T11:38:09.967-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Initialize transport modes.

2019-03-07T11:38:09.967-08:00 avvcbimage Info <16041>: VDDK:2019-03-07T11:38:09.967+08:00 info -[7F239E879700] [Originator@6876 sub=vm:DictionaryLoad: Cannot open file "/etc/vmware/vsphereFeatures/vsphereFeatures.cfg] : No such file or directory.

2019-03-07T11:38:09.967-08:00 avvcbimage Info <16041>: VDDK:2019-03-07T11:38:09.967+08:00 info -[7F239E879700] [Originator@6876 sub=vm:[msg.dictionary.load.openFailed] Cannot open file "/etc/vmware/vsphereFeatures/vsphereFeatures.cfg] : No such file or directory.

2019-03-07T11:38:09.967-08:00 avvcbimage Info <16041>: VDDK:2019-03-07T11:38:09.967+08:00 info -[7F239E879700] [Originator@6876 sub=vm:FeatureStateLib: Error while loading feature config file: /etc/vmware/vsphereFeatures/vsphereFeatures.cfg]  using default feature state values.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Available transport modes: file:san:hotadd:nbdssl:nbd.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:VMware VixDiskLib (6.5) Release build-5993564

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/config": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.

2019-03-07T11:38:09.991-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /root/.vmware/preferences. Using default values.

2019-03-07T11:38:09.992-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: OpenSSL using FIPS_drbg for RAND

2019-03-07T11:38:09.992-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: protocol list tls1.2

2019-03-07T11:38:09.992-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)

2019-03-07T11:38:09.992-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_Init: Initialization is completed.

2019-03-07T11:38:10.008-08:00 avvcbimage Info <9666>: Available transport modes are file:san:hotadd:nbdssl:nbd

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_PrepareForAccess: Prepare to access disk.

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Resolve host.

2019-03-07T11:38:10.008-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_AllowVMotion: Disable VMotion.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/config": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /usr/lib/vmware/config. Using default values.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/root/.vmware/config": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/config": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /root/.vmware/config. Using default values.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:DictionaryLoad: Cannot open file "/root/.vmware/preferences": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:[msg.dictionary.load.openFailed] Cannot open file "/root/.vmware/preferences": No such file or directory.

2019-03-07T11:38:10.009-08:00 avvcbimage Info <16041>: VDDK:PREF Optional preferences file not found at /root/.vmware/preferences. Using default values.

2019-03-07T11:38:10.010-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: OpenSSL using FIPS_drbg for RAND

2019-03-07T11:38:10.010-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: protocol list tls1.2

2019-03-07T11:38:10.010-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: protocol list tls1.2 (openssl flags 0x17000000)

2019-03-07T11:38:10.010-08:00 avvcbimage Info <16041>: VDDK:lib/ssl: cipher list !aNULL:kECDH+AESGCM:ECDH+AESGCM:RSA+AESGCM:kECDH+AES:ECDH+AES:RSA+AES

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

2019-03-07T11:38:10.549-08:00 avvcbimage Info <17818>: VixDiskLib vMotion reservation successfully enabled by 'vSphere Data Protection'

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16011>: Running cleanup of old backups.

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Cleanup: Remove previous mount points and clean up .

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2019-03-07T11:38:10.549-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Resolve host.

2019-03-07T11:38:10.550-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Disconnect: Disconnect.

2019-03-07T11:38:10.550-08:00 avvcbimage Info <16048>: VixDiskLib_Cleanup() found no prior mounts to cleanup.

2019-03-07T11:38:10.562-08:00 avvcbimage Info <18664>: Login(https://vcsa01.lntmh.com:443/sdk) Datacenter: 'New Core Business'

2019-03-07T11:38:10.562-08:00 avvcbimage Info <19728>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 6.7.0 build-10244857',  apiVersion:'6.7.1'

2019-03-07T11:38:10.587-08:00 avvcbimage Info <14692>: Login test is OK.

2019-03-07T11:38:10.620-08:00 avvcbimage Info <0000>: SnapshotManager: initializing at 127.0.0.1:8543, vCenter vcsa01.lntmh.com(administrator@vsphere.local), datacenter(/New Core Business), httpsTimeout_ms(60000), maxDeleteRetries(-1)

2019-03-07T11:38:10.696-08:00 avvcbimage Info <0000>: GET: curl_easy_getinfo succeeded with httpcode(200)

2019-03-07T11:38:10.701-08:00 avvcbimage Info <0000>: AvSnapMgr::getData Succeeded httpCode: 200

2019-03-07T11:38:10.701-08:00 avvcbimage Info <0000>: SnapshotManager version:7.2.80.167

2019-03-07T11:38:10.701-08:00 avvcbimage Info <40642>: Using SnapShot Manager - with fallback to proxy calling vSphere API functions.

2019-03-07T11:38:10.768-08:00 avvcbimage Info <18648>: The snapshot '' could not be removed.

2019-03-07T11:38:10.811-08:00 avvcbimage Info <40751>:  Datastore Macrosan_AutoTier_Lun03

2019-03-07T11:38:10.828-08:00 avvcbimage Info <14664>: no snapshots are present on this VM.

2019-03-07T11:38:10.862-08:00 avvcbimage Info <0000>: (CURL) Logging into datacenter path of 'folder?dcPath=New%2520Core%2520Business', New Core Business => New%2520Core%2520Business

2019-03-07T11:38:10.862-08:00 avvcbimage Info <0000>: (Legacy) Logging into datacenter path of 'folder?dcPath=New%2520Core%2520Business', New Core Business => New%2520Core%2520Business

2019-03-07T11:38:10.862-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:38:10.862-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:38:20.872-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:38:20.872-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:38:30.882-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:38:30.882-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:38:40.894-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:38:40.904-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:38:50.912-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:38:50.932-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:39:00.932-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:39:00.942-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:39:10.942-08:00 avvcbimage Warning <40648>: DataStore/VM Info download failed.

2019-03-07T11:39:10.942-08:00 avvcbimage Warning <0000>: [IMG0016] The datastore from VMX '[Macrosan_AutoTier_Lun03] ZYLWEB01/ZYLWEB01.vmx' could not be fully inspected.

2019-03-07T11:39:10.964-08:00 avvcbimage Info <0000>: (CURL) Logging into datacenter path of 'folder?dcPath=New%2520Core%2520Business', New Core Business => New%2520Core%2520Business

2019-03-07T11:39:10.964-08:00 avvcbimage Info <0000>: (Legacy) Logging into datacenter path of 'folder?dcPath=New%2520Core%2520Business', New Core Business => New%2520Core%2520Business

2019-03-07T11:39:10.964-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:39:10.964-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:21.007-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:39:21.007-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:31.018-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:39:31.018-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:41.033-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:39:41.033-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:41.078-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:39:51.084-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:39:51.084-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:39:51.192-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:40:01.193-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:40:01.193-08:00 avvcbimage Info <14620>: Logging into datacenter 'vcsa01.lntmh.com' with user 'administrator@vsphere.local'

2019-03-07T11:40:01.228-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:40:11.229-08:00 avvcbimage Info <0000>: initial attempt at downloading VM file failed, now trying by re-creating the HREF, (CURL) /folder/ZYLWEB01%2fZYLWEB01.vmx?dcPath=%252fNew%2520Core%2520Business&dsName=Macrosan_AutoTier_Lun03, (LEGACY) /folder/ZYLWEB01%2FZYLWEB01.vmx?dcPath=%252FNew%2520Core%2520Business&dsName=Macrosan%255FAutoTier%255FLun03.

2019-03-07T11:40:11.229-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:40:11.229-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:40:21.239-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:40:21.239-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:40:31.252-08:00 avvcbimage Info <41153>: Using CURL Method

2019-03-07T11:40:31.252-08:00 avvcbimage Info <41154>: Re-using vCS Session Cookie

2019-03-07T11:40:41.263-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:40:41.263-08:00 avvcbimage Info <40756>: Attempting to Download file:/folder/ZYLWEB01%2FZYLWEB01.vmx?dcPath=%252FNew%2520Core%2520Business&dsName=Macrosan%255FAutoTier%255FLun03

2019-03-07T11:40:41.278-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:40:51.280-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:40:51.280-08:00 avvcbimage Info <40756>: Attempting to Download file:/folder/ZYLWEB01%2FZYLWEB01.vmx?dcPath=%252FNew%2520Core%2520Business&dsName=Macrosan%255FAutoTier%255FLun03

2019-03-07T11:40:51.298-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:41:01.299-08:00 avvcbimage Info <41155>: Using Legacy Method

2019-03-07T11:41:01.299-08:00 avvcbimage Info <40756>: Attempting to Download file:/folder/ZYLWEB01%2FZYLWEB01.vmx?dcPath=%252FNew%2520Core%2520Business&dsName=Macrosan%255FAutoTier%255FLun03

2019-03-07T11:41:01.317-08:00 avvcbimage Warning <15995>: HTTP fault detected, Problem with returning page from HTTP, Msg:'SOAP 1.1 fault: SOAP-ENV:Server [no subcode]

"HTTP Error"

Detail: HTTP/1.1 404 Not Found

'

2019-03-07T11:41:11.317-08:00 avvcbimage Warning <40650>: Download VM .vmx file failed.

2019-03-07T11:41:11.317-08:00 avvcbimage Error <17821>: failed to download vm metadata, try later

2019-03-07T11:41:11.317-08:00 avvcbimage Info <9772>: Starting graceful (staged) termination, failed to download vm metadata (wrap-up stage)

2019-03-07T11:41:11.318-08:00 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation  or pre/post snapshot script failed

2019-03-07T11:41:11.318-08:00 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation/pre-script/post-script failed

2019-03-07T11:41:11.318-08:00 avvcbimage Info <40654>: isExitOK()=157

2019-03-07T11:41:11.318-08:00 avvcbimage Info <40659>: snapshot created:false NOMC:false ChangeBlTrackingAvail:true UsingChBl:true, ExitOK:false, cancelled:false, fatal: true

2019-03-07T11:41:11.318-08:00 avvcbimage Info <40654>: isExitOK()=157

2019-03-07T11:41:11.318-08:00 avvcbimage Info <40660>: vcbimage_progress::terminate

2019-03-07T11:41:11.319-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_EndAccess: Disk access completed.

2019-03-07T11:41:11.319-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2019-03-07T11:41:11.319-08:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Resolve host.

2019-03-07T11:41:11.320-08:00 avvcbimage Info <16038>: Final summary, cancelled/aborted 0, snapview 0, exitcode 157: miscellaneous error

2019-03-07T11:41:11.320-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_AllowVMotion: Enable VMotion.

2019-03-07T11:41:11.704-08:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

2019-03-07T11:41:11.704-08:00 avvcbimage Info <17819>: VixDiskLib vMotion reservation successfully released

--------------------------------------------------------------------------------------------------------

----- END avvcbimage log 2019-03-07 11:41:16 CST  (12 warnings, 3 errors, 0 fatal errors)

--------------------------------------------------------------------------------------------------------      

Hello all,

Then i try to backup VM using VDR the following error occured:

Create virtual machine snapshot

Cannot create a quiesced snapshot because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.

How can i fix this issue ?

Please help...thanks.

Hi!

I can not backup my VM, because the VCB stop when it start's backup Hard Disk 2. (scsi0-1-0-WEB-clone_1.vmdk)

VM settings:

Guest OS: Red Hat Enterprise Linux 4 (32-bit)
Hard Disk 1: 30 GB
Hard Disk 2: 1024 GB

C:\Program Files\VMware\VMware Consolidated Backup Framework&gt;

vcbMounter.exe -h virtualcenter -u xxx -p yyy -a moref:vm-789 -r H:\HR_Web -t fullvm -m nbd

Current working directory: C:\Program

Files\VMware\VMware Consolidated Backup Framework

HOSTINFO: Seeing Intel CPU, numCo

resPerCPU 2 numThreadsPerCore 1.

HOSTINFO: This machine has 1 phys

ical CPUS, 2 total cores, and 2 logical CPUs.

Using system libcrypto, version 9

0709F

SSLVerifyCertAgainstSystemStor

e: Subject mismatch: VMware vs virtualcenter

SSLVerifyCertAgainstSystemStor

e: The remote host certificate has these problems:

• The host name used for the connection does not match the subject name on the h

ost certificate

• A certificate in the host's chain is based on an untrusted root.

SSLVerifyIsEnabled: failed to

read registry value. Assuming verification is disabled. LastError = 0

SSLVerifyCertAgainstSystemStor

e: Certificate verification is disabled, so connection will proceed despite the

error

Copying "[Datastore03_SATA] WEB-clone/WEB-clone.vmx":

        0%=====================50%=====================100%

        **************************************************

Copying "[Datastore03_SATA] WEB-clone/WEB-clone.nvram":

        0%=====================50%=====================100%

        **************************************************

Copying "[Datastore03_SATA] WEB-clone//vmware-55.log":

        0%=====================50%=====================100%

        **************************************************

Copying "[Datastore03_SATA] WEB-clone//vmware-56.log":

        0%=====================50%=====================100%

        **************************************************

Copying "[Datastore03_SATA] WEB-clone//vmware-57.log":

        0%=====================50%=====================100%

        **************************************************

Copying "[Datastore03_SATA] WEB-clone//vmware-58.log":

        0%=====================50%=====================100%

        **************************************************

Copying "[Datastore03_SATA] WEB-clone//vmware-59.log":

        0%=====================50%=====================100%

        **************************************************

Copying "[Datastore03_SATA] WEB-clone//vmware-54.log":

        0%=====================50%=====================100%

        *************************************************

Copying "[Datastore03_SATA] WEB-clone//vmware.log":

        0%=====================50%=====================100%

        **************************************************

Converting "H:\HR_Web\scsi0-0-0-WEB-clone.vmdk" (compact file):

        0%=====================50%=====================100%

        **************************************************

Converting "H:\HR_Web\scsi0-1-0-WEB-clone_1.vmdk" (compact file):

        0%=====================50%=====================100%

        **************************************************

Error: Failed to export the di

sk: One of the parameters supplied is invalid

An error occurred, cleaning up

...

Deleted directory H:\HR_Web

TKS!

Hi

I feel like this question should be answered in at least ten knowledgebase articles and other documentations, yet i seem to be unable to find any of them ...

I have BackupExec 2010 and vSphere 4.0 Enterprise Plus (3 ESX 4 servers). So far, I've been testing the nbd transport mode, which works, but gets slow sometimes on VMs with disks >100GB (i read that this is a problem with the service console of vmware esx 4 - not sure though).

Anyhow, since I have all the necessary hardware on site, i thought i could as well connect the server running backupexec (and vsphere server) to the san directly using FC...

... but i can't find a guide, neither from vmware nor from backupexec nor EMC, on what i should pay attention while doing this. Those questions came up before I've even touched the FC-Controller:

- vsphere 4.0 has this storage API thingy ... backupexec 2010 apparently supports it. does that mean that i don't have to install vmware VCB?

- I'm running backupexec 2010 and vSphere Server on the same box...any problems with that?

- i feel really uncomfortable that windows might write something to my vmfs luns, and destroying them with it... (like auto-signing or auto-initializing of new disks). how do i prevent windows from doing so?

- i read about a problem with multi-pathing and san backup mode ... i could just install EMC powerpath, which would handle the multipathing. does that work with vsphere storage api?

any answers (or links to documents i'm apparently unable to find) are very much appreciated.

best regards,

A lot has been said about problems with using snapshots with Domain Controllers and most of what has been said simply translates to

"DO NOT DO IT!"

However, based on how things work and why the problems happen I am not sure that this statement applies to all cases.

USN rollback is caused when you revert a single DC back and the USN number of the local copy is lets say 10 but on its replica partner has the reverted DCs USN of 20. Some people ask the question "well how is it that when i restore a DC from a backup i bring it to same state reverting USN and this is not an issue" for one the database invocation ID is changed on restore and the system marks the server and database as restored and thus knows how to proceed with proper replication. This is obviously not the case with snapshot revert.

Now for questions I have to confirm my theory:

CASE 1

so what happens when you have a single DC environment or SBS system? I would this that in the single DC system the snapshots should be perfectly ok for  Domain Controller as it has no replication partner....Can anyone at VMware confirm this??

CASE 2

Also what if you have 2 DC's and you want to use snapshot prior to an upgrade and do the following:

   1. shutdown replication between servers using "repadmin /options +DISABLE_OUTBOUND_REPL"

   2. Take a snapshot of both servers and enable replication back.

and then if something goes wrong you should be able to safely revert backup IF and ONLY IF you revert BOTH DC's back to the same state and enable replication back as it was disabled during snapshot.

Above 2 cases i would think should be ok and would not cause any USN rollback issues or cause any problems on the domain. Can anyone confirm this as i have not had the chance to test it and even if i do you never really know 100% if any damage occurs in database level even if all checks come back good.

We are having issue to perform VADP backup with EMC² Networker 7.6.2 with a VM which in total equals about 2.3 TB of data.
The setup is the following:

VM (fileserver) running on Windows 2008 R2

The backup server (physical) is running Networker 7.6.2 and is also proxy host for VADP backups.

VMware vSphere ESXi 4.1 Update 1

When we perform an ESX snapshot of the fileserver, no problem.
When we try a VADP backup via Networker, it fails with the following error:

Other client VADP backups (smaller ones) are running fine.

Someone told me that the NBD has certain limits regarding VM Size.
He said when he VM size equals 1TB or more, we should NOT use NBD.

Is anyone able to explain me or provide me with proof of this ?

in the documentation it mentions that for windows, VMware will execute all of the scripts in c:\Program Files\VMware\VMwareTools\backupScipts.d

or  /usr/sbin/pre-freeze-script

I assume  /usr/sbin/pre-freeze-script is a file name and not a diretcory, (can someone verify?)

for c"\....\backupScripts.d  -  what are the allowable file types in this directory? will VMware just try to execute all files in this directory so exe, vbs, bat are all ok?

thanks,

jonathan

Dear all,

I am using ESXi 3.5 (Free version) and I am triailing Veeam Backup & Replication. The most I can get out of it is 5 - 6 Mb/s My VM is 570GB and the whole thing is taking 25 odd hours.

Is this a limitation to the free version or have I go something wrong??

My company is running VmWare Vsphere center server 5.0.0.  Just about everyday we get an alert that the backups failed.  I am new to Vmware and I am not sure why this is happening.  I have included one of the alerts below so that hopefully someone can help me figure this out.  Please excuse me if I leave something out as I have explained I am new to Vmware.  If anyone needs more info please let me know.

Backup has failed. Please check the log for additional information.

1    Information    1/13/2013 7:30:03 PM    Task 'Back up 'mokautil'' changed its state from 'idle' to 'running'.

2    Information    1/13/2013 7:30:03 PM    Task 'Back up 'mokautil'' was started.

3    Information    1/13/2013 7:30:13 PM    Backing up a group of VMs.

4    Information    1/13/2013 7:30:19 PM    Task 'Back up 'mokautil'' changed its state from 'running' to 'idle'.

5    Error    1/13/2013 7:30:19 PM    Task 'Back up 'mokautil'' failed: 'Failed to create a backup.

Additional info:

--------------------

Error code: 3

Module: 435

LineInfo: 555b5abba09500ab

Fields:  $module : C:\Program Files (x86)\Acronis\vmProtect\Windows Agent\vmms.exe

Message: Failed to create a backup.

--------------------

Error code: 32786

Module: 114

LineInfo: 28314c961de7d3b2

Fields:

Message: Failed to prepare for backing up.

--------------------

Error code: 32768

Module: 114

LineInfo: 28314c961de7d32c

Fields:

Message: Instances list is empty.

--------------------'.

Hi Team,

I've been searching the net for info. on CPU ready time on ESX host, I'm already aware for VM's the recommended is 5% CPU ready time anything higher than that the VM would is performing quite poorly.

But what I want to know is ESX host ready such that I can measure at host level the CPU's are over committed resulting in insufficient CPU resource allocation for the VM's but I haven't managed to find any specifics - can anyone shed some light on this or point me in the right direction

Hallo VMware Community,

we are running VSA Backup of CommVault SIMPANA. We are using a VSA Proxy. To the Proxy the VMFS-5 LUNs are mapped read-only so that we can use SAN as transport mode for the VMs which are located on that datastores.

We have testet many things but always still getting the error message "Failure Reason:Could not read data from the virtual disk" and the Job failed. At the beginning we started with one Subclient for all the VMs but now we switched to one Subclient per VM so that the jobs are running sequentially step by step but the error still occurs.

Error Code (at SIMPANA Console):

Description: Unable to read the disk [] for virtual machine [xxx] on Host [xxx]. [Beim Verarbeiten der Anfrage ist mindestens ein Fehler aufgetreten., Failed to ReadCurrVmdkFile (W32.774)]

Source: xxx, Process: vsbkp    

8340  1b88  01/25 00:33:11 89467 stat- ID [readdisk], Bytes [26381910425], Time [133.847090] Sec(s), Average Speed [187.973832] MB/Sec

8340  1b88  01/25 00:33:11 89467 CVMDiskInfo::DecrementMaxNDBHandlesAllowed() - Max allowed NBD Open handles for backup are now [0]

8340  1b88  01/25 00:33:11 89467 CVMDiskInfo::IncrementMaxNDBHandlesAllowed() - Max allowed NBD Open handles for backup are now [1]

8340  1b88  01/25 00:33:11 89467 VSBkpWorker::BackupVMDisk() - Using default extent size

8340  1b88  01/25 00:33:11 89467 VSBkpWorker::BackupVMDisk() - Disabling CRC Processing as change Id [52 47 9b 90 ff f5 be 24-37 6c f9 43 a2 89 58 e3/57] is supplied

8340  1b88  01/25 00:33:11 89467 VSBkpChangeIdFile::ReadChangeID() - Not using a Change ID

8340  6     01/25 00:33:11 89467 ### GetService --- Reopening connection

8340  6     01/25 00:33:12 89467 ### CVIWrapper::_GetDiskInfoArr --- Updating disk label from [Festplatte 1] to [Hard disk 1]

8340  6     01/25 00:33:13 89467 ### CVIWrapper::_GetDiskInfoArr --- Updating disk label from [Festplatte 2] to [Hard disk 2]

8340  1b88  01/25 00:33:13 89467 There are 6 entries in the allocated extent table for xxx.vmdk

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::BackupVMDisk() - Extent Size [262144] bytes [512] sectors [512] bytes per sector

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::BackupVMDisk() - Sending File Header Path:[\501de18e-3138-67f9-2514-daffc1b51880\scsi0-1-xxx_1.vmdk] with size:[450971566080]

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::AddVMMetadataFile() - Adding metadata file [D:\Program Files\CommVault\Simpana\iDataAgent\JobResults\CV_JobResults\iDataAgent\VirtualServerAgent\2\375\VolHdr(501de18e-3138-67f9-2514-daffc1b51880_scsi0-1-xxx_1.vmdk).imf] to list to be uploaded to index cache

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::BackupVMDisk() - Backing up disk/volume [xxx_1.vmdk]

8340  1b88  01/25 00:33:13 89467 VSBkpWorker::BackupVMDisk() - Using Fixed Length Extent Names

8340  234c  01/25 00:33:13 89467 VSBkpWorker::ArchiveExtentProcessor() - Send volume or disk data to MA thread

8340  2134  01/25 00:34:35 89467 VSBkpCoordinator::OnIdle_Running() - Waiting for [1] VMs to be processed.  [xxx]

8340  2134  01/25 00:34:35 89467 VSBkpCoordinator::DumpStreamInfo() - StreamId = 1, RCID = 189844, ReservationId = 137886, MediaAgent = s190a0010, Agent = s190a0010  []

8340  1b88  01/25 00:34:50 89467 CVMDiskInfo::ReadDisk() - VixDiskLib_Read failed Err=3e80 One of the parameters supplied is invalid

8340  1b88  01/25 00:34:50 89467 VSBkpWorker::BackupVMDisk() - Failed to read from virtual disk [xxx_1.vmdk],  [0x80070306:{..\..\..\CommClient\VirtualServer\VMInfo\ArchiveVirtualDiskFile.cpp[CArchiveVirtualDiskFile::GetNextBlock(535)]} + {..\..\..\CommClient\VirtualServer\VMInfo\VmdkVcb4ExtentReader.cpp[CVmdkVcb4ExtentReader::ReadBlock(664)]/W32.774.(Beim Verarbeiten der Anfrage ist mindestens ein Fehler aufgetreten.)-Failed to ReadCurrVmdkFile}]

We are running the latest version of VMware ESXi and also the latest version of the vSphere Server.

Maybe someone of you is also using VSA backup of SIMPANA and can help us to resolve this issue.

Thanks a lot

Best Regards

Philipp

Hi All,

We use port 81 for vCenter as an alternative HTTP port however when im trying to deploy the VDP appliance i get the following error

Unable to verify vCenter listening on specified HTTP Port.  Please re-check values and try again

Ive double checked and vcenter is listening on this port all other credentials are correct as ive deployed version 5.8 sucsessfully last week using the same credentials. Ive also checked the host file on the backup appliance and this shows the correct ip's anyone else getting the same?? Or have any idea what i can double check next?

Thanks

Alex

I was using VDP 5.5. It can show the sequence of VM backup

1. Create Snapshot

2. Reconfigure virtual machine (on VDP to add the VM disk)

3. Show message "Backing up Disk: 1/1 (F)" or "Backing up Disk: 1/2 (I)", with progress bar

4. Reconfigure virtual machine (on VDP to remove the VM disk)

5. Remove Snapshot

But in VDP 6.0, I found that there is no "Backing up Disk" message, and I do not know what VM is VDP backing up. Is it by design, or can it display more message to let me know the progress?