Ensure that you have the required system configuration and browser to deploy and run ECX.
ECX is installed as a virtual appliance. Before deploying to the host, ensure you have the following:
- The correct OVF template, which has an OVA extension, and is approximately 1.4 GB
- vSphere 5.1, 5.5, 6.0
, or 6.5
- Network information and VMware host information
- Either an available static IP address to use or access to DHCP
For initial deployment, configure your virtual appliance to meet the following recommended minimum requirements:
- 64-bit dual core machine
- 16 GB memory
The appliance has three virtual disks that total 400 GB storage:
- 50 GB for operating system and application, which includes 16 GB for the swap partition, 256 MB for the boot partition, and the remainder for the root partition
- 100 GB for configuration data related to jobs, events, and logs
- 250 GB for Inventory data
Users of DPX who are deploying ECX for the purpose of DPX Reporting should use the DPX Reporting (powered by ECX) OVF template. For DPX Reporting requirements, refer to the DPX Reporting Guide, which is available on the DPX product page of the Catalogic MySupport site along with the OVF template.
It is recommended that the ECX appliance, storage arrays, hypervisors and application servers in your environment use NTP. If the clocks on the various systems are significantly out of sync, you may experience errors during application registration, Inventory, Backup, or Restore jobs. For more information about identifying and resolving timer drift, see the following VMware knowledge base article: Time in virtual machine drifts due to hardware timer drift.
Run ECX from a computer that has access to the installed virtual appliance.
ECX was tested and certified against the following web browsers. Note that newer versions may be supported.
- Internet Explorer 11
- Microsoft Edge 20.10240
- Firefox 49.0
- Chrome 53.0.27
If your resolution is below 1024 x 768, some items may not fit on the window. Pop-up windows must be enabled in your browser to access the Help system and some ECX operations.
Application Server Requirements
- File System Requirements
- InterSystems Caché Requirements
- Oracle Requirements
- SAP HANA Requirements
- Microsoft SQL Server Requirements
- EMC Unity 300, 400, 500, 600 (All-Flash and Hybrid Flash)
- EMC UnityVSA
- EMC VNXe 1600 running software version 3.1.3 and later
- EMC VNXe 3200 running software version 3.1.1 and later
- IBM storage systems running IBM Spectrum™ Virtualize Software version 7.3 and later, including IBM SAN Volume Controller, IBM Storwize, and IBM FlashSystem V9000 systems
- IBM storage systems running IBM Spectrum Accelerate version 11.5.3 and later, including FlashSystem A9000/A9000R and IBM XIV storage systems
- IBM FlashCopy Manager systems running IBM Tivoli® Storage FlashCopy® Manager version 4.1.3 and later
Note: IBM providers must be registered by an IBM user with administrator-level privileges.
Any NetApp ONTAP storage system model running specifically listed Data ONTAP versions operating in 7-Mode is supported. The following versions of Data ONTAP are supported:
- Data ONTAP 8.1.0 and later operating in 7-Mode
- Data ONTAP 8.2.0 and later operating in 7-Mode
- Clustered Data ONTAP 8.1 and later
- Clustered Data ONTAP 8.2 and later
- Clustered Data ONTAP 8.3 and later
- Data ONTAP 9.x
- Note that ECX doesn’t support new features specifically introduced in ONTAP 9.x. ECX 2.5.1 was tested against Data ONTAP 9.1 RC1.
Clustered Data ONTAP providers must be registered with a cluster administrator account. Cluster peering must be enabled. Peer relationships enable communication between SVMs. See NetApp ONTAP's Cluster and Vserver Peering Express Guide.
Note: Ensure that TLS protocol is enabled on the NetApp storage system by setting the
tls.enable option to ON. For TLS to take effect on HTTPS, ensure that the
httpd.admin.ssl.enable option is also set to ON. See Enabling or disabling TLS on NetApp's Support site.
NetApp ONTAP File Inventory Job Requirements:
ECX uses SnapDiff in the NetApp ONTAP file level jobs to perform cataloging based on snapshot differences. SnapDiff cataloging is supported on storage system models running the following versions of Data ONTAP:
The following options must be enabled on the volume of the NetApp storage system to catalog:
- create_ucode and convert_ucode - These options are turned off by default.
See Related Topics.
- Inode to Pathname - The Inode to Pathname function creates relationships between file names and relative paths. If Inode to Pathname is disabled on a volume, you must enable it, then delete existing snapshots on the volume. When new snapshots are created with Inode to Pathname enabled, the volume can be cataloged.
- The language code must be set and the UTF-8 variant must be specified on the NetApp storage system. For example, en_US.UTF-8. Only the English locale for vol0 for UTF-8 is supported.
See Related Topics.
- The ECX application and documentation are available in English only. However, cataloging, searching, and reporting functions support international metadata.
Pure Storage Requirements
- Pure Storage FlashArray//m and FlashArray-4xx series
- Pure Storage REST API version 1.5 and later
- vSphere 5.1 and later
- vSphere 5.5 and later
- vSphere 6.0 and later
- vSphere 6.5 and later
Ensure the latest version of VMware Tools is installed in your environment. ECX was tested against VMware Tools 9.10.0.
Third Party License Requirements
For NetApp ONTAP storage systems, a FlexClone license is required to fully utilize Instant Disk Restore and Instant VM Restore features. SnapVault and SnapMirror licenses are also required on both source and destination resources if your workflow includes vault and mirror protection. Similarly, a SnapRestore license is required if your workflow includes individual file recovery. Note that individual file recovery is only supported at the primary site.
For IBM storage systems, Remote Mirroring and FlashCopy licenses are required.
For VMware, a Storage vMotion license is required. A Kroll license is required for individual mailbox recovery on a Microsoft Exchange VM protected by ECX.
Requirements for Installation of ECX through Docker
As an alternative to the VMware appliance deployment model, ECX can be deployed to Linux through Docker container technology. Docker is an open platform for distributed applications. A Docker-based installation requires the following:
- ECX license key
- Server with the following properties:
- O/S: Red Hat Linux 7.2 or later or Ubuntu 16.04 or later
- 350 GB of disk space available and mounted on the /data file system location
- Current version of Docker installed. Download Docker from the following location: https://docs.docker.com/engine/installation/linux/.
Catalogic ECX™ 2.6
© 2017 Catalogic Software, Inc. | All rights reserved.