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

Disclaimers for Data Orchestration for Dell

Introduction​

This page contains general disclaimers about the scope of this Data Orchestration (Golden Copy) documentation and known product and version limitations. It does not include the separate legal End User License Agreement (EULA), Support Services Agreement, or functional specification documentation that governs use of the product.

Documentation Scope​

This documentation covers the Golden Copy feature set as described in Superna's technical administration guides (overview, performance configuration, VM operations, and configuration steps). It does not reproduce entitlement, warranty, indemnification, or support-contract terms from the separate EULA and Support Services Agreement documentation.

note

A separate EULA and Support Services Agreement governs license entitlement, patching and appliance modification policy, installation responsibilities, and day-to-day operational obligations for Data Orchestration. Consult that agreement for support-contract and entitlement terms.

Licensing Dependencies​

Golden Copy functionality is gated by license key, and features described in this documentation set may not be available on every deployment:

  • The base Golden Copy license allows single-cluster recall of data (with or without metadata) to the source cluster.
  • The Golden Copy Advanced license (or Backup Bundle) is required for version-aware recall, redirected recall to an alternate cluster, storage-tier-aware recall, and object storage tiering.
  • The Pipeline license subscription (or Data Orchestration TB subscription) is required for bi-directional sync/move workflows between file systems and object storage, and for custom metadata extraction.
  • The Archive Engine license subscription is required for the end-user self-service archive/recall web portal and administrator-defined data-age archiving policies.
  • Once a license is assigned to a cluster, it is locked to that cluster; an unlock key must be purchased to reassign it.

Version Dependencies for Specific Features​

Several capabilities described in the source guides depend on a minimum Golden Copy build, OneFS/PowerScale release, or paired product version:

  • Fast Incremental performance (avoiding an extra per-file metadata query) requires OneFS 8.2.1 or later.
  • Config export/import and cluster rediscover (retaining clusters and folder definitions) require Golden Copy 1.1.9 or later.
  • High-performance recall tuning requires Golden Copy 1.1.17 or later and is documented specifically for AWS S3 targets.
  • Immutable Zero Trust Backup with Dell ECS Object Lock requires Dell ECS 3.6.2 or later, Golden Copy 1.1.6 or later with the Advanced license, and Ransomware Defender 2.5.8 or later.
  • Include/exclude glob filtering on folder definitions requires release 1.1.4 or later.

Confirm current release and licensing availability before relying on any specific feature or command in this documentation set.

Supported Cloud Storage Targets Vary by Provider​

Golden Copy supports multiple S3-compatible storage targets (Dell ECS, Amazon S3, Microsoft Azure Blob, Google Cloud Storage, and several third-party and on-premises S3-compatible targets), but feature support is not uniform across targets — for example, versioning, checksum validation, multipart upload/download, Object Lock, and load-balanced multi-node uploads are supported on some targets and not others. Customers are responsible for reviewing their chosen target's own rate limiting, billing model, and support terms directly with that storage provider. See References for target-specific configuration examples.

Known Product Limitations​

The following limitations are documented in the source technical guides and should be accounted for when planning a deployment:

  • Symlink files are skipped and are not copied; hardlink files are copied.
  • Alternate Data Stream (ADS) content is not copied with a file.
  • Empty directories (containing no files) are not represented in the object store.
  • A maximum of 80 folders can be run concurrently on an incremental-always schedule; exceeding this is not supported without offsetting folders across different schedule intervals.
  • Report generation for a single job is limited to 15 million success file entries unless additional disk space is added to extend this limit.
  • The CLI displays a maximum of 10 actively running jobs at a time; additional submitted jobs are queued and displayed as running once a slot frees up.
  • The largest tested single-file multipart upload is 1 TB; there is no architectural limit beyond the target's own maximum object size.
  • Thread count and parallel-copy performance settings should only be changed with Superna Support guidance, since increasing threads without addressing the actual bottleneck can reduce throughput rather than improve it.

Operational Responsibility​

Golden Copy job execution and outcomes (success, failure, retry) are visible through the job history and monitoring commands described in References. Regularly reviewing job logs and failures is a customer operational responsibility to ensure backup coverage is complete; the product does not automatically guarantee 100% data protection without active monitoring.

See Also​

  • Compliance Guide – Immutability, auditability, and RBAC posture.
  • References – CLI commands and target-specific configuration notes.