FAQ

Find answers to questions about DR Orchestrator Framework for failover and failback.

What are the RPO and RTO I can achieve using this approach?

For information about recovery time objective (RTO) and recovery point objective (RPO), see the strategy Disaster recovery strategy for databases on AWS.

Is it mandatory to use AWS CloudFormation export variables?

No, you can directly pass the value of the Amazon Aurora global database or the Amazon RDS DB instance directly in the JSON format (for example: -  "RDSInstanceIdentifier": "rds-mysql-instance").

Can I use the DR Orchestrator FAILOVER workflow to fail over more than one AWS database?

Yes, you can pass more than one resource in the input parameter file to fail over more than one AWS database. The following code example shows failing over an Amazon RDS for MySQL read replica and an Amazon ElastiCache (Redis OSS) global datastore in parallel:

{
  "StatePayload": [
    {
      "layer": 1,
      "resources": [
        {
          "resourceType": "PromoteRDSReadReplica",
          "resourceName": "Promote RDS MySQL Read Replica",
          "parameters": {
            "RDSInstanceIdentifier": "!Import rds-mysql-instance-identifier",
            "TargetClusterIdentifier": "!Import rds-mysql-instance-global-arn"
          }
        },
        {
          "resourceType": "FailoverElastiCacheCluster",
          "resourceName": "Failover ElastiCache Cluster",
          "parameters": {
            "GlobalReplicationGroupId": "!Import demo-redis-cluster-global-replication-group-id",
            "TargetRegion": "!Import demo-redis-cluster-target-region",
            "TargetReplicationGroupId": "!Import demo-redis-cluster-target-replication-group-id"
          }
        }
      ]
    }
  ]
}

How can I avoid the InvalidParameterCombination error when I run the DR Orchestrator FAILBACK state machine for Amazon RDS?

The full text of the error is:

"errorMessage": "An error occurred (InvalidParameterCombination) when calling the DeleteDBInstance operation: Cannot delete protected DB Instance, please disable deletion protection and try again."

To avoid the error, modify the RDS instance by disabling DeletionProtection before you run the DR Orchestrator FAILBACK state machine.