Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

AWS DMS replication DB instance in the storage-full status

by | Aug 9, 2021

Wondering why AWS DMS replication DB instance in the storage-full status? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how our Support Techs assist with this AWS query.

 

AWS DMS replication DB instance in the storage-full status

 
Uually, AWS DMS replication DB instances have storage.

You can specify the allocated storage when you create a replication DB instance.

By default, the dms.t2.* and dms.r4.* replication DB instance types have volume sizes of 50 GiB.

The dms.c4.* replication DB instance types have volume sizes of 100 GiB.

Monitor the Amazon CloudWatch metric for FreeStorageSpace to monitor the free storage space of the replication DB instance.

Replication DB instance storage is used mostly for task logs and cached changes that are collected for ongoing replication.

 

Migrations that have a full load only

 
Task logs can cause storage-full issues if there are lots of task logs.

for example, if you enabled detailed debug logging for a task. By default, the AWS DMS task logging level is minimal, but sometimes you need more detailed logging to determine the cause of a migration error or failure.

But detailed debug logging can consume replication storage because AWS DMS writes each and every event to the log files.

Also, too many task logs can cause your replication DB instance to have a storage-full status.
 

Migrations that have ongoing replication

 
Cached events can cause storage issues during a full load phase, especially if you configure your migration to use the StopTaskCachedChangesNotApplied task setting.

If the storage size is too small to store the cached changes, then your replication DB instance has a storage-full status.

Swapped events during the change data capture (CDC) phase can cause storage issues when the changes captured from the source can’t be applied to the target.

AWS DMS first stores the cached events in memory, and then swaps them to storage when the values defined by the MemoryKeepTime or MemoryLimitTotal parameters are exceeded.

If there isn’t enough storage for the swapped data, the replication DB instance has a storage-full status.

 

How to resolve AWS DMS replication DB instance in the storage-full status?

 
Today, let us see the steps followed by our Support techs to resolve it.
 

Delete the task logs

 
If the replication DB instance is in an available status, you can delete the task logs:

  1. Firstly, open the AWS DMS console.
  2. Then, choose Replication instances from the navigation pane.
  3. Next, choose the name of the replication DB instance.
  4. From the Log management section, you see all the tasks and the Log size of each task.
  5. Select the tasks for which you want to delete logs, and then choose Delete.

 

Use CLI to modify the task setting

 
You can also delete the DMS task logs using the AWS Command Line Interface (AWS CLI) by modifying the task setting.

  • Firstly, create a tasksetting.json JSON file using the following command:
"Logging": {
"DeleteTaskLogs": true
}
}
  • Then, execute the command below to modify the task setting.

Please note that the task must have a status of Stopped or Failed to be modified.

aws dms modify-replication-task --replication-task-arn --replication-task-settings file://tasksetting.json

The command above modifies the task setting by changing the parameter “DeleteTaskLogs”: true.

After you have added this parameter and value to the task settings, all of the logs present for the task delete from the replication DB instance.

Once the logs delete, the task setting removes the “DeleteTaskLogs”: true parameter.

After running this command, confirm that the logs will delete from the replication DB instance and that the task setting removed the parameter “DeleteTaskLogs”: true.

To delete the logs periodically, you must modify the task setting with the “DeleteTaskLogs”: true parameter, every time.

You can schedule this command to run periodically using cronjob or Lambda scheduler, as per your implementation.

 

Increase the storage size of replication DB instance

 
If the replication DB instance is in a storage-full status, you can’t delete logs.

You must increase the allocated storage size, or delete the replication task.

To increase the storage size of a replication DB instance:

  1. Firstly, open the AWS DMS console.
  2. Choose Replication instances from the navigation pane.
  3. Choose the name of the replication DB instance that you want to modify the volume size for.
  4. Then, choose Modify.
  5. For the Allocated storage (GB) field, enter a new value.
  6. Finally, select Apply changes immediately, and choose Modify.

Please note that the allocated storage size can’t be decreased after it has been increased.

[Need help to fix DMS errors? We’d be happy to assist you]

 

Conclusion

 
To conclude, here we saw how our Support Techs resolved AWS DMS replication DB instance in the storage-full status issue.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF