Release Notes - Version 3.7

Key features and changes

The Host Server 3.7 requires the YVVA runtime version 1.4.0 or later.

Host Server Functionality

  • The Host Server supports Point-in-Time recovery. Using this functionality the TeamDrive Client is able to rollback a Space to a previous point in time. See details in chapter Snapshot Backup and Point-in-Time Recovery.

  • Added “Outgoing Connection” settings: UseProxy, ProxyHost, NoProxyList, ConnectionTimeout and NetworkTimeout (see Outgoing Connections) (HOSTSERVER-676).

  • Added support for Read Notifications. Read Notifications are disabled by default for all Spaces. This feature must be explicitly enabled for a Space by the TeamDrive Client.

    The setting DefaultReadNotificationtMaxAge determines the maximum age of read notifications, if this value has not been explicitly set at the Space level settings (HOSTSERVER-681).

Administration Console

  • Snapshot relevant parameters can be set per Space. Changes are recorded in the change history of the Space.

  • Read Notification settings can be set per Space. Changes are recorded in the change history of the Space.

  • Added the list of background tasks (“Auto Tasks”) to the Admin Console. The list indicates when a task last ran and the result. Clicking on a task allows the user to Activate or Deactivate tasks (HOSTSERVER-697).

    This page also shows the status of the Host Server services: td-hostserver, s3d and tshs (if active). The command used to determine the status is:

    service td-hostserver/s3d/tshs status
    

    If this system is not correctly installed an error will be displayed.

API

Change Log - Version 3.7

3.7.4 (2018-07-17)

  • Fixed crash in background task when a Registration Server was not available during synchronisation of owner data (HOSTSERVER-720).
  • The “getdepotdata” API call now returns a <flags> tag which may include the restrict-access flag value (see Retrieve Depot Information for details).
  • The “createdepot” API call no longer automatically creates a “contract number” for a depot which starts with “WEB#”.
  • Fixed a bug that prevented the synchronisation of data with foreign Registration Server. The error in log was: “RROR -24903 (0): Authorization failed: device 99999 not found” (HOSTSERVER-725).
  • When moving spaces from one depot to another, then disk usage and traffic was not always recalculated correctly (HOSTSERVER-731).
  • Under certain circumstance published files that were part of a snapshot were not deleted after expiry, although access to the file was prevented (HOSTSERVER-733).
  • Under some circumstance the Host Server set the “Traffic limit exceeded” flag, even when the EnforceTrafficLimit setting was set to False (HOSTSERVER-735).
  • The Host Server now records the name of the user that made changes to a depot. Previously this information was not always available as it was placed in the comments. This function requires the use of Registration Server version 4.0 or later (HOSTSERVER-736).

3.7.3 (2017-11-01)

  • Improved the reporting and logging of connection errors that may occur when the Host Server contacts the Registration Server.

  • During Host Server Setup it is now possible to specify a proxy to use in order to contact the Registration Server. The NoProxyList setting must be specified after setup, if required.

  • Improved input checking on setup of the Host Server. The Registration Name may not contain in special characters. Domain Names may not contain any spaces, and must include at least one ‘.’ character (HOSTSERVER-715).

  • The Host Server will now prevent access to a Depot if all users are removed from the access list. Previously, Depots reverted to unrestricted access when the last user was removed from the access list.

    The Depot users in the access list are now displayed in the Admin Console. Only the Depot owner and users in this list are allowed to create Spaces in the Depot. However, users not in the list are not prevented from using existing Spaces in the Depot.

  • Deleting a Depot in the Admin Console now works the same as deleting a Depot via the API: the Depot is simply marked as deleted (HOSTSERVER-712).

    If the setting ShowDeletedObjects is False, then Depots marked as deleted will not be visible in the Depot list. However, such Depots can be reached by clicking on the Depot link in a Space belonging to the Depot.

    Note that deleting a Depot currently just prevents new Spaces from being created in the Depot. Existing Spaces are still accessable.

  • Moved index on SpaceID, MetaType from MetaData to MetaDataOptions table. This index was previously created on the wrong table (HOSTSERVER-716).

  • Added support for “If-Modified-Since” header. If sent, and BLOB data has not been modified since the specified time, the server will now send a “304 Not Modified” result. This is in order to support caching proxoies (HOSTSERVER-709).

  • Added NonCachingProxies setting. This is a list of the host names or pseudonyms of proxies that are downstream from the Host Server but do not cache any data (HOSTSERVER-711).

  • Version 3.7.3 requires YVVA runtime version 1.4.4.

3.7.2 (2017-08-14)

  • The TPD v3 call “restsnap” will now delete all meta data created for the Space after the last modify time of the snapshot (HOSTSERVER-708).
  • Fixed a database deadlock in TDP v3 call “addmeta” (HOSTSERVER-707).
  • Moved EnableProxyCaching to “Client Settings” (HOSTSERVER-706).
  • A space change history entry is now made when a Space is deleted (HOSTSERVER-705).

3.7.1 (2017-06-20)

  • Initial 3.7 public release.
  • Fixed a bug which caused an error when moving a Space from one depot to another using the Admin Console (HOSTSERVER-680).
  • When accumulating traffic, the process now checks the access time to ensure that traffic is only accumulated for the current month. This fixes the problem that the Object Store log processing can generate traffic changes that occurred in the previous month (HOSTSERVER-702).