Creating a data mover configuration

A data mover configuration allows you to define the location (compute and the networking details) for creating data movers. You must create a data mover configuration only if it is mandatory for the entities that you plan to protect, or if you do not want to use the default data mover location that is automatically defined by R‑Cloud. In addition, creating a data mover configuration is mandatory if your company security policies require it.

The data mover configuration must be assigned to the entities that you plan to protect. You can do this in one of the following ways:

• By specifying the configuration properties of the entities:

  Entity	Instructions
  SaaS applications	Specifying configuration properties for SaaS applications
  Applications	SAP HANA: Specifying configuration properties for SAP HANA application Google Kubernetes Engine: Specifying configuration properties for GKE applications SQL Server: Assigning a data mover configuration Db2: Assigning a data mover configuration
  Instances	Assigning a data mover configuration
  Buckets	Specifying configuration properties for buckets

• By setting up automatic assignment of the data mover configuration. For instructions, see Setting up automatic assignment of data mover configurations.

Prerequisite

The data movers must have access to the entities that you want to protect and to the targets that store the protected data. Depending on your data protection environment, assign the entity the data mover configuration that defines the appropriate networking parameters. You can check under which networking parameters the entity and the target are accessible in your cloud provider management console.

Limitation

You can only assign the application, the instance, or the bucket a data mover configuration that specifies creating the data mover on the same cloud platform.

Considerations

• Without creating and assigning your data mover configuration, data movers are automatically created at the following locations:

  • For SaaS applications:

    • If the SaaS applications run natively in AWS, Azure, or Google Cloud, data movers are created in the original SaaS instance location.

    • If the SaaS applications do not run natively in AWS, Azure, or Google Cloud, data movers are created in compute that is provided and managed by HYCU (HYCU Managed).

  • For instances, applications, and buckets: In the original source of the instance, the application, or the bucket.

• If you want that all the entities that belong to a source automatically use the same data mover configuration, you must enable the Use data mover configuration switch when adding the source to R‑Cloud. For instructions, see Adding sources.

• Only if you plan to keep the IP address of the data mover that uses an Azure resource group for compute private by leaving the Enable public IP switch disabled. Make sure that the created data mover can access the required resources during the data protection procedures.

• Only if you decide to set up labels for the data mover configurations.

  • Setting up labels enables you to automatically assign a data mover configuration to an entity. For instructions, see Setting up automatic assignment of data mover configurations.

  • Labels that you define for the data mover configurations will be applied to the created data movers to make them identifiable. For example, this helps you when granting specific permission sets to the data movers or when optimizing the cloud platform usage costs.

Recommendations

• You can optimize the egress data costs by making sure that the data movers use the same region as the target that stores the protected data.

• Using a specific data mover configuration with a source is recommended if the policies that you assign to its entities use targets that are only accessible from a private network.

Procedure

1. In the Data Movers dialog box, click  New.

2. Enter a name for the data mover configuration and, optionally, its description.

3. From the Protection Set drop-down menu, select the protection set in which you want to make the data mover configuration available.

4. From the Compute drop-down menu, select compute in which the data mover will be created. The available compute options include the computing resources that you added to R‑Cloud as compute or as sources.

5. Depending on the selected type of compute, specify the details for creating the data movers:

   Type of compute	Instructions
   Azure	From the Region drop-down menu, select the preferred region. From the Network Resource Group drop-down menu, select the preferred Azure network resource group. From the Network drop-down menu, select which network in the network resource group will be used. From the Subnet drop-down menu, select the preferred subnet.
   AWS	From the Region drop-down menu, select the preferred region. From the Zone drop-down menu, select the zone of the region which will be used. From the Subnet drop-down menu, select the preferred subnet. From the Security Groups drop-down menu, select the preferred security group.
   Google Cloud	From the Region drop-down menu, select the preferred region. From the Zone drop-down menu, select the zone of the region which will be used. From the Subnet drop-down menu, select the preferred subnet.

6. For Azure: If your network environment requires creating data movers in an Azure resource group with a public IP, use the Enable public IP switch.

7. Optional. Under Labels, define one or more labels for the data mover configuration.

   1. Click Manage.

   2. Enter a key and a value, and then click Add for each label that you want to add.

   3. Click Save.

8. Click Save.

The data mover configuration is added to the list of data mover configurations.

You can later do the following:

• Edit any of the data mover configurations (click  Edit and make the required modifications).

• Delete the data mover configurations that you do not need anymore (click  Delete). Keep in mind that the data mover configuration that you are deleting must not be assigned to any entity.