Creating a Protected Group

Prerequisites

• At least one production site has been created.
• Hosts or host groups and storage devices for host applications have been added to the production site.

Context

The protected objects belonging to one protected group reside on the same storage device. Each protected object occupies independent storage LUNs or volumes.

• If multiple applications are deployed on one remote replication primary LUN or consistency group primary LUN, ensure that all the applications belong to one protected group. If they belong to different protected groups, some applications may become unavailable during data synchronization, planned migration, or fault recovery of protected groups.
• If eReplication Agentless is reinstalled after it is uninstalled from a host, you need to create a protected group for the host after eReplication Agentless is installed.

Procedure

1. In the menu bar, choose Protection.
2. Click Create.
3. Select a protected object.
   1. Select Vastbase as the protected object type.
   2. Set Production Site and Production Host(Group) where the database to be protected resides.
   3. In the Available Database area, select the database clusters you want to protect.
   4. In the displayed Verification dialog box, enter the user name and password of the Vastbase cluster, and click OK.

      Wait until Verification Result of the selected database cluster is normal.

      If the verification fails due to misoperations, you can select the database cluster again and enter the verification information again.

      

      Only one database cluster can be selected for a protected group.

4. Click Next.
5. Set a protection policy.
   1. On the Protection Policy page, the system automatically matches supported protection policies. Select a protection policy based on your data protection solution.
   2. Click Set to set the protection policy for the protected group.
      • For the Vastbase x synchronous replication (SAN) protection policy, perform the following steps:
        1. In the Protection Policy area, click Set to set the protection policy for the protected group.
        2. Choose Replication Policy tab to set the remote replication rate between storage arrays. Table 1 lists the related parameters.
           

           Table 1 Replication policies

           Replication Policy	Description
           Default configuration	The remote replication rate is the default one set on the storage array.
           Manual configuration	Users can set the remote replication rate for each time segment. Configure the automatic remote replication rate of the storage based on the pre-set replication rate of time period. Select Manual configuration. Click a time color block to modify the replication rate during a time segment.

        3. Click OK.

6. Click Next.
7. Specify Name and Description of the protected group.
   • Name: contains 4 to 32 characters, including letters, digits, hyphens (-), and underscores (_), but cannot start with a hyphen (-).
   • Description: contains 0 to 255 characters.

8. (Optional) If you do not want to manually create a recovery plan for the protected group, select Automatically create a recovery plan after creating protected groups in the lower left corner.
9. Click Finish.
10. Click OK.

Related Operations

• If the protected objects of a protected group or their used storage devices change, on the menu bar, select Resources. Refresh resources or storage devices where the protected objects reside. Then go to the protection group page and refresh protected objects of the protection group by clicking More > Refresh. After the command for refreshing information is sent, you can view details about the command execution in Background Task.
  

  If a recovery plan is created for a protected group, the protected object can be refreshed only when the recovery plan status is Ready, Cleared, or Reprotected.

• Information about storage devices and hosts must be refreshed both at the production and DR ends where the protected group resides to ensure that information about the protected group is refreshed successfully.