Reset Option During System Move

There are two ways to reset a DMO with System Move: You can either perform a reset on the source system or on the target system.

Reset of Source System

If you perform a reset on the source system, it is reset to the status before the downtime started. In addition, almost all shadow system artifacts are deleted.

We strongly recommend that you only perform a reset of the source system in the following cases:

on a test system for test purposes
you want to continue working productively on the source system and use the migrated system for testing purposes or keep it as a reference
the migration to the target system failed, or the target system is discarded

Reset of Target System

The Reset option is also available for the SUM run on the target system. After you have started it, the Software Update Manager indicates afterwards as usual the successful reset and prompts you to clean up the SUM directory. Now, you can choose between two cleanup options:

A cleanup to start the DMO with System Move feature on the target host again
A cleanup to start the SUM tool on the target host from the beginning including scenario specification

The difference is that the first option deletes only those data from the SUM directory that has already been generated on the target system side during the DMO with System Move procedure. Only the SUM directory data of the data transfer from the source side is kept. In this way, you can restart the part of the DMO with System Move procedure, which takes place on the target system to continue and complete the procedure.

A regular cleanup, on the other hand, cleans up the SUM directory and several other directories on the target host and stops all running processes on the server. Note that the SUM directory on the source host is not affected by this option. This procedure allows you to restart the Software Update Manager tool on the target host from the beginning, including specifying the scenario. Source system data does not exist.