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™ Bare Metal Restore™ Administrator's Guide
  3. Appendix A. NetBackup BMR related appendices
  4. BMR support for multi-pathing environment
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

BMR support for multi-pathing environment

BMR has compliance support for multi-pathing environments. What this means is, during the client's BMR backup which has BMR known multi-pathing environments set up; BMR automatically marks the multi-pathed disks restricted in that client's captured BMR configuration. This restricts the user to use those disks during recovery. Though any file systems running over the multi-pathed disks can be recovered to alternate non-multipathed disks. For example, if the client setup has EMC PowerPath enabled over SAN LUNs, then the BMR backup will mark those SAN LUNs as restricted. The user can recover file systems on top of them to either local disks or other SAN LUNs not having multi-path enabled.

Why this restriction is?

BMR recovery environment has no multi-path software setup and configured (like EMC PP). Hence BMR recovery environment cannot identify multi-path enabled disks on given target hardware. Currently Supported Multi-pathing environments are:

  • EMC PowerPath on UNIX/Linux/Windows supported platforms

  • Linux Native Multi-pathing

The details of the environment are as described in the following topics:

What does it mean BMR supported multi-pathing environments?

BMR supports only above mentioned multi-pathing environment setups. If the client being BMR backed-up has any one of these multi-pathing enabled; then while capturing client's BMR configuration, BMR resolves multi-paths to exact unique physical disk and shows it in BMR config. Also as mentioned above, BMR marks them restricted and avoids recovery time failure.

What if client has any different multi-pathing environments than above?

BMR backup will fail to identify unique disk names and BMR captured configuration will show multiple-disk names as shown by multi-path software. Also it will not be able to mark the disks restricted automatically. Here you need to copy BMR configuration using administrator GUI (Refer chapter Managing client configurations from NetBackup BMR Administrator's Guide)and identify MP disks and mark them restricted manually. If file systems on top of these MP disks need to be recovered then map them to other non-MP disks. If you ignore MP-based file systems recovery and restore only operating system then post BMR recovery if the multi-pathed disks are attached to the target host then file systems on top of them may come online automatically. Refer tables Actions for nonsystem disks and Import Actions for more details.

If the client setup has operating system volumes based on multi-pathing environment, then BMR cannot recover this system.

Feedback

Was this page helpful?
Previous

About the support for Linux native multipath in BMR

Next

BMR multipath matrix

Feedback

Was this page helpful?