Company Backup and Restore Test: Review Data with 3-2-1, Then Practice Restores Quarterly

Project & Development

Company Backup and Restore Test: Review Data with 3-2-1, Then Practice Restores Quarterly

Intermediate | 4 whiteboard pages · Task board: 5 columns (4 parent tasks, 12 subtasks)

Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.

Review your company's backups and run a restore test (actually bringing data back) once a quarter, four times a year, so every piece of data you protect is restored once a year. File server, business system, and cloud data are relocated under the 3-2-1 rule (three copies, two kinds of storage, one offsite), plus one copy disconnected from the network or unchangeable. For admin or IT staff at small firms guarding against failures, accidental deletion, and ransomware. Start by noting from your backup software or NAS console what is saved, how often, and where. Then check three weak points: backups on the same network as the original, an admin account shared with everyday logins, and data never restored. Restore periods for deleted cloud files vary by service, contract, and settings; check the console and latest guidance. Recovery order after a breach is out of scope. The whiteboard has four pages; the task board has five columns, 4 parent tasks, and 12 subtasks.

0 Likes 0 Copies Author: WeProcess
backup 3-2-1 rule restore test ransomware protection information security
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Read the whiteboard text as plain text

Company Backup and Restore Test

How to use (4 pages): ① On page 1, list the data to protect and today's storage (sections①–⑤) → ② On page 2, choose the 3-2-1 locations for each piece of data (sections⑥⑦) → ③ On page 3, check the pitfalls and decide the closing order and admin split (sections⑧–⑫) → ④ On page 4, run restore drills each quarter and log results (sections⑬–⑮)

1/4 Map the data to protect

① Purpose and scope (start here)

  • Why we are reviewing e.g. Even if the file server breaks, quotes and contracts can be opened by noon the next day
  • Scope and period e.g. File server, accounting system, cloud email and shared drive. Up to four drills in one year
  • What worries us now e.g. The NAS copy exists only in the same office. We have never restored anything

② Data to protect (location, tolerable downtime, owner)

What data Where it is Tolerable downtime Owner
Data 1 e.g. Shared folder for quotes and contracts e.g. File server in the office e.g. Half a day e.g. Office admin lead
Data 2 e.g. Accounting data e.g. Accounting software on one office PC e.g. 1 day (2 hours at month-end) e.g. Accounting lead
Data 3 e.g. Customer list and deal records e.g. Cloud customer management service e.g. 1 day e.g. Head of sales
Data 4 e.g. Staff email and shared drive e.g. Cloud email and file sharing e.g. Half a day e.g. IT lead

③ File server (current storage)

  • e.g. Copied automatically to the NAS every night
  • e.g. The NAS is in the same office and on the same network
  • Last restored: ____

④ Business system (current storage)

  • e.g. The accounting software's own function saves weekly to the same PC
  • e.g. Unclear whether the vendor takes backups under the maintenance contract
  • Questions for the vendor: ____

⑤ Cloud (current storage)

  • e.g. No separate backup for email and the shared drive
  • Pitfall: assuming the cloud is protected automatically. What happens, e.g. files deleted past the retention period cannot be restored
  • How to check, e.g. see in the console how long deleted files can be restored (varies by service, contract, and settings). How to prevent, e.g. choose another storage place in ⑦

2/4 Design where copies live

⑥ The 3-2-1 rule (compare with current storage in ③–⑤)

3 Keep three copies
  • Keep three in total: the original plus two copies
  • With only one copy, you cannot restore if it breaks too
  • e.g. A shared folder now has only the original and the NAS
2 Two kinds of storage
  • Do not keep copies on one type of device only
  • Make sure one failure cannot take out two copies at once
  • e.g. NAS plus an external drive, or NAS plus the cloud
1 One offsite
  • Keep one at another site or with an outside service
  • Also keep one copy disconnected from the network or unchangeable (an extra beyond 3-2-1)
  • e.g. Unplug the external drive after each backup and store it locked up offsite

⑦ Location table (choose three places for each data item in ②)

1st (original) 2nd (different device) 3rd (offsite, disconnected)
Data 1 e.g. File server e.g. Copy to the NAS every night e.g. Weekly to an external drive, stored offsite
Data 2 e.g. Accounting software PC e.g. Export to the NAS daily e.g. Daily to an offsite storage service (ask the vendor if it can be unchangeable)
Data 3 e.g. Cloud customer management service e.g. Export monthly to the NAS e.g. Also copy the export to an external drive, unplug it, and store it offsite
Data 4 e.g. Cloud email and file sharing e.g. Daily to a separate backup service e.g. TBD (decide the order in ⑪)

3/4 Close the gaps

⑧ Pitfall 1: same network (check the 2nd and 3rd places in ⑦)

  • What happens, e.g. ransomware makes the original and the NAS copy unusable together
  • How to check, e.g. in the network diagram or console, see whether the ⑦ destinations connect to the same place as the original
  • How to prevent, e.g. unplug the 3rd copy in ⑦ once it is done. Ask the vendor if unchangeable storage is possible
  • Data affected in ⑦: ____

⑨ Pitfall 2: same admin account

  • What happens, e.g. if an everyday account is hijacked, the backups may be deleted too
  • How to check, e.g. look at the list of accounts that can log in to the backup console
  • How to prevent, e.g. create a dedicated backup account and do not use it daily (decide in ⑫)
  • Devices or services affected: ____

⑩ Pitfall 3: never restored

  • What happens, e.g. when you finally restore, you do not know the password or the files will not open
  • How to check, e.g. see whether update or drill records show the last restore date
  • How to prevent, e.g. restore one item every quarter (plan it in ⑬ and ⑭)
  • Data never restored: ____

⑪ Closing order (place the data flagged in ⑧–⑩)

Vertical axis: Impact when stopped (higher = bigger) / Horizontal axis: Time to restore (further right = longer)

  • Big impact, quick to restore e.g. Shared quote folder. Check in the second-quarter drill in ⑭ that it really restores quickly
  • Big impact, slow to restore Close first. e.g. Accounting data. Prepare the 3rd location in ⑦ and the drill first
  • Small impact, quick to restore e.g. Old document archive. Keep it as is and check once a year
  • Small impact, slow to restore e.g. Old email. Just decide the retention period and owner

⑫ How to split admin accounts (turn the fix in ⑨ into a setup)

  • Dedicated account e.g. Create an account used only for the backup console, separate from everyday email and PC accounts
  • Login protection e.g. Add multi-factor authentication. If you can choose, use an authenticator app or passkey. SMS is better than nothing but weaker. Check the product guide or vendor for supported methods
  • Who holds it and how to store it e.g. No more than two people hold it. Do not write the password on this whiteboard; store it with the method your company has chosen

4/4 Run restore drills

⑬ The five restore steps (pick one item from the upper right of ⑪)

  1. Choose Pick one item to restore e.g. From the accounting data in the upper right of ⑪, last month's data
  2. Prepare a place Restore to a place separate from production e.g. A practice folder or a spare PC. Do not overwrite the original
  3. Restore Restore following the procedure e.g. Write the start and end times
  4. Check Open it and look inside e.g. Files open, data runs to the latest date, counts match
  5. Record Write the time and result e.g. Took 2 hours. Line 3 of the procedure was out of date → go to ⑭

⑭ Quarterly drills (item and result)

Item restored Time taken Result and fixes
Quarter 1 e.g. Accounting data (last month) e.g. 2 hours e.g. Restored. Fix line 3 of the procedure
Quarter 2 e.g. Shared quote folder e.g. 40 minutes e.g. Restored. Name a second person to hold the admin account
Quarter 3 e.g. Cloud shared drive e.g. Planned: 1 hour e.g. Also check how long deleted files can be restored
Quarter 4 e.g. Customer list and deal records (exported) e.g. Planned: 30 minutes e.g. Line up a year of times and report to management

⑮ How to keep a record of results

  • Where to record e.g. Write what was restored, the time, and the result in the table in ⑭ and in the subtask descriptions on the task board
  • What to fix e.g. Fix outdated steps or missing permissions before the next drill, and write them in the Result and fixes column of ⑭
  • Pitfall: no restore order or time decided What happens, e.g. you hesitate over what to restore first, and the downtime drags on How to check, e.g. see whether a record of the restore order exists How to prevent, e.g. line up the times in ⑭, settle the order with the owner, and record it

Task board contents

Not started 16 items

Map your data

On page 1, write down why you are reviewing, the data to protect, where it lives, how long a stop is tolerable, and who owns it. The data you list here becomes the storage plan on page 2 and the drill targets. Press Ctrl+F (⌘F on Mac) and type 3/4 to jump to page 3.

Check backup setup

First step. Open your backup software or NAS console and copy the folders covered, frequency, destination, and last successful date into the matching frames of sections ③–⑤. For cloud services, look for the setting showing how long deleted files can be restored. Done when you have copied them in about 15 minutes.

Set goal and scope

In section ①, write why you are reviewing, the scope and period, and what worries you now. Done when the three notes are filled.

Fill in data table

In the table of section ②, list four pieces of data to protect, then fill in where each lives, how long a stop is tolerable, and who owns it. Done when all four rows have an owner.

Design storage

On page 2, compare the three pillars of the 3-2-1 rule with today's storage from page 1, and choose three places for each piece of data (the original plus two copies). On page 3 you check these places against the pitfalls.

Read the 3 pillars

Read the three columns of section ⑥ and mark any pillar your current storage in sections ③–⑤ is missing. Done when you know which pillars are missing.

Fill the locations

In the table of section ⑦, write the first, second, and third location and the frequency for each piece of data from section ②. Write TBD in any blank and settle the order on page 3.

Pick isolated copy

In the third column of section ⑦, decide how to disconnect the copy from the network or make it unchangeable. If you use a vendor's service, ask the vendor whether it can be set up.

Close the gaps

On page 3, check the three pitfalls, then decide the order for closing them and how to split the admin account. Fixing settings falls under this parent task, so it takes the most time.

Check 3 pitfalls

In each frame of sections ⑧–⑩, write what happens, how to check, and the one step to prevent it. In the last note of each frame, add the data or device affected and the data never restored. Done when the last notes of all three frames are filled.

Rank gaps to close

In section ⑪, place the data flagged in sections ⑧–⑩ by impact when stopped and time to restore. Close the ones in the upper right first.

Split admin account

As in section ⑫, create a dedicated backup admin account and add multi-factor authentication (check the product guide or vendor to see if it can be added). Done once you confirm in the console that the everyday account cannot operate it.

Run restore drills

On page 4, go through the five restore steps once, then plan four drills for the year and decide how to keep records. Track drills in progress in the Restore practice column of the task board.

Do the first drill

Following the five steps of section ⑬, restore data picked from the upper right of section ⑪ to a place separate from production, then open it to check. Done when you write the time taken in the first quarter row of section ⑭.

Build yearly plan

In the second to fourth quarter rows of section ⑭, decide one restore target each. Choose targets so each piece of data in section ② is covered once in the year.

Decide how to log

In section ⑮, write where you record, what to fix, and the restore-order discussion. Done when the three notes are filled and you have written the next drill date and owner in this subtask's description.

Mapping data 0 items

Fixing settings 0 items

Restore practice 0 items

Recorded 0 items

← Back to templates

Preview mode Company Backup and Restore Test: Review Data with 3-2-1, Then Practice Restores Quarterly

Whiteboard preview

① Purpose and scope (start here) ② Data to protect (location, tolerabl... ③ File server (current storage) ④ Business system (current storage) ⑤ Cloud (current storage) ⑦ Location table (choose three places... ⑧ Pitfall 1: same network (check the ... ⑨ Pitfall 2: same admin account ⑩ Pitfall 3: never restored ⑪ Closing order (place the data flagg... Big impact, quick to restore Big impact, slow to restore Small impact, quick to restore Small impact, slow to restore ⑫ How to split admin accounts (turn t... ⑬ The five restore steps (pick one it... ⑭ Quarterly drills (item and result) ⑮ How to keep a record of results Company Backup an... How to use (4 pag... What to protect a... Decisions and steps Pitfalls and worries Drill results and... 1/4 Map the data to p... Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Design where copi... ↙ 3/4 Why we are reviewinge.g. Even if the file server breaks, quotes and contracts can be opened by noon the next day Scope and periode.g. File server, accounting system, cloud email and shared drive. Up to four drills in one year What worries us nowe.g. The NAS copy exists only in the same office. We have never restored anything What data Where it is Tolerable downtime Owner Data 1 e.g. Shared folder for quotes and contracts e.g. File server in the office e.g. Half a day e.g. Office admin lead Data 2 e.g. Accounting data e.g. Accounting software on one office PC e.g. 1 day (2 hours at month-end) e.g. Accounting lead Data 3 e.g. Customer list and deal records e.g. Cloud customer management service e.g. 1 day e.g. Head of sales Data 4 e.g. Staff email and shared drive e.g. Cloud email and file sharing e.g. Half a day e.g. IT lead e.g. Copied automatically to the NAS every night e.g. The NAS is in the same office and on the same network Last restored: ____ e.g. The accounting software's own function saves weekly to the same PC e.g. Unclear whether the vendor takes backups under the maintenance contract Questions for the vendor: ____ e.g. No separate backup for email and the shared drive Pitfall: assuming the cloud is protected automatically. What happens, e.g. files deleted past the retention period cannot be restored How to check, e.g. see in the console how long deleted files can be restored (varies by service, contract, and settings). How to prevent, e.g. choose another storage place in ⑦ ⑥ The 3-2-1 rule ... 3Keep three copies Keep three in total: the original plus two copies With only one copy, you cannot restore if it breaks too e.g. A shared folder now has only the original and the NAS 2Two kinds of storage Do not keep copies on one type of device only Make sure one failure cannot take out two copies at once e.g. NAS plus an external drive, or NAS plus the cloud 1One offsite Keep one at another site or with an outside service Also keep one copy disconnected from the network or unchangeable (an extra beyond 3-2-1) e.g. Unplug the external drive after each backup and store it locked up offsite 1st (original) 2nd (different de... 3rd (offsite, dis... Data 1 e.g. File server e.g. Copy to the NAS every night e.g. Weekly to an external drive, stored offsite Data 2 e.g. Accounting software PC e.g. Export to the NAS daily e.g. Daily to an offsite storage service (ask the vendor if it can be unchangeable) Data 3 e.g. Cloud customer management service e.g. Export monthly to the NAS e.g. Also copy the export to an external drive, unplug it, and store it offsite Data 4 e.g. Cloud email and file sharing e.g. Daily to a separate backup service e.g. TBD (decide the order in ⑪) 3/4 Close the gaps → 4/4 4/4 Run restore drills What happens, e.g. ransomware makes the original and the NAS copy unusable together How to check, e.g. in the network diagram or console, see whether the ⑦ destinations connect to the same place as the original How to prevent, e.g. unplug the 3rd copy in ⑦ once it is done. Ask the vendor if unchangeable storage is possible Data affected in ⑦: ____ What happens, e.g. if an everyday account is hijacked, the backups may be deleted too How to check, e.g. look at the list of accounts that can log in to the backup console How to prevent, e.g. create a dedicated backup account and do not use it daily (decide in ⑫) Devices or services affected: ____ What happens, e.g. when you finally restore, you do not know the password or the files will not open How to check, e.g. see whether update or drill records show the last restore date How to prevent, e.g. restore one item every quarter (plan it in ⑬ and ⑭) Data never restored: ____ Vertical axis: Im... e.g. Shared quote folder. Check in the second-quarter drill in ⑭ that it really restores quickly Close first. e.g. Accounting data. Prepare the 3rd location in ⑦ and the drill first e.g. Old document archive. Keep it as is and check once a year e.g. Old email. Just decide the retention period and owner Dedicated accounte.g. Create an account used only for the backup console, separate from everyday email and PC accounts Login protectione.g. Add multi-factor authentication. If you can choose, use an authenticator app or passkey. SMS is better than nothing but weaker. Check the product guide or vendor for supported methods Who holds it and how to store ite.g. No more than two people hold it. Do not write the password on this whiteboard; store it with the method your company has chosen ChoosePick one item to restoree.g. From the accounting data in the upper right of ⑪, last month's data Prepare a placeRestore to a place separate from productione.g. A practice folder or a spare PC. Do not overwrite the original RestoreRestore following the proceduree.g. Write the start and end times CheckOpen it and look insidee.g. Files open, data runs to the latest date, counts match RecordWrite the time and resulte.g. Took 2 hours. Line 3 of the procedure was out of date → go to ⑭ Item restored Time taken Result and fixes Quarter 1 e.g. Accounting data (last month) e.g. 2 hours e.g. Restored. Fix line 3 of the procedure Quarter 2 e.g. Shared quote folder e.g. 40 minutes e.g. Restored. Name a second person to hold the admin account Quarter 3 e.g. Cloud shared drive e.g. Planned: 1 hour e.g. Also check how long deleted files can be restored Quarter 4 e.g. Customer list and deal records (exported) e.g. Planned: 30 minutes e.g. Line up a year of times and report to management Where to recorde.g. Write what was restored, the time, and the result in the table in ⑭ and in the subtask descriptions on the task board What to fixe.g. Fix outdated steps or missing permissions before the next drill, and write them in the Result and fixes column of ⑭ Pitfall: no restore order or time decidedWhat happens, e.g. you hesitate over what to restore first, and the downtime drags onHow to check, e.g. see whether a record of the restore order existsHow to prevent, e.g. line up the times in ⑭, settle the order w… → 2/4 Design where copi... ↙ 3/4 Close the gaps → 4/4 Run restore drills
100%

Drag to move, scroll to zoom