By using AWS re:Post, you agree to the Terms of Use

Questions tagged with Migration & Transfer

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

AWS Datasync when executing a task and not finding changes to make, counts and charges Requests on an S3 Bucket when performing a verified on the directory / where N files are located ?????

Dear, a task was created in Datasync which transferred 8 files within a directory and subdirectories. My query is when reviewing the logs of the Datasync task, I observe that different requests are generated (created, transferred, verified). When executing a new Datasync task where no transfer was made because no new changes were detected, but when reviewing the task log again, I observed that the request was made on the root (verified directory /). My question is, when Datasync does not find a change to make, it makes N requests on the total number of files and directories that are already updated. Example: if I have 15,000 files updated on a bucket, and when executing a task again that does not make changes, will AWS still charge me and count for listing all the files that have already been transferred? I attach images where I only have 22 objects including directories, files and subdirectories, where 43 tasks were executed, of which 40 did not transfer files (only verified directory /), which, checking my cost manager, made about 1840 Requests (Put, Copy ,Post or List Request) to Amazon S3 ![![![Enter image description here](/media/postImages/original/IMr18LLdAzQ029NZYHaYyj6w) Enter image description here](/media/postImages/original/IM6a6FqBFvR3y9M2cc_47f3g) Enter image description here](/media/postImages/original/IM5rh_GTLaQaq5fKUyCZolkA)
1
answers
0
votes
37
views
asked a month ago

Trying to copy a postgres instance from a local postgres server to an RDS instance via DMS

`Greetings, thanks for looking at my question.` I've followed [this AWS documentation](https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.PostgreSQL.html) and set up a VPC, created a replication instance on DMS and set up the database server (it's on an EC2 instance currently, but ultimately we will be using a local server running postgres and the production database from our rack as the source) as the source endpoint and the RDS instance as the target endpoint. I'm trying to set up streaming replication, however, so the information on logical replication and CDC isn't relevant to my setup. ***The goal is to have our production database instance backed up and replicating to an RDS instance, down the road we hope to spin up EC2s and connect them to this RDS instance to scale up as needed. For now though we are just trying to get it set up for proof of concept.*** So I've done everything advised in the docs, but need to copy the database to the RDS instance and start the replication. I created a Database Migration Task in DMS (Full load, ongoing replication), but it fails and doesn't copy over the database or tables. This is the error message on the AWS DMS dashboard for the Migration Task: ``` Last Error Task 'FB24Y2N4*****************************HLB4R3Q' was suspended after 9 successive recovery failures Stop Reason FATAL_ERROR Error Level FATAL ``` Grateful for any advice from anyone who has successfuly set up a similar architecture. Thanks. *** *Edit to clarify: The problem isn't the error per se, it's that I need to find out why the DMS migration task that I created isn't initially copying the instance from my EC2 Postgres source to my AWS RDS instance endpoint and then beginning and maintaining replication. How do I get my database that I'm trying to replicate on RDS copied over?*
1
answers
0
votes
19
views
asked a month ago