Reduce Production Downtime for Production Upgrade

[aaron_morden2]

We are currently in the process of upgrading our SAP system to ERP EHP4 & NW 7.01. Our Basis team has indicated that Production will need to be down for a minimum of 45 hours to complete the upgrade?

Is this a common amount of time for production to be down? Any suggestions on how to minimize this downtime?

Thanks,

Aaron

[Former Member]

There are quite a few factors to consider:

First, how long did it took to upgrade QA system if the system was build from a copyback from Production ?

The time for the upgrade is dependent on Hardware and size of the data

Will they be using the same steps that were used during the Upgrade of QA ?

Mock practices are very valuable in order to identify whats acceptable from a Production outage prospective and how the outage timing can be reduced if its not acceptable. May be its too late for all this but for next time I will recommend to consider these points.

Hope this helps.

Thanks,

Naveed

[markus_doehr2]

Please check again with the guys.

The downtime is only a short process during the whole upgrade. Most of it is done during the uptime of the system. It's not from beginning to end, that may be 45 hours in total.

Markus

[Former Member]

Hi Aaron,

During the the prepare steps, you can select one of the strategy at the PREP_EXTENSION/INITSUBST phase, below;

• Standard resource use (minimal downtime, slow import, archiving off)

• High resource use (minimal downtime, fast import, archiving off)

• High resource

By doing so, the system is performing all the imports into the shadow system, when the productive is running. At the downtime, upgrade tool performs the downtime steps.

I am frequently, choosing "Standard resource use (minimal downtime, slow import, archiving off)" strategy.

Downtime depends what patches are included into your upgrade.

Best regards,

Orkun Gedik

Edited by: Orkun Gedik on May 11, 2011 4:45 PM