Do you have any reference to this problem in VmWare KB?

Lucky85 wrote: As far as I know NetWorker 8SP1 is not released yet, and even I have this version I was told to don’t install it on production environment.

Non sense... it is GA.  8.1 is something else, but SP1 is GA and current release is 8.0.1.3.

Hello,

we've got the same problem in a similar environment (nw version, esx version)..Have you find a solution for this problem?

thanks

Matteo

Hi,

We have networker server version 8.0.2.4 on Windows 2008 R2. VM Proxies using nsr 8.0.3.2 (windows 2008 R2 platform), vSphere client and server - 5.0, transport mode used ffor VADP backups - hotadd

NW148725 (VADP snapshots are not deleted after backup) was fixed in 8.0 SP2, though we keep getting the snapshot consolidation required on vSphere, did anybody face a similiar issue? to keep on deleting and consolidating the snapshots is another issue which sometimes requires disruption in service

VMware KB: Snapshot consolidation after backing up a virtual machine fails with the error: Failed to consolidate dis…  says that this issue is resolved in VDDK 5.0 U1, whereas nsr 8.0.2.4 uses VDDK 5.0 U2 (cumulative hotfixes) and still there is no respite with Consolidation issues, i am sure others must have also come across this.

Regards

tech88kur

Hi All,

I am also facing the same issues, in some of the VM, After backups getting completed the Snapshots are not getting deleted, so a manual disk consolidation is required, how ever in some VM,the VM file it self gets locked out and we need to Stop/restart out vpxe services(disruption in services, as per solution given by VMWare) in order to do the disk consolidation.

My Env is : 8.1.1.5.Build.306, VMWare V-Center version is 5.5.

We have another DC where we have about 60-70% of VMs having the disk consolidation issues, the env is :

NW Version: 8.1.1.2.Build.280

VShpere client 5.0.

any suggestions would be appreciated.

Hi Ram,

we have also faced the same issue that after completion or failure of VADP backups the snapshot consolidation were not happened. now all that problems are resolved by upgrading entire environment to the latest level.

The previous version of environment which we have faced this issue is.

networker---8.0

Vmware -- 4.5

UCS(blade server) 1.2d

After a long time research we have upgraded all to the latest as Networker to 8.1.1.7 and VMware to 5.5 and UCS to 2.2(2c).

Am suggesting you to upgrade the networker version and VMware version to the latest (Networker--8.2, Vmware--5.5) to resolve this issue.

Regards,

Vijeesh Thayyil

Hi Vijeesh,

May be i wil try to upgrade only the Proxy Storage node to NW 8.2 as Backup server is already NW 8.1.1.5.

Since its only Proxy SN who talks for the VADP Backups.

Today will give it a try.

Thanks

Ram

Hi all ,

I upgrade the networker proxy server to version 8.2 and have more issues with snapshot consolidation problem , the Customer have esxi 5.0. EMC support confirm that the issue will be resolve with the nex version and vddk 5.0u3.

This kind of issue intermittently happens.  VI guys used to have a script in the past to check any snapshot not clean up after VADP backup each day.   

Same issue here.  Upgraded to Networker 8.2.2 and 90% of my VMs need consolidation after backup.

Networker 8.2.2

VMWare vSphere 5.5.0 1993072

vCenter 5.5.0 build 2442329

Backup up to Data Domain OS: 5.4.4.2-453843 Model: DD860

Cisco UCS 2.2(3f)

I am using this powershell script until I can get everything to play nice.   It is a patch, not a fix.  EMC really needs to address this.

Connect-VIServer *Your VIServerName*

Get-VM | Where-Object {$_.Extensiondata.Runtime.ConsolidationNeeded} | ForEach-Object {   $_.ExtensionData.ConsolidateVMDisks() }

Additional information...  In order to run the script to consolidate the disks, I have to edit the EMC Networker Proxy virtual machines and remove the connections to the virtual disks of the servers it ran VADP backups on so it releases them and then the consolidation will run.... very tedious.

So we have Networker 8.2.2.0 Build 926 and we have the same problem.. I called support and suggested I increase the time out in every VMs VMX file.

We have vSphere 6.0 U1

As a work arround for the consolidation problem. we found out that networker appliances attach a snapshot of the affected machine to itself which locks that snapshot and as a result the consolidation fails because the disk is locked by another machine.

To solve this issue, the best way is detach the snapshot from the appliance (Remove it from the VM settings but don't delete it) and then you can go ahead and consolidate the machine...

I'm working on a way to automate this process and will share it soon.

Hi All,

Looks like we all have the same issue .. NW 9.0.1.7 and vSphere 5.5 .. we are having the same issue. we did the detaching one time with VMware support and that did solve at that time only but after two days we got the same issue. if there is an automation procedure please share as it seems the issue has nothing to do with the version at all and it a glitch in the VBA used by EMC, please correct me if am wrong!