Important Update: Cohesity Products Documentation
All Cohesity product documentation are now managed via the Cohesity Docs Portal: https://docs.cohesity.com/HomePage/Content/home.htm. Some documentation available here may not reflect the latest information or may no longer be accessible.
NetBackup™ Release Notes
- About NetBackup 11.1.0.2
- New features, enhancements, and changes
- About new enhancements and changes in NetBackup
- NetBackup 11.1.0.2 new features, changes, and enhancements
- Changes in Cohesity terminology
- Update cloud configuration file on the primary and media server immediately after install or upgrade to NetBackup 11.1.0.2
- Several shutdown commands to be deprecated in a future release
- NetBackup 11.1.0.2 support additions and changes
- NetBackup 11.1 and earlier support additions and changes
- Support for malware scanning of hypervisor backups on OST targets
- Simplified Cloud Scale upgrade
- BMR now uses Windows ADK 10.1.22621 (ADK 2022)
- Operational notes
- About NetBackup 11.1.0.2 operational notes
- NetBackup installation and upgrade operational notes
- If NetBackup 11.1.0.2 upgrade fails on Windows, revert to previous log folder structure
- Native installation requirements
- NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
- About support for HP-UX Itanium vPars SRP containers
- Change in the default path for NetBackup installation
- NetBackup administration interface operational notes
- NetBackup Bare Metal Restore operational notes
- After PIT restore, "The host ID does not exist" error appears
- NetBackup services may not start automatically after BMR restore on a Linux client
- NetBackup Bare Metal Restore on AWS hangs when restoring a Windows 2025 client
- Mirrored dynamic volume may not receive a drive letter after Windows BMR DDR restore
- BMR Restore Failure for ReFS Volumes on Windows (2016 - 2025)
- Post Bare Metal Restore (BMR) operation, windows Start Menu and Search not functioning
- NetBackup Cloud Object Store Workload operational notes
- Full backup after upgrading from a version prior to NetBackup 11.1
- Supported version of RHEL media server as backup host
- Auto Image Replication (AIR) from NetBackup version 11.1.0.2 requires NetBackup 10.2 or later
- Backup jobs become unresponsive and consume significant space on the temporary staging location.
- NetBackup NAS operational notes
- NetBackup Cloud workload operational notes
- NetBackup internationalization and localization operational notes
- Appendix A. About SORT for NetBackup Users
- Appendix B. NetBackup installation requirements
- Appendix C. NetBackup compatibility requirements
- Appendix D. Other NetBackup documentation and related documents
BMR Restore Failure for ReFS Volumes on Windows (2016 - 2025)
During a Bare Metal Restore (BMR) on Windows Server 2016, 2019, 2022, or 2025, ReFS volumes fail to restore and appear in an "Unformatted" state.
This occurs because no version of ADK/WinPE supports bare‑metal or block‑level restore of ReFS volumes, due to incompatibilities between ReFS versions.
Table:
Windows Version | ReFS Version |
|---|---|
Windows Server 2016 | 3.1 |
Windows Server 2019 | 3.4 |
Windows Server 2022 | 3.7 |
Windows Server2025 | 3.14 |
Table:
Environment | ReFS Version |
|---|---|
SRT / ADK WinPE | 3.9 |
The WinPE ReFS driver (3.9) cannot be downgraded or made backward compatible with OS‑specific ReFS versions (3.1, 3.4, 3.7, 3.14).
Microsoft provides no workaround for this downgrade limitation.
As a result:
Restored ReFS volumes appear Unformatted
The target OS cannot read WinPE‑created ReFS 3.9 metadata
The volume becomes unusable after BMR restore
ReFS versions are not backward compatible at the metadata level.
A lower ReFS driver cannot recreate or replay metadata from a higher version
WinPE's ReFS driver is read‑mostly, not designed for reconstruction
BMR restore requires metadata replay, allocation maps, and integrity stream handling - operations that fail on version mismatch
All combinations below fail due to version mismatch:
Table:
Source Volume (ReFS) | Target OS | WinPE ReFS (3.9) | Result |
|---|---|---|---|
3.14 (Windows 2025) | Server 2025 | 3.9 | Fail |
3.7 (Winodws 2022) | Server 2022 | 3.9 | Fail |
3.4 (Winodws 2019) | Server 2019 | 3.9 | Fail |
3.4 (Windows 2016) | Server 2016 | 3.9 | Fail |
WinPE cannot create the required ReFS metadata structures
Version mismatch prevents metadata replay
Restore tools fall back to unsupported APIs
There is no direct solution.
Microsoft has not provided any method to upgrade or downgrade ReFS versions during BMR workflows.
To ensure ReFS volumes are restored with the correct 3.x version matching the original operating system, perform the following steps:
Right‑click the BMR configuration and create a copy using New Client Configuration.
Edit the copied configuration and exclude all ReFS volumes from volume mapping.
Run Prepare to Restore and proceed with the system restore.
After the machine boots into the restored operating system:
Create the ReFS volumes excluded in step 2
Format them using Disk Management or DISKPART
Windows will automatically create the ReFS volume using the correct version for that OS
Verify the ReFS version using: fsutil fsinfo refsinfo <DriveLetter:>
Restore the data for these volumes from Recovery tab in NetBackup Web UI.