In today’s world of modern applications, the database as a service (DBAAS) was a necessary offer of services that provides holders to hold a scalable, efficient and cost -effective solution for managing databases without having to manage a comprehensive infrastructure. As multiple verticals of the company-Across industry, from electronic trading to financing and adopt adopt DBAAS for the application of critical missions, the importance of the strong strategy of recovery and management of the inclusive database. And the costs of downtime – whether it is a database failure due to high traffic or randomly erase the database – will have harmful effects on business operations and reputation.
We focused on helping our service providers to create a robust data recovery strategy with a new version VMware Cloud Director extension for data solutions.
We are pleased to announce general availability Extension of Cloud Director VMware for data solutions Version 1.6. In this blog we will try to explore the latest upgrades and improvements that are packed in this version.
Our manual focus on this version was on three aspects:
- Presentation of the latest data administrator functions (2.2)
- Strengthening the integration of data service manager
- Database users (db) with greater flexibility and control
Introduction of a new VMware data service manager (DSM) 2.2 Function for extension of the VMware cloud director for data solutions
Last year, we started the DSM integration with VMware Cloud Director for data solutions. Now we have made the latest DSM 2.2 features available.
Improved Life Cycle Management
We are now supporting the main version for VMware Data Services Manager PostgreSQL instance (supported by 13, 14, 15 and 16). So users can directly upgrade their VMware Data Services Manager instance to any of the main versions via Extension of Cloud Director VMware for data solutions Dashboard.
Increased availability and recovery after disaster
With multiple deployment/ backup capabilities with multiple places, they can now choose from three different options:
1. Separate deployment we have one node that we have a single VM.
2. Clusted deployment on clusted 3 node VSPHERE across hypervisors.
3. Deployment of a cross clump across different vsphere clusters.
This is a highly used database maintenance and provides high availability. Read it here.
Note that the administrator should first define the Police Infrastructure in VSPhere to offer Cross Cluster Ha.
It is a very similar operation for remote backup replications where users can switch the “Enable backup” button to provide replication sets to create a secondary instance DB.
The above image shows how to create a secondary instance of replication.
Availability of the above secondary instance.
Improvement of backup and removal of protection
Users can now restore and restore deleted database instances (VMware Data Services Manager Postgres and VMware Data Services Manager MySQL Instance.) During a 30 -day detention. Please note that users have flexibility to adjust this retention period on the basis of a request. Users can also set the recovery target (RPO) based on DB needs. These operations can perform through the “Archive” card as shown below
Improved integration with data service manager
First, users will see a new user interface flow with simplified and catgated cards for specific operations and management of VMware data services manager. Together with news and warnings cards that have been introduced for faster and easier operation and management.
Another major improvement we have is the ability to deploy the operator of the data solutions administered by the Provider (DSO) on the VMware Cloud Director (CSE) or VSPhere Kubernetes Cluster (VK). This significantly simplifies and alleviates multiple operations across different UIS so that DB administrators work on VMware Data Services Manager Postgres and VMware Data Services Manager MySQL Databases.
We have announced the depreciation of Tanza MySQL and Tanza Postgres saying that this version will be launched and users will be able to see the “outdated” Tanza & Tanzu Postgres DBS tanza label that is already running. Please note that users can continue to use existing dbs tanz as usual. However, there would be no upgrades of version supported by Goong forward.
Further improvements
We have introduced upgrades to help DB Admin users get more control and visibility for better management and optimization of resources. Users can now consume and use resources for each holding organization, as shown below:
Furthermore, from this issue, administrators can return or undress the conditions back in case of failure / from DB instances. This operation can be performed, as shown below, through the “Source Condition” card, where the administrator can see the problem along with the description report.
Together with the thesis, administrators can now change/delegate ownership of DB instances that help them interpret DB management with specific organizations. This helps to manage Personas administrators to manage fewer instances and at the end of the user increases the speed of the developer by the fact that, depending on the administrator for each change request less. However, there are measures for managing “access management” that provide users partial/ full ownership.
Next steps:
Upgrade your current extension Cloud Director VMware for data solutions to new 1.6. You can directly UP-Degree on version 1.6 from version 1. 5 and 1.4.
Check out our upgrade guide for step-bey-step guide.
If you want to learn more about release details, visit our documentation page.
We hope that these new editions provide our VCSP a great platform for offending robust database management, which provides durable and secure services for business critical applications and business continuity.