DSM 2.2: Using the API to change the database admin password

Many of our customers have security policies in place which require all passwords to be rotated on a regular basis. Many of our customers are also looking at ways to automate this process, and avoid having to login via the DSM UI and update all of their database passwords manually. As you can imagine, doing this manually can be a very tedious task. Fortunately, there is way to automate this process via the DSM API for Postgres databases. In this post, I will demonstrate the steps involved to allow you to automate the changing of DSM provisioned database admin passwords…

DSM 2.2: Onboarding existing Postgres Databases into DSM

One feature that many of our customers have asked about is the ability to ingest existing Postgres databases into Data Services Manager (DSM). As part of DSM 2.2, our team has put together a step by step guide into how to achieve this using the logical replication feature available in Postgres. The guide is included here as part of the official DSM 2.2 documentation. I decided to build a stand-alone Postgres database and follow the instructions to get the database into Data Services Manager. I built a Postgres v15.10 database on a VM running Debian 12 (bookworm). I picked up…

DSM 2.2: Postgres Database Major Version Upgrade (Video)

DSM has had the ability to do minor version upgrades of databases for some time. In fact, minor version upgrades can be automated in DSM by simply setting a maintenance window on the database. Any minor updates that are available and staged will be automatically applied during the maintenance window. And of course, this could be scheduled out-of-hours. With version 2.2, we can now offer our customers ‘major version upgrades’ for Postgres databases alongside minor version upgrades. The following video will share more details about the process, and some of the things to be aware of it doing a major…

DSM 2.2: Database Delete Protection (Video)

Ever have one of those moments when you realised “Oh shoot! I didn’t mean to delete that!”. Now imagine if that thing was a production database. Ouch! But not to worry. With Data Services Manager version 2.2 we have you covered. This release has a new feature called Database Delete Protection. Now if you delete a database, we will keep its backups archived for 30 days by default. This means you can restore the deleted database for up to 30 days after the database was deleted. This is a much sought-after feature that many of our customer has requested. Check…

DSM 2.2: Object Store Service (Video)

A short video on the new DSM 2.2 Object Store service to complement my earlier blog post on the new Data Service Manager 2.2 Object Store service. This service is delivered in partnership with MinIO. This will allow our customers to provision and monitor object stores on vSphere infrastructure. Note that this is a “tech preview” and should not yet be used in production. However, we encourage customers to try and it out and send us their feedback as part of a “proof of concept” or PoC. Also note that customers will need to source a license from MinIO to…

DSM 2.2: Object Store Service (Tech Preview)

In DSM 2.2, we are partnering with MinIO to offer a technical preview of a new Object Storage service. This service allows DSM customers to provision Object Storage on their VMware Cloud Foundation (VCF) environments while enjoying all of the fleet management capabilities offered by DSM. There are a few steps to get the Object Store service configured. In this post, I will go through the setup and demonstrate how a small storage pool is deployed along with the Object Store control plane and Object Store database. Prerequisites You will need to source a MinIO AIStor license, even for testing…

DSM 2.2: Disaster Recovery with Database Replication (Video)

This is the second in a series of videos related to Data Services Manager (DSM) version 2.2 from VMware by Broadcom. In this video, we examine how to configure replication between a primary and a secondary Postgres database. Whilst the video shows the replication being configured between a primary and secondary database managed by the same DSM provider, replication could also be configured between a primary and secondary database managed by different DSM providers. Thus, the primary database could reside on infrastructure managed by one vCenter server, and replicate to a secondary database on infrastructure managed by a completely different…