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. Restoring clients
  4. About SAN (storage area network) support
  5. Restoring Solaris SAN-attached volumes if they are left unmapped
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

Restoring Solaris SAN-attached volumes if they are left unmapped

The following information applies only to Solaris clients.

After a Solaris system is recovered using the dissimilar disk restore feature, you may need to perform the following procedure for SAN-attached volumes that were left unmapped (marked not to restore).

To restore Solaris SAN-attached volumes if they are left unmapped

  1. Determine the differences between the current and previous vfstab files:
    % diff /etc/vfstab /etc/vfstab.old.bmr.dmr
  2. Review the differences.
  3. Copy the entries about the SAN devices from the /etc/vfstab.old.bmr.dmr file. Add them to the /etc/vfstab file or uncomment the corresponding lines that are commented out when vfstab was merged.
  4. Mount the file systems that are on the SAN.
  5. Manually restore the SAN file systems using the NetBackup Backup, Archive, and Restore interface.

Feedback

Was this page helpful?
Previous

About SAN (storage area network) support

Next

About SANs and dissimilar system restores on Windows clients

Feedback

Was this page helpful?