MDM VIRTUAL TO PHYSICAL MIGRATION APPROACHG

[Former Member]

Hi All,

Our current MDM servers are installed on virtual host.Now we plan to move it to physical hosts due to performance

issues and the same is recommended by SAP.

The best approach as per me would be to restore the entire system backup from virtual host on physical host and do

post steps (for establishing connection to interface system). The same way we do migrations for other systems(SAP component)

But some other member are insisting for a fresh installation initially of Production server.

In Phase 1, basis team will do a fresh install of current Prod version of MDM app on . Then, hosting will restore QA data from most recent

backup of QA server,basis will configure MDM application on for QA system and conduct validation.

After successful testing, same approach would be taken for production and production data will be restored on the new server and

final cutover will be done in Phase 2. There would be 2 Prod outages, one for testing prod and second for cutover.

Questions:

1.In phase 1 we would install MDM(oracle DB) with <sid> = Production and then restore Quality DB and recover the DB. Will this work?

  similar to the was we do SID change during refresh activities or this approach is not going to work in case of MDM.

Steps:

Download Media (MDM 7.1 + Oracle 11.2.0.2) for windows

Build new physical servers

Verify access to New servers (App and DB)

Check and verify Hardware pre-requisite for installation

Install Oracle 11.2.0.2 on New database server.

Install MDM 7.1 on App server

Install Database client on MDM App server

Verify installed MDM 7.1 system and verify database connectivity

Take backup of MDM Quality system

Archive Quality MDM repository from Console

FTP archive files to new server

FTP configuration files (mds.ini, mdis.ini, mdss.ini, and mdls.ini)

Restore data from QA servers to new physical servers

Unarchive Repository with  imported archive files.

Place all configuration files to respective locations and modify it accordingly

Perform post steps (for establishing connection to interface system)

Perform testing

2. Or filesystem restore is a far better approach(easier and less risky). Any other challenges.

Please help.

Regards,

Vicky

[hemanth2 · Accepted solution]

Hi Vicky ,

Hope you are doing good.

I would personally go with option 1.As you rightly mentioned, this is nothing but a migration and similar to a production to quality server refresh. You haven't mentioned the usage types that are active, but this should be straightforward enough and sapinst should take care of the DB restore operations well.

Thank you!

____________

Kind Regards,

Hemanth

SAP AGS

[Former Member · Accepted solution]

Hi Hemanth,

Thanks a lot for your time and help.The end result that need to be achieved is to migrate MDM production from Virtual host to Physical. Don't you think a simple migration of whole production MDM backup(windows NT backup/restore) on the new physical host  then Perform post steps (for establishing connection to interface system) will be far more easier.

Or you still think installing a fresh MDM and then doing system refesh..and later again restoring the actual Production backup is lengthy and more complicated?

Regards,

Vicky

[hemanth2 · Accepted solution]

Hi Vicky, yes you are right. The migration would be easier. It actually depends on the strategy you are more familiar with and something you have tried on a test server before doing this on a production engine. I personally would rely on SAPINST more than OS/DB tools, so would like to go with a fresh install and then DB restore . But end of the day this is a Basis call.

[Sriram2009 · Accepted solution]

Hi Vicky

Are you using any conversion tool from VM to Physical(V2P) machine?

We have tired once of SAP system migrated P2V not on V2P

BR

SS