Documentation

- Overview
- FAQ
- Use Cases
- Case Studies
- Business Continuity
- Geo-Replication (Active)
- RDS Read-Replicas (MS SQL Server)
- Cloud DR (RDS/EC2 SQL Server)
- RDS-to-Redshift Replication
- RDS-to-Hadoop Replication
- Geo-Sharding (Active)
- Prerequisites
- Limitations
- RDS/SQL Server User Management
- Supported MS SQL Server Versions
- VPN/VPC - Replication over VPN/VPC
- Get Started - Configure Multi-AZ or Multi-AR with Readable Replicas
- Attach IAM Role to EC2 and Redshift Cluster
- RDS/SQL Server Backup and restore from/to S3
- Encryption:
- Configure Multi-AZ High-Availability Cluster
- Monitor a Continuous Copy Relationship
- Logs and Errors
- Warnings
- Promote RDS/SQL Server Read-Replica to Primary
- Terminate a Continuous Copy Relationship
- Compare Instance Types (Features & Support Details)
- How To Upgrade
- How To Extend the Default Data Storage
- How to create exportable RDS DB snapshots
- External Resources
API Documentation:
- Default API Configuration
- Instance Management:
- User Management:
- Replication Management:
- CreateReplication
- CreateAllReplication
- ReplicationStatus
- AlterReplication
- DeleteReplication
- StartReplicationService
- StopReplicationService
- AnalyzeReplication
- CreateRedshiftReplication
- AlterRedshiftReplication
- DeleteRedshiftReplication
- CreateS3Replication
- AlterS3Replication
- DeleteS3Replication
- GetLogs
- Multi-AZ HA Cluster Management:
- Lambda/node.js Example:
- Disaster Recovery & No-Downtime Migration Management
Encrypting Volume
1. If operating a Multi-AZ HA Cluster, this operation can be performed without a downtime: Shut down one of the Multi-AZ High-Availability cluster member CloudBasic servers first (replication workloads will be transferred to the other server). After the encryption is completed, boot the server back up, confirm replications workload is load balanced, then shut down the other server. Previously encrypted server will pick up the entire replication workload.
If operating a single CloudBasic server, then some downtime will be involved.
2. Create a snapshot of C: drive.
3. Copy the snapshot to same zone, with selecting to encrypt the cloned snapshot (see attached)
4. Create a volume from the encrypted snapshot.
5. Detach drive C: from the server.
6. Attach the newly created encrypted volume as /dev/sda1 {suggested default is to attach it technically as D: drive. Replace "xvdf" with "/dev/sda1")