You can use parallel processes for remote and local copies and to delete clients, to exploit the capacity of your database better.
The transactions contain a Parallel Processes Parameter pushbutton to select the maximum number of processes to be used and their RFC server group.
If you have not yet created an RFC server group, you can go to the RFC server group maintenance. For more information, see Defining RFC Groups for Parallel Processing Jobs.
Two processes per available database CPU is a good guideline. The number of application servers is unrestricted.
Parallel processes are only used during the actual copy phase, not during the analysis and postprocessing phases.
The resource management may only asign a limited number of processes to the client copy. For further information, see: Parallel processing of jobs with asynchronous RFC in the Automatic Protection against Resource Overload section.
The processes monitor each other and restart cancelled processes. You can therefore not cancel the client copy simply by ending the processes. You must tell the client copy first that you want to end the copy. If you display the log of the copy in the transaction SCC3, there is a Cancel Copies pushbutton for current copies. The processes end themselves when they have finished their current tasks. If you do not want to wait for the processes to end themselves, you can cancel the processes in the process overview (transaction SM50) or SAP Server Management (SM51).
Only the main client copy process can use a background process. The parallel processes are controlled by an RFC server group. RFC processes are always dialog processes. Scheduling the main process on a particular server does not affect this.
The RFC server group is only analyzed once at the beginning of the copy phase. A change to the server group or the application server load is only effective in a new copy or a RESTART.