Hi All,

I have a question about vSphere Data Protection. We installed this product a couple of days ago and I am hoping it will help us cut down on Symantec Backup Exec costs. I read somewhere that you can restore a single/multiple file from a VDP backup. I Have been clicking my way in the restore option but I can not find this option anywhere. Does anyone have experience with this?

Thank you,

Andre

new vdp 5.5 appliance 1TB connected to a vcenter 5.5 appliance

configured a dozen or so backups that are working.

have 3 vm's that get

"An unexpected error occurred with the following error code: 10058"

the three vm's are windows 2008 servers.

running job manually or scheduled get the same error

google does not come up with any matches nor does this community have mention of the error code.

any ideas?

Hi,

Has anyone tried to limit concurrent backups?

Default number (8) is just too much for our NAS and i'd like to have 4 or even 2 backups running at the same time.

Jeff Hunter mentions that it's possible:

Setting the record straight on VMware vSphere Data Protection | VMware vSphere Blog - VMware Blogs

"It is possible to change the number of proxies in use by running the registerproxy.sh script located in /usr/local/avamarclient/etc/. Please understand this is something that has not been tested and it is NOT SUPPORTED."

If someone has actually been able to do this I'd like to hear how it's done.

Thanks!

Hello

I currently have the following issue:

We have a IBM x3650 server  with two raid 5 systems. The esxi host is installed on the first raid which currently failed (marked as offline). Now that I can't boot into esxi I would like to copy the virtual machines from the second raid but I don't know how to retrieve the files. I booted clonezilla from a live CD which shows me the partition but I can't see any folder or files. Because of unknown filesystem??

However I would appreciate any advice on how to get my virtual machines.

BR

Fabian

I have a customer that currently has the VDP and it's configured to use a NFS storage as the repository for their VM backup.

Now, they are buying a brand new NAS and want to add it to the VDP and I was wondering how can we do that.

Any thought?

Thank you in advanced.

Regards

José

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

VDP 5.5, I am trying root\changeme but no luck, could it be something else? If it indeed an unknown password how can I recover?

Thanks!

2016-02-02T20:00:16.719-01:00 avvcbimage Info <14625>: WorkOrder Disk Info:

  Prior Disk '2000': file(base):'[wb_prod_ql01os] WB Prod QL01/WB Prod QL01.vmdk', backItUp=1

               snapshot file:'[wb_prod_ql01os] WB Prod QL01/WB Prod QL01.vmdk'

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

               prior change block ID:''

               Datastore:'wb_prod_ql01os' Directly Accessible=1

  Prior Disk '2016': file(base):'[wb_prod_shard01] WB Prod QL01/WB Prod QL01.vmdk', backItUp=0

               snapshot file:'[wb_prod_shard01] WB Prod QL01/WB Prod QL01.vmdk'

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

               prior change block ID:''

               Datastore:'wb_prod_shard01' Directly Accessible=1

.

SNIP

.

2016-02-02T20:00:20.265-01:00 avvcbimage Info <19704>: DataStore Storage Info:wb_prod_ql01os capacity=90999619584    free=30713839616

2016-02-02T20:00:20.265-01:00 avvcbimage Info <19716>: DS Capacity=90999619584    FreeSpace=30713839616    / HD committed=59255284393    unCommitted=594            un

Shared=59055800320

2016-02-02T20:00:20.289-01:00 avvcbimage Info <19704>: DataStore Storage Info:wb_prod_shard01 capacity=1675037245440  free=63387467776

2016-02-02T20:00:20.289-01:00 avvcbimage Info <19716>: DS Capacity=1675037245440  FreeSpace=63387467776    / HD committed=1610612736000  unCommitted=597            un

Shared=1610612736000

2016-02-02T20:00:20.290-01:00 avvcbimage Info <19717>: DS(wb_prod_shard01) does not have enough free space (63387467776   ) for disks used (80530636800).

2016-02-02T20:00:20.290-01:00 avvcbimage Error <19661>: Datastore does not have enough free space for snapshot

I've pasted prudent entries from my VDP appliance log file above.

Basically I am backing up a single disk on a 7-disk VM. You can see in the first log entries above (before the SNIP) that disk 'wb_prod_ql01os' is marked for Backup (backItUp=1), then the next disk, 'wb_prod_shard01' is not marked for backup (backItUp=0).

We then go down the logs (below the SNIP above) and see that VDP has failed due to 'Datastore does not have enough free space for snapshot', but it's pointing at 'wb_prod_shard01' as the culprit! That disk is not marked for backup so why on earth is it causing VDP to fail??

Any help hugely appreciated

Hello,

I am trying to upgrade my VDP 6.1 appliance to 6.1.1. The iso is not being detected when mounted so I was going to run the hotfix. However, I cannot upload the hotfix files to my appliance via ssh. I am able to log in to the vdp-configure web portal and the vmware console using the root account. When I try to log in using putty or winscp it is saying access denied.

Also, all the potential solutions I'm finding via google appear to be broken. I get this error when trying to access the vmware kb articles:  1$deletedMessageForViewDocumentPage

Any advice would be appreciated. Thanks in advance.

Hello,

I am running VDP 6.0.3.3. Before I upgraded my vCenter Server from 5.5u3b to 5.5u3e, I consulted Vmware interoperability matrixes to see that there should be no problem. But the opposite has happened:

All backups end up with the error:

VDP: An attempt made to backup a client failed because no data was found that matches the type of data that the job was configured for.

XXX com.vmware.vdp2.server.error.30915.formatOnVm not found XXX

XXX com.vmware.vdp2.server.common.error.code.formatOnVm not found XXX

I retired one of the VMs, it is no longer in the clients list. But I cannot add it back to the job. In fact, I am not able to add any VM to any job, even those which were never backed up by VDP. The error message is:

VDP: Unable to add client "AAA" to the VDP appliance while creating/editing backup job "BBB". (Full client path: ?)

Do you have an idea, what is going on and how to resolve it ? It's quite urgent.

Thank you in advance.

Regards,

David

Hey guys,

With a fresh VDP 6.1.3 install on top of vSphere 6.5, most backup jobs hang at 92%.  This is not the issue documented in the release notes, and the backups almost never complete. I DID NOT have this issue with VDP 6.1 under vSphere 6.0.

I have tried backing up photon OS machines, centos 6.5 machines, centos 6.6+ machines, and centos 7 machines.  So far the only ones to successfully complete are some of those old centos 6.5 ones.  I'm not sure if the O/S version is a red herring here, or if it's related to some other pattern I just can't identify at the time.

I have tried backing up images with the quiesce option both on and off, and it doesn't seem to make a difference in the result.  The backups hang regardless and are unsuccessful.

I should mention the storage was created along with the appliance and is on VSAN, if that makes any difference, but - this absolutely all worked with VDP 6.1 and vSphere 6.0.

I looked in a failed job's vmimage log in /usr/local/avamarclient/var/ and noticed this at the end:

2017-01-17T04:02:15.693+04:00 avvcbimage Info <9679>: Virtual disk connection to '[vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1.vmdk' has been closed
2017-01-17T04:02:15.693+04:00 avvcbimage Info <19718>: Found Disk from Device Key: '2001'.
2017-01-17T04:02:15.693+04:00 avvcbimage Info <9674>: virtual disk [vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1_1.vmdk will be connected readonly
2017-01-17T04:02:15.693+04:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_OpenEx: Open a disk.

2017-01-17T04:02:15.693+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_GetNfcTicket: Get NFC ticket for [vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1_1.vmdk.

2017-01-17T04:02:16.008+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: Request RandomAccessRO diskKey = 2001, readOnly = 1, openSnapshot = 0.

2017-01-17T04:02:16.094+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

2017-01-17T04:02:16.101+04:00 avvcbimage FATAL <5889>: Fatal signal 11 in pid 15065
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  FATAL ERROR: <0001> uapp::handlefatal: Fatal signal 11
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006b93b1
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba127
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba44b
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba53e
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 0000000000628810
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56c90850
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5050193f
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5051c277
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5051c75e
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5052b142
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5052b678
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56ecab73
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56ecb123
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004284bc
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004291f9
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004993c4
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 000000000070ac4c
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56c88806
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e558cd9bd
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  ERROR: <0001> uapp::handlefatal: aborting program pid=15065, sig=11
2017-01-17T04:02:16.103+04:00 avvcbimage FATAL <5890>: handlefatal: Aborting program with code 176, pid=15065, sig=11
2017-01-17T04:02:16.103+04:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Exit: Unmatched Init calls so far: 1.

2017-01-17T12:00:07.999+04:00 avvcbimage Info <40660>: vcbimage_progress::terminate

the log ends there.

This looks serious to me, but it's hard to figure out where to go from here.

Does anyone have any advice as to how to proceed?

Thanks for any assistan

Hi,

  So we have 2 vCenters one in our Branch Office the other in our Main.  The Main office has vCenter 6 while the Branch has vCenter 5.5 (do to Hardware Compat with 6.0 esxi). I am wondering if I would be able to run VMware Replication between these two vCenters? Yes I know i need to ensure Hardware Compat stays at 9 and ensure all other compatibility are monitored too. Will VR work between different  versions VR ver6 - VR ves 5? Also will VDP replicate across versions also or do both need to be same version which means same version vCenter?

Hello,

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

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

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

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

However, it hasn't gone away...

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

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

Thanks!

due to some reason , I have a abc-00002-delta.vmdk and no other files ( no VMX . no abc-0002-flat.vmdk)

is there any way to mount this vmdk in windows to recover files ？

or any way to mount this vmdk in vsphere ？

I tried to create a new VM and attach the vmdk , there is a error messages

"cannot open the disk '*.vmdk' or one of the snapshot disk is depends on"

Is there a way to see what the status of each running job in VDP is? I know you can see percent complete of the overall job but is there a way to see which machine is being backed up, which have already been backed up and which proxy it is currently using?

I have 6 jobs that back up about 100 virtual machines and the jobs just seem to sit at the same percentage for a long time. They also seem to take an incredibly long time to run.

Hello,

From few months, we're experiencing tragic VDP backup performance to our Synology NAS DS1513+ datastore (5x WD Black 2TB in RAID5) via iSCSI. From the time, nothing changed in our environment (except new NAS Synology DSM software updates).

We're backing up vCenter server (115GB) in 42 minutes, Windows Server 2012 (100GB) in 12 minutes, which is acceptable for us. We also have another W2012 server machine (file server) which is 900GB big (100GB system disk, 800GB data disk), which takes 9 to 11 hours! New bytes are around 0.3 to 0.5%... Previously it took about half this time to backup this VM.

We've checked our network, and from network side, everything it's fine. Our server has aggregated 8x 1Gbps links, Synology NAS has 2x 1Gbps links. The VDP appliance (6.1.2.19 version) - has 4 vCPUs (E5-2430) & 12 gigs of RAM, and it's not using max 30% CPU when backing up, and average 45% or RAM.

I've also tested the RAID5 performance (with DD) on our synology, and write performance is about 278MB/s, mdadm showed 291,7MB/s (disk read). I tried to do storage performance check via VDP (in vdp-configure panel), but it fails every time (exceeded allowed time to complete).

Probably I've exhausted all my ideas for now. Maybe it's VDP appliance fault (low performance)?

We had a failure overnight, I don't know what caused it but all hosts (9 in total) went into a half failed state in that they weren't responding in vCenter but could be pinged. I couldn't restart the management agent from the console so was forced to restart them via iLO.

Once I got all hosts back up, we've been left with one single datastore showing as "Inaccessible" and nothing I seem to do will kick it back into life. I'm not overfly familiar with the logs but it appears to be timing out

VMKernal.log

cpu38:68195)LVM: 15061: Failed to open device naa.600c0ff0001e3c7457b0c45a01000000:1 : Timeout

The Datastore is located on an HP MSA 2040, other volumes from said SAN that are mounted on various ESX hosts elsewhere or Hyper-V Servers have remained up so I know the SAN itself is OK.

I've rebooted all hosts in the cluster (one by one) just to be sure they came up cleanly

The iSCSI targets for this volume all seem to show Active but I did try to remove the targets and re-add them successfully

I had a spare server that I've built from scratch that once I added the iSCSI targets displayed the Datastore in the same Inaccessible state

Over the weekend one of our FreeNAS boxes locked up under heavy load.  I have everything running again except for vSphere Data Protection.  Whenever it begins a backup run it will create snapshots and then a few second later remove them and return the error "VDP: Failed to Attach Disk" in the Report window.  I've reviewed the logs, but they make no sense to me.  (I have attached one of them to this post.)

I have run an integrity check on the Data Protection server, all is well.  I have removed any old/outdated snapshots for the virtual machines.  I have rebooted the Data Protection server.  None of these steps have solved the issue.

I need someone more knowledgeable than me to look at the log file and give ma clue/solution to my problem.

Thanks in advance.

hi all,

I hope someone can help me by my problem, I have always gets these error when I want to take a Snapshot:

Another Task is already in Progress

When my Data recovery runs, I´ll get always these error:

7/3/2009 7:57:11 AM: Normal backup using Backup Job 1

7/3/2009 7:57:13 AM: Failed to create snapshot for ck1, error -3941 ( create snapshot failed)

7/3/2009 7:57:13 AM: Task incomplete

Thanks in advance best regards

andi

First attempt/test at backing up an Exchange server and in VDP reports it says its Success but in Task Failures it says 'VDP: An unexpected error occured with the following error code: 10020'.  I know that VDP doesnt supports guest-level backups of Microsoft Exchange/SQL Servers but that doesnt stop it from backing up the VM itself?  That is i wont be able to restore just Exchnage or SQL but I can restore the entire VM?  That being the case, is the error because of this lack of guest-level backup support?