Registering a Cloud Siris device for use with Datto Continuity for Microsoft Azure
This article describes how to register your Datto Continuity for Microsoft Azure (DCMA) device.
- Datto Continuity for Microsoft Azure
DCMA does not support restoration of files backed up to Azure File Sync.
a VM configured with Storage Spaces will back up correctly, but restores will not preserve the Managed Disk topology – each volume in Windows will become a distinct new Managed Disk.
Datto Continuity for Microsoft Azure supports adding up to seven Protected Systems, with up to six TB of disk space between them.
Datto Continuity for Microsoft Azure does not support Azure Virtual Desktop at this time or Remote Desktop Services (RDS)
The VM must support the Azure runCommand extension.
If you receive the pairing error: 'Unable to validate the virtual machine, please try again later.' and a manual test of runCommand execution fails with the error: 'RunCommandExtension failed with "'powershell' isn't recognized as an internal or external command,"', please see this article for further troubleshooting information.
Azure Virtual Machine Agent
The Microsoft Azure VM agent must be present for the push install to function. If you are migrating existing VMs into Azure from on-prem,the Azure VM agent may not properly install. See Microsoft's Azure Virtual Machine Agent overview (external link) for more information.
For any error encountered during agent installation, check the Windows Event Logs for any corresponding events.
If Visual C++ 2015 runtime is not up to date or not installed properly, this could prevent an install. Make sure that your Visual C++ runtme is up-to-date and fully-installed.
If you see errors related to the C++ runtime, reinstall the latest Visual C++ update.
Figure 1: Datto Continuity for Microsoft Azure environment topology
Azure environment requirements
Before you can register your Azure Cloud SIRIS, you must prepare a basic Azure environment containing:
- A tenant and subscription
- An existing Microsoft Azure VM
- A restore environment
Minimum required VM specifications
- Two virtual CPU cores
- At least 2 GB of free RAM
You must be a Global Administrator and owner of the client tenant to complete this procedure.
Tenant and subscription setup
You will need elevated Azure permissions to set up your Microsoft Azure environment. You must be a Global Admin of the tenant, and the owner of the subscription.
No devices to register
If you have not yet purchased any devices, beginning this process will take you to the No Available inventory screen. Click the Cloud SIRIS button to begin the device purchase procedure in the Datto Store.
Figure 2: The No Inventory screen
Add the new Cloud SIRIS
1. In the Datto Partner Portal, click the Status tab, then select BCDR Status from the drop-down menu.
Figure 3: The Datto Partner Portal
2. Click the Add New button, then select New Cloud SIRIS from the drop-down menu.
Figure 4: The BCDR Status page
Add a new Cloud SIRIS from Inventory
1. In the Datto Partner Portal, click the Status tab, then select BCDR Status from the drop-down menu. Click Add New,→ New Cloud SIRIS.
Figure 5: Select New Cloud SIRIS
2. Click Add New → Inventory.
3. Click the subscription you wish to deploy for the client in question.
4. Start the deployment process. The commitment, retention, and discount terms will be locked in place.
Register the Cloud SIRIS
1. On the Register Cloud SIRIS screen, click Select or Create Client, then give the device a unique name,
2. Click the Connect to Client's Microsoft Azure Tenant button. By doing so, you authorize Datto to connect an enterprise service principal to the Microsoft Azure tenant containing your subscription.
Figure 7: Microsoft account selection
3. The system will prompt you to select your Microsoft Azure account and enter the appropriate credentials.
Figure 8: Microsoft account selection
The system will then connect your Datto Cloud SIRIS to your Microsoft Azure tenant.
4. Choose your client subscription from the Select Subscription drop-down menu, then click the Grant Access button.
5. In the Protect Virtual Machines section, select the Microsoft Azure region containing the applicable client subscription from the drop-down menu.
2. Use the check boxes to select which VMs to protect. When finished, click the Continue button.
Figure 9: Select region and VMs to protect
Configure your subscription
This stage of the registration process lets you configure your subscription based on your needs.
1. Select from the following service options:
What is your subscription type?: Datto Continuity for Microsoft Azure is currently offered on a per-VM basis or a Per-SIRIS basis that can manage disk capacity across a set of VMs. You can protect up to 6 TB of data across all VMs with this subscription.
What service tier would you like?: This option concerns the length of time that Datto retains your protected data. Chose from 1 year time-based retention, 7 year time-based retention, or Infinite cloud retention.
What commitment term do you prefer?: Choose a month-to month, 1 year, 2 year, or 3 year commitments.
How would you like to pay?: At this time, the only payment option is Monthly.
Figure 10: The subscription summary
After making your selections, the system will display your estimated monthly cost at the bottom of the screen. Click the drop-down arrow to see a summary of your purchase. Click the How Billing Works link to learn more about how Datto calculates your cost. After setting your subscription options and viewing your estimated billing information, click the Continue button
Figure 11: Estimated monthly cost
2. On the Review screen, you will see confirmation of the virtual machines you selected to protect. You will need to reboot your Microsoft Azure VMs before backups can begin. Check the Reboot VMs after installation box to perform the reboot now. If you prefer, you can leave this box unchecked and manually reboot the VMs at a later time.
Backups will not begin until you reboot the protected Microsoft Azure VMs.
Review and agree to the terms and conditions at the bottom of the Summary page, then click the Deploy Cloud SIRIS button to complete your registration.
Figure 12: Cloud SIRIS summary
Your newly registered Cloud SIRIS will appear on the BCDR Status page. Until the Cloud SIRIS deployment completes, it will display a status of Building.
Figure 13: The newly registered Cloud SIRIS on the BCDR Status page