(site a)---[replicate local LUNs/shares to remote storage arrays]--->(site b),
(site a)---[replicates local VMs to remote HCI]--->(site b),
(site a)---[local backups to local data archive]--->(site a),
(site a)---[local data archive replicates to remote data archive]--->(site b),
(site b)---[remote data archive replicates to remote air gapped data archive]--->(site b),
(site a)---[replicates to cold storage on aws/gcp/azure]--->(site c),
(site c)---[replicate to another geo site on cloud]--->(site d)
scenario 1: site a is down
plan: recover to site b by most convinent means
scenario 2: site b is down
plan: restore services, operate without redundancy out of site a
scenario 3: site c is down
plan: restore services, catch up later. continue operating out of site a
scenario 4: site b and c down
plan: restore services, operate without redundancy out of site a
scenario 5: site a and b down
plan: cross fingers, restore to new site from cold storage on expensive cloud VM instances
scenario 6: data archive corrupted ransomware
plan: restore from air gapped data archive, hope ransomware was identified within 90 days
scenario 7: site b and c down, then site a down
plan: quit
scenario 8: staff hates job and all quit
plan: outsource
scenario 1: site a is down plan: recover to site b by most convinent means
scenario 2: site b is down plan: restore services, operate without redundancy out of site a
scenario 3: site c is down plan: restore services, catch up later. continue operating out of site a
scenario 4: site b and c down plan: restore services, operate without redundancy out of site a
scenario 5: site a and b down plan: cross fingers, restore to new site from cold storage on expensive cloud VM instances
scenario 6: data archive corrupted ransomware plan: restore from air gapped data archive, hope ransomware was identified within 90 days
scenario 7: site b and c down, then site a down plan: quit
scenario 8: staff hates job and all quit plan: outsource
scenario 9: and so on...