System refresh using LAMA with different number of clients in Source and Target

[former_member700444]

Hi Team,

Is it possible to perform system refresh using Lama where we are having 5 clients (000, 010, 020, 030 and 040) in Target and only 2 clients in Source (000 and 010).

Regards,

Ramana Adabala

[abe_letkeman]

Hi Ramana.

The short answer is, yes.

I suspect your high-level process today looks something like the following:

1. Document and export system- and client-specific settings (RFCs, certificates, users, etc.)
2. Copy the database via storage snapshot or DB restore
3. Post-copy tasks: update RFCs, configure TMS, import users, certificates, execute BDLS, etc.
4. Local client copy from 010 to 020
5. Client-020-specific configuration, import users, BDLS, etc.
6. Local client copy from 010 to 030
7. Client-030-specific configuration, import users, BDLS, etc.
8. Local client copy from 010 to 040
9. Client-040-specific configuration, import users, BDLS, etc.

With SAP LaMa, tasks for the activity remain the same, however they can all be automated with no wait time between tasks. The default for the out-of-the-box system refresh activity includes steps 1-3. Note that for step 2, for systems on AnyDB, storage snapshot is out-of-the-box, however DB restore is a custom process as described here.

Arguably, steps 4-9 are out-of-the-box functionality too. Steps 4-9 can be configured in task lists and added to the list of tasks to be executed in the PCA step of the refresh activity. This is especially possible with the new client copy tool, which allows you to execute a local client copy from any client i.e. client 000, so you don't need to enable user SAP*.

Regarding the new client copy tool for systems on HANA, with the massive performance improvements, it may be possible to use remote client copy, but keep in mind the necessity to lock the source client for the duration if you want a transactionally-consistent copy. Despite the performance improvement with the new tool, the feasibility of this option is limited by the source system's size and the performance of your systems and infrastructure, which determines how long the source client remains locked. With this option, SAP LaMa still proves useful by orchestrating the end-to-end activity by using the standalone PCA operation, or a custom process.

Please reach out to your SAP account executive or technical quality manager to see how we can help you to reach your automation goals.

Best regards,

Abe