Skip to main content
Version: 2.9.0

Requirements and Prerequisites

Introduction

In this article, you'll find everything that you need to begin installation of Superna Disaster Recovery Edition (Superna DR). Be sure to review all of these prerequisites before continuing with any other related guide.

Release Compatibility

Powerscale OneFS Version

VersionFirst Supported Superna Release
8.2.x.y2.5.9.x or older
9.0.x.y2.5.9.x or older
9.1.x.y2.5.9.x or older
9.2.x.y2.5.9.x or older
9.3.x.y2.5.9.x or older
9.4.0.122.5.10
9.5.0.12.5.11
9.7.x.y2.8.3
9.8.0.02.9.0

DR Edition Feature Release Compatibility

Configuration Replication Non-DFS Mode
Source Cluster ReleaseTarget SyncIQ Cluster Release
8.2.x.x8.2.x.x**
9.09.0
9.19.1
9.29.2
9.39.3
9.49.4
9.59.5
Configuration Replication DFS Mode
Source Cluster ReleaseTarget SyncIQ Cluster Release
8.2.x.x8.2.x.x
9.09.0
9.19.1
9.29.2
9.39.3
9.49.4
9.59.5
SyncIQ Policy Failover Non-DFS Mode
Source Cluster ReleaseTarget SyncIQ Cluster Release
8.2.x.x8.2.x.x
9.09.0
9.19.1
9.29.2
9.39.3
9.49.4
9.59.5
SyncIQ Policy Failover DFS Mode
Source Cluster ReleaseTarget SyncIQ Cluster Release
8.2.x.x8.2.x.x
9.09.0
9.19.1
9.29.2
9.39.3
9.49.4
9.59.5
Access Zone Failover
Source Cluster ReleaseTarget SyncIQ Cluster Release
8.2.x.x8.2.x.x
9.09.0
9.19.1
9.29.2
9.39.3
9.49.4
9.59.5
Data Config Migration
Source Cluster ReleaseTarget SyncIQ Cluster Release
9.09.0
9.19.1
9.29.2
9.39.3
9.49.4
9.59.5
Live Ops DR Test Mode
Source Cluster ReleaseTarget SyncIQ Cluster Release
9.09.0
9.19.1
Feature Support Matrix
DescriptionSupported
Overlapping Access Zone with System (/ifs)Yes - Create / Update, No - Delete
Configuration Replication (non DFS mode)Yes - Create / Update, No - Delete
Configuration Replication (DFS mode)Yes - Create / Update, No - Delete
SyncIQ FailoverYes
SyncIQ Failover - DFS ModeYes
Access Zone FailoverNo
Overlapping Access Zone - non System ZonesYes - shares/export/alias, No - Access Zone
Runbook Robot Access Zone Multi clusterNo (only cluster pairs with no common cluster)
Failover with SyncIQ EncryptionYes (8.2 or later only)

System Requirements

Virtualization Platforms

  • VMware vSphere: Version 6.0 ESX host or higher is required.
  • Microsoft Hyper-V: Appliance deployment requires support for the VHDX format.

VMware vCenter Deployment

vCenter 7 and vCenter 8 are supported.

System Resources

  • CPU: 4 vCPUs
  • Memory: 16 GB RAM (Memory may need to be upgraded based on scalability requirements. Refer to the scalability table for more information.)
  • Disk Space:
    • Operating System Partition: 30 GB
    • Additional Disk Space: 80 GB
    • Total Disk Size in VMware: 110 GB

Network Requirements

  • Latency: The latency between the administration PC and the Eyeglass VM GUI must be less than 15 ms (measured by ping).

Authentication and User Management

  • Active Directory (AD) Authentication: An AD authentication provider must be available in the system zone for Role-Based Access Control (RBAC) and SID-to-user resolution API requirements.

Browser Requirements

  • Supported Browser: Google Chrome is required. The browser must support WebSockets.
  • Unsupported Browsers: Internet Explorer is not supported.
  • Cookie Settings: Third-party cookies must not be disabled, as they are required for authentication sessions and file downloads.

Ports Requirements

PortProtocolSource --> DestinationDescription
DNS 53 UDPDNSAppliance --> DNS server OR
Appliance --> GroupNet
(DNS configured on all clusters)
Functional DNS is a requirement for multiple validations needed for failover and Failover Readiness
TLS 443TCP TLS 1.2Appliance --> InternetDR Remote Monitoring or Phone Home remote log upload for support and health checks
NTP 123UDPAppliance --> NTP server in your environmentTime sync should use same NTP as the clusters. Always disable VMware host VM time sync option.
SMTP 25TCPAppliance --> Mail server in your environmentEmail of alarms from Eyeglass to your mail server
HTTP 80TCPAppliance --> Open Suse Mirror RepositoriesURL to allow security updates: Open Suse Download
Security patches come directly from Open Suse and requires the appliance to have access to download the patches and apply on a weekly schedule.
HTTPS 8080TCP TLS 1.2Appliance --> Isilon/Powerscale OneFS clusterREST API is authenticated using the service account created here. Authentication uses Isilon session authentication method.
SSH 22AESAppliance --> Isilon/Powerscale OneFS clusterSSH access for some CLI commands
HTTPS 443TCP TLS 1.2 AES - Unsigned certificateAdmin PC browser --> ApplianceSecures client to browser access
Target Port 80 --> Destination random TCP source port on the browserOnly used to redirect to 443, can be blocked if neededAdmin PC browser --> ApplianceIf connection on IP address port 80 is made, an HTTP 301, 302 redirect is returned on port 80 to switch the browser to https and url https:/x.x.x.x/eyeglass.

No services run on port 80 and this is only used to redirect to port 443 HTTPS.
HTTPS 2011 WebsocketTCP TLS 1.2 AESAdmin PC browser --> ApplianceWebsocket for real-time appliance to browser updates (redirected to 2012)
TLS 2012 WebsocketTCP TLS 1.2 AESAdmin PC browser --> ApplianceWebsocket for real-time appliance to browser updates (redirected to 2012)
SSH 22TCP AESAdmin PC browser --> ApplianceSecure shell access
Proxy login SMB 2 (only) 445TCPAppliance --> Isilon/Powerscale OneFSUsed to authenticate to AD through Isilon/Powerscale OneFS using standard Microsoft SMB authentication request for Role based login proxy interface
Dual DNS DelegationUDPAppliance Port 53 UDP DNS --> Groupnet(x) DNS serversNew in 2.5.6 or later, requires Eyeglass to be able to access the Groupnet DNS servers to validate Dual DNS delegation is configured correctly. The OS DNS is not used since the DNS that must be configured correctly is used by Isilon/Powerscale OneFS itself.
Internet Control Message ProtocolICMPAppliance --> Isilon/Powerscale OneFSIf for any reason ICMP is disabled, or PMTUD is not supported, this causes OneFS to default the MTU to 536 bytes, which typically leads to performance degradation.

Scalability Limits

Eyeglass Scalability Limits and Appliance Memory Minimum Requirements
Scaling Limit AreaTested Scaling LimitsNotes
Number of Managed Clusters (1 appliance)Manages up to 22 clustersContact Support for RAM requirements
SyncIQ Policies Across All ClustersSupports > 100 policies with 64 GB RAM Supports > 200 policies with 84 GB RAM
Access ZonesHandles > 10 zones with 32 GB RAM Handles > 30 zones with 64 GB RAM Handles > 50 zones with 84 GB RAMRequires 32 GB to 84 GB of RAM
Failover Job LimitationsSupports 100 policies in a single failoverRequires 64 GB RAM
Total Object Count (shares + exports + quotas)Handles < 5,000 objects with 16 GB RAM Handles 5,000 - 10,000 objects with 32 GB to 48 GB RAM Handles > 10,000 objects with 64 GB RAM Handles > 20,000 objects with 84 GB RAM
Clusters Added to the ApplianceSupports 4 clusters with 32 GB RAM Supports 4 - 8 clusters with 64 GB RAM Supports > 10 clusters with 84 GB RAM
Performance AuditorRequires a minimum of 32 GB RAM when the Performance Auditor is licensedMinimum 32 GB RAM
Concurrent Administrators (3 or more)Adds 8 GB RAM to the above requirements for each logged-in administrator using RBAC or not using RBAC
info

Each release of the software may adjust memory requirements, and the alarm code (SCA0094) will recommend memory for the supported configuration. The recommendation from Alarm Code SCA0094 takes priority over this documentation.

Next Steps

Now that you've got everything you need, you can go ahead and consult how to download the solution here: Download and Deploy