All News File Synchronisation, Publishing & Copying Miracle Service
Miracle Service Spring Sale 2019 for existing customers
12 Mar 2019
SureSync v8.0.25 released
8 Jun 2018
When restoring a file with ArchiveSync if there was a change in file attributes, such as the Read-Only attribute, the restore of the file would fail indicating that the source did not match the expected values. This has been fixed in 8.0.25.
The timeout in the Communications Agent has been increased from 5 minutes to 10 minutes to allow for very slow file system responses to requests. This has been fixed in 8.0.25.
In certain timing circumstances, a communications fault on the Communications Agent I/O service could go undetected until another I/O operation was attempted. This has been fixed in 8.0.25.
In rare timing circumstances in environments with frequent path losses and recoveries, it was possible for the Communications Agent to become 100% CPU bound and for files to then not be processed. This has been fixed in 8.0.25.
The e-mail alert send routines have been updated to support newer security protocols for sending e-mail via Internet mail servers such as Gmail where TLS/SSL is used. This has been fixed in 8.0.25.
When there was an error on a destination, it was possible for the source to also be flagged as being in error. This would result in an incorrect over reporting condition where the source was reported in the log along with the destination. This has been fixed in 8.0.25.
If a Job was configured to copy create dates, messages about being unable to determine the source for changed security values messages could occur in the log even though security copying was not enabled. This has been fixed in 8.0.25.
SureSync v8.0.24 released
24 Apr 2018
In rare timing circumstances, where dozens of path loss events were occurring in rapid succession, the was possible for orphaned file copies to not be released properly. This could eventually cause actions on the Job to stop or nearly so. This has been fixed in 8.0.24.
In rare instances, an I/O cancel request could make an agent become unresponsive. This has been fixed in 8.0.24.
Download the new version here
It is possible to run the HP3000 beyond 2027
10 Apr 2018
US based Beechglen has managed to extend the drop dead date built into the HP3000 MPE/iX operating system extending it to 2038
Read more from them here
SureSync v8.0.23 released
2 Apr 2018
A fix has been made to backup root purging. In certain circumstances, files might not be purged correctly. This has been fixed in 8.0.23.
In certain timing circumstances, a VSS open could take an unexpectedly long amount of time and lead to a timeout. This would result in "ServerA lost connection to ServerB” type message and an unnecessary path drop. This has been fixed in 8.0.23.
In a multi-way Rule with Advanced Open File Support (VSS) enabled, if you opened a file, made a change, and then copy/paste replaced the current file with an old version of the file while a VSS retry was pending, it was possible to have the newer version "win” and replace the old version. This is very timing and sequence specific. This has been fixed in 8.0.23.
The /E operand has been added to SyncCmd to allow for the testing of all Communications Agents connections stored in the SureSync database into a tab separated output file. Please see the help file for further details.
When using SQL authentication for the SureSync database, you would receive an authentication error launching the Log Viewer from Enterprise Status. This has been fixed in 8.0.23.
A small correction was made to the licensing display. This has been fixed in 8.0.23.
The Telerik controls have been updated. This has been fixed in 8.0.23.
Download the new version here
SureSync v8.0.20 released
23 Aug 2017
When using the alternate locking method, it was possible for a file rename to produce a loop and not be processed corrected. This has been fixed in 8.0.19.
If running a Trial Run on a Job, it was possible to receive System.NullReferenceException and System.InvalidOperationException errors when a backup root thinning operation interfered with normal processing. This has been fixed in 8.0.19.
Corrections and optimizations have been made to the process of automatically purging job log records from the database. This has been fixed in 8.0.19.
A "System.IndexOutOfRange” error could occur which would cancel a Real-Time Monitor or Schedule. This would occur because of a bad retry record. This has been fixed in 8.0.19.
If a large number of open file retries were queued, it was possible for Change Journal event processing to slow down which would cause change events to not be immediately recognized. This has been fixed in 8.0.19.
FTP controls have been updated to the latest version. This has been fixed in 8.0.19.
Corrections have been made to Status Web to address page loads where an icon might be missing. This has been fixed in 8.0.19.
Status Web has been significantly enhanced to include a new login panel, the ability to view Log records and the ability to process alerts. To view logs and process alerts, the web server running Status Web must be able to access the SureSync SQL server. This has been fixed in 8.0.19.
The "Reschedule Point” option was missing from SQL Protection Schedules. This has been fixed in 8.0.19.
In rare instances, when SyncLockStatus is launched automatically after a reboot, it was possible to receive a ‘System.Reflection.TargetInvocationException: An exception occurred during the operation, making the results invalid.’ error. This has been fixed in 8.0.19.
In the SureSync Desktop, when creating a new Rule for a Job under a Real-Time Monitor, the newly created Rule would show under the Jobs node but not directly under the Real-Time Monitor until the Desktop was launched again. This has been fixed in 8.0.19.
Corrections have been made to Enterprise Status handling multiple Schedulers with the same database open. In this scenario, each Job/Schedule/Monitor will list each Scheduler and you will be prompted to select which should execute the item. This has been fixed in 8.0.19.
It was possible to receive an "Unrecognized GUID format” error upon launching the SureSync Desktop if bad data was entered into the connection details for a server. Additional validation has been added to the SureSync Desktop to prevent the issue. This has been fixed in 8.0.19.
Download the new version here