SAP system startup and shutdown, including virtual hosts
Tools for SAP test systems
With TM-TMS, an SAP add-on is offered that largely automates manual user interventions during a system copy and thus relieves the developers/customizing users. Cross-user developments are processed in one package, ensuring consistency. The entire process consists of three areas.
Individual steps know exactly where they have to restart the actual copy run in the event of an error. In general, this means that error situations can be handled as needed and with pinpoint accuracy.
TM-TMS (Transport Manager)
Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.
The process of creating system copies for updates can be broken down into different activities, as shown in Table 1. For each group, the software used for automation is shown, where "UC4" stands for UC4 Automated System Copy and "HP" stands for HP System Copy. All these activity groups are described individually below.
With "Shortcut for SAP Systems" a tool is available that simplifies the SAP system copy and offers additional possibilities.
This is clearly the faster way to achieve the goal!
If necessary, the system is copied incrementally, table by table, on weekends and at night.