Registering a Cloud SIRIS device for use with Datto Backup for Microsoft Azure

This article describes how to register your Datto Backup for Microsoft Azure device.

Environment

  • Datto Backup for Microsoft Azure

Description

Environment topology

Prerequisites

A Global Administrator account for the organization tenant and the owner of the subscription is required to complete this procedure.

Azure environment requirements

Before an Azure Cloud SIRIS can be registered, a basic Azure environment must be prepared, containing:

  • A tenant and subscription
  • An existing Microsoft Azure VM
  • A restore environment

Minimum required VM resources

  • Two virtual CPU cores
  • At least 2 GB of free RAM

Special considerations

  • Datto Backup for Microsoft Azure does not support restoration of files backed up to Azure File Sync.

  • A virtual machine 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 Backup for Microsoft Azure supports adding up to seven Protected Systems, with up to six TB of disk space between them.

  • 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 using Run Command (external link) fails with the error: 'RunCommandExtension failed with "'powershell' isn't recognized as an internal or external command,"', please review this troubleshooting article (external link).
  • 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++ 2017 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.
  • A device cannot be deployed to an Azure tenant that is already associated with an MSP. It would be associated if a device is already present in the tenant regardless if there are any agents associated with it. The existing device will need to be removed, and all associated agents as a result, before registering a new cloud SIRIS.

Registration

If you already have a subscription provisioned through a purchase with your account manager, follow the Register a device with an existing subscription process. If you need to purchase a new subscription during the registration of the new virtual SIRIS device, follow the Register a device and purchase a subscription process below.

Additional Resources