Virtual SIRIS Deployment prerequisites

• Supported vSphere Versions: 6.0, 6.5, 6.7, 7.0, and 8.0.

• Supported vSphere License Versions: Free (with limitations), Essentials, Essentials Plus, Standard (with limitations), Enterprise and Enterprise Plus

• vSphere client required

• A minimum 1 Gigabit (GbE) network connection is required.

Disk storage space

• 60 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 in Tebibytes at least equal or greater than the product model that was purchased (SV3 = 3 Tebibytes (TiB) which would be 3.3 Terabytes (TB) rounded up)

• 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).

Limitations

• To ensure screenshots and local virtualizations can take place, a hypervisor connection on the ESXi host may need to be created. Virtualization on the virtual appliance will depend on the nesting virtualization capabilities of the underlying system and is unsupported. For more information on adding the hypervisor connection, refer to: Connecting a SIRIS to a VMware Hypervisor.

  NOTE  Virtualization via hypervisor is the recommended continuity option in the case of a Disaster Recovery for SIRIS virtual devices as nested virtualizations are untested and may provide unreliable results.

• 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
  • Virtualization
  • ESX upload

• Essentials/Essentials Plus and Standard versions

  • Advanced Verification/ Script Verification is not supported as these license versions do not permit the use of remote serial ports (vspc).

• Generation 2 hypervisor powered by:

  • Windows Server 2012 R2 and Hyper-V manager
  • Windows Server 2016 with Hyper-V Manager
  • Windows Server 2019 with Hyper-V Manager
  • Windows Server 2022 with Hyper-V Manager
  • Windows Server 2025 with Hyper-V Manager

• WinRM must be enabled to communicate with the SIRIS over the hypervisor connection.

• Ports 139, 445, 5985, 5986, and 3260 must be open.

• A minimum 1 Gigabit (GbE) network connection is required.

Disk storage space

• 60 GB of space for the SIRIS operating system VHDx

• Free space on the storage array in Tebibytes at least equal or greater than the product model that was purchased (SV3 = 3 Tebibytes (TiB) which would be 3.3 Terabytes (TB) rounded up).

Limitations

• Service Verification and Script Verification are incompatible with Virtual SIRIS on Hyper-V; they will not run even if configured to do so.

• To ensure screenshots and local virtualizations can take place, a hypervisor connection to the host may need to be created. Virtualization on the virtual appliance will depend on the nesting virtualization capabilities of the underlying system and is unsupported. For more information on adding the hypervisor connection, refer to: Connecting a SIRIS to a Hyper-V Hypervisor.

  NOTE  Virtualization via hypervisor is the recommended continuity option in the case of a Disaster Recovery for SIRIS virtual devices as nested virtualizations are untested and may provide unreliable results.