I have created a new video showing how to create an PostgreSQL database in Data Services Manager (DSM) version 2.0. The objective is to show how simple it is to not only deploy a database, but also how the provisioning steps allows different vSphere infrastructure resources to be selected during the provisioning stage. This is achieved through Infrastructure Policies which we learnt about in the previous video. The demo also touches on features such as automated backups, automated lifecycle management and advanced settings, all of which may be configured at database deployment time.
I continue my journey to learn more about VMware Data Services Manager (DSM). Today, I turn my attention to clustering MySQL to make it highly available on vSphere infrastructure. This is subtlety different to the previous exercise of enabling HA on PostgreSQL. With the MySQL HA implementation, there is no requirement to deploy an additional VM to behave as the witness/quorum such as the PG_Monitor in the case of PostgreSQL. To make MySQL highly available, MySQL InnoDB Cluster is used. This utilizes a feature called group replication to synchronize the different read replicas. It also supports the concept of a…
One the features of Data Services Manager (DSM) that stood out for me was how it could very easily make a standalone database highly available. With just a single click, users can deploy the necessary monitoring VMs (in the case of PostgreSQL, a PG_Monitor) and additional Read Only Replicas. In this post, I will show how to create a highly available database using DSM. I will highlight some of the requirements, and also some of what is taking place under the covers while the HA operation is in progress. Requirements Let’s begin by outline some of the requirements. The main…
In this short video, I provide an overview of the configuration tasks involved in setting up VMware Data Services Manager, a VMware product that allows for the ticket-less, self-service deployment of databases whilst keeping the security, compliance and life-cycle management in the hands of IT (or the vSphere Administrators). If you find the video interesting, please check out some of the more detailed blogs posts around VMware Data Services Manager on this site, such as the architectural overview, the agent deployment steps, and database deployment steps. On a somewhat related note, VMware Data Services Manager version 1.4 is now available.…
In an earlier blog post, the steps to provision a database from a database template using VMware Data Services Manager (DSM) were described. We also previously observed that once the DSM provider configuration is complete, some predefined database templates for both MySQL and PostgreSQL become available for publishing. However, there is also an early access model to allow for the deployment of SQL Server databases using DSM. This does require some additional setup steps to manually create the SQL Server database template. This is the purpose of this post. Once again, we are using the latest version of VMware DSM…
This is the third blog post in a series which describe how to get started with VMware Data Services Manager (DSM), a VMware solution that offers on-demand provisioning and automated management of databases on vSphere environments. In a previous installment, the deployment and configuration of the Provider appliance was discussed. In a follow up post, the steps to provision and configure an Agent were described. In this final installment related to the deployment of DSM, the addition of users is covered. So far the only user we have been dealing with is the Provider Admin. In this post, we will…
After a successful deployment and configuration of the Provider appliance in my most recent post of VMware Data Service Manager, it is now time to turn our attention to the Agent appliance. This component is responsible for initiating operations on a particular vSphere cluster. An Agent can only be part of a single vSphere cluster. However, multiple agents, which are provisioned across many vSphere clusters, can all be managed from a single Provider UI. Just like the Provider appliance, the Agent is also delivered as a .OVA which is available for download from both VMware Tanzu Network and VMware Customer…