Cloud Staging Copy Service and Cloud Staging Area Support | Teradata Data Mover - Cloud Staging Copy Service (CS2) and Cloud Staging Area Support - Teradata Data Mover

Teradata® Data Mover User Guide - 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
hlv1700545853003.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
don1467241476387
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.

Make sure to specify a Cloud Staging Area for using DSA to copy data to or from a Vantage system with Cloud Bridge enabled, or to or from a Vantage Cloud Lake Edition system. Otherwise use QueryGrid, TPT, or JDBC.

Currently the Data Mover supports only AWS S3 cloud storage.
You can create cloud staging area in following two methods:
Following are the general restrictions for a cloud staging area:
  • You can have any one type of configuration (either user defined or Cloud Staging Copy Service defined) in one cloud staging area.
    You can have different configurations for different cloud staging areas, but the configuration has to be uniform in individual cloud staging areas.
  • You can have only one AWS account per cloud staging area. Multiple cloud staging areas cannot share one AWS account.
  • You cannot have duplicate source/target Teradata systems in a source/target pair.
For example, you can have:
    "source_target_pairs": [
    {
      "source_system": "sourceSystemA",
      "target_system": "targetSystemB"
    },
    ,
    {
      "source_system": "sourceSystemB",
      "target_system": "sourceSystemA"
    }
    
But not:
    "source_target_pairs": [
    {
      "source_system": "sourceSystemA",
      "target_system": "targetSystemB"
    },
    {
      "source_system": "sourceSystemC",
      "target_system": "sourceSystemD"
    },
    {
      "source_system": "sourceSystemA",
      "target_system": "sourceSystemB"
    }