Video Screencast Help

BackupExec 2012 has started leaving entries in vCenter VPX_DISABLED_METHODS table

Created: 26 Mar 2013 | 10 comments

We recently installed two hot fixes on our BackupExec 2012 server (hotfix 200433 & Hotfix 201596) which backups up our VMware ESXi V4.1 U3 environment. Our vCenter server and ESXi hosts are fully up to date with V4.1 patches and BackupExec 2012 has all updates applied.

Now we're finding that storage vMotion is disabled on some of our VMs because VMs are being locked during SAN backups but are not always being unlocked at the end of the SAN backup. Entries appear in the vCenter control table VPX_DISABLED_METHODS and are not always being deleted.

Usually if I do another backup of the affected VM the entry is removed from VPS_DISABLED_METHODS then the backup completes.

Looking around the forums I see that BackupExec is not the only affected. The key thing here is that the problem only seems to have started after the hot fixes were applied.

 

Operating Systems:

Comments 10 CommentsJump to latest comment

Guy Dawson's picture

Yes, I've see that and related notes. They provide a work around after the problem has happened but don't stop it happening in the first place. At the moment each time I run backups (VADP via SAN) some of my VMs end up locked.

VJware's picture

afaik this affects other backup applications & VMware is still investigating this issue.

CraigV's picture

...have you checked the Known Issues section below to see if this problem is listed?

https://www-secure.symantec.com/connect/backup-and...

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Guy Dawson's picture

It's not listed there under BackupExec/Virtualisation or BackupExec/VMware. I'm now scanning all the reported issues.

Guy Dawson's picture

Looking back at the install dates for 200433 and 201596 I see that only 201596 was installed recently on the 13th Mar 2013. I'm going to uninstall it and see if we continue to have the problem.

CraigV's picture

Well, if uninstalling the patch works, then leave it as-is, and log a call if you have support with Symantec. If they're not aware of it (ie. it isn't on the Known Issues section!), then this is something they can work on.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Guy Dawson's picture

Hotfix 201596 has been uninstalled and I'll be testing now.

We have support and will open a case shortly. 

Guy Dawson's picture

I uninstalled the patch (hotfix 201596) yesterday and the over overnight VADP job ran sucessfully.

The overnight VADP job backups up 6 VMs via SAN to a SAS tape library.

Yesterday with the patch installed all the VMs were backed up but svMotion was disabled on one VM with an entry left in VPX_DISABLED_METHODS.

This morning with the patch uninstalled all the VMs were backed up and svMotion was enabled on all of them. The VM on which svMotion was disabled from the previous backup has had svMotion re-enabled during the VADP backup.

We're going to run with out the patch over the weekend (lots of VADP backups) and I'll report back on Tuesday of next week. I expect to be raising a support ticket.

Guy Dawson's picture

No joy. Weekend backups without the hotfix still left a good number of VMs with svMotion disabled. Now to open a support ticket.