Data copy strategy advice needed:client copy or system copy?

[Former Member]

Hi all,

Since years we used the 'client copy' method for data refresh of the R/3 system and

we found it very reliable and not causing any problems.

Now we are in a integrated SAP environmen(R3 + CRM + portal) and we are doubting about the strategy.

We did a system copy last year and had numerous problems with it: jobs starting on the wrong systems,

all RFC connections overwritten, user authorisations overwritten, transport requests that can get mixed, ICF

services overwritten...

What could we do?

A client copy for R3 and CRM is possible but what about the portal then?

And what about the JAVA stack?

Is there a best practice?

Thanks for all help or advice,

Hans

[Former Member]

Hi,

Thank you for your answer.

Your solution could help to prevent the RFC problems but what about the user authorisations, transports and jobs?

What is the SAP advice with this issue?

Does SAP support the system copy method?

Thanks in advance

Hans

[Former Member]

hi,

You need to export the profiles using scc8 and import back using scc7.

[Former Member]

Hi,

As you indicated that it has been years since you performed a client copy.

You source system has probably grown a lot since your last client copy.

I would recommend performing a system copy, but take the following steps:

1. Remove Target System Entries in the Host file

2. Export RFC destinations (From Target system before the copy)

a. Go to /usr/sap/trans/bin create a file ( <filename>.ctl > with the following entries

export

file '/usr/sap/trans/data/filename1.dat'

delete from rfcattrib

select * from rfcattrib

delete from rfcdes

select * from rfcdes

delete from rfcdoc

select * from rfcdoc

delete from rfcdessecu

select * from rfcdessecu

delete from rfccheck

select * from rfccheck

delete from rfcgo

select * from rfcgo

delete from rfcta

select * from rfcta

delete from rfcstxtab

select * from rfcstxtab

delete from rfcsysacl

select * from rfcsysacl

delete from rfctrust

select * from rfctrust

delete from rfctype

select * from rfctype

delete from rfccmc

select * from rfccmc

b. Execute the command R3trans -w <filename>.log <filename.>.ctl , a log file will be created in /usr/sap/trans/bin with the file name <filename>.log , R3trans return code should be 000 0r 004

c. To reimport it to the same system at a later point of time create a script <filename2>.ctl in /usr/sap/trans/bin

import

file '/usr/sap/trans/data/filename1.dat'

d. R3trans -w filename2.log -u 1268 <filename2>.ctl

e. The return code should be 000 or 004 , compare the no of table enties in the exported and imported log files , they should be in sync .

I believe there might be a secure store issue with the passwords so they might need ammending.

Regards