Backup and Restore Procedure

Purpose. This procedure sets the backup schedule, monitoring, restore testing and record keeping for every managed client.

1.Scope

This procedure applies to servers, virtual machines, cloud mailboxes, cloud files, databases and network device configurations for every managed client, and to Nova's own systems.

2.Backup schedule

Servers and virtual machines will be backed up nightly with a local copy and an off-site copy. Cloud mailboxes and files will be backed up three times a day. Network device configurations will be backed up after every change and weekly. Retention will follow the client's contract, with a minimum of 30 daily, 12 monthly and 7 yearly points.

• Servers: nightly, local plus off-site
• Cloud mail and files: three times daily
• Device configurations: after change and weekly
• Retention: 30 daily, 12 monthly, 7 yearly minimum

3.Monitoring

Backup jobs report to the monitoring platform. A failed or missed job will raise a ticket automatically and must be investigated the same business day. Two consecutive failures for one client must be escalated to the Network and Infrastructure Manager.

4.Restore testing

A file level restore will be tested for every client each month and a full server or mailbox restore each quarter. Test results, including the time taken and any problems, must be recorded in the ticket and on the client's site documentation.

5.Restore requests

Restore requests must be logged as a ticket with the item, the date required and the reason. The engineer must confirm the target location with the user so that current data is not overwritten and must record what was restored.

6.Immutable copies and ransomware

Off-site copies must be immutable for the retention period so that ransomware cannot encrypt or delete them. Restore credentials must be held in the password vault and not on any domain joined system.