 We started to design and build a system that imports and administrates business data in the main business region, then ships the data as a suite of microservice API endpoints and batch file feeds to the global markets.

The database choice was PostgreSQL and the whole infrastructure is on AWS. Since Aurora PostgreSQL didn’t come into being until right before the project started, the database solution was designed to use RDS PostgreSQL with the same- and cross-region replicas.

In the main market’s AWS region, the master instance serves to write traffic coming from importing upstream data and admin applications, one replica serves in-region API read traffic, while another replica serves all regions’ batch read traffic. In each overseas market, one replica was created to serve that market’s API read traffic.

An architectural level change to address the database replica limit is unavoidable. With the fourth overseas market’s rollout date approaching, the fifth, sixth and the seventh overseas market also had their rollout plan laid out.

However, we must tread very carefully. The system has been running on production for nearly 2.5 years, now serving eight client systems from seven countries. The daily traffic could amount to 20 million accesses, any downtime has impact on real users, any read downtime could result in business loss. 

For the first requirement, AWS Aurora Global Database is a low-hanging fruit solution. It supports cross-region read-only replicas in up to five AWS regions (secondary regions as named in AWS docs, as opposed to the primary region where the master database instance resides,) with less than one second cross-region replication latency. As for the number of replicas, it will allow us 15 replicas in the primary region and 16 in each secondary region . Plus the scalability and availability improvement (think about cross-region failover), migrating to Aurora Global Database is a no-brainer.

Geographically it is easy to group the seven (and more to come in the future) overseas markets into less than five AWS regions. Once we have an Aurora database cluster, adding the first secondary AWS region will automatically turn it into an Aurora Global Database. 

The only problem is, our PostgreSQL database was still on version 9.6.11. Although the lowest Aurora compatible PostgreSQL is 9.6.8. Aurora Global Database is only compatible with PostgreSQL 10.11, 10.12, and 11.7 up.

 For some more buffer time before the next major version upgrade, we chose the newest Aurora compatible PostgreSQL version in our target AWS regions, 11.8, as the upgrade target version. 

 With AWS CLI, the following command checks available engine versions of Aurora PostgreSQL in a particular AWS region:

 $aws rds describe-db-engine-versions --engine aurora-postgresql --query '*[].[EngineVersion]' --output text --region <your-aws-region> 

 Also with AWS CLI, the following commands check available upgrade target versions from a given PostgreSQL version in a given AWS region :

 First, export the AWS region and that region’s RDS endpoint as the terminal tool’s environment variables: 

$export ENDPOINT=https://rds.<your-aws-region>.amazonaws.com

Then, to check available upgrade target versions for RDS PostgreSQL from a given version, use this:

 $aws rds describe-db-engine-versions \
--engine postgres \
--region $REGION \
--endpoint $ENDPOINT \
--output text \
--query '*[].ValidUpgradeTarget[?IsMajorVersionUpgrade==`true`].{EngineVersion:EngineVersion}' \
--engine-version <your-start-version>

 To check available upgrade target versions for Aurora PostgreSQL from a given version, use this: 

--query 'DBEngineVersions[].ValidUpgradeTarget[?IsMajorVersionUpgrade == `true`]'

This is how we found out that it is impossible to upgrade 9.6.11 directly to 11.8, no matter in RDS or Aurora. We have to first upgrade to 10.x, then 11.8.This is how we found out that it is impossible to upgrade 9.6.11 directly to 11.8, no matter in RDS or Aurora. We have to first upgrade to 10.x, then 11.8.

To achieve the least user impact, especially to avoid potential business loss, we set the goal of zero read downtime, and minimizing write downtime as much as possible.

According to AWS doc, there are two ways to migrate from RDS to Aurora:

Migrate from an RDS PostgreSQL DB snapshot, or

Create an Aurora read replica from an RDS instance, then promote it to be an independent Aurora cluster

Both options can achieve zero read downtime, since the existing RDS DB can keep serving the read traffic until the Aurora cluster is ready, then we just switch the applications’ DB connections to the new Aurora cluster.

As for the write downtime, at first glance, the second option looks more appealing.

Option one requires us to stop all DB write operations (importers, admin applications) as soon as we start to create the RDS snapshot, otherwise we would lose all the changes after this point in the new Aurora cluster.

In contrast, option two allows us to keep accepting writes even after the migration starts. The Aurora read replica will replicate all changes from the RDS master after it is created. We only need to stop write operations at this point, wait for it to catch up with the master, and promote it to be an independent Aurora cluster. Then we can switch all read and write applications to the new Aurora DB, then resume the write operations.

However, the AWS doc failed to mention one key fact, which we had to find out only in our first staging rehearsal. In our use case, this rendered option two essentially impossible:

If the RDS master instance has cross-region replicas, no Aurora read replica can be created.

In the end, we had to go with option one, despite the longer write downtime.

After migrating on the staging environment, we noticed severe write performance degradation in the new Aurora DB. Compared with using RDS, importing the same amount of data from upstream now takes ten times longer.

Run ANALYZE to refresh the pg_statistic table (which was recommended in AWS doc for PostgreSQL major version upgrade, both RDS and Aurora)

Tune the Aurora parameter group according to our data’s characteristics (mainly some Autovacuum related parameters needed to be adjusted)

Our migration procedure turned out like this:

Stop all DB writing applications/batch jobs

Create Aurora cluster from the RDS snapshot

Upgrade the Aurora cluster from 9.6.11 to 10.11

Upgrade the Aurora cluster from 10.11 to 11.8

Connect test applications to the new DB clusters

In this article, we know how to migrate PostgreSQl on AWS from RDS to Aurora..

Migrate PostgreSQL on AWS from RDS to Aurora

Software, instructions that tell a computer what to do. The software comprises the entire set of programs, procedures, and routines associated with the operation of a computer system. ... A set of instructions that directs a computer's hardware to perform a task is called a program, or software program.

Remote Desktop Software is a stage that permits IT, experts and overseers, to remotely get to customer gadgets to take care of or investigate innovative issues and offer help for upkeep. It has various remote access and control features without interference, multiple monitors navigation, chat or messaging, screen sharing, file sharing, etc.

Given below are the features of Remote Desktop Softwares:

Unattended Access: With this feature, you won’t have to interrupt the client to grant access whenever a client needs assistance. Instead, at any time of the day, you’ll get single-click remote access to the client’s computer.

Multi-Session Handling: Efficiently multi-task is essential to delivering remote support of high quality. In this, Support sessions can be run at the same time.

Multiple Window Control: When you need to provide support to many users at the same time, the ability to set up several remote desktop control windows works great.

Auto Reboot & Reconnect: One of the essential aspects of the remote desktop tool is rebooting a remote computer and reconnecting it automatically. By clearing caches, flushing the memory, thereby giving you the opportunity to start anew, makes the computer a comparatively clean state.

Remote Screen Scaling: The remote screen scaling feature makes it simpler for you to operate on a remote device that has a screen resolution that is bigger or smaller than yours. With remote desktop software, it is easy to change the remote control window between multiple scaling choices depending on the screen resolution settings of the remote user or client’s preferences.

Given below is the list of Remote Desktop Softwares:

It is a generally involved Remote desktop applications for both online collaborations joint efforts just as remote management. It empowers you to interface with a few workstations remotely. This permits you to expand GPU controller effectiveness for equipment hardware-accelerated picture handling.

It enables you to shift power from one person to another.

It Supports Artificial Intelligence, Augmented Reality (AR) as well as Internet of Things (IoT) implementations.

Allows you to drag and drop files from one system to another.

ISL Light lets you safely and conveniently access remote computers and mobile devices.

It provides maximum protection with two-factor authentication and AES 256-bit encryption.

It is easy to use and provides several different ways to communicate.

Automatic recording of sessions, file transfer.

Possibility of connecting via RDP to an unattended machine.

Easy to use and collaborative options for customization.

This tool enables you to control all your connections remotely on a single platform safely.

It provides a single platform for launching and management of all remote connection.

Allows all your passwords and credentials to be stored in a safe, unified Walnut.

Protect connections from multiple security attacks with the help of granular access control protection.

Allows to create of a template for an effective strategy.

Generate customized reports on the basis of particular criteria.

Remote Utility is a free and open-source remote access tool. For automatic and unattended remote access, you can use this tool.

It provides several tools for remote access.

It provides Integration of Active Directory.

It allows to establish connections of upto 10 computers.

Remote Access Plus is a safe and robust remote support solution for organisations that helps system administrators and IT help desk technicians from a central location to troubleshoot Windows, Linux and Mac computers.

It allows Endpoint access from anywhere, anytime.

Switch easily between several monitors linked to client computers.

Using the Quick Launch tool, it allows to perform administrative tasks.

For those who have started a company that needs continuous assistance from all over the world, LogMeIn is an ideal tool. It is particularly useful for locations where problems can appear at any time.

It allows you to easily access your work and store, share and collaborate across all your devices.

Store, transfer, and collaborate files with a single click.

To freely communicate, you can share the screen with anyone.

RealVNC provides secure remote desktop access and support for a connected world.

Easy and reliable remote support and access.

Share, cooperate, train the team members and encourage them.

Provide an excellent on-demand helpdesk service, boosting customer loyalty.

Helps your ecosystem securely access resources and data.

In this article, we have seen different distant work area programming alongside their highlights. We can pick any of them in view of our prerequisites.

In this blog post, we will know about Remote desktop software, what is it, its features, and a list of Remote desktop software.

rds

Trending Blogposts on rds

Migrate PostgreSQL on AWS from RDS to Aurora

Remote Desktop Softwares

Popular Discussions on rds

PRODUCTS

QUICK LINKS

LEGAL

rds

Trending Blogposts on rds

Migrate PostgreSQL on AWS from RDS to Aurora

Remote Desktop Softwares

Popular Discussions on rds