Database Reference
In-Depth Information
provides an option of excluding certain tables from the copy process, but the customer has
the responsibility for any inconsistencies as a result of this exclusion. A remote client copy
performed over a WAN can have network-related performance bottlenecks as well. One oth-
er drawback of a remote client copy is that for the duration of the copy process, no user
activity is allowed in the source client and therefore will not be available for general use.
However, because of the ease of use and performance improvements made by SAP in recent
releases, this is a viable option for Basis administrators who want to set up a target client
from another SAP system. This procedure also takes care of all post-copy procedures that
would have to be completed manually if another method such as a database copy were used
for the copy process. Transaction code SCC9 is used to perform a remote client copy. The
following illustration shows the initial screen for performing a remote client copy. Once the
source system RFC connection is entered, the rest of the procedure is similar to that of per-
forming a local client copy.
Copyright by SAP AG
Client Refresh
A client refresh involves refreshing the data of the existing target client and is based on the
client copy profile used for the copy process. Instead of a two-step process of deleting the
target client and then performing a client copy, the client refresh process can do it in one
step. Usually, a gold client with clean data is maintained in each system as per the client in-
stance strategy and is used as a source of the client refresh. The client refresh will delete and
recreate data in the target client, depending upon the choice of the client copy profile. The
runtime of the client refresh will depend upon several factors, including the data volume.
