Autonomous AI Database (Serverless) - Cross-Region

1. Define variables for Autonomous AI Database Serverless:

   # Define variables for the Autonomous Database
   
   AZURE_SUBSCRIPTION="my_azure_subscription"
   AZURE_SUBSCRIPTION_ID="my_azure_subscription_id"
   RESOURCE_GROUP="my_resource_group"
   
   PRIMARY_ADB_NAME="autonomous_database_primary_name"
   PRIMARY_LOCATION="azure_location_primary"
   PRIMARY_ADB_ID="/subscriptions/${AZURE_SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Oracle.Database/autonomousDatabases/${PRIMARY_ADB_NAME}"
   
   STANDBY_ADB_NAME="autonomous_database_standby_name"
   STANDBY_LOCATION="azure_location_standby"
   STANDBY_VNET="standby_vnet_name"
   STANDBY_SUBNET="standby_subnet_name"
   STANDBY_VNET_ID="/subscriptions/${AZURE_SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.Network/virtualNetworks/${STANDBY_VNET}"
   STANDBY_SUBNET_ID="/subscriptions/${AZURE_SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.Network/virtualNetworks/${STANDBY_VNET}/subnets/${STANDBY_SUBNET}"

2. Select and verify the Azure subscription:

   
   az account set --subscription "$AZURE_SUBSCRIPTION"
   
   az account show \
     --query "{name:name,id:id,isDefault:isDefault,tenantId:tenantId,user:user.name}" \
     --output json

3. Show the primary Autonomous AI Database Serverless:

   
   az oracle-database autonomous-database show \
     --resource-group "$RESOURCE_GROUP" \
     --name "$PRIMARY_ADB_NAME" \
     --query "{id:id,name:name,resourceGroup:resourceGroup,location:location,lifecycleState:properties.lifecycleState,dbVersion:properties.dbVersion,dbWorkload:properties.dbWorkload,computeModel:properties.computeModel,computeCount:properties.computeCount,storageGbs:properties.dataStorageSizeInGbs,licenseModel:properties.licenseModel,subnetId:properties.subnetId,vnetId:properties.vnetId,supportedRegionsToCloneTo:properties.supportedRegionsToCloneTo}" \
     --output json

1. Do not enclose the entire --cross-region-disaster-recovery object in quotation marks. The Azure CLI extension expects separate key=value tokens for this object argument.

   
   az oracle-database autonomous-database create \
     --resource-group "$RESOURCE_GROUP" \
     --name "$STANDBY_ADB_NAME" \
     --location "$STANDBY_LOCATION" \
     --subnet-id "$STANDBY_SUBNET_ID" \
     --vnet-id "$STANDBY_VNET_ID" \
     --display-name "$STANDBY_ADB_NAME" \
     --compute-model $COMPUTE_MODEL \
     --compute-count $COMPUTE_COUNT \
     --data-storage-size-in-gbs 1024 \
     --license-model $LICENSE_MODEL \
     --db-version $DB_VERSION \
     --character-set $CHARACTER_SET \
     --ncharacter-set $NCHARACTER_SET \
     --cross-region-disaster-recovery \
       remote-disaster-recovery-type=Adg \
       source=CrossRegionDisasterRecovery \
       source-id="$PRIMARY_ADB_ID" \
       source-location="$PRIMARY_LOCATION" \
       is-replicate-automatic-backups=true

1. View existing Autonomous AI Database.

   
   az oracle-database autonomous-database list \
     --query "[?name=='$PRIMARY_ADB_NAME' || name=='$STANDBY_ADB_NAME'].{name:name,resourceGroup:resourceGroup,location:location,lifecycle:properties.lifecycleState,provisioningState:properties.provisioningState,role:properties.role,localDG:properties.isLocalDataGuardEnabled,remoteDG:properties.isRemoteDataGuardEnabled,peerDbId:properties.peerDbId,peerDbIds:properties.peerDbIds}" \
     --output table

2. Display the standby configuration:

   
   az oracle-database autonomous-database show \
     --resource-group "$RESOURCE_GROUP" \
     --name "$STANDBY_ADB_NAME" \
     --query "{name:name,state:properties.lifecycleState,provisioningState:properties.provisioningState,role:properties.role,remoteDR:properties.remoteDisasterRecoveryConfiguration,peerDbIds:properties.peerDbIds,vnet:properties.vnetId,subnet:properties.subnetId}" \
     --output json

1. For cross-region switchover and failover, use with the peer database Azure resource ID from properties.peerDbIds[0] instead of the OCI OCID. The Azure CLI help text can be misleading, but the working commands use the Azure value.

   Get the peer database ID from the database where you run the action. For the working cross-region command pattern, run the action on the current standby or disaster recovery resource so the peer is the current primary database.

   
   # Define variables for the Source Autonomous Database name
   
   ACTION_SOURCE_ADB_NAME="$STANDBY_ADB_NAME"
   
   PEER_DB_ID=$(az oracle-database autonomous-database show \
     --resource-group "$RESOURCE_GROUP" \
     --name "$ACTION_SOURCE_ADB_NAME" \
     --query "properties.peerDbIds[0]" \
     --output tsv)
   
   PEER_DB_LOCATION=$(az resource show \
     --ids "$PEER_DB_ID" \
     --query location \
     --output tsv)
   
   echo "$PEER_DB_ID"
   echo "$PEER_DB_LOCATION"
   

2. If the current primary database variables are already defined and up to date, these values are equivalent:

   
   PEER_DB_ID="$PRIMARY_ADB_ID"
   PEER_DB_LOCATION="$PRIMARY_LOCATION"

A switchover is a planned role transition between the current primary database and the remote standby database.

1. For cross-region Autonomous Data Guard, run the switchover against the current standby or disaster recovery resource. The peer is the current primary database. This approach matches the working failover command pattern and avoids the ResourcePostActionFailed: Conflict error that occurs when the action runs against the current primary database.

   
   SWITCHOVER_SOURCE_ADB_NAME="$ACTION_SOURCE_ADB_NAME"

2. Perform the switchover:

   
   az oracle-database autonomous-database switchover \
     --resource-group "$RESOURCE_GROUP" \
     --autonomousdatabasename "$SWITCHOVER_SOURCE_ADB_NAME" \
     --peer-db-id "$PEER_DB_ID" \
     --peer-db-location "$PEER_DB_LOCATION"

Use failover only when the primary database is unavailable or when the disaster recovery procedure authorizes a failover test.

1. For cross-region Autonomous Data Guard, run the failover from the current standby or disaster recovery resource. Use the current primary database as the peer database. Running the failover against the current primary database can return the ResourcePostActionFailed: Conflict error.
2. Set the failover source and peer database details:

   FAILOVER_SOURCE_ADB_NAME="$ACTION_SOURCE_ADB_NAME"

3. In this example, the failover operation runs on the standby or disaster recovery resource and uses the primary database as the peer database. Perform the failover:

   
   az oracle-database autonomous-database failover \
     --resource-group "$RESOURCE_GROUP"\--autonomousdatabasename"$FAILOVER_SOURCE_ADB_NAME"\
     --peer-db-id "$PEER_DB_ID"\
     --peer-db-location "$PEER_DB_LOCATION"

Use this procedure when an existing cross-region disaster recovery configuration must use backup-based disaster recovery instead of Autonomous Data Guard.

1. For cross-region disaster recovery, run the change against the current standby or disaster recovery resource. Running the change against the current primary database can return the ResourcePostActionFailed: Conflict error.

   
   DR_CONFIG_SOURCE_ADB_NAME="$STANDBY_ADB_NAME"
   
   az oracle-database autonomous-database change-disaster-recovery-configuration \
     --resource-group "$RESOURCE_GROUP"\--autonomousdatabasename"$DR_CONFIG_SOURCE_ADB_NAME"\
     --disaster-recovery-type BackupBased \
     --is-replicate-automatic-backups true

2. Set --is-replicate-automatic-backups to false if the design does not require replication of seven days of backups to the peer region.
3. To change the relationship back to Autonomous Data Guard:

   
   az oracle-database autonomous-database change-disaster-recovery-configuration \
     --resource-group "$RESOURCE_GROUP"\--autonomousdatabasename"$DR_CONFIG_SOURCE_ADB_NAME"\
     --disaster-recovery-type Adg \
     --is-replicate-automatic-backups true

4. Validate the disaster recovery type on the disaster recovery resource after the change:

   
   az oracle-database autonomous-database show \
     --resource-group "$RESOURCE_GROUP" \
     --name "$DR_CONFIG_SOURCE_ADB_NAME" \
     --query "{name:name,lifecycle:properties.lifecycleState,provisioningState:properties.provisioningState,role:properties.role,remoteDG:properties.isRemoteDataGuardEnabled,peerDbIds:properties.peerDbIds,remoteDR:properties.remoteDisasterRecoveryConfiguration}" \
     --output json

1. Use this procedure only to remove the remote standby database from Azure.

   
   az oracle-database autonomous-database delete \
     --resource-group "$RESOURCE_GROUP"\--name"$STANDBY_ADB_NAME"\--yes\
     --no-wait