Vmware Adapter for sap landscape Management Administration Guide for LaMa Administrators OpenTopic

n

Note that DHCP customization specifications may cause an inconsistent 

/etc/hosts

file contents in the target system. PROMPT customization specifications is a more

reliable option. See section 

“Known Issues,”

 on page 53 for more information.

c

Click on the Next tab to move to the next step.

4

In this step called Network Adapters, you select the target Network for the network adapters

of the new copy VM.

Figure 4

‑39.  Define Virtual Host - Network Adapters

n

If you are going to change the virtual network on this step, ensure that the network is also

available to the LaMa. This is needed for the LaMa to be able to manage the new target

system.

n

Changing the virtual network should be considered on the Host Names step in order to

assign the consistent IP addresses and hostnames from a new network.

5

Click Next to move to the next step called Host Names.

Figure 4

‑40.  Define Virtual Host - Host Names

You do not need to provide any input in this step.

6

Click the Next tab to move to the Summary step.

Chapter 4 Operations Overview

VMware, Inc. 

 43

---

Figure 4

‑41.  Define Virtual Host - Summary

Review the various settings that you have chosen so far. You can use the Previous tab to go

back and make appropriate changes, if required. When you are satisfied with the settings and

are ready to proceed further, Click the Define tab to finish defining the new virtual hist

settings.

c

You are now back at the System Copy window.

Figure 4

‑42.  System Copy - Hosts

Click Next tab to proceed to the third step in the System Copy window, called Host Names.

VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators

44 

 VMware, Inc.

---

Figure 4

‑43.  System Copy - Host Names

In this step you may choose a different network for each component of the target SAP system.

Note   If the host is not configured as adaptive instance you will see warnings that you need to

ignore by pressing Ignore Warnings for this step button.

Click Next tab to move to the next step.

d

Figure 4

‑44.  System Copy - Instance Number

In this step called Instance Number, you select the instance number for the SAP instances and then

Click Next.

e

You now move to the step called Consistency. In this step you select the appropriate database

consistency method, depending on what state the database is in, by Clicking on the radio button

against one of the following option —

Figure 4

‑45.  System Copy - Consistency

1

Online: Backup/Suspend IO Mode with a timeout value — Use this option typically for

copying production systems to prevent system outages. A timeout value is provided to ensure

database consistency is done in a timely manner.

Chapter 4 Operations Overview

VMware, Inc. 

 45

---

2

Offline: Stop and Restart System — When you select this option, the SAP LaMa will stop the

system, take the copy and then restart the system after the copy completes.

3

Offline: Database already stopped — Use this option when the database is already stopped.

4

Database was stopped during system snapshot — Use this option when the database has

already been snapshotted prior to initiating the copy process.

5

There is also an option to schedule the cloning operation from here so not to impact the system

activity further at the current instant. You can provide the values for date and time to schedule

the operation.

Note   Offline linked copy of SAP HANA on SLES must be performed with closed hbdstudio on

source machine.

When you have selected one of the options mentioned above, Click Next to proceed to the next

step.

f

Figure 4

‑46.  System Copy - Users

In this step called Users, you can review the new users that will be created on the target system.

Note   For the Copy process the SAP LaMa copies the users from the source system over to the

target system changing them to match with the new System ID.

Click Next to proceed further.

VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators

46 

 VMware, Inc.

---

g

Figure 4

‑47.  System Copy - Rename

In this step called Rename, you can see the target system naming convention.

Note   Observe that the SAP LaMa takes the source system ID and swaps it out for the new target

system ID. Click the Next tab to proceed to the next step.

h

Figure 4

‑48.  System Copy - Isolation

In this step called Isolation, you can choose to isolate the new target system from the source

system. You do this by selecting the appropriate radio button under section Unfence target system

after system copy/refresh. This will prevent it from accidentally communicating as the source system.

Click Next tab to proceed to the next step.

i

Figure 4

‑49.  System Copy - ABAP PCA

In this step called ABAP PCA (Post Copy Automation), you can choose to either enact ABAP PCA

or by-pass it. If you indeed plan to use PCA, choose the appropriate parameters to apply. If no PCA

will be used, then you must uncheck that option and further Click the Ignore Warnings for this step

to proceed. Click Next to proceed.

j

In this step called Summary, you get to see the consolidated view of all the settings you have made

so far. When you are done reviewing the settings, you Click on Start System Copy tab to initiate

the copy operation.

Chapter 4 Operations Overview

VMware, Inc. 

 47

---