Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager 19.11 Virtual Machine User Guide

vSphere permissions to support discovery of distributed vCenter deployments

In a distributed vCenter deployment, such as one vCenter server with datacenters in multiple geographic locations, it is highly recommended to use permission-based discovery if a local PowerProtect Data Manager instance is protecting virtual machines in that location. The benefit of permission-based discovery is that, instead of discovering the entire vCenter, only a subset of virtual machines, hosts, and other related vSphere entities in the vCenter is discovered, which reduces the discovery time, latency impact, and chance of discovery failures.

The permission-based discovery requires a scoped vSphere service account, which is an account with privileges that are defined by PowerProtect Data Manager that are required for accessing local virtual machines, hosts, and other related vSphere entities. This account can be a new account, or you can use an existing account by adding permissions.

Once the account is created, you can apply the required permissions. The following example demonstrates the account permissions steps a user in location A is required to perform to protect virtual machines inside a container, such as a datacenter or a cluster:

  • Provide the account permissions to ancestor containers of the container, such as the vCenter and folders, with Propagate to children unselected.
  • Provide the account permissions to the container, with Propagate to children selected
  • Provide the account permissions to all vSphere entities that relate to the virtual machines in the container, such as folders, datastores, and networks, with Propagate to children selected

It is recommended to work with a virtual administrator within your organization to configure this service account so that the vSphere account added to PowerProtect Data Manager has its account permissions adjusted on the vCenter to resources that are mapped to the same site as the PowerProtect Data Manager instance.

NOTE When adding or configuring this user account, note the following:
  • Each vCenter Server can only be added once to each PowerProtect Data Manager instance. This behavior is common to PowerProtect Data Manager.
  • Setting up a user account with permissions to some remote virtual machines in addition to local ones, although possible, is not recommended.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\