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

Release Notes for Data Orchestration for Dell

Introduction​

This page summarizes the release history for Data Orchestration (Superna Golden Copy), including the current release and prior releases with their notable new features, usability enhancements, and fixed issues. Review this page before installing or upgrading to confirm you understand what has changed.

info

Data Orchestration release numbering follows the underlying Golden Copy product versioning (for example, 1.2.2-25000). Build numbers appended after the version indicate the specific build within that release.

Current Release​

1.2.2-25000 (April 28, 2025)​

Usability Enhancement:

  • Ensured all licenses are successfully removed after executing an uninstall command on all licenses.

Fixed Issues:

  • Fixed an issue where SMTP notifications were not functioning.
  • Fixed an issue with a Redis class definition not found, which caused job failures when Redis is enabled.

Other:

  • Updated Java dependencies, cleaning up redundant imports on Java libraries.

Known Issues:

  • Some Grafana statistics may be missing after upgrading to 1.2.2-25000.
  • No error is shown for a non-existent subfolder in a recall operation.

Historical Releases​

1.2.1​

Usability Enhancements:

  • Added password authentication to the Redis server.
  • Added support for the incremental job to allow exclude/include flags.

PowerScale Version Support:

  • Added support for PowerScale v9.8.
  • Added support for PowerScale v9.9.

openSUSE Version Support:

  • Added support for openSUSE v15.6.

Fixed Issues:

  • Fixed the time format in the CLI command help text (DO-740).
  • Fixed an issue in the archivedfolders export command where an error is thrown when True and False are used with the errors-only flag (DO-741).
  • Fixed an issue where archived folders cannot be paused from the command line (DO-743).
  • Fixed an issue where Prometheus snapshots are not deleted after a backup is run (DO-838).
  • Fixed an issue where archived folders cannot be added without a pipeline license (DO-870).
  • Fixed an issue where the jobs view --follow option does not work with incremental jobs (DO-883).
  • Fixed a bug where adding archived folders fails with an error from the GUI (DO-905).
  • Fixed an issue where the archivedfolders --skip-s3-file-exists flag does not recognize boolean values (DO-909).

Updated Docker and Java Dependencies:

  • Updated all dependencies to up-to-date, stable versions (DO-205).

Statistics Fixes:

  • Fixed tree walk success and fail statistics (DO-794).
  • Fixed the audit job limiting files and sizes to 1000 files and 1000 KB (DO-779).
  • Fixed the missing RERUN statistics in the stats view (DO-763).
  • Fixed inaccurate statistics in pipeline recall for a large number of files (DO-790).
  • Fixed incorrect statistics on paused folders (DO-777).
  • Fixed a statistics issue where pipeline recall showed 0 recalled bytes (DO-782).
  • Fixed inaccurate audit job statistics (DO-768).
  • Fixed an inaccurate rerun job statistics issue (DO-749).
  • Fixed a hardlink statistics inconsistency issue (DO-773).
  • Fixed a hardlink issue when the --skip-s3-file-exists option is used (DO-786).

1.2.0​

SupernaOne Integration:

  • Added integration to SupernaOne, sending Data Orchestration metrics (bytes archived, files archived) and registering appliances to SupernaOne for dashboard visualization.

Feature Enhancements:

  • Added a new row in job statistics for hardlink recalls (total size of files accepted/recalled with hardlinks included, and non-hardlink sizes).
  • Added a new license view showing remaining capacity, with a green indicator when capacity remains, tracking regular license capacity limits.

Usability Enhancements:

  • Improved error messaging for unreachable PowerScale/Isilon clusters and suppressed no-impact errors on cluster startup.

  • Added searchctl settings config export / searchctl settings config importconfig for backup and restore of Data Orchestration settings, including admin lists and email notification settings (email channel passwords are encrypted in the backup).

  • Improved custom metadata size handling for AWS S3 and Azure targets.

  • Improved accuracy of network rate limiting.

  • Added support for special characters in folder names (DO-240).

  • Added dry-run buttons to the GUI (DO-236).

  • Added Azure Archive storage tier support (DO-319), an Azure archive-tier ignore check (DO-303), and an Azure Archive restore indicator (DO-310).

  • Added policy job statistics to the Active Jobs GUI (DO-340) and a GUI for policy creation (DO-339).

  • Added a policy path check with the smart-archiver-recall-folder flag (DO-341).

  • Added a check in the restore process to see whether data is already staged for recall (DO-307).

Cloud Browser for Data Mobility Feature Enhancements:

  • The archivedfolders list --verbose command now shows a new row for archive worker node information.
  • When running Cloud Browser for Data Mobility jobs, pipelines are selected round-robin. Busy pipelines that are next in rotation are now skipped if other pipelines have become free.
  • Added sorting by date and timestamp to Cloud Browser for Data Mobility tables.

Fixed Issues:

  • Fixed a bug where pipeline recall fails during a rerun job (DO-152).
  • Fixed a single node having errors about multiple ZooKeeper node errors (DO-156).
  • Fixed an issue where some job history is missing after upgrade (DO-59).
  • Fixed an issue where scheduled incremental jobs are cancelled until a full job is run (DO-53).
  • Fixed an issue where the trash-after-recall option does not move files to the recycle bucket (DO-161).
  • Fixed an issue where the log parser log shows duplicates in job history (DO-165).
  • Fixed a bug where files archived does not match files accepted in job statistics because of file renaming (DO-109).
  • Fixed missing statistics during archive jobs (DO-178).
  • Fixed a stalled job issue when processing a large number of files (DO-418).
  • Fixed a bug where files with special characters failed to upload for Azure jobs (DO-230).

Archive Engine Fixed Issues:

  • Fixed an issue to allow editing of GCS folders (DO-242).
  • Fixed an issue where the pipeline configuration wizard sometimes does not close after a folder is added (DO-511).
  • Fixed a bug where a cancelled dry run job causes Kafka topic lag and error messages that fill the indexworker log (DO-229).
  • Fixed an issue where setting --customMetaData to true causes an error in the archiveworker log (DO-233).
  • Fixed an Archive Engine configuration wizard UI issue when editing a GCS folder: when adding a recall folder, the folder ID field became empty and the Archive Engine Type changed to recall (DO-243).
  • Removed the tier field for ECS-type folders in the pipeline configuration (DO-237).
  • Fixed an issue where empty collision folders are created for GCS jobs (DO-238).
  • Fixed an issue where the policy file was lost during an archive job (DO-244).
  • Fixed a null exception when navigating to the Archive Engine or Cloud Browser for Data Mobility page (DO-231).
  • Fixed an issue where Archive Engine archive byte tracking files were not created, resulting in a License Manager container restart (DO-84).
  • Fixed an issue where the wrong methods were used for staging and recall (DO-239).
  • Fixed a UI issue where tables do not align properly (DO-234).
  • Fixed a job status issue where jobs display as success even though the job has the status "Needs attention" (DO-235).
  • Fixed an issue where Archive Engine folders cannot be updated when the folder type is recall.
  • Fixed a statistics issue with recall (DO-330).
  • Fixed an issue where the GUI does not show the error count for restore jobs (DO-329).
  • Fixed a bug where the audit job for a multipart file with a size under 1 GB hangs (DO-753).

Cloud Browser for Data Mobility Fixed Issues:

  • Fixed a bug where archivedfolders modify cannot modify the archiveworker-nodes property (DO-225).
  • Fixed a bug where Cloud Browser for Data Mobility jobs stall during copying (DO-223).
  • Fixed an issue where a Cloud Browser for Data Mobility folder cannot be updated from the GUI (DO-458).
  • Fixed a Cloud Browser for Data Mobility page UI issue where the table shows in the wrong region and does not align with the designed layout (DO-491).

1.1.21 (December 14, 2023)​

Usability Enhancements:

  • Job view now displays folders accepted, folders succeeded, and folders failed.

Feature Enhancements:

  • Job error and archive worker logs now include S3 request IDs.
  • Google Cloud Storage (GCS) support added for admin and non-admin users.
  • Improved job monitoring: the Active Copies GUI (per node/cluster) shows total files being copied, small/large file counts and percentages, total TB copied, and a file-size bucket breakdown.
  • Job view now shows changelist/layer processing details, including layer being processed, number of layers, layer size, files per layer, and total changelist files.

Cloud Browser for Data Mobility: Added round-robin distribution of archived folders across concurrent recall jobs, manual pinning of archived folders to specific archive worker resources, and changed SMB email-after-move behavior.

Fixed Issues: Multiple issues fixed, including a recall limitation for data uploaded to Azure prior to build 1.1.4-21050 (workaround: use native S3 tools for that data).

1.1.20 (October 5, 2023)​

Usability Enhancements:

  • Added a Cancel Job button.
  • Expanded job status to Success, Failure, and "Needs Attention" (with reasons such as high error rate, low error rate, or tree walk errors).
  • Added a disk space display script.

Feature Enhancements:

  • Incremental job logging now shows total files in the changelist.
  • Added an archive worker Redis cache.

Fixed Issues: Fixed a job failure on the snapshot extend step, fixed checksum settings reverting to the default (off) after upgrade, and fixed a recall gauge skip-counting issue.

Cloud Browser for Data Mobility: Highlighted folder icons in the path selector tree.

1.1.19-23189 (September 1, 2023)​

Usability Enhancements: Added backup notification and configuration settings.

Feature Enhancements:

  • Extended --follow to rerun jobs.
  • Made notifications list output chronological.
  • Added failed hardlink/softlink rerun jobs to the rerun topic.
  • Added the ARCHIVE_WORKER_RECALL_SKIP_EXISTENT_FILES flag for archive workers to skip files that already exist.

Cloud Browser for Data Mobility: Added multipart cross-region bucket-to-bucket staging copy (including copy-to-trash), overcoming the AWS 5 GB standard-copy limit.

1.1.17 (July 27, 2023)​

  • Multiple issues fixed, including an issue where a job running before an upgrade from 1.1.9 did not continue running after the upgrade (the job was not shown in running jobs or history, and files were not uploaded — verify job state after any upgrade from 1.1.9).
  • Cloud Browser for Data Mobility fix: a trailing slash in --recall-sourcepath could break recall.

1.1.16​

  • Fixed issues only; no new feature content documented for this release.

1.1.15 (May 3, 2023)​

  • Multiple issues fixed, including a backup-and-recover functionality issue where the system could not be fully recovered.

1.1.14 (April 4, 2023)​

New Features:

  • Version-Based Recall: Date-based recall is available in the GUI. During recall, users can enter a date and recall the version of the object most recently uploaded before the selected date.

Usability Enhancements:

  • Auto-retry of failed folders/files, spawning a new job at the end of an archive job.
  • Added a --folder-only option for reruns.
  • Added --follow support for archivedfolders recall.

Cloud Browser for Data Mobility: Support for moving data to a CBDM share, CSV export of a job's affected files, and a faster job history table using an in-memory cache.

1.1.13-23045 (March 6, 2023)​

  • Multiple issues fixed, including a workaround requiring a full archive to re-upload renamed files on a long path.

1.1.12 (February 3, 2023)​

  • Multiple issues fixed, including a job ID loss issue after upgrading to 1.1.11 (workaround: re-archive affected files after upgrade) and a multi-part recall size mismatch under investigation for a later release.

1.1.11 (September 27, 2022)​

New Features:

  • Improved tree walk robustness.
  • Auto-refresh added to the GUI.
  • Custom metadata extraction from files (for example, latitude/longitude from images, author from Word documents).
  • Full file/object transition history tracking.
  • Ability to download files from the Cloud Browser to the user's PC, including single-file download support for all file types from Google Cloud Storage.

Fixed Issues: Fixed a non-admin GUI restriction issue and inaccurate job views for large-file jobs.

Not Available in 1.1.11: Archive to AWS Snowball was not supported, and upload to Azure, Cohesity, ECS, or Ceph through a proxy was not supported.

Supported OneFS Releases​

The following OneFS releases were supported as of the versions documented above:

8.2.x.x
9.1.x.x
9.2.x.x
9.3.x.x
9.4 (minimum February RUP 9.4.0.12, released February 8, 2023)
9.5.x.x (minimum 9.5.0.1)

Supported S3 Storage Targets​

The following S3-compatible storage targets were supported as of the versions documented above:

Dell ECS 3.6, 3.7, 3.8
Amazon AWS S3 - all
Microsoft Azure Blob Storage - all
Google Cloud Storage - all
Cohesity - contact Support
Pure Storage FlashBlade - contact Support
MinIO - contact Support
Wasabi - all
Ceph version 15
note

Direct NAT (private-to-public IP) network connectivity to cloud storage is required. Proxy configurations to reach cloud storage targets are not currently supported.

Deprecation Notices​

  • The default upload tier for Azure targets is planned to change from Cold to Hot in a future release; tier-specific upload to Azure requires an Advanced license.
  • The HTML summary report generated by the export command is planned for deprecation, to be replaced by a downloadable job report from the Data Orchestration GUI.
  • The option to recall metadata only, or re-apply metadata to a previous recall job, has been removed. Run the recall job again if metadata needs to be re-applied.