Modify settings for a cleanroom recovery group

Settings that you can modify for a recovery group include security and post-recovery validation.

For information about auto-scaling and cleanup, see the following: - Configure auto-scaling for your AWS recovery group - Configure auto-scaling for your Azure recovery group - Clean up recovered entities for cleanroom

Go to the recovery group

1. From the Command Center navigation pane, go to Cleanroom > Recovery groups.

2. Click the recovery group.

Configure security

You can associate users or groups with roles to determine which actions users can perform. You can also assign users or groups as owners that have management permissions for the entities in a recovery group.

You can use predefined roles, modify predefined roles, and create new roles.

1. On the Configuration tab, in the Security section, click the edit button.

2. To create a security association between a user or user group and the recovery group that allows you to perform data management operations, do the following:

   1. On the Associations tab, enter the name of the user or user group.

   2. From the Roles list, select the role to assign, and then click Add.

3. To specify who can access the recovery group, do the following:

   1. Click the Owners tab.

   2. Enter the name of the user or user group to assign as an owner.

   3. Click Add.

4. To specify permissions (such as add, edit, or delete) to owners of the recovery group, do the following:

   1. Click the Permissions tab.

   2. Select the permissions.

5. Click Save.

Modify the time delay between priorities

You can enable higher priority VMs/instances to start before processing the next set of machines.

1. On the Configuration tab, in the Customization options section, for Delay between priorities (in mins), click the edit button.

2. Enter the number minutes that you want recovery operations to wait between processing VMs that are assigned different priorities.

3. Click Submit.

Enable recovery operations to continue after failures

By default, when a VM/instance cannot be processed successfully, recovery operations stop. You can specify that recovery operations proceed to the next priority.

• On the Configuration tab, in the Customization options section, enable the Continue to next priority on failure toggle key.

Enable automatic post-recovery validation

You can specify that VMs/instances will be validated after they're recovered.

• On the Configuration tab, in the Validation options section, do the following:

  • To run a threat scan on all VMs/instances, enable the Run threat scan toggle key.

    The count of discovered threats is reset to 0 every 7 days.

    Threat scan requires auto-scaled access nodes. For information, see the following:

    • Configure auto-scaling for your AWS recovery group

    • Configure auto-scaling for your Azure recovery group

  • To run a Microsoft Windows Defender Antivirus scan on Windows VMs/instances, enable the Run Windows Defender toggle key.

Add post-recovery validation scripts

You can specify scripts to validate VMs/instances after they're recovered.

The following environments are supported:

• Windows: PowerShell

• Linux: Linux shell

• On the Configuration tab, in the Validation options section, click Add.

• To add a script, upload a file or enter a UNC path and credentials to access the path.

  UNC path examples:

  • Windows: Enter the UNC path as WindowsPathwin.ps1.

  • Unix: Enter the UNC path as \\Pathtofile\file.sh.

• Enter a descriptive name for the script.

• Click Save.

• To change the order scripts are executed in, click Reorder, and then drag and drop the scripts.

• Click Save.