Managing protection sets

R‑Cloud by default creates a predefined protection set that is named default-protection-set and is represented by the icon. Depending on your business needs, you can do one of the following:

• Use only the default protection set to join your sources. In this case, all the sources that you add to R‑Cloud are by default included in this protection set.

• Create one or more additional protection sets and distribute your sources among them, having in mind that you must implement data protection for each protection set individually. By doing so, you define different scopes of data protection that best suit your needs and gain an at-a-glance view of the sources in each protection set.

Prerequisite

You must have the Administrator role assigned at the subscription level. For details, see Managing users.

Consideration

If you enable HYCU R-Cloud Hybrid Cloud Edition (HYCU) to forward data protection information to R‑Cloud, a new protection set is automatically associated with each HYCU backup controller. With these protection sets, only the dashboard and IAM panels are available. You cannot modify such protection sets. For details, see Viewing information about the HYCU R-Cloud Hybrid Cloud Edition environment.

Tasks

Depending on what you want to do, see one of the following:

I want to...	Instructions
Create a protection set.	Creating a protection set
Move one or more sources to a different protection set	Moving sources to a different protection set
Edit an existing protection set.	Editing a protection set
Delete a protection set that I no longer need.	Deleting a protection set

Creating a protection set

You can create additional protection sets that allow you to have a different data protection setup for different groups of sources.

Procedure

1. In the Protection Sets dialog box, click  Add.

2. Enter a name for your protection set and, optionally, its description.

3. Click Save.

The protection set is created and added to the list of protection sets.

Moving sources to a different protection set

Considerations

• If you move a source to a different protection set, consider the following:

  • Policies will be automatically unassigned from the entities in the source.
  • If you move an AWS account, an Azure resource group, or a Google Cloud project, the credential groups that were manually assigned to the instances in the source will be automatically unassigned from those instances.
• An AWS account cannot be moved to a different protection set if its default AWS IAM role is assigned to an existing target. To be able to move the AWS account to a different protection set, you must either delete the target or make sure that the target uses a different IAM role.

• For Google Cloud: As an alternative to moving projects by using the R‑Cloud web user interface, you can also move Google Cloud projects between protection sets by using a label. For instructions, see Adding or removing Google Cloud projects from a protection set by using a label.

Procedure

1. In the Protection Sets dialog box, click  Move Sources.
2. From the Protection Set drop-down menu, select the protection set from which you want to move a source to a different protection set.

3. From the list of sources that are included in the selected protection set, select one or more sources that you want to move to the destination protection set.

4. From the Destination Protection Set drop-down menu, select the protection set to which you want to move a source.

    Tip  When selecting the sources in the Protection Set and Destination Protection Set lists, you can filter the sources in the following ways:

   • By using the Search field. Typing text in this field automatically filters and displays only the matching items.

   • By using the filtering option:

     1. On the right side of the protection set list, click  Filters.

     2. In the filter box that opens, select your filter criteria.

     3. Click Apply Filters.

   By selecting the Source check box, you select all sources at once.

5. Click to move the selected sources to the destination protection set list. After a source appears in the destination protection set list, you can still exclude it from being moved. To do so, select the source, and then click .

6. Click Next.

7. Review the list of sources that will be moved to the destination protection set, and then click Save.

Adding or removing Google Cloud projects from a protection set by using a label

As an alternative to moving sources by using the R‑Cloud web user interface, you can also do the following:

• Move a project to a different protection set by attaching the hycu-protection-set label to the project in Google Cloud.

• Remove a project from a protection set and from R‑Cloud by attaching the hycu-project-exclude label to the project in Google Cloud.

Adding Google Cloud projects to a protection set by using a label

Prerequisite

The protection set to which you want to add the Google Cloud project must be created in R‑Cloud.

Procedure

In Google Cloud, attach the label to the project as the following key/value pair:

Key	Value
hycu-protection-set	<ProtectionSetName> In this case, <ProtectionSetName> is the name of the protection set to which you want to add the Google Cloud project.

For detailed instructions on how to manage labels, see Google Cloud documentation.

Removing Google Cloud projects from a protection set by using a label

Consideration

If after excluding a Google Cloud project from a protection set and R‑Cloud by using the hycu-project-exclude label, you need to add the same project to R‑Cloud again, contact HYCU Support.

Procedure

In Google Cloud, attach the label to the project as the following key/value pair:

Key	Value
hycu-project-exclude	true

After you attach the label to the Google Cloud project, the project is no longer included in the protection set and R‑Cloud no longer retrieves its information from Google Cloud.

For detailed instructions on how to manage labels, see Google Cloud documentation.

Editing a protection set

You can change the name or description of a protection set.

Procedure

1. In the Protection Sets dialog box, from the list of protection sets, select the one that you want to edit, and then click  Edit.

2. Edit the name of the protection set and its description.

3. Click Save.

Deleting a protection set

You can at any time delete a protection set that you no longer need.

Prerequisites

• The protection set that you want to delete must be empty with no included sources.

• The current data protection scope must be set to a protection set other than the protection set that you want to delete.

Consideration

The default protection set created by R‑Cloud cannot be deleted.

Procedure

1. In the Protection Sets dialog box, from the list of protection sets, select the one that you want to delete from R‑Cloud, and then click  Delete.

2. Click Delete to confirm that you want to delete the selected protection set.