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

Last Published:
Product(s): NetBackup (11.1.0.2)
  1. About NetBackup 11.1.0.2
    1.  
      About the NetBackup 11.1.0.2 release
    2.  
      About NetBackup Late Breaking News
    3.  
      About NetBackup third-party legal notices
  2. New features, enhancements, and changes
    1.  
      About new enhancements and changes in NetBackup
    2. NetBackup 11.1.0.2 new features, changes, and enhancements
      1.  
        Changes in Cohesity terminology
      2.  
        Update cloud configuration file on the primary and media server immediately after install or upgrade to NetBackup 11.1.0.2
      3.  
        Several shutdown commands to be deprecated in a future release
      4.  
        NetBackup 11.1.0.2 support additions and changes
      5.  
        NetBackup 11.1 and earlier support additions and changes
      6.  
        Support for malware scanning of hypervisor backups on OST targets
      7.  
        Simplified Cloud Scale upgrade
      8.  
        BMR now uses Windows ADK 10.1.22621 (ADK 2022)
  3. Operational notes
    1.  
      About NetBackup 11.1.0.2 operational notes
    2. NetBackup installation and upgrade operational notes
      1.  
        If NetBackup 11.1.0.2 upgrade fails on Windows, revert to previous log folder structure
      2.  
        Native installation requirements
      3.  
        NetBackup servers must use a host name that is compliant with RFC 1123 and RFC 952
      4.  
        About support for HP-UX Itanium vPars SRP containers
      5.  
        Change in the default path for NetBackup installation
    3. NetBackup administration interface operational notes
      1.  
        Intermittent issues with X forwarding of NetBackup Administration Console
      2.  
        NetBackup Administration Console fails in Simplified Chinese UTF-8 locale on Solaris SPARC 64-bit systems with Solaris 10 Update 2 or later
    4. NetBackup Bare Metal Restore operational notes
      1.  
        After PIT restore, "The host ID does not exist" error appears
      2.  
        NetBackup services may not start automatically after BMR restore on a Linux client
      3.  
        NetBackup Bare Metal Restore on AWS hangs when restoring a Windows 2025 client
      4.  
        Mirrored dynamic volume may not receive a drive letter after Windows BMR DDR restore
      5.  
        BMR Restore Failure for ReFS Volumes on Windows (2016 - 2025)
      6. Post Bare Metal Restore (BMR) operation, windows Start Menu and Search not functioning
        1.  
          Warning message after BMR restore on Windows
    5. NetBackup Cloud Object Store Workload operational notes
      1.  
        Full backup after upgrading from a version prior to NetBackup 11.1
      2.  
        Supported version of RHEL media server as backup host
      3.  
        Auto Image Replication (AIR) from NetBackup version 11.1.0.2 requires NetBackup 10.2 or later
      4.  
        Backup jobs become unresponsive and consume significant space on the temporary staging location.
    6. NetBackup NAS operational notes
      1.  
        Parent directories in the path of a file may not be present in an NDMP incremental image
    7. NetBackup Cloud workload operational notes
      1.  
        VMs and other OCI assets with CMK-encrypted disks are marked as deleted in NetBackup UI.
    8. NetBackup internationalization and localization operational notes
      1.  
        Support for localized environments in database and application agents
      2.  
        Certain NetBackup user-defined strings must not contain non-US ASCII characters
  4. Appendix A. About SORT for NetBackup Users
    1.  
      About Cohesity Services and Operations Readiness Tools
  5. Appendix B. NetBackup installation requirements
    1.  
      About NetBackup installation requirements
    2.  
      Required operating system patches and updates for NetBackup
    3.  
      NetBackup 11.1.0.2 binary sizes
  6. Appendix C. NetBackup compatibility requirements
    1.  
      About compatibility between NetBackup versions
    2.  
      About NetBackup compatibility lists and information
    3.  
      About NetBackup end-of-life notifications
  7. Appendix D. Other NetBackup documentation and related documents
    1.  
      About related NetBackup documents

Mirrored dynamic volume may not receive a drive letter after Windows BMR DDR restore

In Windows Bare Metal Restore (BMR) environments that use Dissimilar Disk Restore (DDR), mirrored (RAID‑1) dynamic volumes may not automatically receive a drive letter after the restore. This behavior is expected due to the way Windows Disk Management and DDR handle dynamic disks during disk reconstruction and system startup.

Cause

During a BMR DDR restore, disk and volume reconstruction is prioritized over drive‑letter assignment. The BMR process focuses on restoring the disk layout, partition structure, and dynamic disk metadata. Drive letters for non‑system volumes are not guaranteed to be reassigned during this stage.

After the restore, mirrored dynamic volumes may appear in the following states:

  • Resynching

  • Degraded

  • Healthy (no drive letter assigned)

Windows may delay drive‑letter assignment until the dynamic mirror is fully recognized and stabilized. Additionally, if the original drive letter is already reserved, temporarily assigned, or conflicting with another volume during boot, Windows may withhold letter assignment to avoid collision.

In DDR scenarios that involve dissimilar hardware, changed disk order, or other mapping differences, only the system volume (C:) is guaranteed to be auto‑mapped. Other volumes may be restored successfully but remain unmounted. In Disk Management, the mirrored volume typically appears as:

  • Healthy

  • Dynamic

  • No drive letter

The volume is accessible but not mounted, and applications may fail until a drive letter is manually assigned.

Workaround

After the system boots, manually assign the drive letter using Windows Disk Management:

  1. Open Disk Management.

  2. Right‑click the mirrored volume.

  3. Select Change Drive Letter and Paths.

  4. Assign the desired drive letter.

After the letter is assigned, the volume becomes fully functional. No rebuild, reformat, or additional restore operation is required.