In previous posts, a number of benefits of Data Services Manager (DSM) were highlighted. Features such as automated backups, ease of scaling, as well as comprehensive monitoring and alerting were highlighted. Another feature which is a big differentiator in DSM is lifecycle management. In this post, I am going to show the steps in upgrading the DSM appliance/provider, essentially the DSM control plane, when a new update is available. Of course, there is also a plan for lifecycle management on the databases and data services, but that will be a topic for another post. In this post, I will take…
This is a short video which highlights the various aspects of lifecycle management in VMware Data Services Manager (DSM). The demo shows the steps involved in upgrading DSM from v1.3.2 to v1.4. It looks at the steps to upgrade the Provider, the Agents and the version of existing databases which are already deployed. It also highlights points where these updates can be automated from within DSM itself, along with maintenance windows and policies. A more detailed description of the steps are highlighted in this accompanying lifecycle management blog post which covers the same upgrade scenario.
In this post, three aspects of lifecycle management of VMware Data Services Manager are reviewed. An upgrade from DSM v1.3.2 to v1.4 will be used to demonstrate the various aspects of lifecycle management. First, the provider administrator will upgrade the DSM provider. This will be followed by an upgrade of the DSM agents, before finally upgrading the databases. Upgrading from DSM v1.3.2 to v1.4 introduces a new minor version of the supported versions of PostgreSQL and MySQL. If the Allow Minor Version Upgrade option is enabled, then the databases are updated during the next maintenance slot automatically. However, the provider…