Skip to main content

How to Deploy Specific Druva Phoenix VMware role

How to Deploy Specific Druva Phoenix VMware role

Updated yesterday

Overview

Configuration of the Druva Enterprise Workloads VMware role can be a time-consuming process. This procedure will assist in the automation of this deployment.

How to Install PowerCLI

  1. Check if PowerCLI is installed by running the following command

    1. Get-Module vmware* -ListAvailable

  2. If there is no output like shown below proceed to the next steps. If you have output proceed to the next section.

  3. Run the following command to install the module from the Powershell repository.

    1. Install-Module VMware.PowerCLI

  4. You may get prompted to update NuGet, and trust the repository. Both are normal and should be accepted. Below is an example of trusting the repository.

  5. The install should look similar to the following.

  6. Once installed proceed to the next section.

Note: It is sometimes necessary to install using the Allowclober switch.

Example: Install-Module VMware.PowerCLI -AllowClobber

How to connect to a vCenter/ESXi host

  1. Open a Windows Powershell window if not already open.

  2. Run the following command with the vCenter/ESXi name or IP address.

    1. Connect-VIServer <vCener/ESXi host>

  3. Input an administrative account when prompted, and click ‘OK’

  4. Now there should be a response similar to the screenshot below indicating a successful connection.

  5. Now proceed to the next section.

How to deploy the Druva Phoenix role

  1. Connect to the vCenter or ESXi host using the steps above.

  2. Run the following command to create the role:
    Note: Replace “Druva_Phoenix_Role” with the name of the role preferred for the environment.

New-VIRole -Name “Druva_Phoenix_Role” -Privilege (Get-VIPrivilege -Id Datastore.AllocateSpace,
Datastore.Browse,
Datastore.FileManagement,
Datastore.UpdateVirtualMachineFiles,
Global.DisableMethods,
Global.EnableMethods,
Global.Licenses,
Global.SetCustomField,
Global.ManageCustomFields,
Host.Config.Storage,
Network.Assign,
Resource.AssignVMToPool,
VirtualMachine.Inventory.Create,
VirtualMachine.Inventory.Register,
VirtualMachine.Inventory.Delete,
VirtualMachine.Inventory.Unregister,
VirtualMachine.Provisioning.DiskRandomAccess,
VirtualMachine.Provisioning.DiskRandomRead,
VirtualMachine.Provisioning.GetVmFiles,
VirtualMachine.Provisioning.Clone,
VirtualMachine.GuestOperations.Modify,
VirtualMachine.GuestOperations.Execute,
VirtualMachine.GuestOperations.Query,
VirtualMachine.Interact.DeviceConnection,
VirtualMachine.Interact.PowerOn,
VirtualMachine.Interact.PowerOff,
VirtualMachine.Config.AddExistingDisk,
VirtualMachine.Config.AddNewDisk,
VirtualMachine.Config.AddRemoveDevice,
VirtualMachine.Config.AdvancedConfig,
VirtualMachine.Config.Resource,
VirtualMachine.Config.ChangeTracking,
VirtualMachine.Config.DiskLease,
VirtualMachine.Config.RemoveDisk,
VirtualMachine.Config.RawDevice,
VirtualMachine.Config.Settings,
VirtualMachine.Config.CPUCount,
VirtualMachine.Config.Memory,
VirtualMachine.Config.UpgradeVirtualHardware,
VirtualMachine.State.CreateSnapshot,
VirtualMachine.State.RemoveSnapshot,
VirtualMachine.State.RevertToSnapshot,
Resource.ColdMigrate,
Resource.HotMigrate,
Cryptographer.Access,
vApp.Import)

How to update the Druva Phoenix role

  1. Connect to the vCenter or ESXi host using the steps above.

  2. Run the following command to create the role:
    Note: Replace “Druva_Phoenix_Role” with the name of the role in the environment.

Get-VIRole Druva_Phoenix_Role | Set-VIRole -AddPrivilege (Get-VIPrivilege -Id Datastore.AllocateSpace,
Datastore.Browse,
Datastore.FileManagement,
Datastore.UpdateVirtualMachineFiles,
Global.DisableMethods,
Global.EnableMethods,
Global.Licenses,
Global.SetCustomField,
Global.ManageCustomFields,
Host.Config.Storage,
Network.Assign,
Resource.AssignVMToPool,
VirtualMachine.Inventory.Create,
VirtualMachine.Inventory.Register,
VirtualMachine.Inventory.Delete,
VirtualMachine.Inventory.Unregister,
VirtualMachine.Provisioning.DiskRandomAccess,
VirtualMachine.Provisioning.DiskRandomRead,
VirtualMachine.Provisioning.GetVmFiles,
VirtualMachine.Provisioning.Clone,
VirtualMachine.GuestOperations.Modify,
VirtualMachine.GuestOperations.Execute,
VirtualMachine.GuestOperations.Query,
VirtualMachine.Interact.DeviceConnection,
VirtualMachine.Interact.PowerOn,
VirtualMachine.Interact.PowerOff,
VirtualMachine.Config.AddExistingDisk,
VirtualMachine.Config.AddNewDisk,
VirtualMachine.Config.AddRemoveDevice,
VirtualMachine.Config.AdvancedConfig,
VirtualMachine.Config.Resource,
VirtualMachine.Config.ChangeTracking,
VirtualMachine.Config.DiskLease,
VirtualMachine.Config.RemoveDisk,
VirtualMachine.Config.RawDevice,
VirtualMachine.Config.Settings,
VirtualMachine.Config.CPUCount,
VirtualMachine.Config.Memory,
VirtualMachine.Config.UpgradeVirtualHardware,
VirtualMachine.State.CreateSnapshot,
VirtualMachine.State.RemoveSnapshot,
VirtualMachine.State.RevertToSnapshot,
Resource.ColdMigrate,
Resource.HotMigrate,
Cryptographer.Access,
vApp.Import)

See also

Tags:

PowerCLI,VMware,Permissions,vCenter,ESXi, Role

Did this answer your question?