Windows Server Backup

Use the Backup Schedule wizard in the Windows Server Backup MMC snap-in, or script it with the wbadmin command line. Scheduled backups write to a dedicated target disk and use Volume Shadow Copy Service (VSS) for point-in-time versions. Be aware the wizard formats the backup target, so don't point it at a volume holding other data.

The GUI won't schedule backups to a network location for versioned history, but you can target a UNC share using wbadmin from the command line — the catch is that it keeps only the most recent backup at that destination, overwriting the previous one each run. Many admins back up locally first and then copy the VHDs off-box. This limitation is why NAS-centric shops often buy third-party tools.

Yes — a full server backup includes bare-metal recovery components plus system state, so you can rebuild a failed server by booting from Windows installation media and restoring the image. System state backups separately cover things like Active Directory for domain controllers. These features have been built into Windows Server since the 2008 generation, at no extra cost.

Windows Server Backup is free and adequate for a single server with simple needs — full, incremental, and scheduled volume protection with point-in-time restore. Veeam Backup & Replication adds agent-based VM protection, better retention, verification, and replication; its free Community Edition covers up to 10 workloads. Most multi-server or virtualized environments outgrow WSB quickly.