18
Backup and Recovery Internal WebAS 6.40 J2EE Workshop Advanced Class AGSA WebAS Core Team

07 Backup Recovery j

Embed Size (px)

Citation preview

Page 1: 07 Backup Recovery j

Backup and Recovery

Internal WebAS 6.40 J2EE WorkshopAdvanced ClassAGSA WebAS Core Team

Page 2: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 2

Agenda

Backup / Recovery Considerations Backup / Recovery of individual components

Page 3: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 3

Downtime

Inconsistencies

Data loss

Data in a System Landscape

In a system landscape Business data is distributed over several

systems and transferred between them Data is stored in different databases, with no

common checkpoint Data is also stored in file systems

Consequences: Data dependencies between systems No common point of consistency across the

whole landscape

Requirements: Distributed processes must ensure data

consistency System failures may not have an impact on

data consistency Consistent system copies of the whole

environment must be possible

Page 4: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 4

Aspects of a B&R concept

A backup and Recovery concept should answer the following questions:

Which system components and which data need to be backed up Which backup methods shall be used (online/offline) How is data consistency between the system components

maintained Is a Consistent System Landscape backup necessary and in which

situations? What are the impacts of an incomplete recovery and which steps

need to be taken

Page 5: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 5

Architectural Overview Web AS 6.40 Which system components and which data need to be backed up?

Components Internet Communication Manager

ABAP Instance

Database Instance

SCS Instance

SAP J2EE Engine 6.40

IGS (Internet Graphics Server)

Monitoring Tools /SAPCCMSR and

SAPOsCol)

Page 6: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 6

Agenda

Backup / Recovery Considerations Backup / Recovery of individual components

Page 7: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 7

General Backup and Restore Strategies

With respect to backup and restore, two concepts are possible: Backup and restore of a single system component Consistent backup and restore of the complete system environment

In case of failure of a single system component, only this component must be restored and recovered completely, to the point of time of failure

SAP NetWeaver components perform data transfer in such a way that any aborted transfer is reprocessed after the complete recovery of a crashed component, that means data consistency is guaranteed

Therefore, every system component can be backed up and restored individually and independently of the other ones

A consistent backup of the whole system environment is required only in exceptional cases, such as a copy of all systems in the landscape

Page 8: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 8

Supported Backup Methods by SAP NetWeaver 04

Starting with SAP NetWeaver 04 SP Stack 10, online backup & restore is officially supported for all SAP NetWeaver components.

If you keep data outside the WebAS database, you must back up this data separately. This is for instance the case for repositories connected to KM, for TREX indices, for LDAP data, etc.

Data of Web AS 6.40 Java Cluster and deployed applications (EP, KMC) is stored in DB.

Essential data to start, stop, run and monitor the Web AS 6.40 Java cluster is stored on the file system.

Which backup methods shall be used (online/offline) depending on thedata storage type (File system, Database)?

Starting with the SPS 10 of SAP NetWeaver 04ONLINE Backup is supported by SAP without restrictions!

Page 9: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 9

Web AS 6.40 AddIn Installation – J2EE Instance on FS

Page 10: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 10

Web AS 6.40 Java Only Installation – J2EE Instance on FS

Web AS 6.40 Java Only - Which directories need to be backed up?

During any software deployment via SDM and SAPInst, files can be opened.Thus, it is recommended to backup /usr/sap/<sid>/<instance_00>/SDM,while no deployments are proceeded (e.g. when SDM is stopped).

Page 11: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 11

Web AS 6.40 – Directory Structure of J2EE InstanceWhich directories need to be backed up (2)?

The Bootstrap JAVA program synchronizes the binary data from the Javadatabase with the local file system and creates a property file, which describes the processes of the Java instance.

Data consistency between DB and FS is guaranteed by the bootstrapping!

Page 12: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 12

Required Backup Tasks and Methods

A backup concept of SAP NetWeaver 04 Java must include thefollowing tasks:

Page 13: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 13

Individual Backup of Standard Components

For every system component that stores data in a database, use a standard database backup strategy for the corresponding database system

It is recommended to perform a full database backup daily, and to backup transaction log regularly

To protect runtime environment of any system component, backup the runtime infrastructure of every component in an SAP NetWeaver landscape after the initial installation and configuration, and later after every change applied to it

This may reduce downtime after crashes of runtime environments drastically

Generally, all important data stored in file systems must be backed up regularly

Page 14: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 14

Restoring SAP NetWeaver 04 Java Components

Page 15: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 15

Bootstrapping – Synchronisation of Binaries into FS

Page 16: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 16

Backup / Restore in a System Landscape

Backup & restore of a single system component Prevent data loss Ensure recovery to current point in time (point of failure) Ensure data consistency between systems No impact on production systems caused by backup Fast backup/restore/recovery Easy handling

Recovery is the only chance to get back lost/corrupt data after a ‘user

error’ !

Consistent backup & restore of the complete system landscape Synchronization points Consistent system copies (not easy to achieve)

Page 17: 07 Backup Recovery j

SAP AG 2005, Backup & Restore concepts of an NetWeaver Landscape 17

Important Notes

SAP Note 779708: EP6 on Web AS 6.40 Online Backup and Restore Strategy

Starting with SP Stack 10, online backup is officially supported.

SAP Note 711093: Release Restriction Note for Web AS 6.40 HA-Setups for SAP NetWeaver 04 are currently released on project base only Official SAP Consultations are necessary ( 803018)

SAP Note 709354: Release Restrictions for SAP EP 6.0 on Web AS 6.40 DB switch-over solutions on project base only ( 803018)

SAP Note 803018: Central note for NetWeaver04 High Availability

capabilities HA-Setups for SAP NetWeaver 04 are currently released on project base only

(711093 and 709354)

SAP Note 785848: Hom./Het. System Copy SAP Web AS 6.40 SR1 Java