Working with Resource Groups

PowerProtect Data Manager features a powerful access control mechanism which allows you to isolate users of the system to only have access to the assets they need to do their job. These are referred to as resource groups.

Resource groups are controlled from within the Administration > Access Control page of Data Manager, and you’ll start by making sure you have a user or group defined to apply a resource group against. In the example below, I’ve created a user called bob who has permissions as a Backup Administrator, Restore Administrator and a general view User:

PPDM UI showing the Administration: Access Control panel, on the User/Groups tab. There are two users defined on the system, the 'admin' user and a 'bob' user.
Administration > Access Control: bob user

Across on the Resource Groups tab, I’ve got a single resource group defined, which just so happens to be called Bob:

PPDM UI showing the Administration: Access Control panel on the Resource Groups. There is one resource group on the system, called 'Bob' showing 2 assets in it.
Administration > Access Control: Bob resource group

Let’s have a look at what’s defined in the Bob resource group by selecting it and clicking Edit. On my lab system I’ve got two asset types defined on the system: virtual machines and file systems. Two assets in the file system category have been assigned to the resource group, and no virtual machines:

PPDM resource group configuration page for the resource group 'Bob' showing that it has no virtual machines assigned to it and two filesystem assets assigned to it. There are options to view or edit the assets for file system.
Resource Group Bob Membership Overview

If I click View Assets, I can see which file system assets are assigned to the Bob resource group:

PPDM Resource Group View Assets showing two assets visible - E:\ and G:\ from a host called lv426.turbamentis.int.
Viewing the Assets in the Resource Group

If you need to modify the assets (or you’re creating the resource group in the first place), you can use the Edit link to assign ownership. This uses a wizard and I’ll step through the wizard pages below to let you see how that works:

Wizard for Resource Group Asset Selection. Page 1: Selection Method. This shows two methods available to select assets - by policy membership, or manually.
Resource Group Asset Selection – Selection Method Explanation

When you go to Select by Policy, you get a list of policies that are compatible with the workload selected. Since this is the file system workload I’m editing, I get to see file system policies. I can toggle on access for each policy, and I get an updated view of assets that will be included based on policy selection:

PPDM Resource Group Asset Editor showing Select by Policy with two out of three policies selected, each policy adding a single asset to the assets in the resource group.
Resource Group Asset Selection – Select by Policy

In addition to adding assets by policy, under Manual Selection I can optionally select additional assets to include. For me, the advantage of “Select by Policy” is that if your policy uses rules for asset inclusion, the resource group will be actively, automatically updated as matching assets for the rules are found. But, if you do need to manually add a few assets, this is where you can do it:

PPDM Resource Selection wizard showing the step for Manual Asset selection. No assets have been selected on this page.
Resource Asset Selection – Manual Selection

Finally, the summary tells me how many assets have been added through which method and optionally lets me see them:

PPDM Resource Group Asset Selection, Summary Page. Shows two assets added by policy, none manually.
Resource Asset Selection – Summary

Now, if I jump back across to the User/Groups tab and edit the bob user, I can see that for each of the roles bob has been assigned (Backup Administrator, Restore Administrator, and User), bob has been assigned the Bob resource group:

PPDM user editing wizard showing that the user bob has been assigned the 'Bob' resource group for each of its roles: Backup Administrator, Restore Administrator, User.
User Role/Resource Group assignment for the bob user

Now, how does this all work? Well, the net result of connecting the bob user to the Bob resource group is simple: bob will only get to see and interact with the assets that have been assigned. Compare for instance, the admin user view for Virtual Machines and File System assets:

  • Bob's view of the file system asset page, showing only two assets
  • Bob's view of the virtual machine asset page, showing zero assets
  • Admin user view of the file system  asset page, listing many assets
  • Admin user view of the virtual machine asset page, listing many assets

This visibility extends across Data Manager – for instance, if the bob user goes to Jobs > Asset Jobs, they only see asset jobs for the two assets they have visibility of:

PPDM Jobs > Assets page for the user bob showing only jobs related to the two file system assets that bob has access to
bob only gets to see the asset jobs for the assets bob has access to

And finally, not to belabour the point, since bob’s Restore Administrator role is tied to only those assets linked by the Bob resource group, bob can only run restores for those two assets:

PPDM restore page as viewed by bob. Only two assets are visible.
bob only gets to restore the assets that bob has access to

That’s a quick overview of Data Manager’s Resource Group function. It’s powerful, flexible and easy to setup, letting you limit user access to specific assets on the system – great for giving teams in your organisation control over and access to assets they need to protect and restore, while isolating visibility and access to other assets.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.