Hi,

We received few scheduled backup errors for jobs set up for 'individual disks backup' (x1 hard disk) with the 'fall back to the non-quiesced backup if quiescence fails' option checked.

Error:

"VDP: An unexpected error occurred with the following error code: 10020."

Client Log:

server System-serverSystem-1501535800867 Info <0000>: <workorder_finished pid="vmimagew" startUTC="2017-07-10 10:00:00" msgver="1" pidnum="3016" finishUTC="2017-07-10 11:00:00" errorcode="170" wid="server System-server System-1501535800867" errormessage="code 170: completed with errors, client log should be examined" errorrealm="Plugin 3016-vmimagew" />

avvcbimage Warning <19733>: vSphere Task failed (quiesce, snapshot error=45): 'An error occurred while saving the snapshot: Failed to quiesce the virtual machine.'.
avvcbimage Error <17775>: Snapshot 'VDP-1500547dfgf4066f0b8d5dfdfd34a5181cf5ffebe' creation for VM '[xxxx] server/server.vmx' task creation encountered a quiesce problem
avvcbimage Warning <0000>: The VM could not be quiesced prior to snapshot creation and this backup will not be used as a base for subsequent CBT backups if successful.
Warning <40711>:     Consider using the pre-freeze and post-thaw scripts to facilitate VM quiescing
avvcbimage Warning <41146>:     This error might caused by the pre-freeze script returning a non-zero error code.

Unable to find a fix/or much information RE this, please shed some lights on fix to this issue.

Thank you

hi guys

I have this VDP that backups only 8 VMs, and I've been having a problem with one of them - always the same VM (vmware tools up to date, OS W2008 R2)

I get this error message like every  3 days, yeah the issue is fixed as soon as I consolidate the VM - from VM menu - .

this is what is happening I see that one VM is failing so in the Events I see this (vCenter)

XXXcom.vmware.vdp2.server.error.10056.formatonvmfoundXXX

so I found that VDP creates a snapshot not visible from snapshot manager and that creates this problem, so when I found this I have to manually run a Consolidation on this VM

I found this VM always having this hidden snapshot   VM_name_00001.vmdk

anyone knows how to fix this forever, I cannot be consolidating this VM every 3 days...

I have like 8 VDP instances installed and believe me managing this products is very tired, I don't know any other product like Veeam so I ave no way to compared

thanks a lot

Hi,

We are running two host on Esxi on 5.5 on HP DL380G8 Servers.

Planning to have backup of critical files,DB offsite as well.May be whole VM we can backup or specific files or DB we may backup on HP Autoloader 1/8 6250 SAS based and rotate the tapes weekly monthly etc.

Evaluating the option of Veeam B&R and Symantec Backup Exec.

What we planning to have a one of the existing VM inside the Esxi 5.5 to see the Tape-Autoloader.

But realized that  Vmware doesn't support Tape drives directly connected over 5.x onwards. Does.Does anyone know the reason for this while it was fine with prior version of Vmware.

In that case only left with the option of attaching adding another physical server and adding the SAS HBA and Tape autoloader to this server.

This looks to me additional cost of adding the server with OS.

Is there any other way round,I can backup important data offsite of our office premises.

Regards,

Sushil

Thanks to jhunter I was able to perform a migration of my VDP to 6.1. 

The checkpoint restore from Data Domain worked great and the only issue I have left is my replication jobs are not running.  Prior to migration my replication jobs runs every evening to another VDP appliance.  After the migration the replication job did not run.  It does not run when I try manually.  I don't get an error. The job never runs. It doesn't show in the log that I tried to run it or that it failed.  I created a new replication job and the same thing happens.  It never runs and there is no error or a log of it.

Hi, would like to check is it possible to have 2 backup products backing up via vSphere VADP using CBT?

A scenario will be backup product A performing full & incremental backup of VMs using VADP, and another product performing VM incremental replication.

Thanks.

Hi,

Is there a way to manually stop a running VDP Backup Job? There is no such an option in the VDP web interface. If I do "Cancel" on running Tasks, the task itself is cancelled, but VDP Backup Job is still running...

Hello!

I have vCenter and ESX 5.1.

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

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

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

error

27.12.2013 13:26:34

VDP: Backup Job

vSphere Data Protection 5.5

What is it mean&

Hi All,

I've been struggling with another issue in my home lab.  I upgraded to vCenter 6.5 last week and, at the same time, deployed a new vDP 6.1.3 appliance.  Try as I might, I can't seem to get the plug-in to appear anywhere within vCenter.

I have gone into the extensions section of http://<vcenter>/mob and only see config.vmware.vdp2.config.  I can't seem to get config.vmware.vdp2 to show up, even if I delete the .config entry and restart/re-register the vDP appliance.

I have also done the workaround where you log into the vCenter server and add the .war and .jar file manually into the vsphere-client directory, with no luck.

Anyone else seeing this issue?

Thanks,

Dave

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 vSphere community,

Curious what people are doing to backup up physical ESXi servers?   We have IBM TSM, but I'm not sure it can backup an ESX Host.

Strictly looking at ESX host backups at the moment and not virtual machines.

Any suggestions or advice?

Thanks!

Hi.

We have VDP 6.1.2 with 4T capacity (6T net space). We tried to expand capacity from 4T -> 6T (6T ->9T).

On the vdp-configure storage tab we choosed Expand Storage and got the following message:

expand storage

-vdp: There are incorrect number of disks associated with vdp appliance.

We have two 4Tb storage luns assigned to VDP and one 4Tb lun is created for the expansion.

Now it seems that we cannot expand disks couse we don't have enough space on existing luns.

And becouse this error we can't assign the third lun to vdp to cover that required space.

Is there a chicken egg proglem or am I missed something?

How do we assign more disk space (lun) to VDP so we can do the disk expansion?

Enviroment is ESXi 6 with latest updates

Regards

Pasi

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

VMWare announced the End of Availability (EOA) of VMware Data Protection (2149614).

This is quite disappointing, as many customers might have opted for using VDP after the announcement that VMware vSphere Data Protection Advanced became part of VMware vSphere (and did no longer require purchase of a separate license):

"Starting March 1, 2015, VMware vSphere Data Protection Advanced will be consolidated into VMware vSphere Data Protection ... All functionality available with vSphere Data Protection Advanced, previously available as a standalone product, is now included in VMware vSphere Data Protection 6.0."

If I understand it correctly, customers that are using VDP now need to change their backup policies and again need to purchase from VMWare:

"Beginning today, Dell EMC is offering you a complimentary migration to the more robust and scalable Dell EMC Avamar Virtual Edition."

Comments welcome!

Tom

hi,

hope you can advice me selecting a backup solution, 

We  need to buy Essentials Kit, these do not include data protection so we will need to search for a alternative to backups VMs (powered on).

i would like to use veeam but the licences required increase price too much (1 licence for each socket) so im looking for an alternative, what you could recommend?

until now the cheaper i found was cloudbacko, but searching on forums there are many negative opinions.

Hi,

I've been struggling with VDP for a couple of days now.

Here's the setup:

• vCenter appliance 5.5 U2
• 1 VDP 5.5.6
• 1 VDP 5.8

The VDP 5.5.6 is there since a long time ago, it's running fine and I can manage it no problem in the vCenter Web Client.

But, cannot see the "vSphere Data Protection 5.8" option. Therefor I cannot manage the VDP 5.8.

The VDP 5.8 is a fresh install. I've tried registering it using three different users and it doesn't seems to do the trick.

vsphere.local\Administrator

vsphere.local\VDPAdmin (This is a user that I created for the purpose)

MyDomain\VDPAdmin (This is an AD account in my domain. Of course MyDomain is not the real domain name )

All three accounts had permissions defined at the root level of the vCenter as administrators.

Each time it registered successfully. I've rebooted both vCenter and VDP appliance numerous times.

Any help would be appreciated.

Thanks.

Dear all, I have been knocking my VDP about trying to fix it. It had lost data02, and I got that back by running a filecheck discarding the metadata stuff. So, I was then able to gain access to the rollback, but rollback failed.

Now the status looks like this:

root@vdp:~/#: dpnctl status

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: gsan status: up

dpnctl: INFO: MCS status: down.

dpnctl: INFO: Backup scheduler status: down.

dpnctl: INFO: axionfs status: up.

dpnctl: INFO: Maintenance windows scheduler status: enabled.

dpnctl: INFO: Unattended startup status: enabled.

dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

I found this article: Starting the MCS service in VMware vSphere Data Protection 5.1.x fails with the error: gsan rollbacktime does not match … and attempted to run the command specified in there, but it is not successful.

I get this:

root@vdp:~/#: dpnctl start mcs --force_mcs_restore

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: Restoring MCS data...

Permission deniedPermission denied at /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/XML/LibXML.pm line 587.

Could not create file parser context for file "/usr/local/avamar/var/mc/server_data/prefs/mcserver.xml": Permission denied at /usr/local/avamar/lib/MCServer.pm line 128

dpnctl: ERROR: cannot restore MCS data without a password for MCS administrative user id

dpnctl: ERROR: MCS restore did not succeed, so not restarting MCS

dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

So my question is really... How do I specify the password for the MCS administrative user id so that I may force MCS up again?

If I try to start MCS using dpnctl start mcs I get the following:

root@vdp:~/#: dpnctl start mcs

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: Starting MCS...

dpnctl: INFO: To monitor progress, run in another window: tail -f /tmp/dpnctl-mcs-start-output-6153

dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start" - exit status 13

dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

This is what the dpnctl.log looks like:

root@vdp:~/#: tail /usr/local/avamar/var/log/dpnctl.log

2016/06/30-12:50:18 [ "/bin/cat /tmp/dpnctl-get-mcs-status-status-5787 2>&1" exit status = 0 ]

2016/06/30-12:50:18 dpnctl: INFO: "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test" exit status = 13

2016/06/30-12:50:18 rm -f /tmp/dpnctl-get-mcs-status-status-5787 /tmp/dpnctl-get-mcs-status-output-5787

2016/06/30-12:50:18 dpnctl: INFO: "rm -f /tmp/dpnctl-get-mcs-status-status-5787 /tmp/dpnctl-get-mcs-status-output-5787" - exit status 0

2016/06/30-12:50:18 dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

2016/06/30-12:50:18 rm -f /usr/local/avamar/var/dpnctl.lck

2016/06/30-12:50:18 ======= dpnctl 7.1.80-129 (1.139), running as admin, RETURNING at 2016-06-30 14:50:18 CEST =======

2016/06/30-12:50:18 [user "admin"] program (pid 5787) exit status = 1 (error)

2016/06/30-12:50:18 ======= dpnctl 7.1.80-129 (1.139), running as root, ENDING at 2016-06-30 14:50:18 CEST =======

2016/06/30-12:50:18 [user "root"] program (pid 5729) exit status = 1 (error)

Not a lot to work with here... Logfile has absolutely no info that I can understand...

Message was edited by: Ludvig F Aarstad: added more info

Wow, it was as simple as typing su - admin before running the dpnctl start mcs force_mcs_restore command...

Message was edited by: Ludvig F Aarstad: Added solution...

Yesterday I had some time on my hands, noticed 6.5.0b for vCenter appliance was released, and 6.1.4 vdp was available.

Upgraded vCenter appliance no problem (from 6.5.0a). Then tried to upgrade 2 vdp instances to 6.1.4 from 6.1.3. Both upgrades failed (no errors, just failed around 80% stating I had to recover from snapshot). Also, after reverting, the vDP plugin is no longer loaded in the vCenter web interface.

I restored the vdp appliance from snapshot, restarted, still no vdp icon to access. I also removed the vdp from the mob interface, and tried to re-register the vdp appliance using vdp-configure. It failed on re-registering to the vcenter instance.

At this point, I decided to try to just re-create my vdp instances. I downloaded the 6.1.4 ovf file, deployed, and during vdp-configure it fails (tried 3 times, on two different datastore types iscsi/nfs).

I still had the 6.1.3 ovf, so I tried to deploy the older version, fails with the same errors as 6.1.4 is failing with.

Keep in mind I deployed 6.1.3 a month ago with absolutely NO issues. I'm wondering if this has something to do with vCenter 6.5.0b.

The errors when deploying brand new instances (both 6.1.3 and 6.1.4) are attached a screenshots.

As mentioned above, I tried both on NFS and iSCSI datastores (iSCSI datastores running VMFS6).

Anyone know anything about this?

Hi,

After installing the new 1.0.1 and the new plug-in I'm still having the same problem.

Everytime I start a backup the VDR appliance crashe and terminate the job after 58% of the job with the error below:

"Task terminated unexpectedly, possible due to a power failure or system crash"

After this the VDR get disconnected and I have to login again.

Thanks

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

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.