Hi may somebody can help
When creating a new Dataset and attaching backup policy like qsm, then a new snapmirror / vault is with two relations-ship instead only one is created.
-One relation-ship with qsm source "node1:/vol/HR_Data/test node2:/vol/HR_Data/test"
This relation-ship is the only wished . We do not want to have the relation"/-" means all non qtree data! Never non-qtree data are on normal Systems existing on root
volumes like /vol/volz/manualDir. I think the intentions of development, were to avoid that some non qtree data is not saved. But in my opinion this is a bad design,
as no normal Netapp Admin will ever create manual Directories (non Qtree Dirs) on a root volume.
Here some example:
node1:/vol/HR_Data/- node2:/vol/HR_Data/HR_Data_node1_HR_Data Source 00:01:54 Idle (unwanted realtion but created by new dataset )
node1:/vol/HR_Data/test node2:/vol/HR_Data/test Source 00:01:55 Idle (only this qtree contains data)
The "/-" means that all non qtree data will be saved. But qtree data are not saved at all with that. (This will guarantee that manual created Directories/Files will be
saved, but this never happens in practice therefore why ?)
To overcome this, a second relation with the effective data qtree will be created. As consequence we get always two relation instead one.
Of curse workaround would be to create a manual volume & qtree an then selection while creation of dataset (not provisioning) manuall qtree as source. Then "/-" would
not be created!
How we can change this wrong behavior of creating this non qtree "/-" relation which is completely wrong ? Is there an option available ?