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
  3. NetBackup™ Replication Director Solutions Guide
  5. Using NetApp disk arrays with Replication Director
  7. Using NetApp Clustered Data ONTAP with Replication Director
  9. Protecting volumes with nested junctions for Clustered Data ONTAP
NetBackup™ Replication Director Solutions Guide

Protecting volumes with nested junctions for Clustered Data ONTAP

When you snapshot or replicate volumes, any mounted volumes that reside under the top-level volume are not necessarily protected. You should consider the following example scenarios when you create backup policies for volumes with nested junctions.

You may have a volume that is mounted under another volume, as in the example below. Volume B is mounted under Volume A in the SVM VS1's namespace.

Table: To protect volumes with nested junctions

Policy type

Level

Protection strategy

Standard

Top level

To protect the top-level volume in a Standard policy:

  • Create an NFS mount point for the volume "vs1:/vol_A" on the NetBackup client.

    For the example above, you would create the mount point "/mnt/vs1_vol_A".

  • Create the Standard policy and use "/mnt/vs1_vol_A" as the backup selection.

Any snapshot operations or replication operations now protect "vs1:/vol_A". An empty directory for vol_B is created under the replica of vol_A, however vol_B is not protected.

Standard

Lower level

To protect the lower level volume in a Standard policy:

  • Create an NFS mount point for the volume "vs1:/vol_A/vol_B" on the NetBackup client.

    For the example above, you would create the mount point "/mnt/vs1_vol_B".

  • Create the Standard policy and use "/mnt/vs1_vol_B" as the backup selection.

Any snapshot operations or replication operations now protect "vs1:/vol_A/vol_B".

Windows

Top level

To protect the top-level volume in a Windows policy, specify the backup selection as "\\vs1\vol_A" where "vol_A" represents the share that is exported for "vol_A".

Any snapshot operations or replication operations now protect "vol_A". An empty directory for vol_B is created under the replica of vol_A, however vol_B is not protected.

Windows

Lower level

To protect the lower level volume in a Windows policy, specify the backup selection as "\\vs1\vol_B" where "vol_B" represents the share that is exported for "vol_B". The volume, "vol_B" is mounted under "vol_A".

Any snapshot operations or replication operations now protect "vol_B".

See Using NetApp Clustered Data ONTAP with Replication Director.

See About creating backup policies for Clustered Data ONTAP with Replication Director.

Feedback

Was this page helpful?
Previous

About creating backup policies for Clustered Data ONTAP with Replication Director

Next

Limitations to using Clustered Data ONTAP with Replication Director

Feedback

Was this page helpful?