The following image shows a deployment topology in which the Fast Clone Server runs on the source database system:

In this topology, the Fast Clone Server and Fast Clone executable run on the source system. The Fast Clone Console runs on a standalone system. From the Fast Clone Console, you can create cloning configuration files and initiate data unload jobs that run under the control of the Fast Clone Server. You can use either the direct path unload method or conventional path unload method. Fast Clone produces output files on the source system.

After you copy the output files to the target system, you can run the load script on the target system to load data. Fast Clone uses the target database load utility to load data. Alternatively, you can install the target database load utility on the source system and run the load script on the source system. Install the target load utility on the source system if you load data from pipes.

You can also run another Fast Clone Server instance on the target system to accept output files sent from the Fast Clone instance on the source system.

The following image shows a deployment topology that uses two Fast Clone Server instances for distributed data movement:

In this topology, you do not have to manually copy the output files to the target.