VMware Snapshot create and delete are taking too long to complete

  • Article ID:100024755
  • Modified Date:
  • Product(s):

Problem

When performing vStorage backups of a large environment, the Snapshot process will take longer due to the amount of information that needs to be gathered from the environment.

Error Message

bpfis delay on ResetDatabases call:
10:57:25.829 [1748.6164] <2> onlfi_vfms_logf: INF - vmwareLogger: ResetDatabases: (1), m_VmListVersion=3
11:15:24.789 [1748.6164] <2> onlfi_vfms_logf: INF - vmwareLogger: RetrieveVimServiceContent: entered
11:15:24.851 [1748.6164] <2> onlfi_vfms_logf: INF - vmwareLogger: RetrieveVimServiceContent: OK

bpfis delay on releasing memory of the vSphere databases:
06:59:47.077 [6724.624] <2> onlfi_vfms_logf: INF - vSphere_freeze: blib = 0
07:00:43.864 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:01:44.706 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:02:45.549 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:03:46.392 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:04:47.235 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:05:48.077 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:06:48.920 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:07:49.763 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:08:50.605 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:09:51.448 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:10:52.291 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:11:53.134 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:12:53.976 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:13:54.819 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:14:55.662 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:15:56.505 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:16:57.347 [6724.6852] <2> send_keep_alive: INF - sending keep alive
07:17:38.252 [6724.624] <2> onlfi_vfms_logf: INF - dovSphereDisconnect: disconnect for virtualcenter01.symantec.com completed with flags 0 and status 0

Cause

This issue occurs because of the amount of information that needs to be gathered and released in a large vSphere environments.  Smaller environment will not see this issue occuring.

Solution

Create the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SymVmTools
Then create a new key as:
Name : SymVmToolsDisableRefresh
Type:  DWORD
Value: 1

The full key name would then be: HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\SymVmTools\SymVmToolsDisableRefresh

This setting does not apply to 7.6.x VMware Access Host, and should be removed if you are using NetBackup 7.6.

Verify the following file(s) on the VMware Backup Host are version 1.0.273.0 or higher as this version addresses an issue release information from memory:
installpath\VERITAS\NetBackup\bin\vmwaretools.dll
installpath\VERITAS\NetBackup\bin\nbuvmwaretools.dll

Veritas Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Veritas Corporation is committed to product quality and satisfied customers.
This issue is currently being considered by Veritas Corporation to be addressed in a forthcoming Maintenance Pack, Release Update, or version of the product.  Please note that Veritas Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Veritas's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.  Please refer to the maintenance pack readme or contact NetBackup Enterprise Support to confirm this issue (ET2341731) was included in the maintenance pack. 
As future maintenance packs and release updates are released, please visit the following link for download and readme information: 
 https://www.veritas.com/support/en_US/15143.html

 

Applies To

NetBackup 7.0.x and NetBackup 7.1

Was this content helpful?

Get Support