Skip to Content
avatar image
Former Member

Recovery Using Maxdb In Multi Customer Envirment

Dear Friends,

We are having Multiple customer's in a ONE SAP system.

Suppose I am having 5 customer's in a one SAP ECC system.

One of my customer is not able to access the SAP system due to data got corrupted at 3 pm for particular 1 customer.I am having the complete backup till 10 am.

In this scenario i left with only one option to recover the database.If i am doing the recovery of the database in that case all my customer's will loose the data after 10 am if i am doing complete recovery.

Is thier any way so that My Other 4 Customer's data should not got affected by the doing the recovery of the one customer.

Below are details of the system

OS RHEL 5

DB MAXDB 7.7

SAP ECC 6 EHP4

Edited by: sahil garg on Dec 7, 2010 1:28 PM

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Dec 07, 2010 at 02:55 PM

    > Suppose I am having 5 customer's in a one SAP ECC system.

    You mean like 5 different clients?

    Or do you mean MCOD (multiple components in one database)?

    > One of my customer is not able to access the SAP system due to data got corrupted at 3 pm for particular 1 customer.I am having the complete backup till 10 am.

    What exactly do you mean by "corrupted"?

    > In this scenario i left with only one option to recover the database.If i am doing the recovery of the database in that case all my customer's will loose the data after 10 am if i am doing complete recovery.

    >

    > Is thier any way so that My Other 4 Customer's data should not got affected by the doing the recovery of the one customer.

    Be more specific about the way your customers share this database. Then maybe there is an option...

    regards,

    Lars

    Add comment
    10|10000 characters needed characters exceeded

    • Obviously there is no automatic way to get the data of the one client back without affecting the others.

      What you could try is:

      - figure out the affected tables

      - restore and recover the database to a different server

      - export the affected tables from the recovered server. Make sure to only export the rows belonging to the client in question. (you can use loadercli for that)

      Now you have the old version of the data for the affected client.

      For the next step you need to know whether there had still been actions on these tables after the corruption (? what do you mean by that?) happened.

      If there was data entered or changed afterwards, you have to think about how to merge the old with the new data.

      Finally you can import the exported tables into the original server and merge them with the original tables.

      All this should of course be done during a downtime of the whole ERP system, otherwise you may end up with even more problems.

      All in all: pretty bad idea to put these different companies into one system!