Windows Server Backup

Use at MachMotion

svr1.machmotion.local
- Data drive(s) are periodically backed up.
- OS drive is periodically backed up.

Goals

We want to save, as often as is feasible, recent working states of our data files. Everything in \\svr1.machmotion.local\MachMotion is backed up and made available through the "Previous Versions" mechanism.
We want to be able to restore svr1 (domain controller, file server, SVN server, etc.) should it fail or become unusable.
We want to have an off-site backup in case of damage/destruction of the shop.

General Resources

Server
- Description of the Windows NT Backup Restore Utility for Windows 7 and for Windows Server 2008 R2 (support.microsoft.com)
Desktop
- Back up and restore your PC (support.microsoft.com; Win7, Win8.1)
- Backup and Restore in Windows 10 (support.microsoft.com)
wbadmin (docs.microsoft.com)
- Windows Backup tool
Topics of Interest
- How to restore a Windows installation or move it to different hardware (support.microsoft.com)

Configuration

Windows Backup
- Items
  - Bare Metal Recovery
  - System State
  - D:
  - C:
  - RECOVERY
- Schedule
  - 9 AM
  - 12 PM
  - 5 PM
  - 11 PM
- Targets
  - svr1 2016_12_02 09:25 DISK_03

Disk name: WDC WD3003FZEX-00Z4SA0 ATA Device
Disk number: 0
Disk identifier: {4ddc8994-cbef-4ccd-92bc-f7b064c5859f
Total space: 2794.52 GB
Used space : 2794.50 GB
Volumes: <not mounted>[svr1 2016_12_02 09:25 DISK_03]

- - svr1 2016_09_01 11:14 DISK_03

Disk name: WDC WD4003FZEX-00Z4SA0 ATA Device
Disk number: 3
Disk identifier: {560feec4-eceb-4316-825b-aa6eae07c124}
Total space: 3726.02 GB
Used space : 3043.78 GB
Volumes: F:[svr1 2016_09_01 11:14 DISK_03]

I have observed that it will always backup only to the first target if it is available. I have "rotated" targets by disabling that first disk the Disk Management MMC.

Reporting

Backups should provide security (of mind). The second most basic need of the system is answering questions.

Internal Data for Windows Server Backup

- Version
  - Each attempt to back up results in a new "version."
  - Version identifiers look like a timestamp: (MM/DD/YYYY-hh:mm)

Are the backups running/working?

You can get a list of all (recent?) stored backup operations.

> wbadmin GET VERSIONS

will produce a series of records like:

Backup time: 2/19/2019 11:00 PM
Backup target: 1394/USB Disk labeled F:
Version identifier: 02/20/2019-05:00
Can recover: Volume(s), File(s), Application(s)
Snapshot ID: {78479a64-8840-4e40-a682-73646ddac1d4}