Lesson 2 of 6
Copy techniques
9 min
Listen to this lesson
There are two families of technique. A system copy copies the whole database, so every client, the repository and all cross-client data. A client copy copies the data of one client, within a system or between systems, using SAP's client copy tools. Choosing between them is mostly a question of volume, scope and what you must keep in the target.
| Aspect | System copy | Client copy |
|---|---|---|
| Scope | Whole database: all clients, repository, cross-client data | One client's data (scope set by a copy profile) |
| Typical method | Database backup and restore, or export/import with Software Provisioning Manager | Local copy (SCCLN), remote copy (SCC9N), or export/import (SCC8N / SCC7N) |
| Speed for large production data | Usually much faster: database-level copy | Slow for large clients: hours to days |
| Effect on other clients in the target | All replaced | Untouched |
| Effect on repository in the target | Replaced with production's | Untouched; must already match |
| Typical use | Refreshing a QA or pre-production system from production | Building a new client, copying customizing, refreshing small clients |
System copies
For SAP S/4HANA on SAP HANA, the most common refresh method restores a backup of the production tenant into the target system's tenant, then runs post-copy steps. SAP's backup training notes that database copies can be made with backup and recovery, with limits such as not restoring a newer release into an older one. The alternative, database-independent export and import with Software Provisioning Manager (SWPM), is used for migrations and special cases. SWPM also supports system rename. Because a system copy replaces the repository, any transports that exist in CMQ but not yet in CMP disappear and must be imported again (lesson 5).
Client copies
Client copy tools copy client-specific data according to a profile. SAP training lists, among others: SAP_ALL (all client data except change documents and local data), SAP_CUST (client-specific customizing with authorization profiles; application data deleted), and SAP_USER (user master records, roles and authorization profiles). From SAP_BASIS 7.54 the newer tools (SCCLN, SCC9N, SCC8N, SCC7N) are described as considerably faster, can run as task lists, and no longer need user SAP*. During a copy, the target client is locked for logons, and a test run or resource check estimates the size first.
- Size itEstimate the client size (SCC_CLIENT_SIZE) and run a resource check
- Protect usersExport the target client's users with profile SAP_USER if they must survive
- CopyRun the copy with the chosen profile and parallel processes; target client locked
- Check logsRead the copy log in SCC3; restart from the failure point if needed
- Post-processRe-import users, adjust settings, run post-copy steps
- Is the source a large productive client with years of documents?Yes → prefer a system copy; SAP training warns that copying application data from a large productive client needs a lot of time and resources · No → next question
- Must other clients in the target (such as training client 200) survive unchanged?Yes → client copy, or plan to rebuild those clients after a system copy · No → system copy is acceptable
- Do you need only customizing, not application data?Yes → client copy with a customizing profile such as SAP_CUST · No → full data copy method
What would you do?
Contoso needs a fresh CMQ client 100 with production data before a major test cycle. Production's client holds several years of documents, and training client 200 in CMQ must stay available. What is the most practical plan?
- System copy: whole database, fast for large data, replaces every client and the repository.
- Client copy: one client by profile (SAP_ALL, SAP_CUST, SAP_USER), slower for large clients, other clients untouched.
- Newer client copy tools (SCCLN, SCC9N, SCC8N/SCC7N) are faster and run as task lists.
- Choose by volume, what must survive in the target and whether you need data or only customizing.
Check your understanding · not graded
Lesson check
1. What does a system copy replace in the target?
2. Which client copy profile copies user master records, roles and profiles?
3. Why is a client copy of a large productive client often avoided?
4. Which tool supports database-independent system copies and system rename?