Exchange Server backup

Hram Admin 330 Reputation points
2026-01-26T08:27:23.7333333+00:00

Hello!

Suppose you've been tasked to configure Exchange Server backups in Windows Server Backup with the following schedule:

  1. Sunday - Full
  2. Monday through Friday - Incremental or Differential

Maybe I'm missing something but I don't see how I can create two separate schedules in Windows Server Backup - there's only the Optimize Backup Performance window in which I can choose the backup option: either Full Backup or Incremental Backup - and no "Differential" option in there.:

00

Q1: How can I create two separate schedules (for Full and Incremental backups) in WSB?

Q2: Am I getting it right that WSB does not support differential backups?

P.S. Frankly speaking I don't understand what does the Incremental backup option do in the aforementioned screenshot - by default WSB always makes (at least tries) to create incremental backups even when the Backup Option is set to Full backup:02-Backup2-list

Here I've taken two full volume backups in a raw and used space after the second backup became 53.9 GB while it was 53.8 GB after the first backup.

Used space on volume C: (the one that was backed up):

03

Regards,

Exchange | Other
Exchange | Other
A powerful email and collaboration platform developed by Microsoft, designed to support enterprise-level communication and productivity. Miscellaneous topics that do not fit into specific categories.
0 comments No comments
{count} votes

Answer accepted by question author
  1. Hani-Ng 8,105 Reputation points Microsoft External Staff Moderator
    2026-01-26T10:32:51.44+00:00

    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):
        wbadmin start backup -backupTarget:D: -include:C: -vssFull -quiet 
      
      (The -vssFull switch 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.

    1 person found this answer helpful.

5 additional answers

Sort by: Most helpful
  1. Hram Admin 330 Reputation points
    2026-01-27T09:20:02.0533333+00:00

    Hi Hani-NG,

    Thank you so much for your explanation!!! In fact this -

    "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 "

    ...is not true: I've already read those articles and they didn't have the information you posted here :)

    I'd like to clarify a few more points here, please:

    1. "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."

    I don't understand what in WSB let me choose between Application Backup Type and Storage Backup Type: if - according to the text above - Application Backup Type = VSS Backup and Storage Backup Type = Disk Storage then selecting VSS Full Back up may apply for both options if the destination is set to local volume...

    In other words if

    a) I select VSS Full Backup to local volume is it Application or Storage backup type?

    b) I select VSS Full Backup to network volume is it Application or Storage backup type?

    .2. You recommend creating a single schedule with "Faster Backup Performance" option to make sure

    a) Exchange logs are truncated daily
    b) storage space is optimized

    ...but exactly the same results may be achived by using the VSS Full Backups WITHOUT "Faster Backup Performance" option (as we discussed above) - what's the difference in this case???

    (this article in 8. offers to create VSS Full backups without that option).

    Regards,


  2. Hram Admin 330 Reputation points
    2026-01-28T16:34:53.1366667+00:00

    Hani-Ng, I've learnt many MS official curriculums on various Windows Server editions (which contained chapters on Windows Server Backup) and read plenty of articles online but have NEVER seen anything so useful as your posts - thank you so much for your explanations!

    Regards,

    0 comments No comments

  3. Hram Admin 330 Reputation points
    2026-01-28T17:09:06.4333333+00:00

    P.S.

    MS' explanation of incremental backups seems rather weird:

    05

    If Incremental backups may "reduce disk throughput..." then why it is NOT recommended for servers with disk-intencive operations??? Shouldn't the servers with high disk loads aim not to add extra load caused by WSB???


  4. Hram Admin 330 Reputation points
    2026-01-30T08:32:05.98+00:00

    Hani-Ng, thank you so much for your clarification!!!

    Once again: MS documentation may explain dozens of times how to run a backup job and never explain how it is works under the hood!

    Regards,


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.