I have vmware data protection 5.5.6
at this time are not running backups.
I'm trying to move the virtual machine to another datastore and I get the following error:
The method is disabled by 'vSphere Data Protection'
Error stack:
Call "VirtualMachine.Relocate" for object "XXXX" on vCenter Server "XXXX" failed.
this happens to me all the virtual machines that are scheduled backup.
Please your help to move the machines.
When I attempt to run a backup job I receive the following error:
A backup cannot be performed while the VDP Appliance is in the following state: Admin. Any help would be appreciated
hi guys
All of a sudden VDP stopped working, when I try to access VDP from Web Client I get a popup saying:
"The VDP Appliance is not responding. Please try your request again.Would you like to be directed to the VDP Configuration utility to troubleshoot the issue?"
and once there in the Configuration Utility, all services are OK, I only see this with a red X
Failed to retrieve the storage information on the appliance
Any idea what's going on?
thanks a lot
Hey All,
Experiencing an issue where my jobs for VMs running on local disk are failing due to what appears to be a timeout on the take snapshot action. So at first I thought it was a timing issue, so I looked at that. It takes about 1 minute for quiesed snapshots to actually happen.
I found the other articles that mention you should change the --subprocesstimeout=600 parameter to the /usr/local/avamarclient/var/avvcbimageAll.cmd file, so I did that with no luck. I also tried increasing the snapshot removal time, with no luck.
Still, after applying this and rebooting the appliance no dice, even though the snapshot is completing before the VDP task, it's still failing.
VMware KB: vSphere Data Protection backup jobs fail intermittently
I had another VM work just fine that was on a local SSD, but any disks that are otherwise located on slow local magnetic disk fail.
Looking at the logs, it would appear the most interesting entry is bolded and underlined below, which leads me to the following article, which says, your storage sucks, figure out why your snapshots are taking so long. Anyone have an idea how to increase the timeout when snapshots are being "TAKEN" as opposed to being removed? Next up will try removing queising from the config.
2015-01-23T11:42:45.635+04:00 avvcbimage Info <19704>: DataStore Storage Info:ESX4_Local_ESXi_Installable capacity=1995012308992 free=1682109890560
2015-01-23T11:42:45.635+04:00 avvcbimage Info <19716>: DS Capacity=1995012308992 FreeSpace=1682109890560 / HD committed=57196542066 unCommitted=29917971642 unShared=57196542066
2015-01-23T11:42:46.584+04:00 avvcbimage Info <16001>: Found 2 disk(s), 0 snapshots, and 0 snapshot files, on the VMs datastore.
2015-01-23T11:42:46.584+04:00 avvcbimage Info <0000>: isExitOK()=0
2015-01-23T11:42:46.599+04:00 avvcbimage Info <19680>: vmAction runBackupScript: ()
2015-01-23T11:42:46.599+04:00 avvcbimage Info <19681>: vmAction runBackupScript: script is skipped because it is null
2015-01-23T11:42:46.600+04:00 avvcbimage Info <0000>: [IMG0009] Pre-snapshot script: completed successfully
2015-01-23T11:42:46.600+04:00 avvcbimage Info <9692>: a VM snapshot has been requested
2015-01-23T11:42:46.600+04:00 avvcbimage Info <14627>: Creating snapshot 'VDP-1422031366f2a36877d42af6c1a25a994c67b393fa02286299', quieceFS=1
2015-01-23T11:42:46.635+04:00 avvcbimage Info <14631>: Snapshot 'VDP-1422031366f2a36877d42af6c1a25a994c67b393fa02286299' creation for VM '[ESX4_Local_ESXi_Installable] <VMNAME>/<VMNAME>.vmx' task still in progress, sleep for 2 sec
2015-01-23T11:42:48.662+04:00 avvcbimage Info <14631>: Snapshot 'VDP-1422031366f2a36877d42af6c1a25a994c67b393fa02286299' creation for VM '[ESX4_Local_ESXi_Installable] <VMNAME>/<VMNAME>.vmx' task still in progress, sleep for 2 sec
2015-01-23T11:42:50.689+04:00 avvcbimage Info <14631>: Snapshot 'VDP-1422031366f2a36877d42af6c1a25a994c67b393fa02286299' creation for VM '[ESX4_Local_ESXi_Installable] <VMNAME>/<VMNAME>.vmx' task still in progress, sleep for 2 sec
2015-01-23T11:43:12.796+04:00 avvcbimage Warning <16004>: Soap fault detected, Query problem, Msg:'SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
"Name or service not known"
Detail: getaddrinfo failed in tcp_connect()
'
2015-01-23T11:43:12.796+04:00 avvcbimage Error <17773>: Snapshot 'VDP-1422031366f2a36877d42af6c1a25a994c67b393fa02286299' creation for VM '[ESX4_Local_ESXi_Installable] <VMNAME>/<VMNAME>.vmx' task failed to start
2015-01-23T11:43:12.796+04:00 avvcbimage Info <19680>: vmAction runBackupScript: ()
2015-01-23T11:43:12.796+04:00 avvcbimage Info <19681>: vmAction runBackupScript: script is skipped because it is null
2015-01-23T11:43:12.796+04:00 avvcbimage Info <0000>: [IMG0009] Post-snapshot script: completed successfully
2015-01-23T11:43:12.796+04:00 avvcbimage FATAL <0000>: [IMG0003] The VMX '[ESX4_Local_ESXi_Installable] <VMNAME>/<VMNAME>.vmx' could not be snapshot.
2015-01-23T11:43:12.796+04:00 avvcbimage Info <9772>: Starting graceful (staged) termination, Create Snapshot failure. (wrap-up stage)
2015-01-23T11:43:12.796+04:00 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation or pre/post snapshot script failed
2015-01-23T11:43:12.796+04:00 avvcbimage Error <0000>: [IMG0009] createSnapshot: snapshot creation/pre-script/post-script failed
2015-01-23T11:43:12.796+04:00 avvcbimage Info <0000>: isExitOK()=202
2015-01-23T11:43:12.796+04:00 avvcbimage Info <40370>: snapshot created:false NOMC:false ChangeBlTrackingAvail:true UsingChBl:true, ExitOK:false, cancelled:false, fatal: true
2015-01-23T11:43:12.796+04:00 avvcbimage Info <0000>: vcbimage_progress::terminate
2015-01-23T11:43:12.796+04:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_EndAccess: Disk access completed.
Basically the article says, your storage sucks, deal with it and get better storage.
2015-01-23T11:43:12.796+04:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Establish connection.
2015-01-23T11:43:12.796+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_AllowVMotion: Enable VMotion.
2015-01-23T11:43:12.798+04:00 avvcbimage Info <16038>: Final summary, cancelled/aborted 0, snapview 0, exitcode 202: plugin error 02
2015-01-23T11:43:14.907+04:00 avvcbimage Info <17819>: VixDiskLib vMotion reservation successfully released
--------------------------------------------------------------------------------------------------------
----- END avvcbimage log 2015-01-23 11:43:17 EST (1 warning, 4 errors, 1 fatal error)
--------------------------------------------------------------------------------------------------------
I have a VDP dedicated to backing up a single mail server. It has run successfully in the past but now fails. Looks like something is stopping backups 1 hour after every run. Anyone see this before?
7PM - 9AM backup
9AM - 2PM blackout
2PM - 7PM maintenace
<logheader platform="Linux" process_id="avvcbimage" version="6.1.182-57" tz="EDT" />
--------------------------------------------------------------------------------------------------------
----- START avvcbimage log 2013-09-11 19:00:03 EDT [6.1.182-57 Linux-x86_64]
--------------------------------------------------------------------------------------------------------
2013-09-11 19:00:03 avvcbimage Info <5008>: Logging to /usr/local/avamarclient/var-proxy-1/messaging-daily-messaging-daily-1378940400043-7284d4d5d7c7876d35dee47030f770f1c997deeb-3016-vmimagew.
log
2013-09-11 19:00:03 avvcbimage Info <5174>: - Reading /root/.avamar
2013-09-11 19:00:03 avvcbimage Info <5174>: - Reading /usr/local/avamar/etc/usersettings.cfg
2013-09-11 19:00:03 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var-proxy-1/avvcbimage.cmd
2013-09-11 19:00:03 avvcbimage Info <5174>: - Reading /usr/local/avamarclient/var/avvcbimageAll.cmd
2013-09-11 19:00:03 avvcbimage Info <6673>: CTL listening on port 47708
...snip
.
.
...snip
2009-11 19:52:59 avvcbimage Info <16041>: VDDK:DISKLIB-LIB : numIOs = 450000 numMergedIOs = 0 numSplitIOs = 0
2013-09-11 19:56:02 avvcbimage Info <16041>: VDDK:DISKLIB-LIB : numIOs = 500000 numMergedIOs = 0 numSplitIOs = 0
2013-09-11 20:00:02 avvcbimage Info <16037>: Cancelled by MCS
2013-09-11 20:00:02 avvcbimage Info <0000>: Starting graceful (staged) termination, MCS cancel (wrap-up stage)
2013-09-11 20:00:02 avvcbimage Info <16022>: Cancel detected(externally cancelled by Administrator), terminated(1).
2013-09-11 20:00:02 avvcbimage Info <16022>: Cancel detected(externally cancelled by Administrator), terminated(1).
...snip
.
.
...snip
--------------------------------------------------------------------------------------------------------
----- END avvcbimage log 2013-09-11 20:00:26 EDT (5 warnings, 1 error, 0 fatal errors)
--------------------------------------------------------------------------------------------------------
I'm having trouble with my 1TB vdp appliance, the appliance configure status webpage is showing all services are running but when I login to the appliance and run the command dpnctl status is shows gsan as degraded.
I tried stopping/starting the gsan using dpnctl stop gsan, dpnctl start gsan but it returned to degraded fairly soon afterwards
I tried changing hte backup window so its not in maintenance mode to see if that would let me execute manual vm backups but that didn't work
I've also increased the RAM on the appliance from the default 4GB to 6GB
Can anyone tell me if gsan degraded is user fixable or if not will the appliance correct it itself and if so how long (minutes, a few hours, 0.5 days, more)
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.
how to optimize backup time, deduplication, performance of appliance.
Thanks in advance
ok this is the situation (ESXi 5 /VSphere client):
VM (WS2008) didn't boot anymore.
I've managed to download via Data Storage Browser the big SERVER-flat.vmdk file plus 14 out of 15 other file sets containing snapshots.
(SERVER-000002.vmdk to SERVER-000015.vmdk + SERVER-000002-delta.vmdk to SERVER-000015-delta.vmdk).
However there was no way to save SERVER-00001.vmdk and the associated delta file and then the server failed completely (data corruption after the failure of one disk in the Raid array, etc.)
I've rebuild the server on another machine from the -flat file (renaming FILENAME inside SERVER.VMX from SERVER-000015 to SERVER) but this brings me back to the initial server configuration (one year ago).
When I try to add the snapshot files (even renaming the 000002 into 000001 or editing the vmdk file (ParentFileNameHint) it always returns an error.
Error message from esxi502: Reason: The parent virtual disk has been modified since the child was created. The content ID of the parent virtual disk
does not match the corresponding parent content ID in the child.
Cannot open the disk '/vmfs/volumes/51312345-e57af280-etc-etc/SERVER.domain.it/Server-000002.vmdk' or one of the snapshot disks it depends on.
Question 1: Is there any way to incorporate the snapshots, jumping from SERVER-000002 to SERVER.vmdk, seeing that the first one is missing?
Question 2: is there any program that can read/recover data from single vmdk files? (tried already Systools VMware recovery but this does not work with files saved from VM to local disk as the support explained to me)
Any help would be highly appreciated as I'm desperate, not very familiar with VMware and the data is crucial for us.
Thanks a lot!
Hey everyone,
I have been combing the Internet trying so many things.. many of them coming from this very forum. I've had no luck, so I come to you all for ideas!
I am running the vCenter Server Appliance, recently upgraded from 5.5.1 to 6.0.
After the upgrade, I've deployed the vSphere Data Protection 6.0 Appliance (via OVF).
I run through the configuration, allocate storage, it registers with vCenter... no errors whatsoever.
*however* no matter WHAT I do, VDP does NOT show up in the vSphere Web Client. I've seen from screenshots that it should be there, right by the vRealize Orchestrator link on the left, but it just isn't there.
I've been through every log file on the VCSA (that I know of) looking for any errors or any mention of VDP, and there is nothing that indicates anything is wrong.
-I've deployed the VDP appliance again to no avail
-tried 3 different browsers, both regular and "private" modes
-logging in as the vsphere.local\Administrator as well as my own administrator account
-removed the plugins via the MOB and let them re-register
-run the registration to vCenter wizard in the VDP appliance config page soooo many times, with various users
I am just at a total loss here. I mean, it looks like *everything* is working exactly how it's supposed to, no problems at all, except... the link in the web client just isn't there.
I really hope I'm just being dumb and there's something super simple I'm missing... anyone have any ideas to throw my way? Thanks!
I know that the VDP documentation states that the only way to manage the backups is to use the web client plugin, but is there really no way to automate backups? For example by using API calls or directly thorugh the CLI?
I'm looking for a way in which I could automatically include VMs in a backup policy, after a virtual machine gets provisioned by vCAC. I've tried to include a whole ressource pool in the backup policy and each VM which gets migrated there should be backed up, but this does not work.
I expanded the space on the VDP 6 appliance from 2TB to 4TB by expanding the files (from 3 to 6). But it is still showing over 80% full and growing after several days. It should be around 40% now. How can I force it to rebalance the backups between the new files or at least to acknowledge that it can use the new space? It does say the capacity is 4.1TB, but it says the deduplicated size is 3.3TB which is totally bogus.
According to status.dpn, the garbage collection just ran. It took nearly 2 hours and "recovered 12.09 GB". So garbage collection didn't rebalance the files.
hfscheck ran yesterday successfully, so that didn't rebalance.
It has been thru a half dozen 12 hour maintenance windows. no luck.
All services are running, the only alarm is the VDP: [002] The VDP appliance is nearly full.
So how to I get it to rebalance?
Hi all,
I'm trying to use Backup Exec 2010 to perform full/incremental backups of our VM's with GRT enabled. However, at the end of every job, I get a warning saying that it failed to mount the virtual disk image. I went into the debug logs, and found the following:
ENGINE: Status for: 'xxxxxx' updated
BEREMOTE: VDDK-Log: TicketResolveHostName: Resolving IP address for hostname xxxxx
BEREMOTE: VDDK-Log: TicketResolveHostName: Resolved to 10.86.8.47.
BEREMOTE: VDDK-Log: VixDiskLibVim: TicketLogin
BEREMOTE: VDDK-Warn: VixDiskLibVim: Not licensed to use this function.
BEREMOTE: VDDK-Log: VixDiskLibVim: TicketLogout
BEREMOTE: VMDKRemoteImage::Open() Could not open the disk '[VMStorage2] xxxxx.vmdk' Error Text: 'Host is not licensed for this feature' Error: '16064'
BEREMOTE: CDiskLayoutImplementation::DisableAutoMount: Disabling AUTOMOUNT
BEREMOTE: VMwareVirtualSystem::MountDisksUsingVddk() - Enter
BEREMOTE: VDDK-Warn: Refusing to set temp directory second time 'C:\WINDOWS\TEMP\vmware-SYSTEM' to 'C:\WINDOWS\TEMP\vmware-SYSTEM'.
BEREMOTE: VDDK-Log: Mntapi_Init Asked - 1.0 Served - 1.0 was successful,TempDirectory: C:\WINDOWS\TEMP\vmware-SYSTEM.
BEREMOTE: VDDK-Log: TicketResolveHostName: Resolving IP address for hostname xxxxxx
BEREMOTE: VDDK-Log: TicketResolveHostName: Resolved to 10.86.8.47.
BEREMOTE: VDDK-Log: VixDiskLibVim: TicketLogin
BEREMOTE: VDDK-Warn: VixDiskLibVim: Not licensed to use this function.
BEREMOTE: VDDK-Log: VixDiskLibVim: TicketLogout
BEREMOTE: VDDK-Warn: VixDiskLibProvider::NameBasedProvider::Get: Unable to open disk xxxxxxx.vmdk, openflags = 4 - VixError 0x3ec0.
BEREMOTE: VDDK-Warn: DiskLibProvider_GetDisk: Open failed - index 0.
BEREMOTE: VDDK-Log: Error 2 opening disk 0.
BEREMOTE: VDDK-Log: VixMntapi: Operation failed with system error: The system cannot find the file specified.
(2), translated to 4
BEREMOTE: VMDKRemoteImage::mountDisks() Could not open the diskset. Error Text: 'A file was not found' Error: '4'
BEREMOTE: CDiskLayoutImplementation::SetAutoMount: Enabling AUTOMOUNT
BEREMOTE: VDiskMounter::MountAllDisks:failed VirtualSystem::Initialize()
BEREMOTE: Error mounting disks (0xe0009741)
BEREMOTE: IMG_PDI_FSYS::ImgPdiFsys::AttachToDLE (551):
BEREMOTE: Error mounting disk(s): E_IMG_FS_FAILED_TO_MOUNT_VIRTUAL_DISK (0xe0009741).
BEREMOTE: CommonMounter::~CommonMounter called
The relevlant lines to me seem to be the ones that indicate that this host is not licensed for this feature. The other funny thing is that these logs are produced AFTER the vmdk has been completely copied to the backup server.
We're using vSphere Essentials, which includes the vmstorage API's as I recall, any idea what's going on here?
Thanks
Hi,
I'm trying BackupExec 2010 R2 AVVI to backup some virtual machines on a NetApp NFS datastore. All machines have thin provisioned disks. I'm using NDBSSL transport mode.
Every time I do a backup of a thin provisioned disk, BackupExec will backup all the provisioned space and not only the used storage, resulting in overly long backup jobs.
Is anyone having the same effect? Is this VADP problem, or BackupExec problem? Any workaround?
Thanks.
Hello,
No problems backing up with the trial licence. Once I install the free licence I get these error in the logs. (using VDDK 5.0)
3/28/12 15:47:34 [5196.4] Connected successfully to the Host https://192.168.1.6/sdk ...
3/28/12 15:47:34 [5196.4] Calling SnapshotVM module ...
3/28/12 15:47:35 [5196.4] VCB_COM Log Cache begins
Log Cache ends
3/28/12 15:47:35 [5196.4] VCB_COM Log Cache ends
3/28/12 15:47:35 [5196.4] SnapshotVM returned -110.
3/28/12 15:47:35 Err_code: -110 SnapshotVM: Exception Raised - fault.RestrictedVersion.summary
3/28/12 15:47:35 [5196.4] An unexpected error occurred while creating snapshot for the VM having UUID 564d1653-9845-97c5-a97a-6ad6abdd55c8.
3/28/12 15:47:35 [5196.4] DoSnapshotVM : Exception raised - 564d1653-9845-97c5-a97a-6ad6abdd55c8
3/28/12 15:47:35 [5196.4] Trying to disconnect from Host https://192.168.1.6/sdk ...
3/28/12 15:47:35 [5196.4] End of DoSnapshotVM operation
Obviously something is disabled in the free license.
My question is which license do I need get to make this work? We are a small business and will only have two physical servers running ESXi 5.0.
Will this small business version work?
Thanks,
Joe
Hey Guys,
What do you guys think, which is a better product for replication. I am specifically looking at replication and over all stability and performance and feature pack - which one is better?
What do you think?
Thanks
R
Hallo,
i try to register the vdp to vcenter 5.1. I use the embedde SSO. The settings seems to be OK. But after the connection test, i get an error message box without text. If i change the settings to other values, i get a messages that my settings are incorrect. Have anyone a idea where here the problem is?
Best regards
Peter
Hi, I have a strange issue regarding setup of MS cluster on server 2012, after i follow to the letter the instruction how to setup in the box cluster i get error on cluster validation. I have vcenter 5.1 and esxi 5.1 and i followed Setup for Failover Clustering and Microsoft Cluster Service ESXi 5.1, vCenter Server 5.1 document i found on vmware site, after i create and configure two VM by the specification listed in document (Clustering MSCS Virtual Machines on a Single Host) i select cluster validation and got a following error: Validate Storage Spaces Persistent Reservation failed.
I suspected on storage but HP P2000 g3 support SCSI-3. After that i decided to create Quorum disk on local datastore and i used a virtual disk with SCSI BUS Sharing as virtual which is also suported and i got a same error. After that i recreated all on another system (using EVA6400 and HP BL460c gen 8) and again same error. It does not matter if i use a virtual disk or Non-pass-through RDM (virtual compatibility mode) as a quorum again same error. If i can not clear this issue i will not be able to use Microsoft support on the cluster because first thing they ask is a cluster validation raport that need to be with out an error.
Thanks
I just noticed that the (4) VDP appliances I am testing all stopped sending the Email Summary Report after the Daylight Savings time change on Sunday. the last report was generated Sunday morning at 12:00am. Now all the appliances are reporting this:
VDP: Send email summary report error. The email summary report timer is set to the incorrect hour. It does not match the vdrdb value.
The time this error is generated is 11:00:00pm which is exactly one hour from when it should be running.
I think this is a Daylight Savings time issue but dont know how to address it.
Any help would be greatly appreciated.
RickH
Hello All,
I would like to know how we could take a backup of a physical RDM ?
Kindly share ideas and features of the product VDP that would allow or provide a workaround for the backup of the RDM in physical mode.
Also anybody with the knowledge of IBM TSM could provide some steps for TSM backup for RDM in physical mode.
I am looking at VDP or TSM for backup.
Thank you in Advance !
