What are the prerequisites for running Virtual SIRIS on VMware and Hyper-V?
- Virtual SIRIS
- VMware vSphere
This article lists the system prerequisites necessary to run a Virtual SIRIS on a VMware vSphere or Microsoft Hyper-V platform.
VMware vSphere Requirements
- Supported vSphere Versions: 5.5, 6.0, and 6.5
- Supported vSphere License Versions: Free, Essentials, Essentials Plus, Standard, Enterprise and Enterprise Plus
- You must use a vSphere client to deploy SIRIS.
- Datto does not currently support the deployment of virtual appliances to Microsoft Azure.
Free versions of vSphere do not support hypervisor connectivity to Virtual SIRIS products. As a result, the following features will not be available on a Virtual SIRIS deployed to a free vSphere environment:
- Adding hypervisor connections
- Agentless backups
- Screenshot verification
- ESX upload
Disk storage space
- 30 GB free space available on selected datastore for the operating system disk of the Virtual SIRIS to be thick provisioned (Eager Zeroed) during the OVA deployment
- Free space on a datastore equal to the product model that was purchased (SV3000 = 3 TB)
- Storage (VMDK) disk for Virtual SIRIS can either be thick provisioned (Eager Zeroed) or thick provisioned (Lazeily Zeroed) and attached to the Virtual SIRIS appliance after the OVA is deployed but before powering it on for the first time
Note: Thick provisioned (Eager Zero) disks may take a considerable amount of time to configure, depending on the size of the disk(s).
- Server 2012R2 or 2016 operating system with Hyper-V Manager installed
- 16 GB of RAM
- 4 CPU cores
- 1 TB or more for the storage array
- WinRM must be enabled to communicate with the SIRIS over the hypervisor connection.
- Ports 139, 445, 5985, 5986 and 3260 must be open.
Disk storage space
- 30 GB of space for the SIRIS operating system VHDx
- At least 1 TB for the storage array
- A minimum of 16 GB RAM and 4 CPU sockets (x1 cores) attached to the Virtual SIRIS.
- Larger deployments will necessitate additional CPU and RAM.
- Nested screenshot verification requires Hardware Assisted Virtualization exposed to the Virtual SIRIS and at least 3 GB RAM and 1 CPU added in advance to the Virtual SIRIS's VM specification.
Resources needed for Virtualization:
- Using ESXi virtualization for disaster recovery requires additional resources from vSphere. To prepare for emergencies, have enough resources to virtualize all of the protected systems. Keep in mind this requires space on the datastore configured for virtualization equal to roughly the amount of total memory given to VMs created via ESXi virtualization, due to the space needed for the vSwap files as well as other VM configuration files.
- Virtual SIRIS requires an iSCSI adapter on the ESXi host to be used for ESXi virtualization and screenshot verification. This iSCSI adapter must be accessible on the same subnet as the Virtual SIRIS. Click here for a quick video demonstration on how to configure this from vSphere.
- After you set up and register SIRIS, configure it for virtualization from the Virtualization Settings page on the web interface in order for ESXi virtualization and screenshot verification to function. For instructions, see the article Virtual SIRIS Local Virtualization.
Recommended CPU & RAM Allocations for Datto Virtual Appliances:
|Virtual SIRIS Model||CPU: Sockets x Cores||Recommended RAM|
|SV500||4 X 1||16 GB|
|SV1000||4 x 1||16 GB|
|SV2000||4 x 1||16 GB|
|SV3000||4 x 1||16 GB|
|SV4000||4 x 1||24 GB|
|SV6000||4 x 1||24 GB|
|SV10000||8 x 1||32 GB|
|SV12000||8 x 1||32 GB|
|SV18000||8 x 1||32 GB|
|SV24000||8 x 1||32 GB|
|SV36000||8 x 1||48 GB|
|SV50000||10 x 1||64 GB|
|SV60000||10 x 1||128 GB|