Week 2 Unit 1: Introduction to Near-Zero Downtime Maintenance … · 2018-04-06 · Introduction to Near-Zero Downtime Maintenance (nZDM) for Java nZDM is available for… SAP Enterprise

Week 2 Unit 1: Introduction to Near-Zero

Downtime Maintenance (nZDM) for Java

Public© 2016 SAP SE or an SAP affiliate company. All rights reserved. 2

Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaBusiness needs

Business downtime is

critical and costly

Maintenance Windows:

How many per year?

How long will it take?

Most scenarios have to support

distributed business landscape

with minor downtime windows

Message queues to production

or transport logistics allow only

small maintenance windows

Stability and security

improvements are executed at

regular intervals

B2B


Introduction to Near-Zero Downtime Maintenance (nZDM) for JavanZDM Java procedure benefits

Perform maintenance

activities with drastically

optimized downtime

Ability to keep business-

critical functions running

during maintenance

Ability to perform

maintenance testing

without downtime

Supports great number

of maintenance activities

Great flexibility in

adapting the procedure

to different landscapes

and needs

No additional charge for

using the nZDM Java

procedure

various updates

uptime testing

reduced downtime

flexibility system availability

built-in

nZDM

Java


Prepare Maintain Switch Post-processuptime uptime downtime uptime

PRD

RESTART

PRD*

RESTART

Approach 1

Approach 2

Database Switch

System Switch

switchrole

switchcontent

PRD

PRD

PRD*

STOP

PRD*

STOP

PRD

STOP

PRD

STOP

PRD*PRD*

Maintenance (i.e. update

with SAP Software Update

Manager) and testing

nZDM Java replication

PRD

REC

PRD

REC

PRD

REC

Production system

REC

PRD

nZDM Java recording

PRD*

Isolated clone system

with same SAP SID and

hostname(s)

clonePRD

REC

Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaMain phases of the procedure

Maintenance (i.e. update

with Software Update

Manager) and testing

Production system

switchcontent

PRD*clone

REC

PRD

nZDM Java recording

PRD*

Isolated clone system

with same SAP SID and

hostname(s)

PRD*PRD

REC

PRD*PRD switchrole

PRD*

PRD*PRD

STOP

STOP

PRD*

PRDPRD

STOP

PRD*

PRD*PRD

STOP

nZDM Java replicationDatabase switch

System switch

RESTART

Approach 1

Approach 2

RESTART

SwitchPrepare PostprocessMaintain uptimeuptimeuptime downtime


Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaTimeline of the procedure

Clo

ne c

reati

on

an

d is

ola

tio

n

2

3

Various maintenance activities

Production operation

Old

version

Ramp down

6

Phase out

7

Production

operation

8

Old

version

Old

version

1 Start recording on the source

Old

version

New

version

Time t1 t2 t3 t4

5

System or DB switch

4

Technical validationnZDM UI

for Java


PRD*

DB

ASnZDM Java

PRD*

ASnZDM Java

PRD

PRD

DB

REC

Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaSet-up of the procedure

AS

nZDM Java

PRD

PRD

DB

AS

nZDM Java

PRD*

PRD*

DBnZDM Java

replicationProduction

system

REC

PRD

nZDM Java

recording

Production

system

REC

PRD

nZDM Java

recordingnZDM Java

replication

REC

nZDM Java GUI/CLI


Introduction to Near-Zero Downtime Maintenance (nZDM) for JavanZDM Java automation

SAP Landscape Management offers

integration with nZDM for Java that

can be used to automate

maintenance procedures for Java-

based applications

The automated nZDM cloning

procedure includes fencing the

cloned system (network isolation)

After nZDM maintenance, SAP

Landscape Management can swap

these two systems and promote the

cloned system to become the new

production system

Landscape Management


Introduction to Near-Zero Downtime Maintenance (nZDM) for JavanZDM automation – Command line interface

The nZDM command line interface

is provided as a method for

automation as part of scripts or

commands of a high-level

orchestration tool

The CLI client is installed with the

nZDM GUI and connects remotely

to both nZDM source and target

systems


Introduction to Near-Zero Downtime Maintenance (nZDM) for JavanZDM is available for…

SAP Enterprise Portal (SAP EP)

SAP NetWeaver 7.0 EHP 2, SP11 or higher

SAP NetWeaver 7.3, SP7 or higher


SAP NetWeaver 7.4

SAP NetWeaver 7.5

SAP Business Process Management (SAP BPM)

SAP NetWeaver 7.3, SP7 or higher


SAP NetWeaver 7.4

SAP NetWeaver 7.5

SAP Process Orchestration (SAP PRO)


SAP NetWeaver 7.4

SAP NetWeaver 7.5

Database Support

SAP HANA

SAP ASE

MS SQL Server

Oracle

IBM DB2 for LUW

SAP MaxDB (SAP EP only)


Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaCustomer use cases (I)

Ramp

down

Upgrade SAP

Process Orchestration

Ramp

up

Ramp

up

nZDM

preparationRecording

Ramp

down

Uptime Downtime Uptime

Preparation

activitiesDB upgrade

Technical

post MA

Online

replication

Ph

ase

ou

tS

ys s

witch

Go/

No

-Go

Backup &

restore point Go/

No

-Go

Sta

nd

ard

meth

od

nZ

DM

fo

rJava

Post activities

Uptime Downtime Uptime

DB upgradeUpgrade SAP

Process Orchestration

Post activities

Technical

post MA

Target

system


Introduction to Near-Zero Downtime Maintenance (nZDM) for JavaCustomer use cases (II)

New SAP Process

Orchestration

New DB

version

New OS

version

Thank you

Contact information:

[email protected]


© 2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate

company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its

affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and

services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as

constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop

or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future

developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time

for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-

looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place

undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx

Week 2 Unit 2: nZDM for Java

in More Detail


nZDM for Java in More DetailApproaches comparison

System Switch

Easy to use with existing virtual environment

Most effective approach regarding downtime

Fully integrated in LVM

OS and DB updates are possible

Lower resource consumption and performance impact on the source system

Database Switch

Useful when production system has a complex setup (e.g. HA) or has a big

DB size

Minimum modification of existing setup

OS and DB updates are not possible

Higher resource consumption and performance impact


nZDM for Java in More DetailConsiderations

Additional hardware

Load and space aspects

Separate host for GUI/CLI (Windows or Linux)

Online method for cloning should be in place

Isolation

Pretest is recommended


nZDM for Java in More DetailSample nZDM procedure: Prepare source (I)

Uptime

Make sure no other maintenance

activities are planned on the systems

Switch the system to “Business Only”

mode

Original system

Java AS

Java SCS

Database


nZDM for Java in More DetailSample nZDM procedure: Prepare source (II)

Uptime

Download nZDM GUI from SAP

Service Marketplace and install it on

a separate host

Run and connect the nZDM GUI/CLI

to the production (source) system

Use nZDM GUI/CLI to start nZDM

recording

Source system

Java AS

Java SCS

Database

nZDM service

nZDM

GUI / CLI


nZDM for Java in More DetailnZDM recording – DB triggers and table classification

Three types of tables in the source DB

Whitelist – no triggers

Greylist – recording triggers

Frozen – freeze triggers

Option to classify tables manually

Source system

Java AS

Java SCS

Database

nZDM service

nZDM

GUI / CLI


nZDM for Java in More DetailSample nZDM procedure: Create target (I)

Uptime

Clone the source system to a

separate network location

The cloning should be done without

stopping the source system

Cloned system

Java AS

Java SCS

Database

Source system

Java AS

Java SCS

Database

nZDM

GUI / CLI

nZDM service


nZDM for Java in More DetailSample nZDM procedure: Create target (II)

Uptime

Isolate the target

Start the target system.

It will run in “nZDM target” mode

Target system (isolated)

Java AS

Java SCS

Database

Source system

Java AS

Java SCS

Database

nZDM

GUI / CLI

nZDM service


nZDM for Java in More DetailCreate target – System isolation prerequisites

Source/production system should not be

stopped during cloning or fencing

Target/clone system should be able to run

in parallel with the source system

At least one of the application servers of

the source and target systems should be

accessible from the location where the

nZDM GUI is located

Same application server should be

accessible from the target application

server

The database of the source system should

be accessible from the same application

server of the target system


Java AS

Java SCS

Database

Source system

Java AS

Java SCS

Database

nZDM service nZDM service

nZDM

GUI / CLI


nZDM for Java in More DetailCreate target – System isolation possible options

After the online cloning of the source system is done, we

need to start it without conflicts. Here are two options:

Change the hosts/IPs of all the parts – DB, SCS, app

servers

Isolate/fence the target system and run the target system

without changes to its hosts or IPs

Other…


nZDM for Java in More DetailSample nZDM procedure: Prepare target (I)

Uptime

Preform planned maintenance

activities on the target system


Java AS

Java SCS

Database

Source system

Java AS

Java SCS

Database

nZDM

GUI / CLI

nZDM service


nZDM for Java in More DetailSample nZDM procedure: Prepare target (II)

Uptime

Connect the nZDM GUI/CLI to the

target system and start nZDM

replication

Wait for the number of replicated

records to get close to the amount of

recorded data

Prepare/wait for system downtime


Java AS

Java SCS

Database

Source system

Java AS

Java SCS

Database


nZDM

GUI / CLI


nZDM for Java in More DetailSample nZDM procedure: Switch systems

Downtime

Choose to finish the nZDM procedure

Stop the target system when nZDM

replication is complete

Remove isolation of the target and

start it as the new production system

End of downtime


Java AS

Java SCS

Database

Source system (stopped)

Java AS

Java SCS

Database

nZDM service

nZDM

GUI / CLI


nZDM for Java in More DetailSample nZDM procedure: Post processing

Uptime

Revert any changes done to make

the system run in “Business Only”

mode

Upgraded system

Java AS

Java SCS

Database

Thank you


[email protected]



















Week 2 Unit 3: nZDM Java in a

Cluster Setup


nZDM Java in a Cluster Setup Cluster split: Prepare source

Uptime

Switch the system to “Business

Only” mode

Download the nZDM GUI from SAP

Service Marketplace and install it on

a separate host

Run and connect the nZDM GUI/CLI

to the production (source) system

Use nZDM GUI/CLI to start nZDM

recording

Original system (HA/DR)

Java AS

nZDM service

nZDM

GUI / CLI

SAP WD SAP WD

Java SCS SAP SCS

Java ERS SAP ERS

Database Database


Source system

nZDM Java in a Cluster Setup Cluster split: Prepare source

Uptime No HA/DR

Remove a node from the cluster

without stopping the source

Isolate it from the network if needed

Build an nZDM target system out of itJava SCS Java SCS

Java ERS Java ERS

Database Database

SAP WD SAP WDJava AS

nZDM service

nZDM

GUI / CLI


Source system

Java SCS

Java ERS

Database

SAP WD

Target system

nZDM Java in a Cluster Setup Cluster split: Prepare target

Uptime No HA/DR

Perform planned maintenance




replication


Java AS

nZDM service

Java AS

nZDM service

Java SCS

Java ERS

Database

SAP WD

nZDM

GUI / CLI


nZDM Java in a Cluster Setup Cluster split: Switch systems

Downtime

Choose to finish the nZDM

procedure




start it as the new production

system

End of downtime

Source system (stopped)

Java SCS

Java ERS

Database

SAP WD

Target system

Java AS

Java AS

nZDM service

Java SCS

Java ERS

Database

SAP WD

nZDM

GUI / CLI


Upgraded system

nZDM Java in a Cluster Setup Cluster split: Postprocessing (I)

Uptime No HA/DR



mode

Reconnect the application servers

to the updated systemJava SCS

Java ERS

Database

SAP WDJava AS

Java SCS

Java ERS

Database

SAP WD


Upgraded system (HA/DR)

nZDM Java in a Cluster Setup Cluster split: Postprocessing (II)

Uptime

Recreate the HA/DR cluster

Java AS

Java SCS

Java ERS

Database

SAP WD

Java SCS

Java ERS

Database

SAP WD


nZDM Java in a Cluster Setup Cluster split: Summary

Very few additional HW resources needed

HA/DR setup is broken early and recreated after the

downtime

HA/DR cluster setup can’t be tested during uptime

Higher complexity Higher consultancy costs

More difficult for automation


nZDM Java in a Cluster Setup Cluster clone: Prepare system

Uptime

Switch the system to “Business Only”

mode

Download the nZDM GUI from SAP

Service Marketplace and install it on a

separate host

Run and connect the nZDM GUI/CLI to

the source (production) system

Use the nZDM GUI/CLI to start nZDM

recording

Original system (HA/DR)

Java SCS Java SCS

Java ERS Java ERS

Database Database

SAP WD SAP WD

Java AS

nZDM service

nZDM

GUI / CLI


Target system (isolated)Original system (HA/DR)

nZDM Java in a Cluster Setup Cluster clone: Create target

Uptime

Clone the source system

Isolate and start the clone as the

target system

Java SCS Java SCS

Java ERS Java ERS

Database Database

SAP WD SAP WD

Java AS

nZDM service

Java SCS Java SCS

Java ERS Java ERS

Database Database

SAP WD SAP WD

Java AS

nZDM

GUI / CLI


nZDM Java in a Cluster Setup Cluster clone: Prepare target

Uptime

Preform planned maintenance




replication


Target system (isolated)Original system (HA/DR)

Java SCS Java SCS

Java ERS Java ERS

Database Database

SAP WD SAP WD

Java AS

nZDM service

Java SCS Java SCS

Java ERS Java ERS

Database Database

SAP WD SAP WD

Java AS

nZDM

GUI / CLI

nZDM service


nZDM Java in a Cluster Setup Cluster clone: Switch systems

Downtime

Choose to finish the nZDM

procedure




start it as the new production

system

End of downtime

Target system (isolated)Original system (stopped)

Java SCS

Java ERS Java ERS

SAP WD

Java AS

Java SCS Java SCS

Java ERS Java ERS

Database Database

SAP WD SAP WD

Java AS

nZDM

GUI / CLI

nZDM service

Java SCS

SAP WD

Database Database


nZDM Java in a Cluster Setup Cluster clone: Postprocessing

Uptime



mode

Upgraded system (HA/DR)

Java AS

Java SCS Java SCS

Java ERS Java ERS

Database Database

SAP WD SAP WD


nZDM Java in a Cluster Setup Cluster clone: Summary

About twice as many HW resources needed

The system keeps its HA/DR setup at all times

(except system downtime)

HA/DR cluster setup may be tested during uptime

Simplicity (compared to cluster split approach)

Easier for automation


nZDM Java in a Cluster Setup Maintenance activities: Software Update Manager (SUM Java)

Maintenance activities with SUM Java

Software Update Manager is the SAP tool

for maintenance of SAP NetWeaver-based

systems


nZDM Java in a Cluster Setup SUM Java procedure: Supported maintenance activities

Release upgrade (major release change)

System update (EHP installation)

Applying support packages (SPs) / support package

Applying Java patches

Correction of installed software information

Up-to-date installation

UP


nZDM Java in a Cluster Setup SUM Java procedure: Benefits

Improved user experience and unified capability

Transparency about source system state, installed products,

and content to be updated

Overview of process details upon and after SUM procedure

Extended prerequisite checks to optimize the stop-and-start

procedure of instances

Reduced downtime

Thank you


[email protected]



















Week 2 Unit 4: End-to-End nZDM –

Java Procedure Execution


End-to-End nZDM – Java Procedure Execution Demo scenario: Cluster clone

Download and run the nZDM GUI

Connect the nZDM GUI to the source system

Start recording

Clone the source system and isolate the clone (target)

Start the target system

Perform an update using SUM Java

Connect the nZDM GUI to the target system

Start replication

Finish the procedure from the nZDM GUI

Remove target system isolation

Start the target system as the new source


End-to-End nZDM - Java Procedure ExecutionDemo set-up: Cluster clone

nZDM Java GUI

Source system

Target system

Start recording

Landscape view

Landscape View nZDM GUI

Source System Target System

Thank you


[email protected]



















Week 2 Unit 5:

Troubleshooting & Wrap-Up


Troubleshooting & Wrap-UpSummary

nZDM minimizes business downtime during

maintenance of SAP NetWeaver Java-based products

It enables availability of business-critical functionality

during maintenance

Downtime – around one system restart

Flexible, clone-based procedure

SAP Landscape Management, cloud virtualization

SWPM (system copy scenario)

Integration with SAP Landscape Management, CMD

interface

nZDM allows preliminary testing of updated cloned

system during uptime


Java AS

Java SCS

Database

Source system

Java AS

Java SCS

Database


nZDM

GUI / CLI


Troubleshooting & Wrap-UpnZDM Java GUI

If Java GUI loses connection, it tries to

reconnect automatically

If auto reconnection fails or you need to close

the GUI, restart it and manually reconnect

no impact on the nZDM Java procedure

execution

If the GUI loses connection during the

finalization of the procedure, you have to enter

the same connection data for the source

system as for the target system


Troubleshooting & Wrap-UpLogs

All messages from the nZDM Java procedure are

stored in defaultTrace_<number>.trc and

applications_<number>.log files

They are located at:

<Drive>:\usr\sap\<SID>\<instance_name>\<Jxx or

JCxx>\cluster\server0\log

Check the latest defaultTrace_<number>.trc and

applications_<number>.log files for each system

instance. This is valid for the source system and

the target system, if the latter has already been

created

You can find the nZDM GUI/CLI logs under

<NZDM JAVA_dir>\java\log


Troubleshooting & Wrap-UpFurther analysis – DB tables

To perform further analysis, you can also check the following

database tables in your source or target system

BC_NZDM_STATE

BC_NZDM_CHANGE_LOG

BC_NZDM_ERROR_LOG


Troubleshooting & Wrap-UpRecording vs replication errors

Recording errors:

Fatal to the nZDM Java procedure

Recording in the source system is aborted

You have to reset the nZDM Java procedure and

start over from the beginning

Replication errors:

Non-fatal

Replication is stopped

Might be able to resolve the issue and resume

the replication

In the worst case, your target system might be

unusable

If this is the case, you have to create a new

target system and repeat all steps from that point


Troubleshooting & Wrap-UpResetting the nZDM Java procedure

Connect the nZDM Java GUI to the source

system

If the recording has started, choose Abort

Recording. Shortly after, the button changes to

Reset nZDM

Reset the nZDM Java procedure by choosing

Reset nZDM. This also resets the nZDM Java

GUI

Start the procedure from the beginning


Troubleshooting & Wrap-UpInvestigating on the source system

After you have finished the nZDM Java

procedure, your target system will be your new

production system. The source system will be

stopped.

If you need to gain access to the source system

to have some issue investigated there, it is

crucial to isolate it beforehand, the same way

you isolated the target during the procedure.


Troubleshooting & Wrap-UpAdditional resources

support.sap.com/sltoolset

Useful resources:

nZDM Java documentation

SAP Notes

SAP Community Network

nZDM Java BCP component:

BC-UPG-DTM-TLJ

http://support.sap.com/sltoolset


Troubleshooting & Wrap-UpnZDM troubleshooting: Contacting SAP Support

If you need assistance, contact SAP Support by

reporting an incident in the SAP Support Portal

The following details will help with investigation:

AS Java version/SP (source & target)

Trouble ticket

Related logs

Phase in which the error occurred

Depending on the issue, providing an R/3 or OS

level connection can also speed up resolution

Thank you


[email protected]



















Week 2 Unit 1: Introduction to Near-Zero Downtime Maintenance … · 2018-04-06 · Introduction to Near-Zero Downtime Maintenance (nZDM) for Java nZDM is available for… SAP Enterprise

Documents