Hi Hram Admin
Thank you for posting your question in the Microsoft Q&A forum regarding Windows Server Backup (WSB) schedules and Exchange Server behavior. This is a common point of confusion because WSB handles data storage differently from how it handles application consistency (Exchange logs).
Based on your specific questions and the explanation of the behavior shown in your screenshots, I would like to share some information and recommendations that I hope will help.
Create two separate schedules (for Full and Incremental) in WSB?
You cannot create two separate schedules (ex: Sunday Full, Weekdays Incremental) using the Windows Server Backup GUI. The GUI allows only a single backup policy per server.
To achieve a complex schedule, you must use Windows Task Scheduler combined with the wbadmin command-line tool. You would disable the automatic schedule in the WSB GUI and create two Task Scheduler jobs: (wbadmin start backup | Microsoft Learn)
- Sunday Task (Full):
(Thewbadmin start backup -backupTarget:D: -include:C: -vssFull -quiet-vssFullswitch tells Exchange to truncate transaction logs after a successful backup). - Weekday Task (Incremental):
wbadmin start backup -backupTarget:D: -include:C: -delivery:incremental -quiet
For more information, you can referral to:
Use Windows Server Backup to back up Exchange | Microsoft Learn
Using Windows Server Backup to back up and restore Exchange data | Microsoft Learn
Does WSB support Differential backups?
No, Windows Server Backup does not natively support Differential backups. It supports only Full and Incremental.
Regarding your P.S. and screenshots (The "53.8 GB vs 53.9 GB" observation), you noticed that running a second "Full Backup" did not double the used disk space. This is actually expected behavior and is a feature of WSB. It is important to distinguish between Application Backup Type and Storage Backup Type:
- VSS Backup: When you select "VSS Full Back up," WSB signals Exchange to verify the database and truncate (delete) the transaction logs.
- Disk Storage: When backing up to a local disk, WSB behaves like an incremental backup at the block level, even if "Full" is selected. WSB performs block-level comparison between the source volume and the existing backup, writing only the modified blocks to the target disk. It leverages Volume Shadow Copy snapshots so that each backup is presented as a full backup during restoration, while in practice consuming only the storage footprint of an incremental backup.
Your second backup was indeed a "Full VSS Backup" (logs were truncated), but because very little data changed on the disk between the two runs, WSB only wrote the changed bits (~0.1 GB), saving you significant storage space.
Because WSB is efficient at the block level, most Exchange administrators do not need to set up complex schedules via Task Scheduler. I recommend simply configuring a Daily Schedule in the WSB GUI with the "Faster Backup Performance" option enabled. This ensures Exchange logs are truncated daily (VSS Full) and storage space is optimized (Block-level Incremental).
Hope this information helps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.