How to Restore Individual Files with Windows Server Backup
Applies to: Windows Server 2019, 2022 and 2025.
File recovery should restore to an alternate path first when overwriting current data could destroy newer work.
Recovery procedures must be tested before an outage. Protect backup credentials and keep at least one recovery path separate from production. Visit networkmanager.info.
Prerequisites
- Identify backup version and source volume.
- Confirm requested file ownership and authorization.
- Choose alternate restore path.
- Check free space and malware risk.
Procedure
Step 1: List versions
Find the correct recovery point.
wbadmin get versionsStep 2: Inspect available items
Record VersionIdentifier and source volume.
Step 3: Start recovery
Use the correct version and item path; this example restores to an alternate location.
wbadmin start recovery -version:<VersionIdentifier> -itemType:File -items:D:\Shares\Finance\Report.xlsx -recoveryTarget:C:\RestoreReview -notRestoreAcl -quietStep 4: Review restored file
Validate content, timestamp and owner approval.
Step 5: Return to production
Copy through the normal permissions and change process.
Verification
Confirm file presence, hash and expected application readability.
Get-Item C:\RestoreReview\Report.xlsx
Get-FileHash C:\RestoreReview\Report.xlsxRollback and recovery considerations
Delete the alternate review copy only after successful return and audit requirements permit it. If an overwrite occurred, use a later or earlier recovery point to reconstruct the correct version.
Operational notes
Decide carefully whether ACLs should be restored; alternate-path review often benefits from controlled new permissions.
