Setup Automation Account: Runbooks and Hybrid Worker

Everpure Cloud Dedicated for Azure

Audience
Public
Source Type
Documentation

Create Automation Account

  1. In Azure Console, navigate to Automation Accounts and click +Create.

  2. For Region, select a different region than the main region, as the account can not reside within the same protected region.

  3. Under Managed Identities tab, select System assigned.

  4. From the Network tab, select Public.

  5. Last step is to Review + Create.

Create Runbook

  1. On the left panel of the created automation account, click Runbooks. Then create two runbooks with the following requirement: - Name: Runbook 1 for Recovery Plan Post Actions. Type: PowerShell. Version: 5.1. - Name: Runbook 2 for Everpure Cloud Dedicated Actions. Type: PowerShell. Version: 5.1.

  2. After the runbooks are created, access each runbook and click on Edit. Copy and paste the following scripts ASR-plan-actions-runbook, Everpure Cloud Dedicated-actions-runbook, to the runbooks, then click Publish.

  3. The Everpure Cloud Dedicated-actions-runbook will be visited in later steps to edit the variable section after configuring Everpure Cloud Dedicated replication.

Create Hybrid worker

For the requirement of hybrid worker, check Deploy an extension-based Hybrid Runbook Worker.

  1. On the left panel of the created automation account, click Hybrid worker groups.
  2. Select + Create hybrid worker group.
  3. From the Basics tab, in the Name text box, enter a name for your Hybrid worker group.
  4. For the Use run as credential. You can select No, and the hybrid extension will be installed using the local system. You can also select Yes, then you need to add a specific system credentials.
  5. Next, select Add machines to go to the Add machines as hybrid worker page. Select VM using checkbox, then click Add, and advance to the Review + Create.
    Note:

    The selected hybrid worker VM must have network access to the VNET where Everpure Cloud Dedicated resides. As a best practice, create a separate VNET (Connectivity and Tooling VNET as shown in the diagram in the section above) then use VNET peering to connect to both Everpure Cloud Dedicated VNET.