New Features

• Gateway now implements the SOSAPI that was introduced in Veeam version 12. (CLOUD-3590)

• Push/pull cloud data migration supports HTTPS with self-signed certificates. (CLOUD-3749)

Changes

• Fixed an issue that prevented the use of colons in basic authentication passwords. (CLOUD-3716)

• Fixed a bug in "push to the cloud" where the support object is copied to the destination if a complex job name is specified containing characters that are escaped in a URL. (CLOUD-3746)

• Added content-MD5 headers to video clip objects and cloud migration support objects. (CLOUD-3753)

• Fixed an issue where the same next marker was repeatedly returned when paginating through a versioned bucket with delimiter listings and [folder_listings] usePaths = true. (CLOUD-3759)

• Fixed a bug that caused Unicode characters in object names to be translated to "?" on some systems. (CLOUD-3744)

• Improved multi-delete functionality by adding new configuration options such as [gateway]recursiveDeleteMaxRetries, [gateway]recursiveDeleteRetryDelay, and [gateway]recursiveDeleteSynchronousIndexing, see Gateway Configuration. (CLOUD-3708)

• Fixed an issue where deleting a domain containing a bucket with locked objects appears to succeed in Portal (via Management API) but failed. (CLOUD-3608)

• Fixed a 500 server error when paging through an S3 delimiter listing with "versions" on a bucket that does not have versioning enabled. (CLOUD-3752)

• Fixed an error “Too much data to download into memory” that occurred when listing a domain with a large (10s of thousands) number of buckets with long names, though the hard limit on bucket listing remains 10,000. (CLOUD-3704)

• Fixed a bug where a legal hold is dropped on an object if applied under retention using an SCSP copy operation. (CLOUD-3694)

• Fixed a bug where the location response header was incorrect behind an HTTP proxy. (CLOUD-3756, CLOUD-3244, CLOUD-3007)

• If “hosts” under [storage_cluster] is configured with a hostname and storage nodes are rebooted and come up with new IP addresses, Gateway resolves these new addresses. It is no longer required to restart the Gateway in that case. (CLOUD-3143)

• The S3 location query (AKA regions) no longer returns the Swarm cluster name as the location. Rather, a default location may be set in the [s3]region config item. It may also be specified in an S3 bucket creation request. Neither set it default nor specified at creation; the default is empty that clients interpret as "us-east-1".

  To prevent backup failures, Veritas NetBackup users must change their currently configured bucket location from the Swarm cluster name to the default “us-east-1” or configure [s3] region = <cluster.name> in gateway.cfg and restart. (CLOUD-3666)

Upgrade Impacts

See Upgrading Gateway, to upgrade from a version of Gateway 6. See Upgrading from Gateway 5.x, if migrating from Elasticsearch 2.3.3 and Gateway 5.

Starting from Gateway 7.8, Elasticsearch 6.8.6 is no longer supported. Remain on Gateway 7.7 until the rolling upgrade is completed from Elasticsearch 6.8.6 to 7.5.2.

Address the upgrade impacts for this and each prior version since the currently running version:

See for impacts from prior releases.

Watch Items and Issues

These are known operational limitations that exist for Gateway.

• When using the default RHEL/CentOS configuration of IPTABLES, traffic to the Gateway will be blocked unless action is taken to disable IPTABLES or to enable inbound traffic to the front-end protocol port(s).

• Gateway is not compatible with Linux PAM modules that depend upon interactive validation operations such as OTP or biometric scanners.

• Gateway SCSP and Portal do not allow a bucket with object locking to be deleted, even if it is empty. It must be deleted by an S3 client e.g. using "rclone purge" to delete all objects and versions. (CLOUD-3516)

• Gateway 7.10.3 introduces an INFO log about SOSAPI which can be disabled by adding this to /etc/caringo/cloudgateway/logging.yaml. (CLOUD-3708)

  ## Remove this with Gateway 7.10.4. Disables a noisy Gateway 7.10.3 INFO log about SOSAPI - name: com.caringo.gateway.handler.s3.S3ObjectRequestHandler level: warn

See for known issues from prior releases that are still applicable, apart from those appearing above as Fixed.