Network and Storage Protocols
Network and Storage Protocols
I want to create 3 cifs shares independently managed under the same volume, is it possible?
Each share points to a different subfolder under a single volume.? is it possible
I already tried to create cifs shares but it is not solving my purpose of creating different subfolders, its replicating in all shares, if I add or create any folder or file in any share.
share1 creation command (same junction path.)
---cifs share create -vserver vserver_name -share-name Share2 -path /junctionpath_1 -share-properties oplocks,browsable,showsnapshot,access-based-enumeration,show-previous-versions -file-umask 022 -dir-umask 022 -comments "xxxxx"
share1 creation command (same junction path.)
---cifs share create -vserver vserver_name -share-name Share2 -path /junctionpath_1 -share-properties oplocks,browsable,showsnapshot,access-based-enumeration,show-previous-versions -file-umask 022 -dir-umask 022 -comments "xxxxx"
share1 creation command (same junction path.)
---cifs share create -vserver vserver_name -share-name Share3 -path /junctionpath_1 -share-properties oplocks,browsable,showsnapshot,access-based-enumeration,show-previous-versions -file-umask 022 -dir-umask 022 -comments "xxxxx"
Solved! See The Solution
Hi Ontapforrum,
Thanks actually, I created the qtree as suggested and these folders are under the respective share.
picked up your example only...
And let's say, if I do not create these folders in the qtree, and just create folders in the Cuba by right click while in Share Cuba
cifs_engg
Cifs_hr
Cifs_home
so what's the difference between the above folders and the one I created via qtree?
so it's like this, created via Qtree
created via right click
It would be great if you could clarify this also. It would help me to understand when I should use Qtree and when not.
qtree is logically defined (walled) file-system sub-directory under the root volume. It has many advantages over a regular folder, such as you can enforce quota (restrict size for users), during backups, it is more handy b’cos it is a modular directory, hence ndmp backups becomes faster. Most important, administration/managing shares becomes very easy.
Whereas, if you just use regular folder inside the flexvol, you cannot enforce quota/size restriction for users. During backup (especially ndmp), it can be daunting as the size increases. Plus, when you share it out, you will see all other shares which are under the root volume, instead of the just ‘qtree’ share that you shared out.