cancel
Showing results for 
Search instead for 
Did you mean: 

Solution to have a second system online while applying support packs

Former Member
0 Kudos

Hi,

we apply support packages to our CRM system several times each year. The application of these support packages requires a downtime of 3 days for the system. We however have the need for certain parts of the system to be available during that period. The time we can allow for unavailability is 5 hours.

Currently we are thinking of making another copy of our CRM system (reconfiguring it to another SID) and using that copy while the support packages are applied. The copy and reconfiguration takes a long time (several days).

Do you have any other suggestions on how this could be done ?

The database is mirored and most of the data is on a SAN.

I'm wondering if there is not an quick way to just have another instance (or the same one) built use the mirored data and use it until the support packs are done. At that time we could just drop the miror (loosing that data is ok) and resynchronise the disks with the data from the CRM that has been upgraded.

Thank you.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi

I donot know that you are aware of one option in SPAM "downtime minimised Import process". We usually perform this step when we use to perform the Support packages in production server. If you have selected the import mode downtime-minimized, some of the objects that are to be imported are imported inactively. During this phase you can continue to use your system productively.

Read this link:

http://help.sap.com/saphelp_nw04/helpdata/en/29/ff9036e1e4b603e10000009b38f889/frameset.htm

https://help.sap.com/saphelp_nw04/helpdata/en/46/078d380be34e6ce10000009b38f842/frameset.htm

Former Member
0 Kudos

Thank you.

Did this procedure allow you to reduce the unavailability by a lot ?

I don't know if this is an indiscrete question , but how long is your unavailable time to apply SP's ?

Thank you.

Former Member
0 Kudos

Hi

The basic fundamental thing around this process is that: If you follow the downtime minimised strategy all the program objects and program texts are imported into the system.

And actual change would happen in the system downtime (means system is not available)

Practically if we use this: round about 50% time is reduced as it takes in normal patch application.

Answers (0)