Creating Service Profiles
A service profile provides a predefined set of default properties to use when VPGs are defined or edited. Zerto provides a default service profile and the option for the organization to specify their own requirements. The cloud service provider can define service profiles to manage specific service level agreements (SLAs) with its customers.
Cloud service providers can create different service profiles for different situations and can assign one of the service profiles to be the default, to be displayed when a VPG is created.
The Zerto Cloud Manager Service Profiles tab displays the defined service profiles. Zerto Cloud Manager includes a predefined service profile, the System Service Profile.
|
Note:
|
Specify in the Permissions tab for a ZORG whether or not the ZORG can set its own values for SLA properties when defining a VPG or whether it has to use a predefined service profile. For details, see Permissions Tab. |
To create a service profile:
|
1.
|
Select the Zerto Cloud Manager Service Profiles tab. |
The Add Service Profile dialog is displayed.
|
3.
|
Specify the name of the service profile. |
|
4.
|
The default is Disaster Recovery. |
|
5.
|
Select values for the service profile parameters. |
|
•
|
Target RPO Alert: The maximum desired time between each automatic checkpoint being written to the journal before an alert is issued. In reality checkpoints are written more frequently. |
|
•
|
Default Journal History: The length of time all write commands are saved in the journal. Each protected virtual machine has a dedicated journal volume on the recovery site associated with the replicated virtual machine. This enables journal data to be maintained, even when changing the recovery host for the recovery. When specifying a checkpoint to recover to, the checkpoint must still be in the journal. For example, if the value specified here is 24 hours then recovery can be specified to any checkpoint in the last 24 hours. After the time specified, the mirror virtual disk volumes maintained by the VRA are updated. |
When a VPG is tested, either during a failover test or before committing a Move or Failover operation, a scratch volume is created for each virtual machine being tested, with the same size as the journal for that virtual machine. The size of the scratch volume determines the length of time that you can test for. The larger the volume, the longer the testing can continue, assuming the same rate of change being tested. If the journal history required is small, for example two or three hours, the scratch volume that is created for testing will be small as well, limiting the time available for testing. Thus, when considering the journal history you should also consider the length of time you will want to test the VPG.
The longer the information is saved in the journal, the more space is required for each journal in the VPG.
|
•
|
Journal Size Hard Limit: The maximum size that the journal can grow, as a percentage of the virtual machine volume size. The minimum is journal size is 8GB. |
|
•
|
Journal Size Warning Threshold: The size of the journal that triggers a warning that the journal is nearing its hard limit, as a percentage of the virtual machine volume size. |
|
•
|
Test Frequency Reminder: The time recommended between testing the integrity of the VPG. A warning is issued if a test is not done within this time frame. |
|
•
|
Description: A description of the service profile. |
The new service profile is displayed.
|
7.
|
After adding a service profile you can edit it by selecting the service profile and clicking EDIT. |
|
8.
|
You specify a service profile as the default service profile to be displayed when creating a VPG by selecting the service profile and clicking SET AS DEFAULT. The default service profile is identified by the yellow star next to its name. |