10-29-2013 08:14 AM
Hi all,
This is the issue:
Netbackup servers 7.5.0.5 (Linux RH)
Netbackup backup hosts is a virtual Machine (Windows 2008 R2) running NBU 7.5.0.5 Client
Backups start and the VMDrives are mounted in the backup host (using hotadd), backup complete but all the Virtual Drives still mounted in the backup host.
the next day is the same issue, this is creating many snap shots of these VM in the storage.
Is there a solution to this?
We have opened a case with Symantec support but they can't find anything wrong in the log files.
any help will be appreciated.
Thanks
10-29-2013 10:52 AM
One possibility below. If that doesn't help I would contact VMWare Support.
http://www.vmware.com/support/developer/vddk/VDDK-1.2.1-Relnotes.html
- Mounting HotAdded disks may fail and not be cleaned up
In some cases, an attempt to mount a HotAdded disk fails. In such cases, directories can be created but are not removed by the standard cleanup process. To resolve this issue, manually remove the disks from the proxy virtual machine and delete the \tmp\vmware directory created in the current user's Documents and Settings directory, typically found at C:\Documents and Settings\username\Local Settings\Temp\vmware-username\. The next time a snapshot is created or deleted for the virtual machine, redo logs will get cleaned up.
10-29-2013 12:24 PM
Unfotunatelly that did not apply to my case, that directory/file doesn't exist in my WIndows 2008 backup host.
we have a case with VMWare but they are pointing a finger to Symantec, saying that Netbackup has a lock on the snapshot and they can't delete them.
10-29-2013 01:09 PM
During a virtual machine backup, VMware creates mount directories in the C:\Windows\Temp folder on the backup host. After the backup, VMware automatically removes the mount directories. In some cases, such as when the backup uses the hotadd transfer type, NetBackup may be unable to remove the mount directories.
Remove the mount directories from the \Temp folder and retry the backup. The folder name contains a string such as VMware-System.
11-01-2013 06:44 AM
Thanks sri vani
unfortunatelly this did not resolved the issue.
we are working with Vmware and Symantec to find a resolution, we have stopped all backups bacause this is causing a lot critical issues in the Vsphera storage.
11-02-2013 12:32 PM
Evargas, Plz do share with us once it gt fixed
11-02-2013 01:03 PM
hi,
what the Vcenter version?
does the VM using the application-based snapshots or file system quiesced snapshots.
if it using the application-based snapshots, try to disable it and use the file system quiesced snapshots.
this modification requires to change in VMX file and need a reboot of the server...
11-04-2013 04:27 AM
We still working on this, VMware suggested the below resolution wich we are doing at this time.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2017072
Nagalla,
vcenter version is 4.1.0
We are not using Application-base snapshoots
11-04-2013 08:38 AM
i was just going thourgh this doc and thoght of sharing.. please check if your setup is honored all the below requirements and limitations
Page number 35 from the netbackup VMware admin guide.
Notes on the hotadd transport mode
11-04-2013 09:13 AM
Nagalla,
our VMWare setup complies with all the requirements, we have been successfully backing up this environment for a while. we are investigating what changed a month ago which is when we started having this issue.