Server Backup and Disaster Recovery Procedures

The following procedures and methods are used for information services backup.

Daily backup of on-premises virtual machines to on-premises external hard drive
- Windows Server Backup or Windows Backup
- GIOTTO, LEONARDO, TIME-PC
Replication of virtual servers from primary host to secondary host
- Virtual Machines on primary host are replicated every 5 minutes to secondary host using Hyper-V replication
Extended replication of secondary host to cloud host
- Virtual machines on secondary host are replicated every 5 minutes to cloud host at Key Information Solutions
Active Directory synchronization with M365 accounts
- Azure AD sync is deployed on DAVINCI to sync all AD accounts
Daily backup of virtual machines to cloud host
- Synology Active Backup is deployed on GIOTTO, LENOARD, TIME-PC
Daily backup of all M365 cloud data to cloud host
- Synology M365 Cloud backup to Key Information Solutions
- All mailboxes, SharePoint, Teams, OneDrive data is backed up

Disaster Recovery Processes
1. Local Severs (Critical Hardware Failure- to include full outline, process and procedure for restoration in the event of an emergency hardware failure.)
  - RAPHAEL, BRONZINO
  - Use Windows Hyper-V Manager or Powershell from the KIS extended Hyper-V host to initiate unplanned failover
  - Start VMs from KIS extended host
  - Configure remote users with VPN access to KIS network
  - Verify connection to GSC servers
  - Assess failed GSC hardware and repair or replace
  - Reinstall Hypervisor on GSC hardware
  - Configure for replication to KIS server
  - Initiate planned failover to GSC servers
  - Connect users to GSC VPN for access to GSC VMs
2. Virtual Machines (to include full outline, process and procedure for restoration.)
  - Davinci, GIOTTO, HVadmin, Leonardo, Time
  - Restoration of the Hypervisor as noted above
  - Reverse the replication as noted above
  - VMs are restored using Planned Failover replication in Hyper-V Manger

Disaster action checklist

Last Updated: 2024-3-21

This checklist provides possible initial actions that you might take following a disaster.

Plan initiation:
1. Notify senior management
2. Contact and set up disaster recovery team
3. Determine degree of disaster
4. Implement proper application recovery plan dependent on extent of disaster
5. Monitor progress
6. Contact backup site and establish schedules
7. Contact all other necessary personnel–both user and data processing
8. Contact vendors–both hardware and software
9. Notify users of the disruption of service
Follow-up checklist:
1. List teams and tasks of each
2. List all personnel and their telephone numbers
3. Determine applications to be run and in what sequence
4. Ensure that all personnel involved know their tasks
5. Notify insurance companies