Business Continuity & Disaster Recovery

Overview

This section contains pointers to get started with different solutions for creating backups and recovering from an unforeseen data loss.

In production, you should be using an orchestrator like Docker Swarm, Kubernetes, or Kubernetes in Azure Kubernetes Service.

WorkflowGen files

SMB file shares

You should have at least three different storage shares to handle WorkflowGen persistent files. If you used custom SMB file shares, you should have a strategy to back up the disks for the file share. If a problem occurs, you can restore a backup. Don't forget to restore the database data to the exact time as the file share backup.

Azure Files

For Azure Files, see the following documentation on backups and restorations:

• Back up Azure file shares

• Azure storage disaster recovery planning and failover

Azure Disks

For Azure Disks, see the following documentation on backups and restorations:

• Backup and disaster recovery for Azure managed disks

Database

On-premise database

See the Operations section in the WorkflowGen Technical Guide for information on backup and restoration of on-premise databases.

Azure SQL

See the following Microsoft documentation about business continuity for Azure SQL:

• Overview of business continuity with Azure SQL Database

Kubernetes

Creating backups and recovering with them in Kubernetes can be complicated, but tools exist to help manage this. Here's an article about backups with Kubernetes:

• Kubernetes: Backups and recovery

There are two main tools for backup and recovery:

• Velero

• kube-backup

Azure Kubernetes Service

As with other Azure Services, Microsoft provides guides for backups and restorations:

• Best practices for business continuity and disaster recovery in Azure Kubernetes Service (AKS)