Scratch install vs. system restore for HA system

[Former Member]

Hi All,

We are planning for a Mimix High Availability install and would like to know whether our initial install of the HA systems (R/3 in one LPAR and CRM/BW in another LPAR) should be full DR type restore or a new install of R/3, CRM, and BW. Lakeview has recommended a scratch install and we have a vague memory that change the server name on an already installed SAP system can cause problems. What type of install did you perform during your initial setup of the HA systems? Did you load your production database on the HA systems during the initial install or wait until you were ready to start replication?

TIA,

Stan

[Former Member]

Typically what we would do to start a new target system would be to take a backup of the live sap database (this needs to be inactive so that a sync point can be established) and then to restore the backup on the target machine.

From a sap point of view using the dns settings we keep the same name for the sap system but change the ip address dependent on which server or partition is the live and hence source system.

The decision on which way to go with use of an initial system or a recent copy of production data depends on the amount of data being generated or changed and therefore the time to synchronise once the mimix journal applies are activated.

[Former Member]

Hi Stan,

Welcome to the SAP/Mimix/i5 world!

There are many ways to install/configure Mimix correctly. We did scratch installations when replacing the production/backup servers. Afterwards restore database, reset the journals, security,... just like a TST-refresh, then start Mimix with ClearPending.

Mimix should be able to replicate UserProfile, AuthorizationList, IFS, etc (Volker doesn't agreed with this point). I would reset the same passwords... to make them as close as I can, add them into Mimix replication objects, then let the Mimix audit jobs to verify it.

Doreen mentioned a document called "SAP Specific Best Practices" available from Lakeview before. You probably want to check that out.

Good luck,

Victor

[Former Member]

Hi Vic,

sorry I didn't want to mention, that Mimix is not able to do that. Most installations I know, are not configured to that. But, you can definetely use Userprofile adjustment etc. as well.

I would still agree with you, to create a "pretty similar" system before replication.

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

[Former Member]

Hi Volker,

Sorry that I misunderstood your message!

We are one of the early-adopters of SAP-Mimix. Even though we have made small changes from time to time, some configuration has been kept since day1, like the UserProfiles.

Thank you,

Victor

[Former Member]

We left our R/3 H/A system with the same SID as production. That helps when you do a refresh--saving and restoring to the same library avoids access paths rebuilds and makes journal starting cleaner.

Just something else to keep in mind.

[Former Member]

Hi Stan,

as Mimix "only" replicates the DB, a few libs and the IFS (or even not) and nothing of the rest of the system, I would not go for a full scratch install. I would start with a homogenious systemcopy with special things in it - e.g. my "easy homo copy" and then you need to discuss how you want to start the server with what IP names etc.

Most likely you want to switch host names - at least the logical hostname. So, the SAP profiles need to be adjusted.

But, I don't see any benefit (except additional effort) from a scratch install.

(you should ensure, that the GIDs and UIDs of the users are the same - this makes IFS easier)

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de