Skip to Content

LVM 2.0 POC Installation

Dear LVM Gurus.

We are going to install SAP NW 7.4 system on LVM managed machine to learn
the functionality and perform POC sessions for customers.

My question is:

Can I install the system that will be managed by LVM before I obtain and configure
Storage and VM adaptors, and add the system to LVM later?

Is there any specifics steps for installation of new LVM managed systems?

Regards

Vladimir Kogan

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Jan 07, 2014 at 01:05 PM

    Dear Vladimir,

    yes, you can install the new "SAP NW LVM managed" system first (and eventually manage it partially e.g. for start/ stop via SAP Host Agent and SAP Instance Agent) before exploiting all the Storage- and Virtualization related use-cases. Of course some customizing and configuration steps/ discovery activities may need to be repeated if you want to extend the scope to the "full" solution later on.

    And right from the beginning you should install the "managed" system having the full scope for the final PoC use-cases in mind (all prerequisites for "adaptive" or "virtual" installation, e.g. consider virtual hostnames, central user management, storage and filesystem layout, ...)

    Regards

    Edmund

    [BTW, eventually (even if you've got a fully different HW/SW stack) you may find some usefull hints in the document http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102155

    describing a SAP NW LVM sample implementation for an IBM environment ...]

    Add a comment
    10|10000 characters needed characters exceeded

    • Dear Vladimir,

      the virtual Hostname allows to "decouple" the SAP Instance(s) from the virtual machine -

      implementation is definitely required e.g. for all the "provisioning-like" Use-Cases (SAP System Copy, SAP System Refresh, SAP DI Provisioning).

      The naming proposal is an example, and you can adapt that to your environment: From my experience clients often built their naming conventions based on instance type [db|ci|cs|di], SID, network, and organisational informations. Those virtual hostnames then need to be either pre-registered in DNS, or SAP LVM has the functionality of dynamic name resolution updates in a (Linux or Windows) DNS Server.

      I had a look into SAP Note 1843134 - seems that the Hyper-V adapter for SAP LVM currently supports the following VM operations:

      a) Activate

      b) Deactivate (OS Shutdown)

      c) Deactivate (Power Off)

      d) Suspend

      e) Pause

      f) Provisioning a virtual machine from a template

      For those it may be sufficient to start w/o virtual hostnames (and have the SAP instances bound to the VM), but if you have provisioning use-cases in mind for the future you should implement the virtual hostnames for the SAP instances ...

      best regards

      Edmund

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.