Skip to main content

Amazon Relational Database Service (RDS)

Amazon RDS is a managed Relational Database engine in the cloud. The database engines to choose from include :

Amazon Aurora
Microsoft SQL Server

Amazon RDS handles routine database tasks such as provisioning, patching, backup, recovery, failure detection, and repair.

High Availability using the Multi-AZ Deployment Option

If you choose to run RDS with the Multi-AZ Deployment Option, it can failover automatically in case of disaster.

You can also choose to replicate it to another region.

Amazon RDS backups are automatically turned on by default and enables point in time recovery of the database instance. The database and transaction logs are backed up and stored for a user-specified retention period. This allows restoration of the database instance to any second during the retention period, up to the last five minutes. The automatic backup retention period can be configured to up to thirty-five days.

Database Snapshots

Database snapshots are user-initiated backups of the database instance. It is stored in Amazon S3. The database snapshots are kept until it is explicitly deleted. You can create a new instance from a database snapshot whenever you desire. Although database snapshots serve operationally as full backups, you are billed only for incremental storage use.

Read Replicas

Read Replicas are available in RDS for MySQL, PostgreSQL, and Amazon Aurora. Read replicas provide enhanced performance and durability for database instances.

The read replicas operates as a DB Instance which allows read-only access. This feature allows the scaling out beyond the constraints of a single DB instance. For heavy workloads, applications which require to read lots of data can read from multiple copies of the database thereby increasing aggregate read throughput.

More information about Amazon RDS can be found in this link :


Popular posts from this blog

How To Migrate Mailboxes from Exchange 2010 to Exchange 2016 using PowerShell

The Scenario

Your organisation have decided to migrate from Exchange 2010 to Exchange 2016. The Exchange 2016 server have been installed into your current Exchange Organization. The Mailbox role have been installed on the Exchange 2016 server and you are ready to start moving mailboxes from the Exchange 2010 server to the Exchange 2016 server.

Migrating a Mailbox from Exchange 2010 to Exchange 2016

Using New-MoveRequest

Migrating a single mailbox involves invoking the cmdlet New-MoveRequest from the Exchange Management Shell on the Exchange 2016 server. Make sure that your user account that you have logged into the server with have the Organization Management role.

The common parameters that I use for the New-MoveRequest cmdlet is :

New-MoveRequest -Identity '' -TargetDatabase "DB02" -BadItemLimit 10

The -Identity parameter identifies the mailbox to be migrated. I usually use the e-mail address of the mailbox for the identity since it's uniqu…

How to Schedule an Exchange PowerShell Script in Task Scheduler

Exchange Management Shell
Since Exchange 2007, Microsoft has provided the Exchange Management Shell so administrators can manage all aspects of the Exchange server from the command line.

The Exchange Management Shell has Exchange specific PowerShell cmdlets. These Exchange cmdlets are not normally available in an ordinary PowerShell command environment.

An example of what can be done in the Exchange Management Shell is to run a PowerShell script to list all the mailboxes on the Exchange server to a file. You can output columns based on display name, size of the mailbox, last logon, and other available mailbox attributes.

You can also schedule a batch migration of mailboxes from one database to another such as the migration of mailboxes from Exchange 2010 to Exchange 2013.

Scheduling the PowerShell Script

Once you have written a PowerShell script and utilised the Exchange cmdlets, you can run it with no problems inside the Exchange Management Shell. If you were to try to run it under a …

Getting a List of Installed Applications on Local and Remote Computers


A few months ago, I was asked to have a look at a PowerShell script which was supposed to be able to list installed applications on the local and remote Windows computers on the network.

The script was from the Microsoft Gallery site.

Here is the original script, with explanations of what it's supposed to do.

Unfortunately if you run the script, it will only list the applications installed on the local PC but outputs the same results for all the computers that you are trying to inventory.

I found that the program was very well structured so perhaps the author did this on purpose. Anyhow, I modified the Function FindInstalledApplicationInfo($ComputerName)
and used .NET's remote registry functions in place of the original PowerShell registry functions which looks at the local registry only. In this way, the .NET's remote registry functions can look at the local re…