At the moment we are constantly bombarded with marketing related to enterprises moving their SAP estates to “the Cloud” and the potential cost savings and simplification benefits that this may have to offer; SAP have even provided us with a tool to help manage our SAP estate when we’ve made that move to the Cloud – SAP Landscape Virtualization Management (LVM). Whilst moving to the Cloud is inevitably going to happen at some point in the future, SAP customers can benefit now by deploying SAP LVM on-premise.
Whilst SAP LVM Enterprise Edition is chargeable and provides much richer functionality, SAP LVM Standard Edition is available to any SAP customer already owning at least one active SAP application license at no extra cost. With this in mind, it is worth a second look at the benefits SAP LVM Standard Edition could offer to your SAP estate without having to move to the Cloud.
So let’s take a closer look at some of the benefits that you could take advantage of with very little effort.
SAP LVM Out-of-the-Box
SAP LVM is installed on a NetWeaver Java AS. Out-of-the-box, SAP LVM can be used to operate SAP instances and databases as standard via the SAP Host Agent deployed on each managed host. Standard operations include stop, start, mass stop, mass start, restart and mass restart that can be performed in your web browser without the need to logon to the host directly. You can even schedule system restarts to occur out of hours so that technical personnel don’t have to work late to restart non-production systems for example.
SAP LVM Custom Instances
SAP LVM can be extended to manage custom instances such as SAP Replication Server (SRS), SAP Business Objects and SAP Router using scripts registered at the Host Agent.
See how this can be achieved in our SAP LVM Custom Instance blog post.
SAP LVM Custom Operations
SAP LVM can be extended to perform custom operations or to add custom hooks into existing LVM operations such as stop and start. Again, this is achieved using scripts registered at the host agent. An example of a custom operation might be to freeze and unfreeze a cluster whilst you restart the SAP Central Services / Enqueue Replication instances that are overseen by a Windows or UNIX cluster. A custom hook would be needed to intercept SAP system stop and start requests to prepare the cluster (freeze/unfreeze) so that cluster monitoring does not incorrectly start or stop the instance whilst valid SAP LVM initiated stop/start operations are being performed.
See how this can be achieved in our SAP LVM Custom Operations blog post.
SAP Host Agent and LVM
SAP LVM operations are heavily reliant on the stability and resilience of the SAP Host Agent and as such, the SAP Host Agents should be patched regularly. Of course, with some customers having an SAP estate with large numbers of servers, this can become an arduous task. Solution – setup the automatic SAP Host Agent Automatic Update procedure as documented in another of our blog posts.
If you’d like to learn more about the capabilities of SAP LVM or SAP LaMa or are considering your own deployment, drop us a line with no obligation mailto:email@example.com