This update is for HYPER Core G4, HYPER Edge G2, HYPER Echo G1 and HYPER Echo G2.
Upgrading to this release will not require a reboot if the system is running on 5.3.x version branch.
Reboot is required when upgrading from 5.2.1 and older versions.
Introduction
This update focuses on improvements in reliability and transparency of Replication and Granular File Recovery. It also adds UI fixes and improvements.
Key fixes
Source and Destination Desynchronization
We have fixed the well known issue that sometimes caused the source and destination to become desynchronized. This problem occurred due to complex interactions between protection schedules and replication processes. The issue arose from a timing mismatch between replication and protection cycles. When a long replication overlapped with a new protection cycle, it caused retention rules to be incorrectly applied on the destination. This led the destination to mistakenly delete recovery points, resulting in the source and destination becoming out of sync. Now, retention rules are handled more robustly, ensuring that recovery points are maintained correctly on both source and destination no matter how long the replication takes.
Replications failing due to "Init Ingest Replication Failed"
When multiple replications were running in parallel and replicating to the same replication target, if they tried to authenticate at the same time, this error was raised. Understating the reason for failure made us address this forever and fix it by implementing a more efficient authentication process to handle multiple concurrent replications.
Key improvements
Making replication process more transparent
One of the complaints we addressed is the replications were not transparent enough to understand what the system is working on. So to make this more transparent, we enhanced the replication tasks with subtasks. These are explaining each step like retrying and waiting times between attempts in case something goes wrong during a replication. Also we added history for recovery points on replicas.
Resolved Issues
Replication
Fixed an issue that might cause a second replication of a VM to start while the first one hasn't finished yet.
Fixed an issue that might cause replication to fail if 4+ replication schedules are in place simultaneously.
Fixed an issue that could result in replicated RPs not being visible in the UI after replica deletion and manual replication using CLI.
Fixed an issue causing the 'Recover VM to replication target' feature not to work.
Fixed an issue that resulted in successfully finished Replicas not visible on the target system.
Fixed a issue causing a failure when copying to New Virtual Machine from Replica.
Improved the replication process transparency by introducing subtasks.
Improved the replication observability by adding progress history to replicas.
Improved the replication user experience by advising the next actions when replication fails due to a desynchronization.
Security
Updated internal components to proactively patch vulnerabilities in the user authentication mechanisms.
Granular File Recovery
Fixed an issue that could cause Granular File Recovery to return an empty file under certain conditions.
Fixed an issue that prevented the users from creating an ISO image with files bigger than 4GB.
Fixed an issue that cause the recovered zip files to become empty after system reboot.
Added ability to delete recovery tasks that are no longer required.
Improved handling of large numbers of files (50000) in one .zip file.
Improved process for downloading large files.
Improved handling of multiple File Recovery mounts.
Web UI
Corrected the message UI displays if “Recover VM to replication target” is disabled.
Added the ability to filter by Replications to the Tasks Page.
Corrected button name for “attach ISO”
Improved data validation for Replication target address fields.
Added the replication target information to the Replication job descriptions.
Added job descriptions for pending replications.
Fixed an issue that could cause the “Protect VM” modal window not to load
Fixed an issue causing a Replication Targets Page Error "An error occurred while loading the replication targets."
Fixed an issue which could result in Job progress showing up inconsistent in Job list vs Job view.
Fixed an issue causing the “Discard” button from recovery files menu to disappear.
Fixed an issue causing the checkboxes in "Protection & replication tasks" card to reset themselves.
Improved the display of Compliance rules section on non-standard window sizes.
Monitoring and Alerting
Removed false protection and replication failure reports for VMs that are not protected.
Improved display for failed replication events in the alert emails.
Known Issues
If there is no space on the storage pool, uploading a file to image repository will get stuck.
Replications can fail between 5.2.1 and 5.3.x.
If on boot SynetoOS can’t connect to scr.syneto.eu, the Syneto Web UI is blocked. Connection to syneto.eu is required for the Cloud Monitoring Service operation.
During granular file Recovery the UI may prevent removal of an ISO mount.
If storage space is insufficient, the UI may give a False positive when creating an ISO image for file recovery.
The 'ñ' Character in Recovery Files causes encoding issues.
The replica won’t get deleted if active file recovery mounts are tied to it.
Some isolated scenarios can result in 2 replication tasks running at the same time.
Ongoing Improvements and Future Releases
SynetoOS 5.3.3 continues the now established monthly release cadence of ongoing updates. Your feedback is extremely valuable to help us in our commitment to provide an excellent operating system. Please try out the new release and share your feedback and thoughts to help us shape SynetoOS's future features to bring the maximum value for you.