Current Release - Release Notes - Golden Copy Archive Engine

Software Releases Publication

Current Release - Release Notes - Golden Copy Archive Engine

Home

Release Date	Version
04/02/2024	1.1.22-23290

What's New in Superna Archive Engine Release 1.1.22

New in Superna Archive Engine Release 1.1.21 (12/14/2023)

New in 1.1.21

Azure Deep Archive (Or Equivalent) Support

Restore from deep_archive skips now for existing files.

Dry run to calculate the amount of data to be archived before the job is run

The GUI enables users to initiate dry archive runs, giving them a preview of the potential impact of the archive job without actual execution.

Fixed in 1.1.21

SA-1567 Policy based archiving appends extra string to the Powerscale prefix inside bucket

Uploaded data key is incorrect due to issue that occurs when GCAE source path/policy path shares a common parent folder and is similarly named to GCAE upload folder’s path. For example, GCAE upload folder path = /ifs/data/folder & archive policy path = /ifs/data/folderPolicies.

SA-1554 Recall staging/restore from `DEEP_ARCHIVE` shows `0` stats, including with email

Recall staging/restore from DEEP_ARCHIVE shows 0 stats, including with email.

SA-1377 Not able to recall from deep_archive when Redis is set

Not able to recall from deep_archive when Redis is set

Workaround: add “export REDIS_PATH_CACHE_FOR_FILES=false” to /opt/superna/eca/eca-env-common.conf

SA-364 Unable to navigate to lower folders when recall folder is not configured

Both Archive Engine folders are required to be configured, or GUI has issues loading results for Active Directory users.

Workaround: Make sure both the staging folder and recall folder are configured.

SA-688 Cloud Browser - graphql error when browsing certain path - DataFetchingException Unclosed character class

Unable to browse AWS paths with certain (combination) of non-alphanumeric characters.

SA-361 Non-alphanumeric character support

test folder and file name with white space and special characters

SA-889 SA source paths should be allowed at the same path as a recall folder source path

The recall button should only allow actions on folders below the SA sourcepath and not the SA sourcepath itself.

Workaround: do not recall from the same level as the recall folder’s sourcepath

SA-1037 archivereport topic not created when running policy walk

When an archive job is run where a policy walk step is included, if the archivereport-<folder id> topic does not already exist, it will not be created until after the policy walk is done. The policy walk will succeed but it will take a very long time as each event waits for the archivereport event submission to time out.

Workaround: Any archived folder that has been given policies should at least begin an archive job before running an archive job with policies. This can be done by either running the archive job before adding the policies, or by pausing all the policies linked then running an archive job. After an archive job has been run, this issue will not occur as long as the topics aren’t deleted.

SA-1065 files not in the path listed in smartarchiver meta object are recalled and cleaned up from recall bucket

Users should not use GCAE staging bucket for non-GCAE data. These will be recalled and removed from the staging bucket during a GCAE recall

SA-1048 Archives only list paths for 1 folder when multiple upload folders are added to the same recall folder

Archives only list paths for 1 folder when multiple upload folders are added to the same recall folder

SA-1070 Blank screen when ‘Configured Only’ is selected

Blank screen when ‘Configured Only’ is selected

SA-1016 DEV: Active Jobs GUI to include policy job stats

Run archive job with SA policies enabled; Archive Running Jobs/ Archive History Jobs in Active Job currently does not include any policy-related stats.

p.s. Archived stats do include all archived folders and files.no

SA-1594 Azure restore indicator in Cloud Browser causes a blank screen

mouse pointer hoovers restore indication in CB, and the application goes blank
restore indicator for the restored AWS object is no longer showing restored status and also gives a blank screen when moving the mouse over it

SA-1659 Metadata error when customMetaData is set to true

Metadata error when customMetaData is set to true

SA-1664 Edit AE folders for GCS

Not able to add/edit Archive Engine folders for GCS storage using GUI

Workaround: use CLI for adding/editing Archive Engine folders for GCS storage

SA-1676 Remove tier for ECS folder in Pipeline config

The pipeline config wizard requires input for the tier field when editing the Archive Engine folder to ECS storage

Workaround: either use CLI for editing or enter a space for the tier field

SA-1677 The cancelled dry run job needs cleanup

Sometimes, a cancelled dry run job can still hinder the next archive/recall action.

Workaround: if errors persist in indexworker log, perform a cluster down/up.

SA-388 Not able to recall if SA archive bucket and recall bucket are in a different region

Archive Engine recall will fail if the main bucket and recall staging bucket are in different regions.

SA-385 add “GoldenCopy Pipeline Recall” job type in GUI

Unable to use the filter by job type for “GoldenCopy Pipeline Recall” job type.

SA-382 recall job creates report under full category

Archive Engine recall job report is generated under full instead of recall.

Workaround: Find Archive Engine recall job report under full.

SA-349 show all staged folders in 'Staged for Recall'

Having multiple Archive Engine configurations may make some objects staged for recall not show on UI. This has no effect on the recall process and is purely an issue with the display.

SA-324 wrong bucket name in pipeline recall error message

Error message for failed Archive Engine recall job shows main archive bucket name instead of recall staging bucket name.

SA-792 Recall from Azure archive storage

Recall from Azure Archive storage tier is not supported.

SA-1207 Fail to apply ACL to recalled file with UTF-8 character in the file name

Fail to apply ACL to recalled file with UTF-8 character in the file name

SA-566 Language-specific character is replaced with '?'

Language-specific character is replaced with '?'

SA-1637 Recall job shows inaccurate stats

Recall job shows inaccurate stats

SA-1639 No archiveengine object is created after the folder is staged for recall

No archiveengine object is created after the folder is staged for recall

SA-116 Clouds deep archive recall support

Archive Engine cannot recall on content with deep archive tiers.

SA-942 Pipeline Configuration wizard create folder fails

Pipeline Configuration wizard create folder fails

What’s New in Superna Archive Engine Release 1.1.20(10/05/2023)

New in 1.1.20

User Driven Archive and Recall notification email

The notification email addresses of users are gathered by capturing their email during the user’s first login.
Email notifications containing details regarding the outcome of the GCAE upload and recall jobs were added.

New configurations/environment variables in 1.1.20

docker-compose.yml

ERROR_RATE_THRESHOLD_PERCENTAGE
- Set in eca-env-common to override the default
- added to allow setting the threshold at which the error rate becomes high in the jobs view. 10% is the default - meaning <= 10 is considered ‘Low Error Rate’ and < 10 is considered
ECA_ENABLE_PATH_CACHE_ARCHIVEWORKER
- Set in eca-env-common to override the default and to ENABLE
- This allows caching finished work in archiveworker in order to avoid re-working uncommitted events in the case of an archiveworker restart

Fixed in 1.1.20

SA-1472 Unable to modify the recall schedule

Update recall folder schedule and get the error: Exception while fetching data (/updateArchivedFolder): No value present.

Workaround: Use GUI to edit folder recall schedule.

SA-1202 CB only lists folders for 1 cluster

CB only lists folders for 1 cluster

New in Superna Archive Engine Release 1.1.19(09.01.2023)

New in 1.1.19-23189

Dry Run functionality was added.

Fixed in 1.1.19-23189

SA-389 Plus sign-in path causes issues with SA archive

Having plus signs in either staging folder paths or Archive Engine source paths causes content to the archive with an incorrect key.

Workaround: Change names of paths not to include plus signs.

SA-1208 Staged For Recall inconsistent listing of folders

Staged For Recall inconsistent listing of folders

New in Superna Archive Engine Release 1.1.17 (07/27/2023)

Fixed in 1.1.17

SA-508 smart-archiver-sourcepaths parameter do not accept comma character

When the user tries to add different smart archiver sourcepaths with comma, the process to store them is separating that informed paths by comma character so, the configuration of that paths is wrong

New in Superna Archive Engine Release 1.1.16(06/07/2023)

Fixed in 1.1.16

SA-875 Isilon Management GUI incorrect display for licenses

Isilon Management GUI incorrect display for licenses

SA-365 Not able to recall if the upload bucket and recall bucket use different access credentials

Not able to recall if the upload bucket and recall bucket use different access credentials.

Workaround: None.

SA-946 archive folder path is not cleared after archived completed

After folder is successfully uploaded, the staging path is not cleared. all files are deleted but folders stay

SA-966 User can access share with Deny all permission

User can access share with Deny all permission

New in Superna Archive Engine Release 1.1.15 (05/03/2023)

Fixed in 1.1.15

SA-60 Archive job cannot finish when there is no data in staging area

archive job cannot finish when there is no data in staging area

SA-831 Error rerun pipeline recall job

error rerun pipeline recall job

SA-825 importconfig fails to restore SA folder

Import config failed for SA archive folder due to recall folder is not restored first

SA-658 Searchbar in SA and Cloud Browser page fails when "\" character is used instead of "/"

When searching a path on the Smart Archiver page or Cloud Browser page, The “/” and “\” characters should be both accepted and interpreted as “/” in either case, but when “\” is passed an error is thrown from the back end.

SA-325 not able to rerun failed pipeline recall job

Re-running failed Archive Engine recall staging jobs does not work.

Workaround: Run a new recall staging job to rerun.

SA-794 Fail to apply metadata error when subdir is skipped for recall

Fail to apply metadata error when subdir is skipped for recall.

What’s New! In Superna Archive Engine can be found here.

Supported OneFS releases

8.2.x.x

9.1.x.x

9.2.x.x

9.3.x.x

9.4 via the February RUP 9.4.0.12 (PSP-3079) released Feb 8th 2023

9.5.0.1

End of Life Notifications

End of Life Notifications for all products are available here.

Technical Advisories

Technical Advisories for all products are available here.

New in Superna Archive Engine Release 1.1.14 (04/04/2023)

Fixed in 1.1.14

SA-354 folder object is recalled when recall source path is at the same level

Archive folder and recall folder have sourcepath at the same level

SA-773 Restore Pipeline Recall job shows "Staged" twice

Pipeline recall from deep-archive, job view shows “Staged:”entry twice

SA-775 folder stats has wrong FULL/DEEP_RESTORED and FULL/DEEP_RESTORE_ACCEPTED

folder stats has wrong FULL/DEEP_RESTORED and FULL/DEEP_RESTORE_ACCEPTED

SA-848 Restore accepted stats not incrementing

The stats for when objects are accepted to be restore are not incrementing.

SA-246 AD user share paths listing graphql error

Giving access to an NFS share that is below the path of another share to a single user can cause errors while navigating the Archive Engine page.

Workaround: Give user access to only the highest of the paths.

Known Issues

Known Issues Recall

Known Limitations

SA-363 Safari support for single file download

Single file download is not supported on Safari.

Workaround: None.

SA-59 Archive folder to work with include/exclude options

archive folder to work with include/exclude options

SA-1404 GCAE with symlinks and hardlinks

Symlinks are not archived, hardlinks are treated as individual files.