Release Date: June 20, 2022
Data Management for VMware Tanzu enables Enterprise organizations to host their own Database-as-a-Service offering on VMware-based infrastructure.
The following table identifies the supported component versions for Data Management for VMware Tanzu version 1.x:
Data Management for VMware Tanzu Version | VMware vSphere Version (Edition) | VMC Version | MySQL Version | Postgres Version | Microsoft SQL Server Version |
---|---|---|---|---|---|
1.3.0 | 6.7.x through 7.0.x (Enterprise Plus Edition) |
SDDC 1.14v6 | 8.0.28 | 10.21.0, 11.16.0, 12.11.0, 13.7.0 |
2019 in Standard, Developer, and Enterprise editions |
1.2.0 | 6.7.x through 7.0.x (Enterprise Plus Edition) |
SDDC 1.14v6 | 8.0.26 | 10.20.0, 11.15.0, 12.10.0, 13.6.0 |
Not Applicable |
1.1.1 | 6.7.x through 7.0.x (Enterprise Plus Edition) |
SDDC 1.14v6 | 8.0.26 | 10.19.0, 11.14.0, 12.9.0 |
Not Applicable |
1.1.0 | 6.7.x through 7.0.x (Enterprise Plus Edition) |
SDDC 1.14v6 | 8.0.26 | 10.18.0, 11.13.0, 12.8.0 |
Not Applicable |
1.0.1, 1.0.2 | 6.7.x through 7.0.x (Enterprise Plus Edition) |
Not Applicable | 8.0.23 | 10.17.0, 11.12.0, 12.7.0 |
Not Applicable |
1.0.0 | 6.7.x through 7.0.x (Enterprise Plus Edition) |
Not Applicable | 8.0.23 | 10.15.0, 11.10.0, 12.7.0 |
Not Applicable |
Before upgrading, ensure the following:
After upgrading, ensure the following:
Update all the components of a database before you perform any operations like manual backups, cloning, restore, or recover. If Auto Minor Version Upgrade is not activated for a database, you can manually update the VMs.
For the upgraded database clusters, you can clone the existing Primary database to create a new Standalone database. You can create a new HA cluster by creating replica databases of the newly created Standalone database.
For the upgraded Standalone databases, you can clone the existing Standalone database to create a new Standalone database. You can create a new HA cluster by creating replica databases of the newly created Standalone database. You can delete the original Standalone database.
For a Provider HA cluster, perform the following steps:
Upgrade the Primary Provider VM.
Use the following API to delete all the Standby Provider VMs in a cluster.
DELETE https://<provider-ip-address>/appliance/provider-ha/{instanceUuid}
Reboot the Primary Provider VM.
With only the Primary node in the cluster, perform some actions, such as creating a database or a Namespace.
Configure two more Provider VMs in 1.3 release, and then register them as Standby VMs to the existing Primary Provider VM to form a complete Provider HA cluster.
If you have configured a Tanzu Net Token, Data Management for VMware Tanzu will automatically download a new release and upgrade the control plane software and database templates in your installation. If you have not enabled automated updates, you can also choose to do on-demand manual updates for the Provider VM and on-demand manual updates for the database. The Agent VM is updated automatically.
If you deployed Data Management for VMware Tanzu in an air-gapped environment, you must download the new release and manually populate the database templates and software updates in the Provider Repo.
If you have configured a Tanzu Net Token, Data Management for VMware Tanzu will automatically download a new release and upgrade the control plane software and database templates in your installation. If you have not enabled automated updates, you can also choose to do on-demand manual updates for the Provider VM and on-demand manual updates for the database. The Agent VM is updated automatically.
If you deployed Data Management for VMware Tanzu in an air-gapped environment, you must download the new release and manually populate the database templates and software updates in the Provider Repo.
Release Date: June 20, 2022
Data Management for VMware Tanzu 1.3.0 includes new and changed features, known issues, and resolved issues.
Data Management for VMware Tanzu 1.3.0 includes support for these PostgreSQL versions:
Data Management for VMware Tanzu 1.3.0 includes support for MySQL version 8.0.28.
Data Management for VMware Tanzu 1.3.0 includes early access provisioning for Microsoft SQL Server 2019 in Standard, Developer, and Enterprise editions.
Data Management for VMware Tanzu version 1.3.0 includes the following new and changed features:
High Availability Database Clusters
Data Management for VMware Tanzu enables you to create High Availability (HA) clusters of databases for PostgreSQL and MySQL database engines with auto promotion and manual promotion functionalities to provide high reliability and to prevent downtime.
Introducing Microsoft SQL Server Databases (Early Access)
Data Management for VMware Tanzu enables you to create Standalone Microsoft SQL Server Databases and manage customised database templates that are used to create these databases.
Enhanced Namespaces
Namespaces are created as a pool of resources and a Namespace can be shared across organizations and used by multiple databases. %= vars.name_long %> also enables you to modify associations of organizations to Namespaces and modify resources in a Namespace. Therefore, multiple Namespaces can be associated with different agents, as required, that are created from a shared resource pool. More than one Namespace can be associated with an Environment (Agent) or an Environment (Agent) can have an exclusive Namespace. Enhanced Namespaces provide simplified deployment experience, improved resource management, and Agent Isolation.
Enhanced Role of Provider Administrator
Provider Administrator role is enhanced and it can perform operations on databases such as, create, backup, clone, restore, PITR, replicate, and recover databases. Thus, this imparts enhanced control of the Provider Administrator on operations in Data Management for VMware Tanzu and provides two ways of onboarding an agent for a simplified user experience.
Onboard Agents through the Provider Console
Data Management for VMware Tanzu enables you to onboard an Agent through the Provider console as well as the Agent console. Therefore, you have redundancy in onboarding agents and you can have the option to onboard through the Provider console if the Agent IP is unreachable and vice versa.
Enhanced Reporting
Data Management for VMware Tanzu enables you to download information on databases and system audit events either in XLSX or CSV format. Based on the downloaded data, you can perform various analysis and take informed decisions based on data.
Sync with vSphere Modifications
Apart from scheduled updates to environments and VMs that occur once in 24 hours, Data Management for VMware Tanzu enables on-demand sync of environments with the vCenter resource modifications of the vSphere. Thus, changes made in the vSphere, due to requirements of Data Management for VMware Tanzu environments, can be synced and applied on demand.
Release Date: March 09, 2022
Data Management for VMware Tanzu 1.2.0 includes new and changed features, known issues, and resolved issues.
Data Management for VMware Tanzu 1.2.0 includes support for these PostgreSQL versions:
From Release 1.2.0, Data Management for VMware Tanzu extends support for PostgreSQL 13.
Data Management for VMware Tanzu version 1.2.0 includes the following new and changed features:
Enhanced Log Management
Flexibility in Managing Environments:
Flexibility in Managing Databases:
Enhanced Role of Provider Administrator
Release Date: December 14, 2021
Data Management for VMware Tanzu 1.1.1 includes support for these PostgreSQL versions:
Data Management for VMware Tanzu version 1.1.0 includes the following new and changed features:
Release Date: December 01, 2021
Data Management for VMware Tanzu 1.1.0 includes new and changed features and resolved issues.
Data Management for VMware Tanzu version 1.1.0 includes the following new and changed features:
Flexibility in Database Configurations:
Flexibility in Infrastructure Configurations:
On-demand Updates to Provider and Databasees:
Deployment of Provider VM, Agent VM, and database in VMware Cloud Service on AWS:
Authentication Functions:
Release Date: September 30, 2021
Data Management for VMware Tanzu 1.0.2 resolves these issues:
Intermittent failure of Promote Replica operation
Sometimes, promoting a Replica database to a Primary database failed when the DHCP server assigned the same IP address to both the Primary database and the Read Replica database. Now, Data Management for VMware Tanzu ensures that the same IP address is not assigned to these instances.
OS software updates that require reboot were not applied to databases
OS software updates that required reboot were not applied to the databases for which you did not select Enable Auto Minor Version Upgrade during the creation of the database. Now, OS software updates that require reboot are applied independent of selecting Enable Auto Minor Version Upgrade during the creation of the database.
SSH connection successful even after disabling SSH access
If you disabled SSH access to a database, SSH connections to the database were still successful. Now, SSH connection depends on enabling or disabling SSH access to a database.
Provider restore failed
The process of restoring a Provider backup on a Provider VM failed. Now, the Provider restore operation works more reliably.
Release Date: August 12, 2021
Data Management for VMware Tanzu 1.0.1 includes support for new MySQL version 8.0.26.
Data Management for VMware Tanzu 1.0.1 includes support for these new PostgreSQL versions:
Starting with version 1.0.1, VMware distributes the Data Management for VMware Tanzu Provider and Agent virtual appliance .ova
s and the Air-gap Environment Repository on VMware Customer Connect in addition to distributing this software on VMware Tanzu Network.
Data Management for VMware Tanzu 1.0.1 resolves these issues:
Promote Replica fails for PostgreSQL 10 and 11
Due to a file permission error, promoting a Replica to Primary fails when the databases was deployed with PostgreSQL 10.x or 11.x.
Database Template publishing occasionally fails
Publishing a database template occasionally fails when the Provider Repo is located in AWS S3.
Release Date: July 19, 2021
This is the first release of Data Management for VMware Tanzu.
Data Management for VMware Tanzu version 1.0.0 includes the following:
Simplified Database Provisioning and Management for Users:
Tailored Managed Data Services Offering for Providers:
Centralized Control Plane Management for Providers:
Centralized Infrastructure Management:
Data Management for VMware Tanzu 1.x has these known issues and limitations:
Infrastructure:
Deployment:
You cannot move to Standalone Provider mode from a High Availability (HA) Provider deployment.
Data Management for VMware Tanzu supports the following Agent concurrency limits:
8 parallel database deployments (create, restore, PITR, clone, add replica operations) with a bounded waiting queue of size two (2).
Operations with an unbounded waiting queue:
(Resolved in v1.3.0) If you experience intermittent failure while publishing database templates in an HA setup, perform the following steps:
/data/manifests/extracted-manifest
folder is created and has JSON files in it.data/manifests/extracted-manifest
folder of the Provider node where all the json files are present.data/manifests/extracted-manifest
folder that you create in these nodes.Organizations and Users:
Database Configuration:
Sometimes, powering on database VMs can conflict with virtual machine affinity/anti-affinity rule. Therefore, to successfully power on all the VMs in a database cluster after you have powered them off, keep the vSphere DRS turned off.
Do not perform recover operation on a Primary database of a cluster. You can clone the Primary database or you perform the restore or PITR operation on the Primary database, and then perform the recover operation on the cloned or restored database.
A user is permitted to modify only certain configuration properties after a database is successfully provisioned.
You cannot change the database server administrative password from the console or API after the database has been provisioned.
(Resolved in v1.3.0) To prevent databases from moving into an unstable state, you need to update the Provider VM and Agent VM before you manually update OS of databases, and then the Engine of database VMs after the OS update is completed.
Certificates:
POST https://agent-ip/onboarding/api/tenant/onboarding?action=add-trusted-certificates
Request parameters: {
"certificate: <cert file>",
}
Failover: