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, 6.5, and 6.7
- Supported vSphere License Versions: Free, Essentials, Essentials Plus, Standard, Enterprise and Enterprise Plus
- vSphere client required
- Microsoft Azure not currently supported
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 open 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 (Lazy Zeroed) and attached to the Virtual SIRIS appliance after deploying the OVA 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).
- Generation 2 hypervisor powered by either:
- Windows Server 2012 R2 and Hyper-V manager
- Windows Server 2016 with Hyper-V Manager
- 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 is required.
- 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. You will need space on the datastore configured for virtualization roughly equal to the amount of total memory given to VMs created via ESXi virtualization, due to the space required for the vSwap files as well as other VM configuration files.
- To ensure you can take screenshots or bring up a VM, you must create a hypervisor connection on the ESXi or Hyper-V host.
- After you set up and register SIRIS, configure it for virtualization from the Virtualization Settings page on the web interface for ESXi virtualization and screenshot verification to function. For instructions, see the article Virtual SIRIS Local Virtualization.
- Service Verification and Script Verification are incompatible with Virtual SIRIS on Hyper-V; they will not run even if configured to do so.
Recommended CPU and RAM allocations for Datto virtual appliances
|Virtual SIRIS Model||CPU: Sockets x Cores||Recommended RAM|
|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|
- Connecting A SIRIS To An ESXi Host And Offloading A Virtualization To An ESXi Host
- Connecting A SIRIS To A Hyper-V Hypervisor / Virtualization Offload To A Hyper-V Host