VMware admins added disk space to guest - now snapshots are failing
Created: 13 Oct 2011 | 9 comments
Anybody run into this issue? Admins report they increased disk space on a guest on Oct 4th and from that point on that guest is failing backups with snapshot errors. They report latest VMware Tools is installed. Log for bpfis is reporting:
03:59:53.760 [3852.7012] <4> bpfis: INF - FIS_ID=boecatprod01_1318499990 03:59:53.760 [3852.7012] <4> bpfis: INF - Freezing ALL_LOCAL_DRIVES using snapshot method VMware. 03:59:53.760 [3852.7012] <4> bpfis: INF - ACT=boecatprod01 03:59:53.760 [3852.7012] <4> bpfis: INF - Created mount point E:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_ALL_LOCAL_DRIVES_3852 03:59:53.776 [3852.7012] <2> vnet_pbxConnect: pbxConnectEx Succeeded 03:59:53.776 [3852.7012] <2> logconnections: BPRD CONNECT FROM 169.143.75.159.63307 TO 169.143.74.127.1556 fd = 652 04:00:11.966 [3852.7012] <4> bpfis: INF - Deleted mount point E:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_ALL_LOCAL_DRIVES_3852 04:00:11.966 [3852.7012] <32> bpfis: FTL - VfMS error 11; see following messages: 04:00:11.966 [3852.7012] <32> bpfis: FTL - Fatal method error was reported 04:00:11.966 [3852.7012] <32> bpfis: FTL - vfm_freeze: method: VMware, type: FIM, function: VMware_freeze 04:00:11.966 [3852.7012] <32> bpfis: FTL - VfMS method error 7; see following message: 04:00:11.966 [3852.7012] <32> bpfis: FTL - VMware_freeze: VIXAPI freeze failed with 36 04:00:11.966 [3852.7012] <32> bpfis: FTL - VfMS error 11; see following messages: 04:00:11.966 [3852.7012] <32> bpfis: FTL - Fatal method error was reported 04:00:11.966 [3852.7012] <32> bpfis: FTL - vfm_freeze: method: VMware, type: FIM, function: VMware_freeze 04:00:11.966 [3852.7012] <32> bpfis: FTL - VfMS method error 7; see following message: 04:00:11.966 [3852.7012] <32> bpfis: FTL - VMware_freeze: VIXAPI freeze failed with 36 04:00:11.966 [3852.7012] <16> bpfis: FTL - snapshot creation failed, status 156 04:00:11.966 [3852.7012] <4> bpfis: INF - Thawing ALL_LOCAL_DRIVES using snapshot method VMware. 04:00:11.966 [3852.7012] <8> bpfis: WRN - ALL_LOCAL_DRIVES is not frozen 04:00:11.966 [3852.7012] <8> bpfis: WRN - snapshot delete returned status 20 04:00:12.060 [3852.7012] <4> bpfis: INF - EXIT STATUS 156: snapshot error encountered 04:00:16.178 [3500.512] <2> logparams: E:\Program Files\Veritas\NetBackup\bin\bpfis.exe delete -nbu -id boecatprod01_1318499990 -bpstart_to 300 -bpend_to 300 -clnt deninfrap8b.jeppesen.com -S oxfordc -noserverstate 04:00:16.178 [3500.512] <4> bpfis: INF - BACKUP START 3500 04:00:16.178 [3500.512] <32> bpfis: FTL - cannot open E:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.boecatprod01_1318499990.0 04:00:16.178 [3500.512] <4> bpfis: INF - EXIT STATUS 0: the requested operation was successfully completed
Discussion Filed Under:
Comments
What version of NBU? You need
What version of NBU?
You need the latest vmware rollup patch because growing the volume can cause backup issues aka data loss.
What does it say in the details of vsphere?
This seems to be a quiescing issue.
Nothing has changed...
NBU 7.1.0.1. Not sure about
NBU 7.1.0.1.
Not sure about the details in vSphere - will try to get the admins to collect the logs there. I agree that it appears to be a quiescing issue... and we've dealt with some of those in the past. I'm just wondering if there is a known issue with a guest whose disk has been grown.
Will provide more detail when I gather it. Thanks!
In your case it seems like a
In your case it seems like a quiescing issue, however a data loss situation does exist IF a NTFS volume has been grown.
Nothing has changed...
Thanks - do I need to open a
Thanks - do I need to open a case to get this "rollup patch"?
Open a ticket and via a
Open a ticket and via a private message send me the case number. I will call you as soon as I can.
Nothing has changed...
ElanMBX
is it Vstorage API ???
how many VM's affected with snapshot ??
If this post has helped you, please vote or mark as solution.
Before break-up, make sure you have a good backup..... ;-)
It is vStorage-API - and this
It is vStorage-API - and this seems to be the only guest with the issue.
Did you try taking a test snap on Guest machine ?
If so is that went fine ? If not try with and without quesing option ?
What does the OS on the guest machine ?
Thanks, Karthikeyan Sundaram.
Has the additional disk space
Has the additional disk space been used by the server?
Just wondering if it is still sitting there as partly unused space and casuing a confusion?
Try rescanning the disk on the client and them expanding the drive if it has not already been done.
How big is the drive now - there are limits for vShper backups.
Finally for no, in case it is just co-incidence, is this an App server (SQL / Exchange etc.)?
If so it may be that the databases have grown (hence needing the extra space) and vSphere cant quiece it any more - if that is the case you can disable the app quiece in the VMWare tools config on the client. There is a tech note which icant spot at the moment.
It amy also now be timning out so check out this one: http://www.symantec.com/docs/TECH141518
Authorised Symantec Consultant
Don't forget to give a "Thumbs Up" or mark as "Solution" if someones advice has helped you.
Would you like to reply?
Login or Register to post your comment.