Hello

At the moment we face the problem that we can't backup our vCenter Server VM with our VDR.

We just get the error:

Failed to create snapshot for <vm>, error -3960 ( cannot quiesce virtual machine )

If I manually start a snapshot with the option to quiesce the VM the snapshot works fine.

I already reinstalled the tools (including reboot) but this hasn't helped.

At the moment we have no idea what else could be the reason for that.

And how you guys backup your vCenter? Also with VDR, VCB, third party like Symantec, ... ?

I really would appreciate  to get some tips & recommendations.

Regards

Patrick

Hello,

I installed vDP in lab environment to test the product.  Everything was working well for few days.  Since Saturday, I am facing with this error

“the most common cause for this error is that the time on the vdp appliance and your sso server are not in sync”

I checked esxi5.1 host (inside vcenter) to make sure the time are in sync with web client.    I am using NTP (pool.ntp.org) under configuration on esxi 5.1 and NTP client is enabled and running. 

How can, I resolve this error.  vDP appliance disconnect and when, I try to reconnect faced with above error.  Appreciate your help

Ram

Hello,

I have tried to deploy VDP of several versions with the same result in order to evaluate the product but can't get it to backup a single host regardless of powered on or shut down. The deployment were done following the VDP administration guide to the point.

During the process I started out with VDP 5.1 then upgraded both vcenter server and VDP to 5.5 and 5.5.6 respectively with almost the same issue. I have set new vdp users with administrative permissions, redeployed vdp, tested several different vm hosts in all possible states with or without snapshots present but same result. Backup starts but fail in under a minute due to what looks like no permission to read the .vmx file, I can however download and view the file using infrastructure client as long as the vm host is shut down.

I have also tried all suggested solutions that I could find on the kb, no special chars in the datacenter etc.

I am starting to get a bit frustrated and the feeling is that this product is flawed. Any ideas would be greatly appreciated.

The most recent attempts in VDP 5.5.6 give the following log output:

====================================================================================================================================================

Client Name ::CentOS QNAP Management Server  |  Workorder ID :: null  |  Completed Time ::Tue, 8 Apr 2014 23:42:57 CEST

=====================================================================================================================================================

<browse env-locale-cs="ANSI_X3.4-1968" ack="no" msgver="1" targetCid="514330c10e51fd762447275e43f5f51df0a8780b" maxelems="1" filesize="21332" cid="b99ef535b8c7d127017ffa9288ebd64a2d613302" showdebug="false"><file inode="423343" date="2014-04-08 19:32:41" internal="0" group="root" protection="lrwxrwxrwx" name="var-proxy-7" size="31" links="1" viewable="1" user="root">

*********** /usr/local/avamarclient/var-proxy-7/InitialTestBackup-1396993349036-514330c10e51fd762447275e43f5f51df0a8780b-1016-vmimagel.log ***********

<logheader platform="Linux" env-locale-cs="ANSI_X3.4-1968" process_id="avvcbimage" version="7.0.182-99" tz="CEST" />

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

-----  START avvcbimage log 2014-04-08 23:42:31 CEST  [7.0.182-99 Linux-x86_64]

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

2014-04-08T23:42:31.936+2:00 avvcbimage Info <5008>: Logging to /usr/local/avamarclient/var-proxy-7/InitialTestBackup-1396993349036-514330c10e51fd762447275e43f5f51df0a8780b-1016-vmimagel.log

2014-04-08T23:42:31.936+2:00 avvcbimage Info <5174>: - Reading /root/.avamar

2014-04-08T23:42:31.936+2:00 avvcbimage Info <5174>: - Reading /usr/local/avamar/etc/usersettings.cfg

2014-04-08T23:42:31.936+2:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var-proxy-7/avvcbimage.cmd

2014-04-08T23:42:31.936+2:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd

2014-04-08T23:42:31.938+2:00 avvcbimage Info <6673>: CTL listening on port 51445

2014-04-08T23:42:31.939+2:00 avvcbimage Info <10684>: Setting ctl message version to 3 (from 1)

2014-04-08T23:42:31.939+2:00 avvcbimage Info <16136>: Setting ctl max message size to 268435456

2014-04-08T23:42:31.942+2:00 avvcbimage Warning <6788>: Found unknown section 'browse-from-catalog' in workorder, ignoring

2014-04-08T23:42:31.943+2:00 avvcbimage Warning <17809>: VAMI Statistics Push Provider DISABLED.

2014-04-08T23:42:31.961+2:00 avvcbimage Info <18664>: Login(https://vcenter.lab.local:443/sdk) Datacenter: 'Datacenter01'

2014-04-08T23:42:31.961+2:00 avvcbimage Info <0000>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 5.5.0 build-1623101',  apiVersion:'5.5'

2014-04-08T23:42:32.024+2:00 avvcbimage Info <14692>: Login test is OK.

2014-04-08T23:42:32.079+2:00 avvcbimage Info <0000>: VM Info: VMX version 4(F), ctk enabled(T), fault tolerant (F), Guest OS CentOS 4/5/6 (64-bit), Cloud UUID = NoUUID. version=8

2014-04-08T23:42:32.129+2:00 avvcbimage Info <14625>: WorkOrder Disk Info:

  Disk '2000': file(base):'[QNAP02-Datastore201] CentOS QNAP Management Server/CentOS QNAP Management Server.vmdk', backItUp=1

               snapshot file:'[QNAP02-Datastore201] CentOS QNAP Management Server/CentOS QNAP Management Server.vmdk'

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

               prior change block ID:''

               Datastore:'QNAP02-Datastore201' Directly Accessible=1

2014-04-08T23:42:32.130+2:00 avvcbimage Info <11979>: proxy VM DNS name is: 127.0.0.2,vdp-hq-esx01.lab.local,vdp-hq-esx01,192.168.0.12

2014-04-08T23:42:32.130+2:00 avvcbimage Info <18672>: proxy VM Instance name is: vdp-hq-esx01.lab.local-proxy-7

2014-04-08T23:42:32.130+2:00 avvcbimage Info <17793>: proxy VM Moref is: vm-1401

2014-04-08T23:42:32.130+2:00 avvcbimage Info <16010>: vCenter 'Datacenter01' is vcenter.lab.local

2014-04-08T23:42:32.130+2:00 avvcbimage Info <11981>: VM's host is hq-esx02.lab.local

2014-04-08T23:42:32.130+2:00 avvcbimage Info <11982>: VM's primary storage location is [QNAP02-Datastore201] CentOS QNAP Management Server/CentOS QNAP Management Server.vmx

2014-04-08T23:42:32.130+2:00 avvcbimage Info <11983>: VM's vCenter ID is vm-1277

2014-04-08T23:42:33.320+2:00 avvcbimage Info <0000>: Proxy Host Name=hq-esx01.lab.local(5.1 build-1157734) VM Host Name=hq-esx02.lab.local(5.1 build-1157734)

2014-04-08T23:42:33.320+2:00 avvcbimage Info <11984>: VM's backup account on vdp-hq-esx01.lab.local is /vcenter.lab.local/VirtualMachines/CentOS_QNAP_Management_Server_Ui0niBEuhZa7fTHZF4vjOg

2014-04-08T23:42:33.320+2:00 avvcbimage Info <11986>: Changed block tracking is engaged for this VM

2014-04-08T23:42:33.320+2:00 avvcbimage Info <11988>: A reference to a valid prior backup is not available so this will be a full level zero backup.

2014-04-08T23:42:33.404+2:00 avvcbimage Info <17779>:  task task-5528 migration status:0

2014-04-08T23:42:33.446+2:00 avvcbimage Warning <6788>: Found unknown section 'browse-from-catalog' in workorder, ignoring

2014-04-08T23:42:33.448+2:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var-proxy-7/avvcbimage.cmd

2014-04-08T23:42:33.448+2:00 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd

2014-04-08T23:42:33.448+2:00 avvcbimage Info <7084>: target[0]=[QNAP02-Datastore201] CentOS QNAP Management Server/CentOS QNAP Management Server.vmdk

2014-04-08T23:42:33.461+2:00 avvcbimage Info <18664>: Login(https://vcenter.lab.local:443/sdk) Datacenter: 'Datacenter01'

2014-04-08T23:42:33.462+2:00 avvcbimage Info <0000>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 5.5.0 build-1623101',  apiVersion:'5.5'

2014-04-08T23:42:33.486+2:00 avvcbimage Info <14692>: Login test is OK.

2014-04-08T23:42:33.508+2:00 avvcbimage Info <16041>: VDDK:OBJLIB-LIB: Objlib initialized.

2014-04-08T23:42:33.508+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Attempting to locate advanced transport module in "/usr/lib/vmware-vix-disklib".

2014-04-08T23:42:34.430+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Advanced transport plugin was successfully loaded into vixDiskLib.

2014-04-08T23:42:34.430+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Enabling advanced transport modes.

2014-04-08T23:42:34.430+2:00 avvcbimage Info <16041>: VDDK:OBJLIB-LIB: Objlib initialized.

2014-04-08T23:42:34.431+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Initialize transport modes.

2014-04-08T23:42:34.431+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Available transport modes: file:san:hotadd:nbdssl:nbd.

2014-04-08T23:42:34.431+2:00 avvcbimage Info <16041>: VDDK:VMware VixDiskLib (5.5) Release build-1556136

2014-04-08T23:42:34.451+2:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_Init: Initialization is completed.

2014-04-08T23:42:34.451+2:00 avvcbimage Info <9666>: Available transport modes are file:san:hotadd:nbdssl:nbd

2014-04-08T23:42:34.451+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_PrepareForAccess: Prepare to access disk.

2014-04-08T23:42:34.451+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2014-04-08T23:42:34.451+2:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_AllowVMotion: Disable VMotion.

2014-04-08T23:42:35.106+2:00 avvcbimage Info <17818>: VixDiskLib vMotion reservation successfully enabled by 'vSphere Data Protection'

2014-04-08T23:42:35.106+2:00 avvcbimage Info <16011>: Running cleanup of old backups.

2014-04-08T23:42:35.106+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Cleanup: Remove previous mount points and clean up .

2014-04-08T23:42:35.106+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2014-04-08T23:42:35.106+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Disconnect: Disconnect.

2014-04-08T23:42:35.106+2:00 avvcbimage Info <16048>: VixDiskLib_Cleanup() found no prior mounts to cleanup.

2014-04-08T23:42:35.131+2:00 avvcbimage Info <18664>: Login(https://vcenter.lab.local:443/sdk) Datacenter: 'Datacenter01'

2014-04-08T23:42:35.131+2:00 avvcbimage Info <0000>:      - connected to 'VirtualCenter' - version: 'VMware vCenter Server 5.5.0 build-1623101',  apiVersion:'5.5'

2014-04-08T23:42:35.154+2:00 avvcbimage Info <14692>: Login test is OK.

2014-04-08T23:42:35.762+2:00 avvcbimage Info <14644>: The VM '[QNAP02-Datastore201] CentOS QNAP Management Server/CentOS QNAP Management Server.vmx' has no old snapshots to delete.

2014-04-08T23:42:35.784+2:00 avvcbimage Info <14664>: no snapshots are present on this VM.

2014-04-08T23:42:35.784+2:00 avvcbimage Info <15994>: Logging into datacenter path of 'folder?dcPath=Datacenter01'

2014-04-08T23:42:35.943+2:00 avvcbimage Info <14673>: All Datastore Info:

  datastore:'Local-hq-esx01                   '  capacity=434865438720    free=425348562944

  datastore:'QNAP02-Datastore201        '  capacity=2973996417024   free=2415045640192

2014-04-08T23:42:35.943+2:00 avvcbimage Info <14675>: All VM Info (7/7):

  VM:'CentOS QNAP Management Server/          '  last modified on '08-Apr-2014 21:39'

  VM:'vcenter.lab.local/                 '  last modified on '08-Apr-2014 12:39'

  VM:'vcenter/                                '  last modified on '08-Apr-2014 13:11'

2014-04-08T23:42:36.038+2:00 avvcbimage Info <14677>: All VM file Info:

  File:'CentOS QNAP Management Server-ctk.vmdk            ' last modified on '05-Mar-2014 10:22'  size=1049088

  File:'CentOS QNAP Management Server-flat.vmdk           ' last modified on '05-Mar-2014 10:22'  size=17179869184

  File:'CentOS QNAP Management Server.nvram               ' last modified on '05-Mar-2014 10:22'  size=8684

  File:'CentOS QNAP Management Server.nvram.txt           ' last modified on '30-Jan-2014 19:00'  size=8684

  File:'CentOS QNAP Management Server.vmdk                ' last modified on '24-Feb-2014 15:49'  size=620

  File:'CentOS QNAP Management Server.vmsd                ' last modified on '24-Feb-2014 15:49'  size=43

  File:'CentOS QNAP Management Server.vmx                 ' last modified on '08-Apr-2014 21:39'  size=3004

  File:'CentOS QNAP Management Server.vmx.txt             ' last modified on '30-Jan-2014 19:00'  size=2984

  File:'CentOS QNAP Management Server.vmxf                ' last modified on '08-Apr-2014 21:39'  size=284

  File:'vmware-2.log                                      ' last modified on '29-Jan-2014 08:18'  size=114456

  File:'vmware-3.log                                      ' last modified on '29-Jan-2014 08:44'  size=122823

  File:'vmware-4.log                                      ' last modified on '29-Jan-2014 08:52'  size=125758

  File:'vmware-5.log                                      ' last modified on '31-Jan-2014 11:44'  size=154480

  File:'vmware-6.log                                      ' last modified on '31-Jan-2014 11:59'  size=254378

  File:'vmware-7.log                                      ' last modified on '24-Feb-2014 15:37'  size=148629

  File:'vmware.log                                        ' last modified on '05-Mar-2014 10:22'  size=141769

2014-04-08T23:42:36.038+2:00 avvcbimage Info <14620>: Logging into datacenter 'vcenter.lab.local' with user 'vdpuser@LAB.LOCAL'

2014-04-08T23:42:36.216+2:00 avvcbimage Warning <0000>: No HTTP content was returned from datacenter from downloadFileData 'vcenter.lab.local'.

2014-04-08T23:42:36.216+2:00 avvcbimage Warning <17803>: Download VM .vmx file retry, count=0.

2014-04-08T23:42:41.269+2:00 avvcbimage Warning <0000>: No HTTP content was returned from datacenter from downloadFileData 'vcenter.lab.local'.

2014-04-08T23:42:41.269+2:00 avvcbimage Warning <17803>: Download VM .vmx file retry, count=1.

2014-04-08T23:42:46.389+2:00 avvcbimage Warning <0000>: No HTTP content was returned from datacenter from downloadFileData 'vcenter.lab.local'.

2014-04-08T23:42:46.389+2:00 avvcbimage Warning <17803>: Download VM .vmx file retry, count=2.

2014-04-08T23:42:51.389+2:00 avvcbimage Error <17804>: Max retries for downloading VM .vmx file exceeded, count=3.

2014-04-08T23:42:51.389+2:00 avvcbimage Error <17821>: failed to download vm metadata, try later

2014-04-08T23:42:51.390+2:00 avvcbimage Info <9772>: Starting graceful (staged) termination, failed to download vm metadata (wrap-up stage)

2014-04-08T23:42:51.390+2:00 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation  or pre/post snapshot script failed

2014-04-08T23:42:51.390+2:00 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation/pre-script/post-script failed

2014-04-08T23:42:51.390+2:00 avvcbimage Info <9763>: snapshot created:false NOMC:false ChangeBlTrackingAvail:true UsingChBl:true

2014-04-08T23:42:51.390+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_EndAccess: Disk access completed.

2014-04-08T23:42:51.390+2:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.

2014-04-08T23:42:51.390+2:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_AllowVMotion: Enable VMotion.

2014-04-08T23:42:51.392+2:00 avvcbimage Info <16038>: Final summary, cancelled/aborted 0, snapview 1, exitcode 157: miscellaneous error

2014-04-08T23:42:51.929+2:00 avvcbimage Info <17819>: VixDiskLib vMotion reservation successfully released

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

----- END avvcbimage log 2014-04-08 23:42:56 CEST  (9 warnings, 4 errors, 0 fatal errors)

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

*********** /usr/local/avamarclient/var-proxy-7/InitialTestBackup-1396993349036-514330c10e51fd762447275e43f5f51df0a8780b-1016-vmimagel.alg ***********

<logheader platform="Linux" env-locale-cs="ANSI_X3.4-1968" process_id="InitialTestBackup-1396993349036" version="7.0.182-99" tz="CEST" />

Is it possible to force the integrity check to a certain time, we've set the the maintenance window but integrity check always occurs 15:00-16:00, which is outside of the mantenance window.  It seems that it ignores the configuration so is there a setting or command that defines this?

Hello,

as stated above my backup job is failing and I don't know why.

From the vSphere Web Client I get the following message on the task console:

And from the logs I deducted that the important part is the one below:

/usr/local/avamarclient/var/Backup_test....log

All my software if version 6.0.

If there is anymore information I can provide please tell me.

Facing issue with VDP 6.1 when initiating backup. Refer to attached logs.

2016-05-17T04:44:23.519-10:00 avvcbimage Info <16041>: VDDK:VixDiskLib: Unable to locate appropriate transport mode to open disk. Error 13 (You do not have access rights to this file) at 4559.

Failed to open NBD extent.

2016-05-17T04:44:23.511-10:00 avvcbimage Info <16041>: VDDK:Cnx_Connect: Error message: Failed to connect to server  host:902

2016-05-17T04:38:04.477-10:00 avvcbimage Info <16041>: VDDK:2016-05-17T04:38:04.464+10:00 error -[7FAC95207700] [Originator@6876 sub=transport] Mounting VM vm-496 using transport hotadd failed : Could not connect to ESX host host04.ad.bgep.co.uk: Failed to connect to server host04:902.

Hello !

I have a problem.

Every day I see error for one of my servers in "Reports": 

2016-07-05T06:00:47.971+06:00 error -[7F2F3FA5E700] [Originator@6876 sub=transport]

   Cannot use mode hotadd to access [Cisco2-datastore] FileSrv1/FileSrv1_1.vmdk: Cannot mount using this method.

   (Mounting VM vm-3198 using transport hotadd failed : Cannot access datastore for one of the disks of Virtual Machine FileSrv1..)

In the same time, I havn't this error for other servers.

Hi all,

We have some servers running InterSystems Caché databases that are not VSS-compatible. We're using a VM backup solution (Veeam) to create quiesced backups of the VMs.

I have made pre-freeze and post-thaw scripts to quiesce the databases which work fine.

I'm currently testing the error handling behaviour. If for whatever reason we can't quiesce the database we want the backup to fail. I have read many reports of people whose attempts to create quiesced snapshots failed because their pre-freeze or post-thaw scripts returned a non-zero error code, so I thought this would be straight forward to set up.

However no matter what I do I can't make the snapshot operation fail. It looks as though VMware Tools can't detect the value returned by the batch scripts, or at least that it doesn't act on them if they're over 0. I've tried batch files with the following:

1. exit /b 1

2. notepad nonexistentfile.txt

3. notarealcommand

I've also tried a batch script with just 'pause' in an effort to meet some built in time out.

Nothing I do makes the snapshot operation fail. hostd.log reports that the batch file ran successfully each time.

Does anyone know how I can let VMware Tools know that the operation has failed? The utility we use to suspend the Caché database returns errorlevels we can act on appropriately in the batch, but we can't get that information back to vSphere to fail the snapshot operation.

We are running ESXi 4.1 build 582267

The VMware Tools version is 8.3.12 build 559003

The guest OS for the systems I'm testing is Windows Server 2008 R2 with SP1

Curiously, contrary to the VMware documentation, VMware Tools attempts to run C:\Windows\pre-freeze-script.bat and C:\Windows\post-thaw-script.bat instead of C:\Program Files\VMware\VMware Tools\backupScripts.d\*.* when we take a quiesced snapshot. I don't know if this is related.

I've not logged a service request yet as there's some mix up with our service contract and who is allowed to log cases on it.

Any help would be great.

Thanks,

Tom Browning

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/

http://vbscs.wordpress.com/2013/08/31/veeam-nightmare/

Opening up a thread for exchange of thoughts and experiences about backup of greater vmware environments. ~2000 VM's with ~100 TB of data volume.

Requirements are:

1. Data Backup should run as fast as possible

2. File Level recovery is a very nice to have

3. Deduplication is a must at this amount

4. No guest agents!

5. Fast recovery

Any thoughts, hints and opinions are appreciated

Hi All,

When i tried to start the VM of Vmware Data recovery appliance, its giving me the error like

"your cpu does not support long mode. use a 32bit distribution"

I tried to search for 32 bit version of data recovery but not able to find out.

Please help

Regards,

Suhag Desai

Hi community..

I'm in the process of testing TSM Client version 6.2.3. My primary focus is it's ability to backup VM Guest sessions..

The way I have structured this is very simple..

I've upgraded the TSM Client on the VCB Proxy Server..

Normally this server would VCB the guests to a local storage pool (700GB of local Disk), then kick off a TSM session to backup the VCB'ed guests to tape.

What I am aiming for is to use the new TSM to tape via vStorage API features of the TSM Client ver6.2.3.

I must admit a little reading, some poking about with the dsm.opt and I had the first test guest server backing up via the GUI..

It took a little more effort to get the CLI happening.

Roughly the command I'm calling is.

dsmc.exe backup vm Guest_Name -vmbackuptype=FULLVM -optfile=dsm.opt
All in all this works a treat.

It's definitly slower than using VCB but as this method pushes the backup directly to tape it actually takes less time.

How can I put that to make it a clear statement.

"The guests are in snapshot for a longer period of time, but the overall backup time is less as the guest is exported directly to tape rather than firstly hitting the local VCB Proxy's disk."

The problem I have is I can't restore..

I have a call open with IBM but don't appear to be getting any honest attention.. I fear this is because they simply don't know.

With the restore I'm running

dsmc restore vm myvm -vmname="myvm_restore_name" -datacenter="dirA/datacenters/myDatacenter" -host="myHostName" -datastore="myDatastore"

But it fails to find the Datacenter

The error is

ANS4166E Creating a Virtual Machine, but the datacenter 'dirA/datacenters/myDatacenter' was not found. (Of Course I'm using our actual VMWare details of FSA/Head_Office/Prod-HO-DR)

If I simplify my restore command to

dsmc restore vm myvm -vmname="myvm_restore_name" -host="myHostName" -datastore="myDatastore"

this also fails but with the error ANS4166E Creating a Virtual Machine, but the datacenter 'Head_Office' was not found.

Any assistance would be greatly appreciated.

hi guys

suddenly my Backup Scheduler won't start (I can see that in status VDP configure tab). It was working fine.

I manually start it. No go.

I used command: dpnctl stop mcs - dpnctl start mcs. Same thing it won't work. Logs for this process

any idea what could be causing the issue? Which logs to check?

thanks

Hello,

Can somone please tell me the best way to do backups using VEEAM in a SAN environment with 3 hosts and 2 arrays with the VMWare Standard Acceleration Kit?  I'd prefer not to purchase another device to back up to and I definitely want backups to both the LAN and Cloud.  I'm planning on implementing a full 10GB solution.  Let me know if you need any more info!

Thanks,

T

Hi All,

If a disk is provisioned using thick eager zeroed, will the CBT consider all disk sectors in use and back up the entire disk rather than just the used disk space? How does it work? Please share your thoughts

Thanks

Ali

Hi,

I've used Nakivo Backup & Replication with ESXi 5.5 for a long time without any issues. Iv'e recently upgraded to a new host with ESXI 6.5u1 and now I'm having problems backing up my guests.

The problem is that a full initial backup works 100% but following incremental backups almost always result in guest shutting down. The issue is that Nakivo will try and remove the sanpshot after a completed backup job but the guest is still using that snapshot. This gives me the error that the *-00001.vmdk is corrupt and the guest cannot boot.

I'v tried everyting, even a support call with two techs from Nakivo and they belive that this is a problem with vmware and not nakivo.

Please help...

We haev a1 TB disk attached to one of our VDR appliances, the free space has now reached 0. I have deleted a number of restore points by marking them for deletion and then running integrity check yet the free space is still 0.

I've read that this shouldn't necessarily cause jobs to fail as it works off "slabs" rather than just the amount of free disk space and that by removing restore points won't necessarily increase free space due to the way de-dupe works but I would expect some space to come back, no?

I presume reclaim should free up some space but so far it hasn't. Is it possible to run a reclaim manually? Or is there something else you can do?

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 !

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