MCD DB BB HANA ST Hardware Migration

- Replication Method Preparation

Document Details

Classification: SAP INTERNAL Status: COMPLETE Access: <DEFINE> This Version: N/A
Published Version: N/A SPC Task Owner DB Team: NAME

TinyURL = https://wiki.wdf.sap.corp/wiki/x/I8b5d Content Owner = Kamalnath

Vadapalli Expiry date =EXP_2019_12

Note: Please use comment function to provide the reason for the requested action.

Report Page Options

Note: Only MCD GSS DB L3 is intended to use review options.

Review Page Options

ON THIS PAGE

 I. Description
 II. RACI Matrix
 III. Preperation Steps
 IV. References

I. Description
This page describes the preperation steps to be done for Hardware Migration using Replication
Method.

II. RACI Matrix

This part contains a RACI Matrix

Responsible 2L DB Team
Accountable 3L DB Team
Consulted 3L DB Team , 2L DB Team
 Informed 3L DB Team , 2L DB Team

III. Preperation Steps

DO NOT STOP the Source Primary System in any case for any of the Below Preperation Steps.

DB Team to do the following atleast 3 days before the downtime.

St Action
Description Command to Check Action
ep Required If
  Inform
TL
Immediat
ely
through
SPC
ticket that
the
topology
is not
matching .
 Topology
should be
matched/
Corrected
to proceed
with the
request
using
Topology Checking number of Nodes: Replicatio
Source &
Check: n
Login as <sid>adm Target
Approach
System
Source and .
1 cdpy doesnt not
Target System python have
should be of landscapeHostConfiguration.py  Dependin
number of
the same g on the
nodes.
Topology (on Source & Target) Topology
difference
,
Necessary
corrective
action to
be done
match the
Source
Topology.
 Inform
TL and
Engage
3L DB
team
incase of
further
assistance
required.
 1. Sour Actions for
ce Issue#1
Syste
m  Check if
has the SPC
Repli Ticket has
catio confirmati
n on from
Enab TL that
led Existing
& replicatio
also n on
Targ Source
et System
has can be
Repli disabled
catio 24hrs
Replication n Before the
Check : enabl downtime
Login as <sid>adm
Source System ed . If Not ,
hdbnsutil -sr_state Request
2. Sour TL to
Check if ce
2 on Source (primary) & on confirm
Source & syste
Target(Primary) the same
Target system m by
has has
if mode = none , Replication is NOT updating
Replication Repli
enabled the ticket
enabled catio and
(HA/DR) n moving it
Enab to TL
led componen
& t
Targ
et  Disable
Syste the
m Replicatio
does n ONLY
nt on Target
have System .
Repli Follow
catio Wiki →
n 05 - MCD
enabl DB BB
ed HANA
(no Disable
detai system
ls replicatio
abou n
t
Targ
et
syste Action for
m Issue#2
HA/
DR )  Check if
the SPC
Ticket has
details
about
Target
system
HA/DR
If not
available
inform TL
that there
are no
details
about
HA/DR
for Target
system . If
not
provisione
d , same
should be
requested
by TL to
SM team.
 Action for
issue#1:

Downgrade (Re-
install) the Target
system if the
1. Versi
Target system is
on is
on Higher
not
Version when
the
compared to
same
Source System.
as
Checking if SID , Instance number & Follow Wiki →
sourc
DB Version are same : MCD DB BB
e
HANA
Syste
Login as <sid>adm. Downgrade
m.
2. Insta
SID Check: Upgrade the
================= nce
system if the
DB Version , env | grep -i "SAPSYSTEMNAME" Num
Target system is
SID & ber
Instance Number Check: on Lower
Instance Num is
================================ Version when
Check: =
not
compared to
env | grep "DIR_INSTANCE" the
3 Source System.
Source and same
Follow Wiki →
Target System format of DIR_INSTANCE --> Sour
DIR_INSTANCE=/usr/sap/<SID>/HDB< MCD DB BB
should be of ce
InstanceNumber> HANA Upgrade -
the same syste
Manual DB
Version m.
upgrade
DB Version Check: 3. SID
========================= is
HDB version
not
the
(on Source & Target) Action for
same
Issue#2 (
as
Sour
If Target system
ce
doesnt have the
Syste
same instance
m.
number. rename
the Instance
number . Follow
Wiki → MCD
DB BB HANA
IM Rename
instance ID
Action for
Issue#3:

If the SID doesnt

Match with
Source system .

Uninstall &
Install the
database . Follow
Wiki → MCD
DB BB HANA
Downgrade

Before this SM
team has to
rename the
filesystems to
match the SID.

Note :
Downgrade (or)
Upgrade should
be on HA/DR
sites if existing
onTarget system
accordingly
 Login to the database using SYSTEM
user on Source & Target System.

Non-MDC:-
====================
SELECT * FROM M_INIFILE_CONTENTS
WHERE
FILE_NAME = 'global.ini' AND
LAYER_NAME =
'SYSTEM' AND SECTION = If Source Enable
Encryption 'persistence' AND KEY = System has Encryption on
Check : 'data_encryption' AND VALUE = Encryption Target System.
'TRUE';
Enabled but
4 Check if MDC:- Target Follow Wiki →
Source system ==================== system MCD DB AC
has Encryption SELECT * FROM doesnt have HANA Data
SYS_DATABASES.M_INIFILE_CONTENTS
Enabled Encryption Volume
WHERE FILE_NAME = 'global.ini'
AND SECTION = Enabled Encryption
'persistence' AND KEY =
'data_encryption' AND VALUE =
'TRUE';

No Records would mean Encryption

is NOT enabled.
Some or All
Login to the database using SYSTEM Plugins Install the
Plugin Check : user on Source & Target System. existing on required Plugins
Source
5 Check for select distinct(plugin_name) system are Follow Wiki →
Plugins on from M_PLUGIN_MANIFESTS; not MCD DB BB
Source System Available on HANA IM Add
(on Source & Target ) target Plugins
System.
Correct the
Timezone On
Timezone
Target system to
Check: Login to <sid>adm Match with
Timezone is
Source System /
Check if Option 1: date Not Same as
Application host .
Target System Option 2 : env | grep TZ Source
6 Follow Wiki →
has the same System
(on Source & Target) MCD DB BB
timezone as
HANA
Source System
TimeZone
Setting
 Install the
components on
Additional
Target System.
Software on
Source DB
Depends on the
Host: Check SPC ticket if TL has provided type of
details about additional component. Additional
Check if TL
If Components.
has mentioned For SDA connectivities check the Additional
about any source system using the below query Components Following Wikis
additional
exist on can be referred
Components/S Login to the database using SYSTEM Source accordingly.
7 oftware user on Source system & execute the System
installed on below. For Further
the Source
Client assistance Reach
System(DB
Installations 3L DB Team.
clients like
:
Sybase , select distinct
MCD DB BB
MSSQL etc REMOTE_SOURCE_NAME,ADAPTER_NAME
from M_REMOTE_CONNECTIONS HANA Smart
which are
Data Access
installed on
the Source
MCD DB BB
DB)
ASE ST Client
Installation

DB Team to do the following Only 24 Hrs before the downtime. ( Check if Confirmation is
given by TLO in the Ticket)

Step Activity Description Wiki Link

ONLY TO BE Done if source
system has replication
enabled:
Disable Disable Replication → 05 -
8 Replication on Break the replication from MCD DB BB HANA Disable
Source System primary to HA/DR on Source system replication
System.
 Enable Replication → 03 -
MCD DB BB HANA HSR
Setup HA ---- To be marked
Enable Replication from for delete
Source system to Target
Enable
System. Under Validation :
Replication
9 from Source
Monitor the Replication sync Automated Procedure is being
System to
and ensure it is completed and evaluated if this can be used
Target System
is in Active Status before in this scenario : "ACE8727 :
downtime HEC: HANA UNX HSR
ENABLEMENT "

For >= SPS12 , Replication

parameters can be copied
automatically after enabling
the replication after setting the
required parameters on Source
MCD DB BB HANA
Match the System . (Refer Wiki)
10 Parameter mismatch in
parameters
Replicated systems
For < SPS12 , parameters have
to be copied manually . How to
find the parameters which
needs to be copied → (Refer
Wiki)

Once the preperation steps are complete

 Update the ticket with the status .

 Move the ticket to SAF team to stop the applications as per the scheduled downtime and
move the ticket back to DB team for migration .
 Monitor the Replication sync and ensure it is completed and is in Active Status before
downtime

IV. References
Type Link
Wiki
Note
Ticket
KT
Training