Hi.

Due to a backup issue, (hot-add jobs fail over to network mode), Veeam support suggest me to try to add a snapshot disk manually.

I did the next steps:

- Take one snapshot.

- Edit settings of another VM.

- Add existing disk (Independent/Non persistent). (Selecting the vmdk generated by the snapshot)

Always the same error:

2014-02-06T10:37:21.922Z| vmx| I120: AIOMGR: AIOMgr_OpenWithRetry: Descriptor file '/vmfs/volumes/c3b7ee43-70d6b515/vpsrv05 - timbratges nou/vpsrv05 - timbratges nou-000001-delta.vmdk' locked (try 4)

2014-02-06T10:37:32.230Z| vmx| I120: AIOGNRC: Failed to open '/vmfs/volumes/c3b7ee43-70d6b515/vpsrv05 - timbratges nou/vpsrv05 - timbratges nou-000001-delta.vmdk' : Failed to lock the file (40003) (0x2013).

2014-02-06T10:37:32.230Z| vmx| I120: OBJLIB-FILEBE : FileBEOpen: can't open '/vmfs/volumes/c3b7ee43-70d6b515/vpsrv05 - timbratges nou/vpsrv05 - timbratges nou-000001-delta.vmdk' : Failed to lock the file (262146).

2014-02-06T10:37:32.230Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/c3b7ee43-70d6b515/vpsrv05 - timbratges nou/vpsrv05 - timbratges nou-000001-delta.vmdk" : failed to open (Failed to lock the file): ObjLib_Open failed. Type 8

2014-02-06T10:37:32.230Z| vmx| I120: DISKLIB-LINK  : "/vmfs/volumes/c3b7ee43-70d6b515/vpsrv05 - timbratges nou/vpsrv05 - timbratges nou-000001.vmdk" : failed to open (Failed to lock the file).

My VM's are located on a NFS 3 datastore.

Anyone have any idea about how to solve it ?

Thanks

Hello all,

Hi everyone,

I want to use VDP 5.1 until 2TB, but when I tried to download it I got the following error message:

You either are not entitled or do not have permissions to download this product

Check with your My VMware Super User, Procurement Contact or Administrator.

Someone know how can I get it?

Thank you in advanced

Vannessa

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

Hi,

I'm using VDP to backup a Vcenter Linux Appliance amongst other VM, on a Vsphere 5.5 infrastructure.

Everything was just fine until the day the email notification indicated that de backup of my vmware appliance failed on every single backup (all the other vms are ok).

When I look further I realise that the backup is actually ok. I extracted the logs of failed clients from VDP web interface.

In the log there is only 1 warning.

Here is my log (warning in red...).

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

2014-04-14T19:00:15.456+4:00 avtar Info <5174>: - Reading /root/.avamar

2014-04-14T19:00:15.456+4:00 avtar Info <5174>: - Reading /usr/local/avamar/etc/usersettings.cfg

2014-04-14T19:00:15.456+4:00 avtar Info <5905>: Incremental flags: --flagfile=/usr/local/avamar/etc/usersettings.cfg --password=**************** --vardir=/usr/local/avamar/var --server=arsoidataprotect --id=root --bindir=/usr/local/avamar/bin --sequencenumber=105

2014-04-14T19:00:15.456+4:00 avtar Info <5946>: File system character encoding is UTF-8.

2014-04-14T19:00:15.456+4:00 avtar Info <5588>: - Creating process lock file "/usr/local/avamarclient/var-proxy-7/avtar.lck", pid=24942

2014-04-14T19:00:15.456+4:00 avtar Info <8940>: Starting back up at 2014-04-14 19:00:15 GST as "root" on "arsoidataprotect" (4 CPUs) [7.0.181-86]

2014-04-14T19:00:15.456+4:00 avtar Info <5731>: Not using include/exclude list

2014-04-14T19:00:15.456+4:00 avtar Info <8474>: - Log file path: Sauvegarde Vcenter Appliance-Sauvegarde Vcenter Appliance-1397487600017-31c6896d4f35d974baf96d89c25572c2985faa76-1016-vmimagel_avtar.log

2014-04-14T19:00:15.456+4:00 avtar Info <6555>: Initializing connection (Avamar Deduplication Engine v2.0.0)

2014-04-14T19:00:15.937+4:00 avtar Info <5552>: Connecting to Avamar Server (arsoidataprotect.sd.intranet.sante.gouv.fr)

2014-04-14T19:00:15.937+4:00 avtar Info <5554>: Connecting to one node in each datacenter

2014-04-14T19:00:15.940+4:00 avtar Info <5993>: - Connect: Connected to 10.153.6.54:29000, Priv=0, SSL Cipher=AES256-SHA

2014-04-14T19:00:15.944+4:00 avtar Info <5993>: - Datacenter 0 has 1 nodes: Connected to 10.153.6.54:29000, Priv=0, SSL Cipher=AES256-SHA

2014-04-14T19:00:15.947+4:00 avtar Info <5581>: Logging in on connection 0 with Session Ticket

2014-04-14T19:00:15.947+4:00 avtar Info <5582>: Avamar Server login successful

2014-04-14T19:00:15.947+4:00 avtar Info <5018>: - Session ID: 0

2014-04-14T19:00:15.949+4:00 avtar Info <10632>: Using Client-ID='31c6896d4f35d974baf96d89c25572c2985faa76'

2014-04-14T19:00:15.949+4:00 avtar Info <5550>: Successfully logged into Avamar Server [7.0.81-86] (Compression enabled)

2014-04-14T19:00:15.949+4:00 avtar Info <7562>: Back up of stdin on server "arsoidataprotect.sd.intranet.sante.gouv.fr" for /10.153.6.220/VirtualMachines/VMware_vCenter_Server_Appliance_UqELzCQ5Xb261oD3tCf27Q

2014-04-14T19:00:15.968+4:00 avtar Info <5586>: Loading cache files from /usr/local/avamarclient/var-proxy-7

2014-04-14T19:00:15.968+4:00 avtar Info <5769>: Filecache is disabled.

2014-04-14T19:00:15.968+4:00 avtar Info <8650>: Opening cache file /usr/local/avamarclient/var-proxy-7/p_cache.dat

2014-04-14T19:00:16.299+4:00 avtar Info <5573>: - Loaded cache file (100,663,840 bytes)

2014-04-14T19:00:16.664+4:00 avtar Info <6426>: Done loading cache files

2014-04-14T19:00:16.664+4:00 avtar Warning <18692>: Changed streamformat-out to none since raw format is only for DDR use

2014-04-14T19:00:16.664+4:00 avtar Info <6995>: Parsing 'pax' stream format from stdin

2014-04-14T19:00:16.667+4:00 avtar Info <8478>: Using backup #105 timestamp 2014-04-01 19:07:08 GST label "Sauvegarde vCenter Appliance-Sauvegarde vCenter " as base for incremental backup

2014-04-14T19:00:16.667+4:00 avtar Info <10818>: Backstream creating root backstreamdir object

2014-04-14T19:00:16.668+4:00 avtar Info <8648>: Directory elements will be sorted: No

2014-04-14T19:00:16.668+4:00 avtar Info <8649>: Sub-file change blocks enabled: Yes

2014-04-14T19:15:16.115+4:00 avtar Info <8688>: Status 2014-04-14 19:15:16, 22.87 GB (187.3 MB, 0.80% new) 388MB  19% CPU  24564711424 input bytes, (1 open files) VMFiles/1/virtdisk-flat.vmdk

2014-04-14T19:30:17.406+4:00 avtar Info <8688>: Status 2014-04-14 19:30:17, 48.90 GB (210.9 MB, 0.42% new) 392MB  16% CPU  52504117248 input bytes, (1 open files) VMFiles/2/virtdisk-flat.vmdk

2014-04-14T19:45:17.571+4:00 avtar Info <8688>: Status 2014-04-14 19:45:17, 97.26 GB (396.9 MB, 0.40% new) 392MB  30% CPU  104435810304 input bytes, (1 open files) VMFiles/2/virtdisk-flat.vmdk

2014-04-14T19:58:27.855+4:00 avtar Info <5163>: Backup complete, wrapping-up session with Server

2014-04-14T19:58:28.020+4:00 avtar Info <7238>: Stream complete: 134,217,800,704 bytes read from stream

2014-04-14T19:58:28.021+4:00 avtar Info <5156>: Backup #118 timestamp 2014-04-14 19:58:27, 0 files, 125.0 GB (0 files, 475.6 MB, 0.37% new)

2014-04-14T19:58:28.021+4:00 avtar Info <7539>: Label "Sauvegarde Vcenter Appliance-Sauvegarde Vcenter Appliance-1397487600017", scheduled to expire after 05/14/14 (2014-05-14 15:00:00 UTC), daily,weekly,monthly,yearly backup, backup type: synthetic_full

2014-04-14T19:58:28.021+4:00 avtar Info <6083>: Backed-up 125.0 GB in 58.21 minutes: 129 GB/hour (0 files/hour)

2014-04-14T19:58:28.026+4:00 avtar Info <5587>: Updating cache files in /usr/local/avamarclient/var-proxy-7

2014-04-14T19:58:28.032+4:00 avtar Info <5069>: - Writing cache file "/usr/local/avamarclient/var-proxy-7/p_cache.dat"

2014-04-14T19:58:28.382+4:00 avtar Info <5546>: Cache update complete /usr/local/avamarclient/var-proxy-7/p_cache.dat (96.0MB of 365MB max)

2014-04-14T19:58:28.391+4:00 avtar Info <7883>: Finished at 2014-04-14 19:58:28 GST, Elapsed time: 0000h:58m:12s

2014-04-14T19:58:28.399+4:00 avtar Info <8468>: Sending wrapup message to parent

2014-04-14T19:58:28.400+4:00 avtar Info <5314>: Command completed (1 warning, exit code 0: success)

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

Any ideas ?

Thanks.

Philippe

Hi,

I want to deploy a VDP Appliance and connect it to a remote vCenter, that is, not the one on which the appliance is deployed. Say I have deployed the ova template in vCenter1, but during the configuration I want to connect it to vCenter2. The reason behind this is, that the whole environment managed by vCenter2 is very small and I don't want to deploy a 1TB+ appliance there. Both vCenters run in the same DC, so there are no communication or latency issues, also - the VM that vCenter2 is running on is registered with the vCenter1.

During the configuration i get the "VDP not found in vCenter inventory" error (not using english browser version so this might be slightly different). From what I understand, during configuration the appliance wants to discover itself within the vCenter1 inventory, altohugh I have provided it with connection info for the vCenter2. An error is reported in the vami-ovf.log:

2014-04-24 05:03:28,486 INFO  [http-nio-8543-exec-10]-services.VcenterConnectionTestService: Testing VDP connection to vCenter at: [vCenter2] port: [443] and SSO at

: [vCenter2] port: [7444]

2014-04-24 05:03:28,658 INFO  [http-nio-8543-exec-10]-reconfig.VcenterConfigurationImpl: Validating permissions for vCenter user: [domain\userWithAdminRightsOnVCenter]

2014-04-24 05:03:28,659 INFO  [http-nio-8543-exec-10]-vi.VIAccess: Attempting to obtain AVE VM with IP Address: [10.x.x.x]

2014-04-24 05:03:28,666 INFO  [http-nio-8543-exec-10]-vi.VIAccess: Local Client not found

2014-04-24 05:03:28,667 ERROR [http-nio-8543-exec-10]-reconfig.VcenterConfigurationImpl: Failed to obtain either Authorization Manager from service instance or VDP VirtualMach

ine.

2014-04-24 05:03:28,667 INFO  [http-nio-8543-exec-10]-vi.VIAccess: Attempting to obtain AVE VM with IP Address: [10.x.x.x]

2014-04-24 05:03:28,674 INFO  [http-nio-8543-exec-10]-vi.VIAccess: Local Client not found

2014-04-24 05:03:28,689 INFO  [http-nio-8543-exec-10]-service.AdapterUtils: MCS Web Services URL: https://localhost:9443/services/mcService  MCUserId="MCUser"  MCUserPswd="***

**************************"

2014-04-24 05:03:28,704 INFO  [http-nio-8543-exec-10]-httpclient.HttpMethodDirector: I/O exception (java.net.ConnectException) caught when processing request: Connection refus

ed

2014-04-24 05:03:28,704 INFO  [http-nio-8543-exec-10]-httpclient.HttpMethodDirector: Retrying request

2014-04-24 05:03:28,706 INFO  [http-nio-8543-exec-10]-httpclient.HttpMethodDirector: I/O exception (java.net.ConnectException) caught when processing request: Connection refus

ed

2014-04-24 05:03:28,706 INFO  [http-nio-8543-exec-10]-httpclient.HttpMethodDirector: Retrying request

2014-04-24 05:03:28,708 INFO  [http-nio-8543-exec-10]-httpclient.HttpMethodDirector: I/O exception (java.net.ConnectException) caught when processing request: Connection refus

ed

2014-04-24 05:03:28,708 INFO  [http-nio-8543-exec-10]-httpclient.HttpMethodDirector: Retrying request

2014-04-24 05:03:28,710 INFO  [http-nio-8543-exec-10]-http.HTTPSender: Unable to sendViaPost to url[https://localhost:9443/services/mcsdk10]

java.net.ConnectException: Connection refused

DNS lookup zones are configured, as are the firewall ports.

Is it at all possible to connect VDP to a remote vCenter?

1) Are there any limitations on the maximum FC and Ethernet through-put supported by VDP advanced version ?

2) Maximum data size capability of 8TB by VDPA is combined of all the 10 VDP appliances (maximum supported per vCenter), or for a single appliance ?

3) If 8TB limit is for a single VDP appliance, then is it possible to manage 80 TB (using 10 VDP appliances) per vCenter server.

Thanks,

Sanjeev

I'm trying to understand if a snapshots of a windows 2008 R2 VM that's running inside an ESXi 5.1 with  just a scsi disk is application consistent or not.

Reading here it seems yes, it's app consistent but there's a couple of things that I do not understand.

What does it mean: Restore must be done using the backup application’s guest agent. https://communities.vmware.com/The vSphere APIs for Data Protection provide no host agent support for this.

If I restore the entire VM, is this consistent or not?

Hi,

i have freed space removing older backup but vdp not releasing space.

my error log:

root@vdp-00:~/#: mccli event show --unack=true

0,23000,CLI command completed successfully.

ID      Date                     Type    Code  Category Severity Domain Summary

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

1667003 2014-07-28 14:29:48 CEST WARNING 22415 SYSTEM   PROCESS  /      The server is approaching full capacity.

1666923 2014-07-28 14:24:49 CEST WARNING 22630 SYSTEM   PROCESS  /      Server has reached capacity.

1659796 2014-07-28 06:15:37 CEST ERROR   22408 SYSTEM   PROCESS  /      A checkpoint of server data is overdue.

1657176 2014-07-28 03:16:42 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1657174 2014-07-28 03:14:32 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1657077 2014-07-28 03:10:29 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1656836 2014-07-28 02:51:29 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1656152 2014-07-28 02:00:13 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1655727 2014-07-28 01:26:30 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1655507 2014-07-28 00:58:34 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1654226 2014-07-27 23:21:01 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1654224 2014-07-27 23:20:52 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1647646 2014-07-27 14:29:03 CEST WARNING 22415 SYSTEM   PROCESS  /      The server is approaching full capacity.

1647573 2014-07-27 14:24:49 CEST WARNING 22630 SYSTEM   PROCESS  /      Server has reached capacity.

1635686 2014-07-27 00:47:14 CEST ERROR   22409 SYSTEM   PROCESS  /      A checkpoint validation (hfscheck) of server checkpoint data is overdue.

1633648 2014-07-26 22:27:31 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633647 2014-07-26 22:25:20 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633558 2014-07-26 22:21:28 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633521 2014-07-26 22:19:18 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633342 2014-07-26 22:06:50 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1633341 2014-07-26 22:06:42 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1632918 2014-07-26 21:38:17 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1632774 2014-07-26 21:28:33 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1632749 2014-07-26 21:26:23 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1632457 2014-07-26 21:07:18 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1629914 2014-07-26 18:15:04 CEST ERROR   22408 SYSTEM   PROCESS  /      A checkpoint of server data is overdue.

1626551 2014-07-26 14:28:52 CEST WARNING 22415 SYSTEM   PROCESS  /      The server is approaching full capacity.

1626540 2014-07-26 14:25:24 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1626491 2014-07-26 14:24:49 CEST WARNING 22630 SYSTEM   PROCESS  /      Server has reached capacity.

1626183 2014-07-26 14:03:20 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1619232 2014-07-26 06:09:24 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1614592 2014-07-26 00:52:01 CEST ERROR   1     SYSTEM   PROCESS  /      syncthread::commit timed-out waiting for map.commit()

1605944 2014-07-25 14:28:14 CEST WARNING 22415 SYSTEM   PROCESS  /      The server is approaching full capacity.

1605913 2014-07-25 14:24:49 CEST WARNING 22630 SYSTEM   PROCESS  /      Server has reached capacity.

Can you help please?

Thank You

Failed to lock the file

Cannot open the disk 'E:\Win_7_21.00.03\Windows 7Home.vmdk' or one of the snapshot disks it depends on.

Module DiskEarly power on failed.

Failed to start the virtual machine.

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

Can I recover my files . I need to back the current files in that VM up.

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!

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,

Hi,

I have a couple virtual machines on a NFS datastore running on a NetApp Filer. Everything works well normally. The storage is not overloaded.

On my regular virtual machines, never backed up using VMware Data Recovery, a snapshot removal takes only a couple seconds and the machine stays unresponsive for a very small/insignificant time.

But after I do a backup with VMware Data Recovery, the snapshot removal process starts to take 30 seconds or more. And this is for all snapshot removals on the VM. The Virtual Machine becames unresponsive for that time, losing all kind of network connectivity and even the Vi-Client console stalls.

If I move the virtual machine to local storage, the snapshot removal is again fast. Moving it back to the NFS datastore makes it slow again.

I tracked the problem down to the Change Block Tracking (CTK) feature.

VMware Data Recovery adds a ctkEnabled = true, scsi0:X:ctkEnabled = true  to the Virtual Machine advanced configuration when it perform a backup of it.

As soon as I set these entries to false, the Virtual Machine snapshot removal works as it should. It just takes some seconds to consolidate the snapshot.

If I backup the virtual machine again with VDR, the erratic behavior shows up again, because VDR resets the values to "true" again.

I can reproduce the problem using the following steps:

1. Create or clone a virtual machine, using an NFS datastore as the vmdk target (in my case, on a NetApp FAS2020).

2. Boot the machine (don't need an OS for the problem to show up) 3. Take a snapshot. Wait and remove a snapshot. It should take some seconds 4. Backup the machine using VDR 5. Take a snapshot and remove it (same as step 3).  The problem shows up!!

Result of the procedure:

- Snapshot removal takes 30 seconds or more on step 5. Considerably more time than step 3 (before VDR backup).

- If you have an OS on the machine, ping the machine during snapshot removal on step 5. The machine is unresponsive during the snapshot removal operation.

Is anyone having the same problem?

Any idea what can be causing this?

Thanks.

I have been trying to export an OVF template using the vSphere Client Version 4.1.0 Build 258902 of a VM from an ESXi server running 4.1.0 Build 260247 using a licensed version of vSphere 4 Standard.  On some of my VMs, I can export them fine.  However, I have a couple that timeout.  For the ones that fail, I get the popup progress dialog that provides esitmates of time, etc., and it proceeds for a time and them just times out.  It gets about 35% done before I get the error "Failed to export Virtual Machine:  The operation timed out".  The time of duration of my last try was about 16.5 minutes.

The image I am having problems with as provisioned storage of 204 GB, and used storage of 10.63 GB.  Guest OS is Ubuntu 10.04.2 64 bit, but I doubt that is the issue.  VM version is 7.  CPU 3 and memory is 4 GB.  I stopped the VM before exporting it, and it does not have any snapshots yet taken of it.

I have noticed a couple other threads asking for help on this topic with no answers, so I have started another thread to hopefully get somebody's notice.  There seem to be a few others out there with this issue.

I would download the files directly via browsing the datastore, but that seems to take a crazy amount of time to do ... literally hours and hours.

Here is a section of the system logs:

<version>657</version>
[        :QuickInf:P:16] 2011-04-15 13:18:52.610  Current Memory Usage (gc/virtual/physical/paged): 21.271016/566.923264/189.149184/161.140736
[viclient:SoapTran:W:21] 2011-04-15 13:18:57.363  Invoke 1339 Finish WaitForUpdates on PropertyCollector:session[5212368b-16bc-8738-4b84-7fb725fe7fef]52855471-0a5a-fa3f-e500-ba80952e0ade [192.168.30.6] - Serial:0.000, Server:899.974
Suppressed: VirtualInfrastructure.Soap.MethodInvocationSoapImpl: The request failed because the remote server '192.168.30.6' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
[viclient:Error   :W:21] 2011-04-15 13:18:57.363  ConnectionError occurred while executing WFU
VirtualInfrastructure.Exceptions.RequestTimedOut: The request failed because the remote server '192.168.30.6' took too long to respond. (The command has timed out as the remote server is taking too long to respond.)
   at VirtualInfrastructure.Soap.SoapServiceWrapper.DoInvokeSync(ManagedObject mo, MethodName methodName, Object[] parameters, Int32 timeoutSecs)
   at VirtualInfrastructure.Soap.SoapTransport.VirtualInfrastructure.Transport.InvokeMethod(ManagedObject mo, MethodName methodName, Object[] pars)
   at VirtualInfrastructure.ManagedObject.InvokeMethod(MethodName methodName, Object[] pars)
   at Vmomi.Core.PropertyCollector.WaitForUpdates(String version)
   at VirtualInfrastructure.Updates.PollerDispatcherImpl.ExecuteSingleWFU()
   at VirtualInfrastructure.Updates.PollerDispatcherImpl.PollWaitForUpdates()
System.Net.WebException: The command has timed out as the remote server is taking too long to respond.

   --- End of inner exception stack trace ---

I have a vmdk file tfrom an SMVI backup that i am trying to mount on a different server adn wehn i try to add it and point top that datastore location no files show up so i can't restore my files.  The file is quite larre so i can't move it around too much but tried different locatoins with the same results. The file is called...server_1-flat.vmdk.  Is there any reason this file cannot be mounted.  Any help is appreciated.  thanks

Hallo,

first i must say, that we don't need a backup of the Exchange 2010 enviroment, this will be taken with NetApp SnapManager for Exchange.

But the OS VMDK files are on a NFS Datastore and this should be backed up by SnapManager VI.

But if i try to create a quiesced Snapshot of the VM i got this errors:

Das Gastbetriebssystem hat während der Stilllegung einen Fehler gemeldet. Der Fehlercode lautet: 5 Die Fehlermeldung lautet: 'VssSyncStart' operation failed: IDispatch error #8454 (0x80042306)

Das Gastbetriebssystem hat während der Stilllegung einen Fehler gemeldet. Der Fehlercode lautet: 3 Die Fehlermeldung lautet: Quiesce operation aborted

Das Gastbetriebssystem hat während der Stilllegung einen Fehler gemeldet. Der Fehlercode lautet: 3 Die Fehlermeldung lautet: Error when notifying the sync provider.

After i tryed to make a SnapShot i got this result in „vssadmin list writers“

Writer name: 'Microsoft Exchange Replica Writer'

   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

   Writer Instance Id: {a07f7d02-edb2-45a4-aa62-b1360f6067cd}

   State: [8] Failed

   Last error: Retryable error

Writer name: 'Microsoft Exchange Writer'

   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

   Writer Instance Id: {4e8c2d55-eaa5-4d63-b680-2763f4a95366}

   State: [8] Failed

   Last error: Retryable error

And some other writers are reorting a timeout.

We tryed already to exclude the Exchange VSS Writers from the VMware Tools like described in the KB article: http://kb.vmware.com/kb/1007696

But this didn’t work perhaps because we have ESXi 5.0 and the article is only up to ESXi 4.1.

Is there a way to get a quiesced VMware Snapshot only from the operating system?

Best regards

Stefan

We are using VADP to protect a Windows 2008 server (active directory and file).  It appears that after enabling this backup with CBT, the D drive on this server is set to read only and I can't figure out why.  The symptoms appear to be exactly what are described in this post:  http://communities.vmware.com/thread/313272

However, the fixes described there (set disk.EnableUUID to false) didn't work for me.  The drive is still read only after a reboot.  I verified that diskpart says it is not readonly.

Just to confirm, the errors I saw after the backup started were this:

Source:        VDS Dynamic Provider
Event ID:      10
The provider failed while storing notifications from the driver. The Virtual Disk Service should be restarted. hr=80042505

Source:        volmgr
Event ID:      57
The system failed to flush data to the transaction log. Corruption may occur.

Then we get these of course:

Source:        Ntfs
Event ID:      141
Description:
{Delayed Write Failed} Windows was unable to save all the data for the file D:\pics\Thumbs.db; the data has been lost.  This error may be caused if the device has been removed or the media is write-protected.

I am stuck.  Any ideas?

EDIT:

vSphere 4.1

Latest tools

Guest is Windows 2008 (not R2)

I was trying to make backup to a the vcenter vm with Veeam B&R 6.5 last patch, and i got the followed error: timed out waiting for all VDDK disks to close, so i tried to fix the error restarting managment agents on the host, consolidating the disk on the vm but nothing help.

So, i tried to clone the vm to make sure no vmdk are damage or are not working properly but when i try to do it, i get the error: error caused by file vm/vm-000002.vmdk, i can´t find that file browsing the datastore.

What should I do?? We are working with vSphere 5.0

Hello Everyone,

     So, I'm working with VDP and trying to backup 7 vms. I don't have this issue at any other client of ours. I have a client that the VDP runs at the default time set and fails to backup all the servers. I have yet to have it backup every server without any issues.

The error in vSphere Web Client tells me the following:

VDP: Backup job (*****) failed to backup client ******. Execution error: E10052:Failed to create snapshot.. Job ID: ******************** (Full Client path: )

After browsing around I was able to finally find the avamarclient logs and received a bit more information on the root issue here:

After the VDP Job fails. I notice that the snap is actually there, as I check the Snapshot Manager and see the "VDP-Job###" listed.

So, when I rerun the job manually it goes ahead and removes the VDP-Snapshot. Then begins to re-snap the VM. I know these VMs lock up for less than a minute when VDP runs. I feel as if when Virtual Center is being snapped it freezes the I/O on that VM and makes VDP lose it's connection to vCenter Server and then fails the VDP backup. So, we thought to get another set of 1TB Drives and put them in a RAID-1 Configuration and create another datastore to strictly be dedicated for VDP backups.

Even after this implementation we still are seeing the issue.

Does anyone have any suggestions as to what to try to get VDP working properly. Also, I have redeployed mutliple times to ensure it wasn't corruption in VDP itself.

Thank you to anyone who assists !