New functionality and change list¶

Release 19.08¶

Release 19.08 is an enhancement to previous release 18.11 with some scalability, security, and usability improvements, new features and fixes to issues that were found in 18.11.

What’s new in Zadara Cloud¶

NVMe SSD Support¶

7.62TB NVMe SSD’s are now supported. These drives provide enhanced performance at lower price per GB.

Cloud-in-a-Box¶

Zadara now supports a Cloud-in-a-Box configuration based on a 2U device that contains 2 storage nodes and 12 HDDs. This configuration is ideal for small on-prem needs like remote branches.

User Guides¶

Updated versions of VPSA Storage Array User Guide and VPSA Object Storage User Guide are available *http://guides.zadarastorage.com* in HTML format. Users can also download a PDF file.

What’s new in VPSA Storage Array and All Flash Array¶

VPSA Storage Array – New Engine¶

New larger Engine was introduced for VPSA Storage Array to serve use cases that need extreme performance.

IO Engine Type	Dedicated Compute Resources	Base Flash Cache	Max Drives	Max Raw Capacity
200 (Baby)	2 CPU, 6 GB RAM	20 GB	5	24 TB
400 (Basic)	4 CPU, 12 GB RAM	20 GB	10	60 TB
600 (Boost)	6 CPU, 20 GB RAM	40 GB	20	100 TB
800 (Blast)	8 CPU, 28 GB RAM	60 GB	30	150 TB
1000 (Blazing)	10 CPU, 36 GB RAM	80 GB	40	200 TB
1200	12 CPU, 52 GB RAM	100 GB	60	240 TB
1600	16 CPU, 68 GB RAM	120 GB	80	300 TB
2400	24 CPU, 100 GB RAM	180 GB	80	360 TB
3600	36 CPU, 144 GB RAM	240 GB	80	360 TB

VPSA All Flash – Engines¶

Revised VPSA All Flash Engine specifications

IO Engine Type	Dedicated Compute Resources	Max Drives	Max Raw Capacity	Max Customer (Host) Capacity
F800	8 CPU, 48 GB RAM	30	120	60 TB
F1200	12 CPU, 72 GB RAM	60	200	100 TB
F2400	24 CPU, 116 GB RAM	80	320	160 TB
F3600	36 CPU, 176 GB RAM	100	400	200 TB
F4800	48 CPU, 236 GB RAM	120	400	200 TB

Security¶

12110 - For security reasons User API Tokens are no longer stored in the DB.

Note

It is recommended to use the VPSA’s user Access-Key for authentication purposes in custom applications which are utilizing the VPSA RestAPI. Application that already authenticates using the VPSA Access-Key prior to version 19.08, will continue to work as exptected.

It’s not possible anymore to retrieve the existing token by API or GUI.

Starting of VPSA version 19.08, the API token is displayed only once when generated. The API token will not be returned as part of the /api/users/login API response.

In order to get a new token, navigate to the user information section in the VPSA management interface or use /api/users/{id}/access_key API by providing username and password. For additional information: http://vpsa-api.zadarastorage.com/19.08/#users

Warning

Upon generating a new Access-Key, the existing token will be revoked!

Remote Clone¶

Make a given snapshot of a source volume, available instantly (before data is copied) on another VPSA, in the same cloud or in a different cloud over any distance. Unlike Mirroring that might take a long time to replicate the data (depending on capacity and the link bandwidth), the cloned new volume is available immediately. Blocks of data are retrieved from the source volume on demand. In addition there is an option to have the system retrieve all the data in the background.

Most common use cases are:

Instant Mobility - Rapid Migration of volumes between VPSAs with minimal downtime for the migrating application.

Useful for:

Volume migration from a VPSA that runs out of capacity into a VPSA that has free capacity
Volumes migration between VPSA Gen2 and VPSA Gen3
Volumes migration between sites
Volumes migration from Private cloud to the public cloud

Offline Processing - Create an instant clone of a volume on another VPSA (local or remote) for offline processing without affecting the original production volume.

Useful for:

Dev and Test
Analytics
Reporting

VPSA All Flash Array - Pool Shrink¶

New ability to remove drives form a given pool and return them for the cloud resources for re-allocation. This will allow users to stop paying for drives that are no longer needed.

Volume Auto Expand¶

To avoid situations of volumes running out of capacity, you can set a policy for automatic volume expansion as long as there is free capacity in the pool.

Multiple Custom Networks (Virtual Interfaces)¶

Customer that needs to connect one VPSA to more than one network for hosts access, can now do it with Multiple Custom Networks (Virtual Interfaces). #10033

IPv6¶

IPv6 is now supported on the FE network, for host and UI connectivity.

Custom networks can be either IPv4-only or IPv6-only. Since IPv6 natively has Global addresses, there is no explicit need to configure additional public IP address for global routing of IPv6 address. Hence Public IP configuration always uses IPv4 addresses.

Interoperability¶

VMware

VPSA All Flash is now certified for VMware ESX 6.7 for iSCSI connectivity.

https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=san&productid=47868&releases_filter=428,427,369&deviceCategory=san&details=1&partner=598&isSVA=0&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc
VPSA Storage Array is now certified VMware ESX 6.7 for NFS connectivity.

https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=san&productid=46452&releases_filter=428,427,369&deviceCategory=san&details=1&partner=598&arrayTypes=3&isSVA=0&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc

Veeam

VPSA Storage Array is now certified as backup target for Veeam as “Veeam Ready - Repository”

https://www.veeam.com/kb2961

What’s new in VPSA Object Storage¶

Scalability¶

Zadara object Storage now supports unlimited number of objects per container.

The internal elastic load balancer was extended to scale for larger Object Storage configuration.

Multi Zone¶

Zadara Object Storage now supports Multi Zone configurations where the data is Synchronously replicated across two zones. |

IPv6¶

IPv6 is now supported on the FE network, for host and UI connectivity.

Custom networks can be either IPv4-only or IPv6-only. Since IPv6 natively has Global addresses, there is no explicit need to configure additional public IP address for global routing of IPv6 address. Hence Public IP configuration always uses IPv4 addresses.

Deprecation Note¶

Authentication mechanism for Swift API v2 has been deprecated. Object Storage users which are are utilizing Swift API are expected to adjust their clients to use the v3 authentication mechanism.