Netbackup 6.5.1 and VMWare

[Mark_Casemore]

I have created a policy to backup our virtual servers (running on VMware ESX server v3). I have followed the document "how to configure and use NetBackup 6.5.1 for VMware". At the end it runs a validation on the new policy which fails with the following error message:


Policy: VCB-TEST -- client: L-curric-prt-01 --
Snapshot could not be created with VMware method

Policy: VCB-TEST -- client: l-admin-prt-02 --
Snapshot could not be created with VMware method

Policy: VCB-TEST -- client: d-admin-prt-01 --
Snapshot could not be created with VMware method

Policy: VCB-TEST -- client: d-curric-prt-02 --
Snapshot could not be created with VMware method

Anybody seen this error before, thanks.

[Andy_Welburn]

In the first instance I would check the logs on the NetBackup proxy server. It may be having issues connecting to the ESX or Virtual Centre Servers or they may indicate another issue.
Good starting point would be the bpVMutil & bpfis logs.

[Mark_Casemore]

Cheers for that, I looked at the bpfis log and found this:

12:14:47.707 [396.5196] <2> onlfi_vfms_logf: UNLOCK fd = 1624
12:14:47.707 [396.5196] <2> onlfi_vfms_logf: removing C:\Program Files\Veritas\NetBackup\VMcache_lock
12:14:47.707 [396.5196] <2> onlfi_vfms_logf: get_VM_names: release_id_lock returned 0
12:14:49.707 [396.5196] <4> delete_mount_point: Deleted mount point C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_ALL_LOCAL_DRIVES_396
12:14:49.707 [396.5196] <32> onlfi_freeze_fim_fs: VfMS error 11; see following messages:
12:14:49.707 [396.5196] <32> onlfi_freeze_fim_fs: Fatal method error was reported
12:14:49.707 [396.5196] <32> onlfi_freeze_fim_fs: vfm_freeze: method: VMware, type: FIM, function: VMware_freeze
12:14:49.707 [396.5196] <32> onlfi_freeze_fim_fs: VfMS method error 7; see following message:
12:14:49.707 [396.5196] <32> onlfi_freeze_fim_fs: VMware_freeze: Unable to locate VM l-curric-prt-01
12:14:49.707 [396.5196] <2> onlfi_freeze_fim: After freeze
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   f_type=0 (F_REG)
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fs_name=ALL_LOCAL_DRIVES
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fs_type=NTFS
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   mnt_device=ALL_LOCAL_DRIVES
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   raw_device=
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   volume_group=
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fi_fs_name=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_ALL_LOCAL_DRIVES_396
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fi_mnt_device=
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fi_raw_device=
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fi_args=mntpt=H:\VCBMNT,Virtual_machine_backup=2,APP_TYPE=FS,BACKUP_TIME=1200917679,POLICY_NAME=unknown,NBU_CLIENT=backup,VM_CLIENT=l-curric-prt-01,NBU_MASTER=backup,SCHED_NAME=unknown,SCHED_TYPE=unknown,POLICY_TYPE=29,PFI_BACKUP=0,NBU_CATALOG=0
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fi_handle=00000000
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   mnt_flag=0
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fi_flag=0
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   fm_flag=0
12:14:49.707 [396.5196] <2> log_fs_dev_rec:   cs_flag=0
12:14:49.707 [396.5196] <32> onlfi_verify: VfMS error 11; see following messages:
12:14:49.707 [396.5196] <32> onlfi_verify: Fatal method error was reported
12:14:49.707 [396.5196] <32> onlfi_verify: vfm_freeze: method: VMware, type: FIM, function: VMware_freeze
12:14:49.707 [396.5196] <32> onlfi_verify: VfMS method error 7; see following message:
12:14:49.707 [396.5196] <32> onlfi_verify: VMware_freeze: Unable to locate VM l-curric-prt-01
12:14:49.707 [396.5196] <2> onlfi_thaw: fim=auto
12:14:49.707 [396.5196] <2> onlfi_thaw: fim=VSS
12:14:49.707 [396.5196] <2> onlfi_thaw: fim=VSP
12:14:49.707 [396.5196] <2> onlfi_thaw: fim=VMware
12:14:49.707 [396.5196] <2> onlfi_thaw: fim=NAS_Snapshot
12:14:49.707 [396.5196] <2> onlfi_thaw: fim=VSS_Writer
12:14:49.707 [396.5196] <16> bpfis main: FTL - snapshot verify failed, status 156
12:14:49.707 [396.5196] <4> bpfis Exit: INF - EXIT STATUS 156: snapshot error encountered
12:14:49.707 [396.5196] <2> ol_cleanup: removing C:\Program Files\Veritas\NetBackup\temp\unknown+396+1.std_filelist
12:14:49.707 [396.5196] <2> online_util: release_id_lock:fis_id = 1200917679
12:14:49.707 [396.5196] <2> bpfis Exit: INF - Close of stdout complete

I think you are correct in saying its having issues connecting, I just need to find out why now.

[Mark_Casemore]

Mmmm, just looked all the way through the log, I only posted part of the log as you can imagine it's quite long.  Should I be worried about this?

12:14:42.113 [396.5196] <8> onlfi_initialize_vfms: vxvm_init: Veritas Volume Manager not installed.,

Many thanks

[Andy_Welburn]

I presume the logs you were investigating were on the NB Proxy server?
What is installed on this (with regards to NetBackup)?

[Just for completeness(?) our NB Proxy is also a media server and has the Admin Console installed - for reasons on this see previous discussions - & checking the services NetBackup Volume Manager is running!]

[ahlip]

Hi Mark,

If you are failing during the policy verification, then almost certainly you are missing some of the pre-requisites that needs to be in place. Note that the NetBackup VMware documentation, while good, does have some details missing. If you could send me a private message, I will be happy to attempt to assist you via email. Cheers.


regards,
Lipz

[ReneeC]

I am having the exact same issue and was wondering if you ever received a resolution?  I have the credentials set up for both the Virtual Infrastructure server as well as the ESX server and have validated the logins, yet I still get the error.  When I configure the policy and search for VM's, it doesn't find anything...and I have changed the VMware refresh timeout.

Just wondering what fixed it for you, if anything.  Thanks

[Mark_Casemore]

Silly question, how do I PM you???

[Mark_Casemore]

Ooops, found it, cheers

[JackWang]

almost same problems as mine. Please post what is your resolution. thanks,

[jpackett]

I also have same issue. Has there been resolution to this yet?

[mc1903]

Hi,

Could any of you please explain what licenses I need to get this up and running?

My customer already has a NBU 6.5 Enterprise Master Server & several Media Servers, now they wish to add another Media Server for the VMware VCB backup.

Do they just need the 1 x NBU 6.5 Enterprise Server and 1 x Enterprise Client License for Windows... or do they need a license for each ESX server (of which they will have 8, each with 4 DC CPU's)?

Additionally, the tape library they are connecting to is SAN attached - with 4 or 8 drives... Do they need additional licenses here?

Any help or pointers will be greatly appreciated...

Martin

[Stumpr2]

I noticed a new prompt when I called symantec support at 800-342-0652

There is a number to press for questions on licenses.

I haven't tried it but perhaps someone in the forum has.

hey, why not try it yourself and post your results?

please?

[ahlip]

NBU Media server serving as the VCB proxy server is still licensed as a Media server (or SAN Media) as per normal. If you wish to use NBU6.5.1 VMware VCB integration, then you need to license 1 x Enterprise Client per ESX that you are backing up. In your case, that would be 8 x Win Tier3 Ent Client lic.

For tape lib/drive use with NBU sharing among multiple backup servers, you will traditionally need to purchase NBU Lib tape drive options + NBU SSO lic (all per drive)

[Stumpr2]

LipZ,

Are you discouraging mc1903 from calling symantec?

Bob

[Mark_Casemore]

O.k.  Still working on this as there are still teething problems.  What I have found is there are "bugs" in VCB 1.1, I went back a version to 1.0.3 and it seemed to work.  I can now browse the virtual machines when creating the policy (used to receive either " Policy: VCB-TEST -- client: d-curric-prt-02 -- Snapshot could not be created with VMware method" when validating the policy or "file read failed" when browsing the clients), the error I am having now is with the snapshot provider, but I think this is another issue.  Any more findings and I will post them up.  Does someone now how to add an attachment to these posts as I would like to attach the call details I have, it may be of use to someone else for troubleshooting.

Many thanks.

[mc1903]

ahlip,

Many thanks for the info. It was the simple/straight forward answer was looking for... Cheers,

Martin

[Srikanth_Gubbal]

Hi,

guys this is the most hot topic being discussed in total backup..

i was trying this for the past 2 months, i got frustated and raised a call with symantec.

they concluded that "This issue was not encountered when using VMware Consolidated Backup 1.0.3 Update 1 - Build: 58377 So I would recommend using this version"

even after downgrading the VCB i got the same error... but i was able to probe ESX server, but not VC.

they asked me to check with VMware.

when i contacted VMware, they concluded 6.5.1 is not supported and reffered a doc..

http://www.vmware.com/pdf/vi35_backup_guide.pdf

as of now, i am struck and thought not to touch that for few days... let's wait for the best...

regards,

Srikanth.

[Mark_Casemore]

Ah, that sounds similiar to what happened to me, I had entered the credentials of both our ESX hosts and our Virtual Centre server, as soon as I took the ESX host credentials (wanted to use VC incase machines were moved to other ESX hosts) I could not browse the server, even though I'd left the VC server in.  As soon as I put the ESX hosts credentials back, hey presto, it started working again.  I would check what credentials you have entered.

[ahlip]

I have been using VCB build 58377 without issues, but my target was an ESX 302U1 (no VC) so may not have chance to get the problems that you guys encountered.