CLOUDBASIC RDS Always-On/Geo-Replicate for SQL Server HA/DR/Redshift/S3

Starting from $1.37/hr or from $9,950.00/yr (17% savings) for software + AWS usage fees

If SQL Server is part of your cloud or hybrid cloud system architecture, CloudBasic RDS Always-On/Geo-Replicate (Multi-AZ-R/Multi-AR) for MS SQL Server Web/Standard/Enterprise and Redshift/S3 Data Lake, could become your solution for: (1) Readable-Replicas: create RDS/EC2 SQL Server Multi-AZ-R and/or Multi-AR (Cross-Region; hybrid) Readable-Replicas for High-Availability (HA), to off-load primaries, Data-Locality or Disaster Recovery (DR). All RDS/SQL Server editions, including Web Edition, are supported. (2) RDS/SQL Server-to-Redshfit SCD Types 1-2 data streaming: setup seamless no-ETL, no... See more

Customer Reviews

15
Create Your Own Review

Simple and inexpensive solution to replicate SQL Servers from West to East coast

  • By Versant Holdings, LLC
  • on 12/16/2014

Versant delivers its RN Residency program, based on a multi-tenant SaaS solution across a landscape of organizations with disparate IT infrastructure capabilities.

Our customer base spans 100+ hospitals, including Tenet Healthcare, Baptist Health of South Florida and Texas Health Resources.

We migrated our systems to AWS a year ago. Then shortly after, as part of our business continuity planning, selected the pre-AWS Marketplace version of CLOUDBASIC REPLICATE to handle our RDS SQL Servers replication from West to East coast. As a result we are in a position to switch our primary systems location to East coast at any time.

Not only natural disasters, network or power outages can be the reason for our systems to go down. Software or human errors can also cause our systems to malfunction for prolonged period of time. With tens of thousands of concurrent users, throughout 100+ hospitals, our systems must remain operational 365x24x7.

We have recently upgraded CLOUDBASIC REPLICATE to the latest AWS Marketplace version. The latest version appears to be as stable as the previous one. But the vendor has simplified the system management. We receive same priority support as before.


Jane Olson,
Asst. VP, Service Delivery,
Versant Holdings, LLC

Easy setup. Various deployment scenarios.

  • By J.P, Solution Architect
  • on 12/08/2014

We were looking to utilize AWS as a fail-over site for our on-premise SQL Server based applications. We turned to the AWS Market place to find solutions to help us speed up implementation. Found this product, and within minutes were able to stream SQL Server data to an RDS SQL Server on AWS. All we had to do is enter source and destination SQL server connection strings. Then selected if we wanted a one time migration of the SQL server or also wanted the system to setup for us continuous data replication

We realized that within AWS this product can do Geo-replication providing read-only access to the replica instance, which would allow us to run reporting against the SQL Server replica. It can also do continuous AWS cross-region replication in parallel. We are considering to migrate our primary systems to AWS and deploy our systems with Geo-replication in a primary west coast AWS location and also maintain a fail-over location on east coast.

We experienced some problems at the beginning but were able to resolved them with the help of this source: http://help.cloudbasic.net

Powerful Yet Simple Replication Solution

  • By George K
  • on 12/03/2014

The most important feature we were looking for was to be able to access the end point of the replica for our reporting.

This product replicates between SQL servers manages by us. We have to ensure the destination SQL Server is used in read-only mode, but this gives us the flexibility to setup replication in various scenarios: on-prem to AWS, across AWS regions, zone-to-zone. It does seem that SQL Server Web edition is supported in all scenarios as well. Since we can launch this server behind VPC we are planning to setup secure continuous db replication of on-prem to AWS.

We experienced some setup problems at the beginning. But after visiting the known issues help section, all went smooth after that.

Works very well. Easy to use. Some minor issues need to be addressed.

  • By John M.
  • on 11/30/2014

We intended to use this software to do a one time migration of SQL databases from our co-located datacenter to AWS.
Then figured it is very easy to setup continuous replication from East to West coast (AWS in California to AWS in Virginia). We currently use EC2 SQL Server Web edition in California, replicating to a small RDS Web Edition in Virginia. Will be finalizing implementation of Pilot Light fail-over DR setup.

Some minor issues that we hope will be addressed in the next version:

- took us a while to figure out why the destination connection string to RDS was not working. Turned out port 1433 should be removed from the connection string (
- Data Source=*******.rds.amazonaws.com:1433;Initial Catalog=*****;Persist Security Info=False;User ID=****;Password=****

- in the Quick Setup Wizard, if option 3 (Replicate source DB structure plus data plus setup continuous replication) is selected, after the initial transfer is completed, we would suggest that the continuous replication (CDC schedule) is setup automatically upon successful completion of the initial transfer. We were wondering why the CDC was not scheduled even that we selected option 3 ... then we figured had to click a little orange button in the logs.

- for our EC2 instance type (M3.medium) the windows service executing the CDC schedule was not starting. Had to manually re-install it.

Doesn't work

  • By Mark Wong
  • on 11/19/2014

Lack of documentation

Try to set it up to replicate between 2 RDS MS SQL within the same region. Doesn't seems to let me specify a port on the connection string. Took me a while to figure out it doesn't like hostname:port.

Using the Quick setup wizard, it will always try to create the destination database and the "Do nothing" when destination database already exist option doesn't work. I then dropped the database to let it run. OK then it worked for a initial transfer.

Later I restart the whole process again doing the advance option. Initial replication went okay. The schedule job that perform track changes never kick in. Well, the scheduler doesn't seems to do schedule. At least the schedule - execution log always show ...

Finally, I do a "manual" track changes transfer. The log said it managed to find 100 rows of changes (Did insert 100 new rows to the table). I found on the destination only 88 new rows got inserted.

Given the above, don't think I can use this version 1.0 at all.