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

Post Bare Metal Restore (BMR) operation, windows Start Menu and Search not functioning

Problem

Post Bare Metal Restore (BMR) operation, windows Start Menu and Search not functioning.

This behavior has been observed on the Windows Server 2019 (2K19) EFI client.

Cause

The most probable cause is that the AppX State Repository database was not properly updated during the recovery process.

While application files were successfully restored, the system's internal registration database was not synchronized, leading to failures in initializing built-in Windows components.

Solution

Follow the Microsoft's documentation and recommendations for registering the Appx Package.

Apart from official documentation, the following procedure may assist in resolving registration-related inconsistencies.

Recovery Procedure

  1. Open PowerShell as an administrator.
  2. Run the following command:
    Get-AppXPackage -AllUsers | Foreach {
      Add-AppxPackage -DisableDevelopmentMode -Register 
    "$($_.InstallLocation)\AppXManifest.xml"
    }
    

    This command re-registers all installed AppX packages by reading their respective AppXManifest.xml files and rebuilding the associated registration data

Functional Impact

Executing this command performs the following actions:

  • Enumerates all installed AppX packages across all user profiles

  • Parses each AppXManifest.xml

  • Rebuilds package activation and identity mappings

  • Re-indexes packages in the Windows State Repository

  • Re-applies required security identifiers (including ALL APPLICATION PACKAGES)

  • Reconstructs AppX deployment metadata

This process helps resolve AppX package registration mismatches and related shell initialization issues.

Post-Registration Action

After completing the re-registration:

  • Restart the Windows Shell by restarting the explorer.exe process to ensure the updated registrations are applied.

Preconditions and Validation Checks

Before performing AppX package re-registration, verify the following:

AppLocker Configuration

  • Ensure no AppLocker Deny rules are blocking packaged applications.

  • Open secpol.msc and navigate to: Application Control Policies → AppLocker

  • Confirm that no rules deny execution of Packaged Apps.

Required Directories

Ensure the following directories exist:

  • C:\Windows\System32\AppLocker

  • C:\Windows\AUInstallAgent

If missing, create them.

Do not delete these directories if they already exist.

AppReadiness Directory

  • Verify that C:\Windows\AppReadiness exists.

  • If missing, create the directory.

This location is required for AppX staging operations.

Registry Validation

  • Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx

  • Confirm that the PackageRoot registry value points to:C:\Program Files\WindowsApps

Optional Service Restart

If required, restart the AppX deployment service before or after package re-registration:

Restart-Service AppXSVC -Force

Official Error Context
  • 0x80073CF9 (Install Failed): Officially defined as "The package deployment failed because the staging operation could not be completed.".

    In a BMR Scenario:

    This typically indicates that:

    The Staging Operation is the process where Windows prepares the application before committing it to the State Repository.

    • The AppReadiness directory is missing

    • The AUInstallAgent staging directory is missing

    • Directory permissions are incorrect

  • 0x80070003 (Path Not Found): Officially refers to a "Deployment Target Access failure."

    In a BMR Scenario:

    This confirms that: may be missing or inaccessible due to stripped or incorrect SIDs.

    This indicates that the database contains registration references, but the physical directory structure is either missing or inaccessible.

    • The AppX database cannot locate the required directory structure

    • C:\Windows\SystemApps or

    • C:\Program Files\WindowsApps