Softpedia >Windows >System >Backup and Recovery >Cloud Xtender >  Changelog

Cloud Xtender Changelog

What's new in Cloud Xtender 2.1.0.0

Dec 13, 2016
  • [u] Introduced new Eldos driver for better support of Windows 10 / Server 2016.
  • When adding multiple cloud connections from the same provider, an error can be returned stating "the cloud connection already exists".
  • An error can be returned when trying to delete a cloud connection.
  • Fully cached files can report remote conflict error.

New in Cloud Xtender 2.0.5.5 (Sep 13, 2016)

  • [u] When scanning a remote cloud drive, the folders found are now being display in the progress dialog (otherwise it can look like the app has hung).
  • [n] Sync action feature (experimental). This allows external process to be called, based on certain file sync actions. You can read more on this feature at - https://support.division-m.com/hc/en-us/articles/214027263
  • The cancel button now works correctly when scanning remote cloud storage.
  • Slow or bad connections to the Cloud Xtender service can result in exception dialogs begin displayed when using Windows Explorer.
  • Improved handling of errors when syncing.
  • Improved catching of illegal characters in the Azure container name.

New in Cloud Xtender 2.0.0.0 (Aug 23, 2016)

  • [n] When connecting to cloud service, Division-M application credentials are now used for Google, OneDrive, Box and Dropbox services (you can still use your own keys, see - http://divisionm.zendesk.com/entries/109495363, but these are no longer required).
  • [n] Added right-click option to resync all files in folder (and sub folder), to and from the server.
  • [u] Improved the notification system.
  • Long folder mount point names not displaying correctly in the client.
  • Invalid cloud provider tokens could lead to file appearing to be in sync when it was not.
  • File encryption was not syncing files in certain circumstances.
  • When creating OneDrive cloud connection, some users were getting the error "Public clients can't send a client secret."
  • OneDrive not showing bytes used in the client.
  • Creating/editing placement rule not working on sub folder for folder mount points.
  • Remote file size not being reported correctly for OneDrive.
  • Adding a Box cloud connection results in an error (as reported by a small number of users).
  • Fixed a number of issues with the Explorer context library.
  • Many minor bug fixes / updates to the client.

New in Cloud Xtender 1.8.0.0 (Apr 28, 2016)

  • If bi-directional syncing is enabled, under some rare circumstances modified local file can be overwritten by the remote file.
  • The encryption types available are not being limited to the types specified for production (all encrypt ions methods are being display). Now the types available are limited to AES 256 and Triple DES (this can be changed by adding the DWORD value "Enable Advanced Encryption Methods" and setting to 1).

New in Cloud Xtender 1.7.0.0 (Apr 28, 2016)

  • At time Cloud Xtender can utilize an excessive amount of CPU which can impact the system.
  • The drive size being reported can be incorrect.
  • If an existing file is renamed, and the operation fails because the new file name also exists, this new file is now deleted and the rename is rescheduled.
  • The file system health check which was run daily after midnight, now runs weekly after midnight.

New in Cloud Xtender 1.6.0.0b (Apr 28, 2016)

  • Fixed an icon issue with the client.

New in Cloud Xtender 1.6.0.0a (Apr 28, 2016)

  • The installer was installing an incorrect version of the client, which could result in an error when clicking on the cloud drive in the interface.

New in Cloud Xtender 1.6.0.0 (Apr 28, 2016)

  • There was a bug in the new cloud connection Id generation, this caused additional checking when a file's tracker was loaded.
  • When there is a large number of files in the processing queue (30,000+), the associated cloud drives performance can be impacted.
  • During a health check on a cloud drive with many files (in the 100,000+ range), the scanning can take an excessive amount of time.
  • When a file was pushed to the cloud, the file's last write value was incorrectly being set to the cloud's version of the file.
  • If cloud operation failed, the retry could cause the file system to hang briefly.
  • If a cloud provider was deleted from the system, modifying a file that was located on the cloud service would result in an access denied error.
  • We have improved file operation queuing making it less system intensive.
  • The location of temp and log files has changed, there are now located in "\ProgramData\Division-M\Cloud Xtender".
  • The underlying volume GUID for a mount point will be the same each time the mount point re-mounts.

New in Cloud Xtender 1.5.5.0 (Apr 28, 2016)

  • If a file contains a reference to a cloud provider that has been removed, errors can be generated which may prevent other files from syncing correctly.
  • When creating file cache (in remote file mode), it is possible that the file requested may not return then correct file offset (only during the cache creation process).
  • The client manager, when displaying an error may show the error dialog twice.
  • The context menu can display menu items not relevant to the select item.
  • When creating a cloud connection, the Id is now generated based on the cloud connection details. This means that if the connection is deleted and then recreated, the files reference to the connection will remain correct.

New in Cloud Xtender 1.5.2.0 (Apr 28, 2016)

  • Improved cache performance on hosts with slow internet connections.
  • The ability to map folders (in addition to local drives) to cloud services.
  • Windows can send file system requests which may not match the file system case of the underlying file system. This can result in remote files not being found due to the incorrect case of the request.
  • If the underlying cloud provider changes for a given rule (or is no longer available), it could force Cloud Xtender to continually check each file mapped to the previous rule provider.
  • Added a new wizard style interface to client to assist in setup.
  • The calculated bytes displayed next to the pie chart was not updating correctly.

New in Cloud Xtender 1.5.0.0 (Apr 28, 2016)

  • Implemented the new "Transporter" sync, streaming and caching engine (this encompasses a large number of changes/fixes to file syncing, streaming and the caching technology).
  • Alternate stream files can cause a file system error when being written to a Cloud Xtender drive.
  • When moving files to a folder that is using a different provider, the files was moved, however it remained on the same provider. This is not desirable, so now an access denied message is returned, and a notification message is sent.
  • When creating a cloud connection, and specifying a "Remote" sync mode, the underlying cache rule is being set to none (not allowing any caching to occur). This is now defaulting to 1 hour.
  • An access denied error can be received when access a cached file.
  • There is a memory leak in the cache access code.
  • The folder caching feature can fail to generate a file name hash on multilingual characters.
  • File caching for encryption and remotely synced files is now explicitly denied access (caching not possible with encrypted files), and a notification is sent.
  • Improved support for Windows 10.
  • A number on minor fixes to the client interface.
  • When upgrading, the installer will now uninstall the existing version first before installing the newer version (this happens automatically).

New in Cloud Xtender 1.4.7.0 (Apr 28, 2016)

  • Changes to a file may not be detected resulting in the file not being synced back to the cloud service.
  • When a rule is monitoring a file on a cloud connection (aka bidirectional monitoring), changes to the cloud based file may not be detected (this issue was not fully rectified in the 1.4.5.0 update).
  • Scanning the remote cloud connection may miss a number of remote folders.
  • The Google cloud provider date/time modified value can be inconsistent if the file is opened via the Google web interface.
  • When renaming a local files, the remote file may take some time to be updated with the new name.
  • When clicking the help link for Dropbox, the Box connection details is being displayed.
  • Fixed a number of cosmetic client issues.

New in Cloud Xtender 1.4.6.0 (Apr 28, 2016)

  • Cloud drive scanning tasks (aka health monitor) now cache folders for improved performance.
  • There is not limit on the number of repeat notification email that can be sent (there is a limit on the number of emails that can be sent in a given time).
  • When setting encryption on an existing rule, it is possible to get an "Encryption method not defined." error.