SAP Landscape Management 3.0, Enterprise Edition

Relocating Not Running Systems and Instances

You relocate an instance or a set of instances from one host to another, either physically, or virtually in either direction. The operation retains the status of the instances. Not running instances are unprepared and prepared.

Prerequisites

  • The general prerequisites for instance operations have been met.

    For more information, see General Prerequisites for Instance Operations.

  • Optional: You have specified a preferred host.

    For more information, see Setting a Preferred Host for an Instance.

  • The technical users associated with the instances to be relocated are available on the target host as well.

  • You have set up a flexible license mechanism.

    Relocating the SAP instance including the message server (CI or ASCS) invalidates the system license because the host name changes. Therefore the flexible license mechanism does not bind the license to the message server host of the SAP system but instead to a fixed SAP Host Agent within the landscape.

    For more information, see Flexible License Mechanism.

  • The instance status is Not runningNot running.

  • You have ensured that all instances on which your current instance depends are running.

  • If you want to relocate to another operating system version, the target operating system version is not configured by default. Ensure that the operating system versions are configured in the Required Host Type section of the instance properties.

    For more information, see:

  • If you relocate SAP instances connected to an SAP HANA database, ensure that you have installed the hdbclient with the -H <virtual-hostname> option. If this is not the case, the hdbuserstore entry is only generated for the current physical host. Check the<hdbclient-dir>/install/installation.ini. This file must contain an HOSTNAME=<virtual-hostname> entry.

    For more information, see Secure User Store (hdbuserstore) in the SAP HANA Security Guide at https://help.sap.com/viewer/b3ee5778bc2e4a089d3299b82ec762a7/latest/en-US/dd95ac9dbb571014a7d7f0234d762fdb.html.

Context

You can relocate instances either on the entire system or on an individual instance. So you can flexibly decide if you want to relocate only one host (for example, in the case of a host outage) or relocate all hosts in the system (for example, in the case of a system scale up).

Procedure

  1. Choose Operations.
  2. Choose Systems from the tabs.
  3. From the Operations dropdown for the instance, choose Relocate (Not Running).

    To relocate multiple instances at once, choose Start of the navigation pathMass Operations Next navigation step Relocate (Not Running)End of the navigation path and ensure that the entities on which you want to execute the operation are displayed and selected.

  4. Assign a host to each instance or choose Host Assignment and one of the following options:
    Option Description

    Preferred

    Assign a preferred host that you have set for an instance.

    • If the instance is in status Not running Not Running or Running Running, the currently assigned host is set as the preferred host.

    • If the instance is in status Initial Initial, the host assignment is not applicable.

    • If the preferred host is not available or locked, no host is automatically assigned to the instance.

    Last Used

    Assign the last used host to the instance. If the last used host is not available, SAP Landscape Management assigns the first fit host.

    First Fit

    Assign the first available free host to an instance.
  5. Optional: SAP Landscape Management checks if the host assigned to the instance meets the requirements of the instance. These requirements include RAM, SAPs, and so on. To ignore this host check, select the Ignore Host Check checkbox.
  6. Optional: SAP Landscape Management checks if intersystem dependencies are defined, and either performs the necessary action or prompts you to decide whether to proceed with the operation. To ignore any intersystem dependencies, select the Ignore Intersystem Dependencies checkbox.
  7. Optional: Select the Set Note checkbox and enter a note to be displayed in the Description column of the instance.
  8. Choose Execute.

Results

Unprepare
    • For database instances:
      1. Unregisters the database from the operating system.
      2. Detaches the database from the host. That is, stops the database listeners, if necessary.
      3. Creates configuration files required for an attach process during a prepare operation.
    • For SAP instances that do not represent a database:
      1. Stops the instance agent
      2. Unregisters the instance agent from the operating system.

        • For Unix-like systems: Removes the agent from file /usr/sap/sapservices

        • For Windows systems: Removes the agent from the Windows service registry

    • For custom instances:
      1. Performs necessary actions to unregister the instance on the host.
      2. Calls operation acc_<custom instance type>_detach.
      3. No processes of the custom instances are running.
  2. Unbinds virtual IP addresses or unmounts the file systems configured.

    If the potential SAP HANA master node is relocated and there are tenants with virtual hostnames registered on this host, they will be unbound.

    When you unprepare an SAP HANA tenant database node:

    • Checks if this node is a potential master host.

    • If the node is a potential master host, unprepares the virtual hostnames of all tenants which have virtual hostnames registered on the SAP HANA tenant database node.

  3. Calls the storage adapter or virtualization adapter to unprepare the IP addresses.
  4. The instance status is Initial Initial.
  5. Receives service port bindings needed for an attach operation.
Prepare
  1. Calls the storage adapter or the virtualization adapter to prepare the IP addresses.
  2. Binds virtual IP addresses and mounts the file systems configured.
    When you prepare an SAP HANA tenant database node:

    • Checks if this node is a potential master host.

    • If the node is a potential master host, prepares the virtual hostnames of all tenants which have virtual hostnames registered on the SAP HANA tenant database node.

    If the potential SAP HANA master node is relocated and there are tenants with virtual hostnames that need to be registered on this master node, they will be bound.

    • For database instances:
      1. If database instances were unprepared using SAP Landscape Management, writes the respective service entries if not present.
      2. Attaches the database to the host. That is, registers the database with the operating system.
      3. If necessary, starts the database listeners.
    • For SAP instances that do not represent a database:
      1. If an SAP instance was unprepared using SAP Landscape Management, writes the respective service entries if not present.
      2. Registers the instance agent with the operating system.

        • For Unix-like systems: Adds the agent to file /usr/sap/sapservices

        • For Windows systems: Adds the agent to the Windows service registry

      3. Starts the instance agent.
    • For custom instances:
      1. Calls operation acc_<custom instance type>_attach.
      2. Performs the necessary actions to register the instance on the host.

  4. The instance status is Not running Not Running.

Related Information