Virtual Machine is not visible in "Browse for Virtual Machine" in NetBackup 6.5.3 (Solaris) using VCB
Updated: 21 May 2010 | 7 comments
This issue has been solved. See solution.
Hi,
I am new to VCB.
Virtual Machine (host name of virtual machine) is not visible in "Browse for Virtual Machine" in NetBackup 6.5.3 (Solaris) while trying to add VM client in the policy. I am facing this problem with only one VM. Other VMs are working fine.
Details:
VMware ESX version: 3i, 3.5
VCB Version: 1.5.0.2192
Virtual Centre Service Version: 2.5
NetBackup Version of proxy server: 6.5.3 - Media Server
OS of proxy server: Windows Server 2008 Enterprise Edition SP1, 64 Bit
Master Server: Hosted on Solaris with 6.5.3 of version
Your help is truly appreciated.
Thanks
discussion Filed Under:
Comments
Troubleshooting VCB
• NetBackup GUI checks a file on the proxy for latest list of VM names in this directory:
Program Files\Veritas\NetBackup\online_util\fi_cntl\
• Furthermore run the VM locator utility direct from the proxy:-
Program Files (x86)\VMware\VMware Consolidated Backup Framework\vcbVmName.exe
vcbVmName searches for VMs visible to VCB proxy and obtain basic VM identification information
Useful for troubleshooting “VM not found” types of errors. It will report identification information about VMs, such as UUID and MOREF.
• create following directories for debugging the process/daemon logs:
Program Files\Veritas\NetBackup\logs\bpVMutil
Program Files\Veritas\NetBackup\logs\bpfis
Program Files\Veritas\NetBackup\logs\nbproxy
• Lastly is the datastore/LUN that this VM is located also accessible/presented to the proxy server.
If using a SAN you can also use the vcbSanDbg utility will show you identification information about all of the mass storage attached to the VCB
Proxy. It will indicate weather the disk contains a VMFS partition and will also report its UUID.
Also, does the VMware Credentials setup in NetBackup have permissions against the failing VM within your Virtual Infrastructure.
Use the VI Client and check permissions are the same for the working and the failing VM's returned within Browse Virtual Machines.
Consider the jump to 6.5.4 as there is a gamut of fixes and handful of improvements/enhancements that make NetBackup/VCB marriage less stressful.
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Hi, Thanks for your reply. I
Hi,
Thanks for your reply.
I just want to confirm one thing. I have forgot password of vcb user. If I change the password of vcbuser and update the same in cridential of netbackup will other backup be running without failure.
To run vcbVmName, I must have vcb user id and password.
Thanks.
Can someone reply on this,
Can someone reply on this, because I am really vew new to VCS.
As long as the vcbuser
As long as the vcbuser credentials match those on the virtualcenter server machine. You should be OK.
I have a local user account on the virtualcenter server called vcbuser
That accounts password also matches whats in the credentials on NetBackup
Set the account not to expire (of course)
You then give the vcbuser the permissions within the Virtual Infrastructure against your VM's
If you need assistance on that let me know. Particularly which permissions.
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Thanks for reply. In our
Thanks for reply. In our backup environment vcb user is already created in Active Diectory. So, I need to change the password in AD then in the credentials on NetBackup.
Appriciated if you can tell me the permissions. This would be for my future refrences.
Create a VCB User Create a
Create a VCB User
Create a VMBackup user account on the in Active Directory (preferred) or locally on the vCenter server.
Use the VCB Backup User Role in VC 2.5 or apply the following privileges:
- VirtualMachine > Configuration > Disk Lease
- VirtualMachine > State > Create Snapshot
- VirtualMachine > State > Remove Snapshot
- VirtualMachine > Provisioning > Allow Virtual Machine Download
- Virtual Machine > Provisioning > Allow Read‐only Disk Access
For Hot-Add mode, the following privileges will also be required:
- Datastore > Browse Datastore
- Virtual Machine > Configuration > Add Existing Disk
- Virtual Machine > Configuration > Remove Disk
- Virtual Machine > Configuration > Change Resource
-------------
Symantec Support gave these details when I had trouble attempting to restore a FullVM
Performing FullVM restoring these permissions are required
ESX/VC:
* Ensure that each username can login to all systems (you may want to create one admin account on all systems to simply the testing)
* Ensure the user has permission to create a VM on the target system
* Ensure the user has access to LUNs on the target system
* Ensure the user has write privilege on target system storage devices
* Verify that the user can create a new VM on each target system from VirtualCenter
Your Virtual Center user (if applicable) needs the following privileges:
* Allow ReadOnly
* Disk Access
* Allow Virtual
* Machine Files
* Download
* Inventory of VMs
The issue is most likely related to Permissions with ESX/VC.
References:
http://vmetc.com/2008/01/09/create-a-vcbuser-vcb-b...
http://viops.vmware.com/home/docs/DOC-1392
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Thanks for all your help.
Thanks for all your help. Problem is resolved now.
Would you like to reply?
Login or Register to post your comment.