Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.
Version: 2.15.0

Pre-Requisites for Data Orchestration for Dell

Introduction​

This page covers the platform compatibility, licensing, and infrastructure requirements to consider before deploying Data Orchestration.

Licensing​

Data Orchestration capabilities are enabled through the following license types:

LicenseEnables
Golden Copy Backup Bundle & Adv License and Pipeline License subscription, or Data Orchestration TB subscriptionSynced backup copies (single or versioned), one-time copy to long-term storage/archive, data shuffle workflows, and bi-directional hybrid cloud workflows (Pipeline, Cloud Browser for Data Mobility)
Archive Engine subscription licenseSelf-service, end-user data archiving portal and administrator age-based archive policies
note

Golden Copy Advanced or Backup Bundle licensing also increases the number of configurable recall targets to 5 (with a target selectable at recall time). The Golden Copy Basic license supports 1 recall target configured at a time.

Platform Compatibility​

Supported OneFS Releases​

  • OneFS 8.2.x
  • OneFS 9.1.x
  • OneFS 9.2.x
  • OneFS 9.3.x
  • OneFS 9.4 (via the February RUP, 9.4.0.12, or later)
  • OneFS 9.5.x (minimum 9.5.0.1)
info

Fast Incremental performance requires OneFS 8.2.1 or later, since the change list API on earlier releases does not include file metadata, requiring an additional file system query per file in the change list.

info

For the most current platform compatibility information, refer to the Platform Support page.

warning

OneFS 9.3 and later changed session authentication behavior in a way that is not backward compatible with the session handling Golden Copy and Search & Recover previously relied on, which can cause authentication sessions and PowerScale API calls to fail. If you are deploying against OneFS 9.3.x or later, extend the cluster's session timeout values (as root, on the source PowerScale cluster) before configuring folder definitions:

isi_gconfig -t web-config session_absolute_timeout=2160000
isi_gconfig -t web-config session_inactive_timeout=2160000

Supported Object Storage Targets​

Data Orchestration has been tested against the following S3-compatible object storage targets: Dell ECS, Dell ObjectScale, Amazon S3, Microsoft Azure Blob Storage, Google Cloud Storage, Cohesity, OpenIO, Ceph (version 15/Octopus or later), MinIO, Scality (open source), Wasabi, IBM Cloud Object Storage, BackBlaze S3, Cloudian, Pure Storage FlashBlade, Weka S3, Hitachi Vantara HCP CS, Quantum ActiveScale, Vast Data, and NetApp ONTAP.

note

Target support varies by feature (for example, versioning, checksum support, multipart upload/download, and advanced metadata). Review the vendor-specific notes in the Golden Copy Admin Guide's Limitations and Requirements chapter before selecting a target, and confirm rate limiting, billing, and quota behavior directly with the storage provider.

Browser Requirements​

  • Supported: Google Chrome, Microsoft Edge (Chromium-based).
  • Browser extensions/plugins that interfere with UI functions are not supported and must be disabled.

Infrastructure Requirements​

Golden Copy VM and Virtual Accelerator Nodes​

Data Orchestration deploys as one or more Golden Copy virtual machines:

  • The first VM acts as the control node.
  • Additional Virtual Accelerator Nodes (VANs) can be added to scale out copy throughput — a standard scale-out configuration is 6 VMs (1 control node plus 5 VAN nodes), and clusters can scale up to 99 nodes for high-throughput requirements.
  • All Golden Copy and VAN nodes require an NFS mount to the source PowerScale cluster.

Sizing depends on throughput requirements and file size profile:

  • Standard deployments should plan for adequate memory to support parallel copy threads; large-file-dominant file systems (files consistently over 64 MB) require additional VM memory to support multipart upload/download.
  • Disk latency (read and write) should be under 20 ms.
  • Additional disk space is required for each folder definition beyond a small number, to store per-folder copy history.

See the Design Guide for detailed scale-out and performance-tuning guidance.

Network Requirements​

  • SSH and HTTPS (port 8080) from Golden Copy/VAN nodes to the PowerScale IP pool in the system zone.
  • HTTPS (port 443) from Golden Copy/VAN nodes to the target S3 object storage endpoint.
  • NFS access from Golden Copy and Virtual Accelerator Nodes to the PowerScale system zone IP pool.
  • Golden Copy nodes connecting to S3 targets over the Internet (for example, AWS or Azure) require outbound NAT to the Internet.
  • Active Directory authentication must be configured on PowerScale to resolve UID/GID values on files.

Encryption​

  • In-flight: end-to-end TLS 1.3 encryption of data in transit.
  • At-rest: provided by the target cloud provider, typically using provider-managed keys as the default option.

See Also​

  • Concept – What Data Orchestration is and the terminology used throughout this documentation.
  • Design Guide – Architecture and performance planning for Golden Copy VMs and Virtual Accelerator Nodes.
  • Use Cases – Common scenarios for Data Orchestration.