Cloud Staging Copy Service Configurations | Teradata Data Mover - Cloud Staging Copy Service with Data Mover - Teradata Data Mover

Teradata® Data Mover Installation, Configuration, and Upgrade Guide for Customers - 20.01

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Data Mover
Release Number
20.01
Published
November 2023
Language
English (United States)
Last Update
2023-12-05
dita:mapPath
jvt1700556161677.ditamap
dita:ditavalPath
stp1591127384938.ditaval
dita:id
pqq1467243714524
Product Category
Analytical Ecosystem

The Cloud Staging Copy Service (CS2) is a REST service packaged with Data Mover. The Cloud Staging Copy Service provides a method of copying data from a source system to a target system through cloud storage. The name of this cloud storage is Cloud Staging Area.

Currently the Data Mover supports only AWS S3 cloud storage.
The Cloud Staging Copy Service copies data in the following three steps:
  1. Takes data backup from the source system to the Cloud Staging Area.
  2. Copies data from the Cloud Staging Area to the target system.
  3. Cleans up the backup data from the Cloud Staging Area after the copy task completes.
To take back up to and restore from cloud storage, the Cloud Staging Copy Service uses DSA. This service interacts with DSC to handle the following:
  • Configuring DSC to copy data from the source to the Cloud Staging Area, and from the Cloud Staging Area to the target.
  • Creating and executing a DSA backup job to back up data from the source to the Cloud Staging Area.
  • Creating and executing DSA restore job to restore data from the Cloud Staging Area to the target.
  • Calling DSA to cleanup backup data from the Cloud Staging Area after the DSA restore job completes.

The Cloud Staging Copy Service runs as a service embedded on the Data Mover host. The service provides a REST API that uses port 3443. You do not have to interact directly with the Cloud Staging Copy Service. You interact with the Data Mover interfaces. The Data Mover Daemon and Agent handle the interaction with the Cloud Staging Copy Service. Port 3443 only needs to be open to incoming traffic on the Data Mover host if there is an external Data Mover Agent. Otherwise, all traffic to port 3443 is local.

There are three main supported configurations for running Data Mover DSA jobs with the Cloud Staging Copy Service:

Configuration 1: DSC Running with Cloud Staging Copy Service on the Data Mover Server

Configuration 1 is the default setup when you do not have an existing DSA environment. The bundled DSC and the Cloud Staging Copy Service come with Data Mover are enabled for use.

Configuration 1: Example Data Mover system setup when using the bundled DSC and CS2.

See Configuring DSC to Run on the Data Mover Server for configuration instructions.

Configuration 2: Data Mover Using Cloud Staging Copy Service and an External DSC

Use configuration 2 when you have an external DSC, one or more of your Data Mover source or target systems is running a version earlier than 16.00, and the Cloud Staging Copy Service is enabled for use on the host.

Configuration 2: Example diagram of Data Mover system set up when using CS2 and an external DSC

See Configuring Data Mover to Use an External DSC for configuration instructions.

Configuration 3: DSC Running with Cloud Staging Copy Service on the Data Mover Server and Externally

Use configuration 3 when you have an external DSC, all your Data Mover source and target systems are version 16.00 and later, and the Cloud Staging Copy Service is enabled for use on the host. Here, both the external DSC and the Data Mover bundled DSC can coexist.

Configuration 3: Example Data Mover system setup when using CS2, bundled DSC, and external DSC.

See Configuring DSC to Run on the Data Mover Server and Externally for configuration instructions.