Information
Sie befinden sich auf der internationalen Website von Espresso Tutorials. Möchten Sie zur deutschen Website wechseln?
Taux forfaitaire
19 $US par mois
SAP S/4HANA Upgrades & Updates: Mastering Zero Downtime Option is a practical guide for SAP teams and IT professionals aiming to update/upgrade SAP systems without disrupting business operations. Based on real-world company upgrade experience, this book delivers a structured approach to planning, executing, troubleshooting, and governing SAP S/4HANA upgrades using SAP’s Zero Downtime Option (ZDO). As organizations demand continuous system availability, traditional upgrade outages are becoming increasingly unacceptable. ZDO enables upgrades and updates while keeping systems available to business users, transforming how SAP modernization projects are executed. Designed for CIOs, SAP Basis teams, architects, and project managers, this book combines strategic insight with deep technical expertise. Readers will learn ZDO architecture, SUM confi guration, bridge subsystem concepts, custom code readiness, rollback strategies, CTI integration, monitoring, and post-upgrade stabilization techniques. Through detailed scenarios, project lessons, and real-world case studies, this book provides practical guidance for executing successful zero-downtime upgrades across on-premise, RISE PCE, and hyperscaler cloud environments, with confi dence and precision.
Zero Downtime Option is an advanced SUM tool option for performing S/4HANA upgrades and updates, with minimal to near-zero technical downtime
The main advantage of ZDO is that there is no major long-running technical downtime SUM phase as with other upgrade approaches such as standard and nZDM. Disruption is therefore minimal, and the business can continue to run when actual upgrade phases are taking place in the maintenance phase.
The core ZDO architecture is illustrated in Figure 2.1.
Figure 2.1: ZDO architecture
At the end of the SUM pre-processing phase, the system has two instances:
The architecture diagram in Figure 2.1 shows how this dual-system operation enables SAP systems to stay online in the bridge subsystem while SUM executes the technical phases during the maintenance phase, which traditionally required downtime.
In this section, I explain the key concepts associated with the ZDO approach.
The new concept of a bridge subsystem was introduced with ZDO. This is like a clone of the source system (the old release) that runs in parallel to the system being updated during system maintenance.
Once the switch to the bridge subsystem has been completed, the daily production workload continues to run on the newly created ‘shadow’ (SHD) schema, while the remaining update takes place on the main schema. This enables the SUM tool to carry out upgrade tasks during uptime, which in other approaches would typically be performed during downtime.
In summary, the business can continue to run on the bridge subsystem, where SAPHANADBSHD schema accepts all the DML connections from the source system while the original instance and its relevant schema (SAPHANADB) undergo the upgrade.
Once all the SUM pre-requisite tasks are completed prior to the pre-processing phase, all the active users from original instance will be rolled over transparently to the bridge subsystem.
This is your internal, existing, main instance from which the bridge subsystem is created. All the current production workload will start running on this bridge subsystem.
Internally, all system processes will be shared between the main system and the new bridge subsystem. Actual upgrade maintenance is done in the background.
During the SUM phase, the following tasks will be carried out:
The Software Update Manager transparently connects users from one database schema to another, without impacting users. After this schema switch, nothing changes with regard to the SAP logon user interface in order to log in to the system.
Internally, SAP will start connecting to the SAPHANADBSHD bridge subsystem schema, instead of the SAPHANADB original schema, to continue business operations in the bridge subsystem.
While production business operations continue to run on the source release and on the SHD DB shadow schema, the remaining update phases run in parallel on the main original schema. The Software Update Manager can therefore perform the upgrade during uptime activities in other approaches, this would be done during downtime.
At the end of the upgrade, the application server needs to be restarted to activate the new release version. This usually takes two to 20 minutes, depending on how the SAP ASCS and application servers are interconnected.
The SUM tool prompts and performs the restart of the SAP application once the following SUM tool steps have been completed:
There is no further need for the bridge subsystem, and the completion of the above phase indicates the end of the bridge subsystem.
The most important thing to note here is that the HANA database is not restarted during the entire upgrade process.
This solution is new and is not available for standard or nZDM methodologies.
SAP app server connectivity
From past project experience, I have noticed that the final restart step can sometimes take less than two minutes. However, if the app servers are not connected to each other, it can take around 45-50 minutes, or manual intervention is needed. I therefore recommend making sure that all app servers are connected instantly with each other, and, in pre-production servers, you need a similar number of servers, so this can be tested in advance.
An upgrade procedure is started when the system is still running on the old version. Once you are in the pre-processing phase, SUM works internally on two schemas within the one HANA DB instance:
The ZDO bridge concept is illustrated in Figure 2.2.
Figure 2.2: ZDO bridge concept
The SUM tool creates HANA views for each of the tables in the bridge schema, which will keep looking for any data that has been updated via DML transactions in the original schema. At this point, only one version of the tables (V1) exists, which represents the source release. The original schema continues to be used to access production traffic.
One critical and important milestone phase is the preparation (REQ_USER_ROLLOVER_PREP) and rollover/transition of users to the bridge system. All active jobs/users/work processes are transitioned automatically to the bridge schema, and the bridge subsystem has an active connection.
Once the final phase (REQ_USER_ROLLOVER_FINAL) is completed, and all users are transitioned to the bridge subsystem, the actual/original database system schema is renamed by affixing SHD to its name, which is then used by the bridge subsystem. For example, the SAPABAP1 database schema is renamed SAPABAP1SHD (or, as shown in the image, SAPHANADBSHD).
The original system, in which the upgrade is performed, is still connected to the original database schema (SAPABAP1 in the example).
Although the actual upgrade is carried out on the new version (V2), V1 will keep referencing the data from the old/source release and the production system will continue to be used on the bridge subsystem without impacting the business.
In addition, if no table structure adjustment is needed during the upgrade, no new/extra V2 table is created. Refer to the example shown in Figure 2.3, for Tab 2, V1=V2. The generated view (View 2) still points to this table.
Figure 2.3: ZDO bridge—deep dive
The shadow instance is one of the most critical architectural components in a ZDO upgrade. Standard or nZDM upgrades also use a shadow instance, but the way it is leveraged in ZDO is significantly different. With ZDO, the production system remains online throughout the uptime process, in the bridge subsystem, where it uses shadow schema on the HANA database.
Let’s look at some of the main enhancements to the shadow system with ZDO.
The shadow instance handles all table activations and DDIC (data dictionary) changes without touching the live tables. These updated structures are ready to take over once the bridge subsystem is no longer in use.
If any errors occur in the shadow system, they do not interrupt business operations. SUM has the capability of safely stopping or rolling back the shadow creation process.
Trigger-based synchronization enables you to capture changes made during uptime, via CRR technology delta logs are applied, so structural changes are always in sync. The final cutover period therefore needs minimal downtime, because both the shadow and original instances are always synchronized.
As the business continues to run using the bridge subsystem, many large tables are cloned and processed in the shadow system. ZDO-specific enhancements support efficient clone creation, trigger-based updates, and faster comparison and activation.
ZDO-specific SUM improvements enable better parallel processing in the shadow instance:
This is why SUM host sizing is so important for ZDO.
Shadow instance enhancements to bridge switchover ensure that cutover is faster, there are no inconsistencies, and user transition is completely transparent, without any major changes.
As highlighted in Figure 2.4, the ZDO approach enables nearly all upgrade activities to be performed during uptime, thereby isolating heavy technical tasks, improving activation logic, supporting bridge mode synchronization, and drastically reducing downtime during final cutover.
Figure 2.4: Shadow system enhancements
Questions et réponses générales sur notre contenu d'apprentissage.
Le contenu de l'apprentissage est conçu pour tous ceux qui souhaitent acquérir des connaissances sur SAP d'une manière simple, compacte et pratique. Notre plateforme d'apprentissage propose des contenus pour les débutants, les apprenants avancés et les experts. Cela vous permet d'élargir vos connaissances étape par étape et de développer continuellement vos compétences pour devenir un expert SAP.
Nos produits, qu'il s'agisse de livres, de vidéos ou de formations en ligne, transmettent les connaissances SAP de manière concise et pratique, afin que vous puissiez les appliquer directement dans votre travail quotidien, même si vous disposez de peu de temps. Vous bénéficiez d'une large couverture des sujets SAP pertinents, d'un contenu de haute qualité en quatre langues et de formats d'apprentissage conçus pour répondre à vos besoins individuels. Cela vous permet de rester à jour et de développer continuellement votre expertise.
Nos livres se caractérisent par une orientation pratique claire et une présentation compacte et facile à comprendre. Nous expliquons les sujets SAP complexes de manière concise - sans termes marketing inutiles - afin que les lecteurs puissent rapidement saisir l'essentiel et appliquer directement les nouvelles connaissances.
Nos livres imprimés peuvent être retournés dans les 14 jours, dans leur état d'origine. Les frais de retour sont à votre charge.
Nous n'expédions actuellement les livres qu'en Allemagne. Si vous commandez depuis l'étranger, nous vous recommandons de passer par Amazon. Vous trouverez le lien en sélectionnant "Buy eBook" sur n'importe quel produit de notre boutique en ligne. Amazon vous indiquera alors les versions eBook et imprimées disponibles à l'achat.
Vous pouvez également accéder à l'ensemble de notre contenu par le biais d'un abonnement numérique, à partir de 19 dollars par mois.
Notre équipe est toujours heureuse de vous aider et répondra à vos questions le plus rapidement possible (généralement dans les 1 à 2 jours). Vous pouvez également nous contacter si vous avez des questions à poser à l'un des auteurs. Courriel : contact@espresso-tutorials.com
