Skip to Content
Virtualization

LVM Provisioning Template - Copy

Tags:

Official Product Documentation: System Copy Template Steps

The following template steps are executed during system copy with SAP NetWeaver Landscape Virtualization Management:

Template stepDescriptionDependent stepsProperties
Create Computer System ConfigCreates a configuration for the new host in landscape virtualization management (LVM).none
Create System ConfigCreates a configuration for the new system in LVM.
Stop SAP InstanceStops source SAP instance. Relevant only for offline system copy.
Stop DatabaseStops source database instance. Relevant only for offline system copy.
Prepare DatabasePrepares source database for system copy.
Finalize DatabaseThis operation will do necessary postprocessing steps after copy of DB.
PROVISIONProvisions a new host. Used only in scenarios, that provisioned host (VM based and storage based).
STARTActivates/starts the host provisioned in the previous step.This step is used only in scenarios, that provisioned host (VM based and Storage based).
WaitForResourceStateWaits for host to be available in the Virtualization Manager.This step is used only in scenarios, that provisioned host (VM based and Storage based).
AddResourceAdds newly provisioned host into LVM configuration.This step is used only in scenarios, that provisioned host (VM based and Storage based).
Unprepare DBUnprepares a database instance.This step is used only for provisioning VM based systems.
Start DatabaseStarts source system database.

Storage based systems:

Clone Volumes - system copy provisioning

VM based systems:

Start SAP InstanceStarts source system instance.

Storage based systems:

VM based systems:

Prepare Clone VolumesPrepares volumes in the storage that will be used for new system after the system copy process is finished.This step is used only for provisioning storage based systems.
Mount ORA Redo LogsMounts a directory for Oracle Redo logs. Applicable only for systems with Oracle database.
Clone Volumes With DB Backup ModeCreates new volumes in storage that will be used for new system after the system copy process is completed.– In case the online copy scenario is executed for storage based systems
Clone Volumes - system copy provisioningCreates new volumes in storage that will be used for new system after the system copy process is completed.
Post Clone VolumesChecks if new volumes exist and exports paths for them in the storage system. This step is used only for provisioning storage based systems.
Umount ORA Redo LogsRemoves already mounted directory for Oracle redo logs. Applicable only for systems with Oracle database.
Update Instance Mount ConfigUpdates mount points into system configuration in LVM. This step is used only for provisioning storage based systems
Finalize Clone VolumesMakes final split of new volumes if it is required. This step is used only for provisioning storage based systems.
Clear CacheClears cache of the operation system on the host.

Storage based systems:

VM based systems:

Prepare DBPrepares target database for system copy.
Prepare SAP InstanceActivates virtual hostname on a host, mounts volumes from storage (created in previous steps) on a host, and checks the status of instance and diagnostics agents.This step must be executed for each application server instance.
System FencingModifys firewall rules in IP tables of the operating system (OS) to ensure system is fenced and decoupled from the network.
Create UsersCreates all needed users for OS access to new system. They can be created in LDAP or locally.
Check MountsChecks if mount points created on OS of the hosts are working and file system is accessible

Storage based systems:

VM based systems:

Change Profile PCA EnableAdds parameters and values to the profile. So the post-copy automation operation will be enabled.
Mount ORA Redo LogsMounts directory for Oracle Redo logs. Applicable only for systems with Oracle Database
ExecuteOperation/Host_AgentExecutes specified hook.
SAPINST renameCalls Software Provisioning Manager tool to perform a copy of the original system. Then renames it to a new one called target system and changes the files ownership to target user in target host. If all instances are running on the same host, then there will be only one SAPinst step. If instances are running on different hosts, then tthe number of SAPinst steps are equal to the number of different hosts.
System FencingRestores back the original rules in IP tables of the operating system to allow access to the network again after the new system was created with different name and hosts.

Storage based systems:

VM based systems:

Start DatabaseStarts the database of the new system.
Start SAP InstanceStarts SAP central instance of the new system.
Start SAP InstanceStarts SAP instance of the new system and must be executed for each application server instance.
Remove DirectoryClears files and directories created from Software Provisioning Manager.

Storage based systems:

VM based systems:

Post System Copy AutomationRuns post-copy automation to perform initial setup of the new system. Applicable only for NetWeaver ABAP system.

Storage based systems:

VM based systems:

Java Post System Copy AutomationRuns post-copy automation to perform initial setup of the new system. Applicable only for NetWeaver Java system.

Storage based systems:

VM based systems:

Change Profile PCA RevertRemoves changes in profile files made from step “Change Profile PCA Enable”  or set the default values to the parameter in profile.

Storage based systems:

VM based systems:

Umount ORA Redo LogsRemoves already mounted directory for Oracle redo logs.
Activate SystemPerforms final enablement of system to be ready for monitoring in LVM.

Storage based systems:

VM based systems:

back to top

No comments