Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for Microsoft Exchange Server Administrator's Guide
  3. Troubleshooting backups and restores of Exchange Server
  4. Troubleshooting Exchange jobs that use Granular Recovery Technology (GRT)
Veritas NetBackup™ for Microsoft Exchange Server Administrator's Guide

Troubleshooting Exchange jobs that use Granular Recovery Technology (GRT)

Note the following when you use NetBackup to perform backup or restore operations using Granular Recovery Technology:

  • Disable or uninstall QLogic SANSurfer software. It may conflict with the portmapper for Client for NFS.

  • Before you install NFS on the media server or client(s), look for the ONC/RPC Portmapper service. If it exists, stop it and disable it. Otherwise, the installation of NFS Services for Windows fails.

  • Exchange GRT operations can fail for the VM backup images that use display names that contain parenthesis. For example, a GRT live browse restore from the Backup, Archive, and Restore (BAR) interface fails with the following error:

    database system error

  • (Exchange 2010) The "Company" information for task objects is not restored.

  • A status 1 error may occur for a GRT-enabled backup if the granular processing operations failed to complete successfully. The job details under the Activity Monitor or error log should indicate if this failure is what caused the status 1. Look at the bpbkar debug log for more information.

  • NetBackup must be able to contact the proxy host (if applicable) or destination client.

    If NetBackup cannot contact this client, then errors appear in the "Problems" or "All Log Entries" reports. The following error messages appear in the NetBackup error logs:

    The granular proxy <clientname> for client <clientname> could not be 
    contacted.  Unexpected results may have occurred.  See bprd debug log for more 
    details.
    Could not connect to <clientname> for virtual browse operation, errno=#, 
    bpcd_status=#

    See Exchange granular clients and non-VMware backups .

  • For Exchange 2010, the following situations cause a restore to fail with a status 5:

    • Restores of a private mailbox item to a Public Folder

    • Restores of a Public Folder item to a private mailbox

    In the ncfgre log, the following error appears:

    EWS Failed to get mailbox properties
  • If you attempt to restore an Exchange 2010 Public Folder item to a subfolder that has not been previously created, the restore fails with a status 5. The following error appears in the progress log:

    MNR - error writing file: %1

    Use one of the following workarounds to resolve this issue:

    • Retry the restore operation. NetBackup receives an error when it attempts to create the new subfolder. However, the subfolder is created. A second restore attempt to the same subfolder location is successful.

    • Create the subfolder manually before you attempt the restore. If the subfolder exists, the restore is successful.

  • Technical Support may want nbfsd logs from the media server. Use the Verbose setting carefully as the nbfsd log can grow very large.

Feedback

Was this page helpful?
Previous

Troubleshooting Exchange snapshot operations

Next

Increased memory usage with Exchange 2010 and 2013

Feedback

Was this page helpful?