MoreCore Platform
Disaster Recovery
Failure Scenarios
MOR-PLN-039 Version 1 Last Review Date: Nov, 2024

Failure Scenarios

1. Failure Scenario List

Failure IDFailure ScenarioDescriptionConfirmation MethodRecovery ProcedureMoreCore Restoration Time
1Azure Down (Global)Microsoft Azure is down globallyPlatform down. Can't sign in to portalPlanN/A
2Azure Primary Region DownWhen Australia South East is unavailablePlanN/A
3Azure Secondary Region DownWhen Australia East is unavailablePlanN/A
4Azure Availability Zone DownPlan
5Azure Specific Resource CorruptedWhen a particular resource, ie. VM is not available or not operating as expectedPlan
5AAzure Specific Resource Failure - App ServiceCMMS is not availablePlan
5BAzure Database CorruptionCMMS is available but some functionlity not workingPlan> 12 hours
5CAzure Database Resource FailureCMMS is not availablePlan>30 Seconds
6Azure Service DownPlan
7App Code FailureCMMS is working but not as intended and/or error mesasges are occuring in the logPlan

2. Failure Verificaton Procedures

Failure ID 1 - Azure Down (Global)

Assesment Method

Attempts to reach MoreCore environments fail
Azure status monitor indicates widespread or complete outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Attempts to sign in to portal.azure.com fail

Recovery Plan

Recovery Procedure

Failure ID 2 - Azure Primary Region Down

Assesment Method

You received a notification from Azure Service Health
Azure status monitor indicates outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Azure logs / Service Health indicate Region is unavailable
CMMS is not working as expected

Certain funcationality is not working as expected

Recovery Plan

Recovery Procedure

Failure ID 3 - Azure Secondary Region Down

Assesment Method

You received a notification from Azure Service Health
Azure status monitor indicates outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Azure logs / Service Health indicate Region is unavailable
CMMS is working as expected

Recovery Plan

Recovery Procedure

Failure ID 5 - Azure Specific Resource Corrupted

Assesment Method

Check the Azure Portal for any alerts or error messages
Azure status monitor indicates outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Azure logs / Service Health
CMMS is NOT working as expected

Certain functionality is not working

Recovery Plan

Recovery Procedure

Failure ID 5A - Azure Specific Resource Failure - App Service

Assesment Method

Check the Azure Portal for any alerts or error messages
Azure status monitor indicates outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Check Azure logs / Service Health
CMMS is NOT reachable

HTTP 400 is most probably what you would be experiencing

Recovery Plan

Recovery Procedure

Failure ID 5B - Azure Database Corruption

Assesment Method

Check the Azure Portal for any alerts or error messages
Azure status monitor indicates outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Check Azure logs / Service Health
CMMS is NOT reachable

HTTP 400 is most probably what you would be experiencing

Run Integrity Checks (for SQL Databases)
  • DBCC CHECKDB: If you're using Azure SQL Database (or SQL Server in general), run the DBCC CHECKDB command to check the database for corruption. This command checks the logical and physical integrity of all the objects in the database.

    DBCC CHECKDB('YourDatabaseName');

    If any corruption is found, DBCC CHECKDB will provide error messages and, in some cases, suggest repair options.

  • Automatic Fix: In cases where corruption is detected in SQL databases, you can use the DBCC CHECKDB command with the REPAIR_ALLOW_DATA_LOSS option, but this should only be done as a last resort because it may result in data loss.

    DBCC CHECKDB('YourDatabaseName', REPAIR_ALLOW_DATA_LOSS);

Recovery Plan

Recovery Procedure

Failure ID 5C - Azure Database Resource Failure

https://learn.microsoft.com/en-us/training/modules/configure-replication-manage-failovers-azure-cosmos-db/?source=recommendations (opens in a new tab)

Assesment Method

Check the Azure Portal for any alerts or error messages
Azure status monitor indicates outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Check Azure logs / Service Health
CMMS is NOT reachable

HTTP 400 is most probably what you would be experiencing

Recovery Plan

Recovery Procedure

Failure ID 6 - Azure Service Down

Assesment Method

Check the Azure Portal for any alerts or error messages
Azure status monitor indicates outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Check Azure logs / Service Health
CMMS is reachable but not all functionality is working

Look in the browser console, see if erros are present

Recovery Plan

Link TBC

Failure ID 7 - App Code Failure

Assesment Method

Check the Azure Portal for any alerts or error messages
Azure status monitor indicates outage

Check Azure Status via https://status.azure.com/ (opens in a new tab)

Check Azure logs / Service Health
CMMS is NOT working as expected

Issues such as press a button and nothing appears to happen.

  • If you look in the browser debug section you may see errors in the console

Recovery Plan

Recovery Procedure