Release Notes - Version 4.x

Change Log - Version 4.0

4.0.8 (2024-03-05)

  • Admin Console: fixed display of the server name in the header.
  • Certain functions used to corrected traffic records on update are no longer required, and are no longer executed starting with version 4.0.8 (HOSTSERVER-901). This speeds up the update process.
  • Fixed possible divide by zero error in Space cleanup completion routine.
  • Admin Console: fixed “Space Restored” button (HOSTSERVER-902). This button now performs the same operation as reactivate_space() in the yvva console. Setting the “Deactivated for restore” flag, also performs the same operation as the deactivate_space() in the yvva console.
  • Fixed the SQL error: “Field doesn’t have a default value” which can occurs when on certain client requests (HOSTSERVER-904).

4.0.7 (2023-11-30)

  • Added SMTP authentication settings: SMTPUser and SMTPPassword (HOSTSERVER-851).

  • You can now specify that emails must be sent using secure SMTPS by specifying the protocol as part of the SMTPServerHost value (HOSTSERVER-841) as follows:

    smtps://<host-name-and-port>

  • The default value of the HttpsUsedByClients setting is now True (HOSTSERVER-895).

  • Support for OpenSSL 3 which no longer supports the legacy DH keys has been added.

  • The Host Server will now retry when the upload of a block fails during a Multipart upload to the Object Store (HOSTSERVER-874). A warning is written to the log when block upload fails. Currently, up to 20 failures in a row are allowed, before the entire upload is aborted.

  • Fixed Snapshot takes which may report the error: Symbol ‘lock’ not initialized (HOSTSERVER-878).

  • PBPG keys and messages may now use n line endings as well as rn (HOSTSERVER-881). This was found in some very old keys.

  • Fixed problem when deleting Soft Locks. Some locks where not deleted even though they had expired by exceeding the DefaultSoftLockMaxAge (HOSTSERVER-880).

  • The Host Server now responds to an error that the Registration Server does not have the public key of the Host Server by resending the request with the public key included (HOSTSERVER-879). This is only done once for each Registration Server which then stores the public key.

  • On installation, when getting the volume size, a temporary file was created with root permissions that could not be altered or deleted by the Host Server later in production (HOSTSERVER-876).

  • Some additional security features have been implemented (HOSTSERVER-884 / HOSTSERVER-899).

  • Added setting CleanupFileDelay (HOSTSERVER-891). This is the number of days a file will be retained after being marked for deletion during the Space cleanup process. The default is 60 days.

  • After Space cleanup the Host Server will now send an email notification to Administrators if a files was not found, or a large percentage of the files in the Space were marked for deletion (HOSTSERVER-892). The new setting NotifyCleanupDeleteLevel specifies this threshold as a percentage. The default value is 50%.

    When a snapshot is deleted, deleted files which would be restored when the snapshot is restored can be deleted. A new setting DelaySnapshotFileDeletion determines whether the deletion of such files is also delayed, as is done by the cleanup process.

  • Fixed “Invalid default value” error when updating the Host Server (HOSTSERVER-897). This occurs when updating to a MySQL 8 and database TIMESTAMP columns have a zero (“0000-00-00 00:00:00”) date as default.

  • When a user is switch to a Provider that is not on the DisableSnapshotsList, and EnableSnapshotsByDefault is True, then snapshots will now be enabled for all Spaces in all depots belonging to the user (HOSTSERVER-898).

4.0.6 (2023-05-24)

  • The distributor code for the space and depot owner is now returned to the client by the “get statistic” call (HOSTSERVER-869).

  • Added new “CLIENT” settings: DisableSnapshotsList and DisableReadConfList (HOSTSERVER-866).

    Snapshots are disabled for all spaces in a Depot if the provider of the Depot owner is in the DisableSnapshotsList list.

    Read Confirmation are disabled for all spaces in a Depot if the provider of the Depot owner is in the DisableReadConfList list.

    By default both settings are set to: HODR,HDGU,XHDR,XHDG.

  • Meta data handling has been changed to include the functionality of Host Server 4.1 (HOSTSERVER-865). Meta types are now classified as follows:

    • <=0: Invalid
    • 1-599: Enabled by default & Supports change notification
    • 600-999: Disabled by default & Supports change notification
    • 1000-1399: Disabled by default & No change notification
    • 1400-1999: Enabled by default & No change notification
    • 2000+: Invalid

    In addition, meta data values other than 1 (Soft Lock) and 1000 (Read Notification) will now be deleted if they reach the specified “max age”.

4.0.5 (2022-11-16)

  • Corrected the reply in the case where “getlog” is called with an out-of-date recovery number (HOSTSERVER-863).

4.0.4 (2022-09-21)

  • Fixed a problem regarding support for clients with version number 5.0.0 or later (HOSTSERVER-861).

  • Added function to check if a space is missing BLOB data (HOSTSERVER-853).

  • The Host Server no longer needs to be upgraded after installation (HOSTSERVER-857). Previously, the admin was required to run “upgrade_now”, after installation. These steps are now executed automatically after installation. An upgrade of an existing Host Server still requires a manuel “upgrade_now” execution.

  • Settings RegServerURL and ServiceHostURL while now default to the HTTPS protocol unless explicitly specified in the setting as HTTP (HOSTSERVER-858).

  • Added “Cleanup Uploads” autotask which removes partial uploads to the Object Store that are no longer required (see Cleanup Uploads).

    The new setting LastUploadCleanup indicates the last time this task ran. You can restrict the run time of the task using the UploadCleanupTimeout setting which is set to 40 minutes by default.

4.0.3 (2022-06-09)

  • Space global ID’s generated must be 32 bytes long. This is required by older TeamDrive clients.

4.0.2 (2022-03-09)

This release also includes a number of security improvements, please contact TeamDrive for further details.

  • TeamDrive Protocol (TDP) v1 will be automatically disabled for Depots that are not accessed by TeamDrive 3 clients for 6 months (HOSTSERVER-828).

    TDP v1 can now also be manually disabled for a Depot in the Admin Console.

  • Updated MariaDB connector (native MySQL client libs) (HOSTSERVER-839).

  • Fixed a bug which lead to “provider users” referenced from the history to be marked as deleted.

  • Ensure that an error is written to the various Host Server logs if a database upgrade is required (HOSTSERVER-843).

  • Fixed a bug which caused an exception of the form: “Type mismatch in delete file attempt: ...”, and prevented deletion of a space on S3 storage.

  • If initialisation of S3 fails in apache module then the TDP v3 protocol will now no longer return an error on every request. Instead an error is only returned when access to S3 is actually required (HOSTSERVER-849). This means that uploading BLOBs and downloading recently uploaded BLOBs of a space still work, if S3 is offline.

4.0.1 (2021-10-08)

This is a security update.

  • A number of security issue have been fixed, please contact TeamDrive for further details.
  • Logging functions now encode r and n characters to prevent “Log Poisoning” (HOSTSERVER-835).

4.0.0 (2021-08-31)

The Host Server 4.0 requires the YVVA runtime version 1.5.8 or later.

Note that as of version 4.0, the database must now be upgraded manually using the upgrade_now;; command on the YVVA console (see Step 4) Update the database).

Host Server Functionality

  • Set security headers in Apache configuration (HOSTSERVER-821).

  • The Host Server will now pause up to 5 seconds before sending the reply to the client if the download limit is exceeded, see DownloadLimit (HOSTSERVER-808).

    If the limit is exceeded, the Host Server will send an email to all System Administrators that receive emails. This notification is sent at most, once per hour.

  • Depot overflow behavior has been changed significantly in 4.0 (HOSTSERVER-795)

    The Host Server now allows upload of files to continue when the depot of a space is over the 100% limit. However, files uploaded in this time may not be downloaded by clients. Only once the depot is below the 100% limit are those files released for download. Files uploaded before the overflow may always be downloaded.

    Depots now have an “overflow limit” and a “maximum overflow upload rate” which apply when the depot is full. This value depends on the actual depot storage limit as follows:

    Depot limit Overflow limit Max Upload Rate
    < 3 GB 10 GB 1 GB per day
    < 120 GB 50 GB 2 GB per day
    >= 120 GB 100 GB 4 GB per day

    When a depot reaches the depot limit plus the overflow limit, the depot is “frozen”. When a depot is frozen upload and download of files is no longer permitted. This means that the only way to “unfreeze” a depot is to increase the depot storage limit.

    In the frozen state deleting files, snapshots or emptying the trash may not work because of file uploads that may be queued before these operations prevent the operations from being synchronised.

    A number of emails are sent to the owner of the depot, the managers of the account that owns the depot, and to certain administrators of the Host Server. In the Admin Console you can mark an Admin User as a receiver of “Email Notifications”. By default, this is enabled for all administrators.

    Emails are sent when the storage exceeds 20% and 50% of the overflow limit, and when it exceeds 100% of the overlimit an email is sent to inform users and managers that the depot has been frozen.

    Note that these emails are in addition to the warning emails send when the depot is 80% and 100% full, however these emails are not sent to the Host Server administrators.

  • The Host Server nows sends a notification emails to the depot owner, and managers of the account that owns the storage usage exceeds 80% and 100% of the storage limit (HOSTSERVER-768).

  • The Host Server also sends notification emails if the depot network traffic reaches 80%, and when traffic exceeds the limit (HOSTSERVER-793). Emails are sent to the depot owner and to managers of the account that owns the depot.

    The 100% usage notification is also sent to Host Server administrators that have been selected to receive email notifications.

  • Added functionality to recalculate the size used by a space, on disk and in the cloud (HOSTSERVER-738).

    Buttons are provided in the Admin Console to initiate the calculation of disk usage for a space and for all spaces in a depot.

    After a space has been restored, recalculation of disk usage is automatically scheduled.

    Depot size recalculation is triggered if a depot exceeds 100% storage usage, and the size of the depot has not been recalculated in the last 180 days.

  • This version implements Amazon Signature Version 4. This can be enabled by adding the option UseSignatureV4=True to the S3Options setting (HOSTSERVER-766).

    Note that this signature type only works for Amazon (and fully Amazon compatible) object stores, Azure and OpenStack still use the Version 2 signatures.

  • Added the S3Region setting which determines the region used in Amazon Version 4 signing process. By default the value “eu-west-1” is used.

    The region must be set according to the following mapping: Amazon Regions and Endpoints

  • The Host Server will now automatically delete spaces in a depot to reduce disk usage, when the limit of a depot is exceeded by a certain amount (HOSTSERVER-759). See Depot Overflow and Automatic Space Reduction for details.

    Two settings have been added to support this feature: EnableSpaceReductionProcess` and ``AllowAutoDeleteSpaces (see Resource Management Settings for details).

    Spaces will not be deleted if the depot has been active within the last 6 months.

  • The Apache module and the s3d service now check the database version. If the database structure in not up-to-date the Apache module generates an error, but will continue normally as soon as the database is update. The s3d quits if the database version is not he require version, currently this is version 3.7 level.

  • Added TransferConnection setting which is used to support the transfer of the Host Server Object Store to a different service provider (see TransferConnection) (HOSTSERVER-771).

  • Added the UseIPWorks setting (default: False). Set this value to True in order to use the IPWorks-based cloud access implementation.

  • Added various binary hardening measures. Maximum POST request size for API calls is is now 10 MB.

Administration Console

Note

Please clear the browser cache after the server update.

  • You can now specify whether snapshots should be enabled or disable for a new space on the depot level. Here you can choose between always enabling or disabling snapshots for spaces created in the depot, or you can make it depending on the value of the EnableSnapshotsByDefault setting. This is the default (HOSTSERVER-785).

    Note that changing this value does not change whether snapshots are enabled or not for existing spaces.

  • Using “Set Space Status” and “Unset Space Status” on the space depot page, you can now set and remove a status from all spaces in a depot. The status’ that may be set/removed are: “Disabled”, “Readonly”, “Deactivated for maintenance” and “Deactivated by provider” (HOSTSERVER-761).

  • On the Space Depot page the “Recalc Depot Size” button can be used to initiate the recalculation of the sizes of all spaces in the depot. This process is performed in the background and may take a while.

  • On the Space Details page you can use the “Recalculate Disk Usage” button to initiate recalculation of the disk space used. This process is performed in the background and may take a while.

  • On the Space Depot page, the “Restore Spaces” button may be used to undelete all spaces in the depot. This function can be used after restoring the space of a depot from backup.

    If the space directory does not exist on disk, then the space cannot be restored, and this will cause the process of restoring spaces to stop.

    An empty space directory will be restored as an empty space. After restoring a space, recalculation of the disk space of the space will be initiated.

  • It is now possible to set a volume space limit to 0, which means unlimited.

  • The Admin Console can now “rollback” a failed restore snapshot attempt (HOSTSERVER-807). This case is clearly shown in the Admin Console, if the space is in the “Restoring” state, and a notice on the space indicates that a restore to snapshot is in progress. If this operation is not completed within a few minutes it is OK, to press the “Space Restored” button, to undo any changes to the space log files.