Cloud Staging Copy Service can create all the necessary DSA configuration for each source/target pair to run backup/restore jobs using S3.
A sample cloudstagingarea.xml file for creating a cloud staging area by Cloud Staging Copy Service defined target groups is:
{ "name": "cs2-cloudstagingarea", "storage_type": "S3", "s3_properties": { "access_key_id": "ABCDEFGH", "secret_access_key": "AbcDEfgHIjklmNop123/456qRstUVwXyZ", "buckets_by_region": [ { "buckets": [ { "bucket_name": "example-bucket", "prefix_list": [ { "prefix_name": "backup", "storage_devices": 100 } ] } ], "region": "us-west-2" } ] }, "source_target_pairs": [ { "source_system": "sourceSystemA", "target_system": "targetSystemB" }, { "source_system": "sourceSystemA", "target_system": "sourceSystemC" } ] }
You need to provide the following details in the cloudstagingarea.xml file.
- s3_properties which contains s3 information as well as the region/bucket/prefix_list.
- access_key_id
- secret_access_key
Restrictions for Using the Cloud Staging Copy Service Defined Target Groups
Following are the restrictions for a cloud staging area created by Cloud Staging Copy Service defined target groups:
- You need to provide the access_key_id and secret_access_key for authentication. The process does not support any other authentication methods.
- In s3_properties you can provide only one value for each of the following parameters:
- buckets_by_region
- bucket_name
- prefix_list
- You cannot specify a source_system_target_group or target_system_target_group inside a source/target pair.
- Cloud Staging Copy Service creates the target groups using the media servers listed in default shared target group for the Teradata system specified in the source/target pair. If a default shared target group does not exist, then Cloud Staging Copy Service cannot create a cloud staging area.
- When you start the configuration, theCloud Staging Copy Service always atempts to create a new S3 AWS account in DSC, and does not reuse the existing account. If the access_key_id of the existing account matches with the access_key_id in new configuration, the configuration error occurs.