VCB permission

[abaum]

All - I have had no problems using VCB for the past 8 months or so. I upgraded my VC to v2.5 last night and now my VCB backups fail. The error msg is:

Error: No permission to perform this action.

I have verified that the acct I am using can login to the hosts. It has the VCB user role in VirtualCenter. Where else can I check to see it has the appropriate permissions? And waht has changed in VC2.5 that would affect a direct backup bypassing VC?

My command line for VCBmounter references the ESX host, not my VC server.

adam

[abaum]

Here's more info. If I use the root acct, everything works. My acct and my backup acct are in the wheel group so I can't see where I am having permissions problems. Any ideas?

adam

[kjb007]

Have you checked the vmkernel and vmkwarning files?

Also, if your role is in vc, then maybe your role lost its permission set. Did you try and reapply that permission in vc?

-KjB

[dmn0211]

Could be the account permissions in Virtual Center have been reset. Would check the permissions listed below.

To create a VCB role

1 Log on to the VI Client as a user with Administrator privileges.

2 From the VI Client, click Administration in the navigation bar.

3 Click the Roles tab.

4 Click Add Role.

The Add Role dialog box appears.

5 Type a name for the new role, for example, VMware Consolidated Backup User.

6 Select the following privileges for the new role. Click the plus :smileyplus: signs to expand

the lists, as needed.

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

7 Click OK to complete the process.

[Guillir]

Abaum,

VCB role isn't a default role, so you or someone else have created that, right?

Roles created in VC are assigned to Windows accounts (AD domain or local VC server users).

You told you are not using VC, so you should use local ESX Server users (Service Console Users) to your backup job.

And the VCB role should be created at ESX Host, not VC, and assigned to an appropriate Service Console Users.

In this way, an VC upgrade wouldn't affect your backup job.

Where are created the VCB role (VC or ESX host)?

The minimum permissions you should include in VCB role are: (thanks Tropix

Virtual Machine > Configuration > Disk Lease

Virtual Machine > State > Create Snapshot

Virtual Machine > State > Remove Snapshot

Virtual Machine > Prosisioning > Allow Read-only Disk Access

Virtual Machine > Prosisioning > Allow Virtual Machine Download

Regards,

Guilherme Schäffer

Infiniit | www.infiniit.com.br

[abaum]

Guilherme, VCB is a role in the VC 2.x. I think 2.02 introduced it. The actual role name is "Vmware Consolidated Backup User". I thought i posted the solution to the problem, but I didn't. Turns out I was using an outdated VCB Framework. Once I upgraded it, the problem went away.

adam

[kjb007]

Don't forget to mark the question as answered and give points for helpful posts.

-KjB