Client copy taking a long time explanation

[Former Member]

My upper management wants an explanation on why client copy takes so long about 10 days for 125Gb.

I have told them that SAP recommends doing a database copy which I can probably finish in about 24 hrs.

I told them that if I do a database copy from Production to our Development system we would look all clients (4 of them).

We would loose all version management, applied support packs and others.

I told them that client copy has to delete client and recreate client during a client copy. I also run client copy with 6 processes. I use the rrfc connection for the client copy since I do not have enought space to do a client transport ( i do not know if this is faster).

They have told me that other companies do client copy in 2-3 hours. I said that they must be using some third party software.

Please let me know how long does it take you to run a client copy and also if you have any other suggestions.

One abaper says that his old company could run a client copy in 3 hours (Mssql).

I told him to show me proof.

Does using MSsql or Oracle make that much of a difference.

Sorry for the long message

Thanks very much

Joe

[Former Member]

Hi Joe,

that is always a big discussion ...

There are at leats 4 ways doing something like that:

- local client copy

- remote client copy

- client transport

- Systemcopy

You are correct: SAP doesn't suppor the client copy tools for productive clients. Therefore, this is working as designed ;-( ... and you would have to live with the time or do a systemcopy.

A local client copy is pretty fast - especally when you delete the target client beforehand. The remote client copy is the worst you can ever do ;-(((

10 days sounds too long to me, but 1-3 days sounds reasonable. As you more or less cannot work in the source client, this is not really good.

Client Transport is the best when you do not like the systemcopy. The export will be done in 6-24h and the import is not of big interest. If you do not have about 15% of your DB size left for the export, you should STRONGLY buy more DASD! (I do expect, you are on 6.40 or above)

I have never seen an MSS or Oracle environment with that size and then 3 hours for a remote copy. Either it would be local or smaller ...

For about an 30GB client it took me remote on Oracle 17h- there you see, that it is at least awfully slow.

I think, in your case client transport should be the solution .... (even when it is in total pretty slow either, but the export is pretty fast).

What HW do you have with how many CPUs and what type and RAM ?

Do you use GB Ethernet between that ? Is CHGTCPA & F4 set to 1MB or 8MB or is it still on 8KB ?

Regards

Volker Gueldenpfennig, consolut international ag

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

[Former Member]

Volker

Our Development system is a Iseries 810 (2 cpu).

85% total dasd usage.

Sap 4.6c - support pack 52 - kernel 2129 - os400 V5r2

Production system 825 (2 cpu)

65% total dasd usage

Sap 4.6c - support pack 52 - kernel 2129 - os400 V5r3

I did change from 3mb to 8mb (chgtcpa)

We're using ethernet.

I have done client copy in the past and it always takes me about 10 days to finish.

Thanks

Joe

[Former Member]

Hi Joe,

if you believe it or not:

This is pretty old hardware ;-((

OK, then this seems to be the case and can only optimized (a bit) with a client delete beforehand.

I would not suggest the transport option, as you will hit a limit of 2GB IFS files - then you could split but then there is more or less no compression any more => your DASD on the trans host might become full ... (it might be an option, that it "nearly fits" if it is located on the PRD site)

I would hope for you, that you uprade your HW and SAP soon ... then Client transport becomes a valid option ...

Regards

Volker Gueldenpfennig, consolut international ag

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

[Former Member]

Volker

I have been at this company for about 1 year.

I have told my director to upgrade and always buy more memory and dasd.

He's finally listened to me.

We're getting a 520 for our development system with 6gb of memory. I wanted more memory.

740gb of Dasd

This should be coming in about 2 weeks.

For our production we're getting a 550 with 12gb of memory

Aboud 740GB of dasd.

This should be here in about 1 month

This should hep us with the client copy.

I hope that the client copy will only take about 2-3 days.

Both systems will come with V5R4 already installed.

Our old system will be on V5R2.

Volker

Can I just do a 21 - Full system save on old v5r2

And then do a 23 - user library restore on new sytem (5vr4)

Thanks

Joe

[Former Member]

Hi Joe,

that is good news )

(even when the copy will not become a lot faster - but you should be able to move to client transport)

I have never done a complete copy with different OSs ... I would not try it, but if oyu know what you are doing exactly and do not mix up OS libs & IFS with user-ones, it should work when you use DLTR3PKG on the target.

You can let me know, then we could discuss the best approach.

Regards

Volker Gueldenpfennig, consolut international ag

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