关于Windows Server Backup Catalog与系统镜像恢复后备份可用性的技术咨询

Hey Jeff, great question—this is a super common pain point when mixing full system imaging tools like Macrium Reflect with Windows Server Backup (WSB). Let’s break this down clearly:

1. Will those 2 weeks of recent backups show up after restoring an old system image? #

Short answer: No, not by default. Here’s why:
When you restore a 2-week-old system image, you’re rolling back everything on your server’s OS volume—including the WSB catalog, which tracks all the backups WSB has created. The old catalog only knows about backups up to the date of the image, so it won’t recognize any backups made in the 2 weeks since then.

But don’t panic: the backup files themselves are still perfectly intact on your storage location. You just need to tell WSB they exist by importing the catalog copy stored with the backups.

2. Where are WSB catalog files located? #

There are two key places:

• Local server (OS volume): The primary catalog lives in C:\Windows\System32\wbadmin. Look for files like catalog.wbc—this is the main database WSB uses day-to-day.
• Backup storage location: WSB automatically saves a copy of the catalog alongside your backup files (whether that’s an external drive, network share, or other storage). This is your safety net if the local catalog gets lost or rolled back.

You can verify the current catalog’s status with this admin command prompt command:

wbadmin get catalog

3. Is the catalog on the server or the backup storage? #

It’s both:

• The working catalog is on the server’s OS volume (so it’s fast to access for daily operations).
• A redundant copy is stored with your backups, specifically for scenarios like the one you’re describing—when the local catalog is rolled back or corrupted.

Fixing the issue: Accessing those recent backups after restoring the image #

To get WSB to recognize the 2 weeks of backups made after your system image, you just need to import the catalog from your backup storage. Here’s how:

1. Open an elevated Command Prompt (right-click, "Run as administrator").
2. Run this command, replacing <backup-storage-path> with the actual path to where your WSB backups are stored (e.g., D:\WSB-Backups or \\backup-server\wsb-share):

   wbadmin restore catalog -backuptarget:<backup-storage-path>
   

3. Follow the on-screen prompts to confirm the import. Once done, open Windows Server Backup and you’ll see all your recent backups listed.

Pro tip to avoid this hassle in the future #

Consider manually exporting a copy of the WSB catalog to your backup storage after each daily backup. Use this command:

wbadmin export catalog -backuptarget:<backup-storage-path> -exportpath:<path-to-save-catalog>

This gives you an extra copy you can quickly import if you ever need to restore an old system image again.

备注：内容来源于stack exchange，提问作者Jeff Margel