Documentation
CloudBasic:
- What is CloudBasic:
- Most common scenarios:
- Using CloudBasic:
- Prerequisites
- Limitations
- Supported MS SQL Server Versions
- Deployment Guide (PDF)
- Release Notes
- Get Started - Configure Multi-AZ or Multi-AR with Readable Replicas
- SQL Server to SQL Server Replication
- SQL Server to Redshift
- SQL Server to S3 Data Lake
- Monitor a Continuous Copy Relationship
- Promote RDS/SQL Server Read-Replica to Primary
- Terminate a Continuous Copy Relationship
- Logs and Errors
- Warnings
- How To Upgrade
- Updating your version
- CloudBasic advanced features:
- Working in AWS:
- RDS Assemblies Activation Test
- RDS/SQL Server User Management
- RDS/SQL Server Backup and restore from/to S3
- RDS/SQL Server Snapshot-Restore
- VPN/VPC - Replication over VPN/VPC
- Compare Instance Types (Features & Support Details)
- How To Extend the Default Data Storage
- Attach IAM Role to EC2 and Redshift Cluster
- Deployment guide:
- Additional topics:
API Documentation:
- Default API Configuration
- Instance Management:
- User Management:
- Replication Management:
- CreateReplication
- CreateAllReplication
- GetReplicationsList
- ReplicationStatus
- AlterReplication
- DeleteReplication
- StartReplicationService
- StopReplicationService
- AnalyzeReplication
- CreateRedshiftReplication
- AlterRedshiftReplication
- DeleteRedshiftReplication
- CreateS3Replication
- AlterS3Replication
- DeleteS3Replication
- GetLogs
- RebuildDbReplicaIndexes
- RebuildDbReplicaIndexesStatus
- ReseedTable
- ReseedTableStatus
- Multi-AZ HA Cluster Management:
- Lambda/node.js Example:
- Disaster Recovery & No-Downtime Migration Management
- Service Management:
How To Upgrade
There are two ways to upgrade CloudBasic server's processing power:
Option 1: Launch another instance and configure a Multi-AZ HA Cluster
(supported in version 7.16 and above and for EC2 instance type Large and above in version 7.nn, XLarge and above in version 8.nn ).
All it takes is to add the IP of the other server (got to AdvancedMulti-AZ HA Cluster). The cluster will load balance the replication processing and the workload of the previously ran as standalone server will be reduced by 50%. On top of this you will gain High Availability benefits. If one of the servers is down for maintenance or affected by an outage, the other one will pick up the processing.
Option 2: Upgrade to a larger instance type.
You do not have to boot up a new server from the AWS Marketplace. You need to:
2.1. Stop the server
2.2. Right-click on the server > select "Instance Settings" > select "Change Instance Type"
2.3. Select a larger instance type:
2.4. Boot up the server
All existing replications will continue to work.