* Qtrees enable you to partition your volumes into

smaller segments that you can manage individually. You can set a qtree's size or security style, back it up, and restore it.

* * *

We use qtrees to partition your data. We might create qtrees to organize our data. Or to manage one or more of the following factors: quotas:can limit the size of the data used by a particular project, by placing all of that project's files into a qtree and applying a tree quota to the qtree. backup:can use qtrees to keep your backups more modular, to add flexibility to backup schedules, or to limit the size of each backup to one tape. Security style:If you have a project that needs to use NTFS-style security, because the members of the project use Windows files and applications, you can group the data for that project in a qtree and set its security style to NTFS, without requiring that other projects also use the same security style. CIFS oplocks setting:If you have a project using a database that requires CIFS oplocks to be off, you can set CIFS oplocks to Off for that project's qtree, while allowing other projects to retain CIFS oplocks.

* In general, qtrees are similar to volumes. However, they have

some key differences.
Functionality
Enables organizing user data Yes Enables grouping users with similar needs Yes Accepts a security style Accepts oplocks configuration Can be backed up and restored as a unit using SnapMirror Can be backed up and restored as a unit using SnapVault Can be resized Supports Snapshot copies Yes Yes Yes Yes Yes (using quota limits) No (qtree data can be extracted from volume Snapshot copies) Yes No (except as part of a FlexVol volume) 4,995 per volume

Qtree

FlexVol volume Yes Yes

Yes Yes Yes No Yes Yes

Traditional volume
Yes Yes Yes Yes Yes No No (can be expanded but cannot be reduced in size) Yes

Supports quotas Can be cloned Maximum number allowed

Yes Yes 500 per system

Yes No 100 per system

* Using some special characters in qtree names, such as commas and

spaces, can cause problems with other Data ONTAP capabilities, and should be avoided. * The following characters should be avoided in qtree names:

* Space:-

Spaces in qtree names can prevent SnapMirror updates from working correctly. * Comma:- Commas in qtree names can prevent quotas from working correctly for that qtree, unless the name is enclosed in double quotation marks.

* You can create, delete, and rename qtrees. In addition,

you can display their status and access statistics. You can also convert directories at the root of a volume into qtrees. You do many of these operations using your UNIX or Windows client.

* create qtrees using the qtree create command. You can also
specify a style permission for the new qtree. qtree create path [-m mode] mode is a UNIX-style octal number that specifies the permissions for the new qtree. If you do not specify a mode, the qtree is created with the permissions specified by the wafl.default_qtree_mode option. qtree create /vol/users/news -m 770

* To find the security style, oplocks attribute, and SnapMirror

status for all volumes and qtrees on the storage system or for a specified volume, you use the qtree status command.

* Step
Enter the following command: qtree status [-i] [-v] [vol_name] The -i option includes the qtree ID number in the display. The -v option includes the owning vFiler unit, if the MultiStore license is enabled.

* display statistics on user accesses to files in qtrees on your system using the qtree
stats command. * This can help you determine which qtrees are incurring the most traffic. qtree stats [-z] [vol_name] The -z option clears the counter for the designated qtree, or clears all counters if no qtree is specified. system> qtree stats vol1 Volume Tree NFS ops CIFS ops -------- -------- -------------vol1 proj1 1232 23 vol1 proj2 55 312

* If you have a directory at the root of a volume that you want to

convert to a qtree, you must migrate the data contained in the directory to a new qtree with the same name, using your client application. Steps * Rename the directory to be made into a qtree. * Create a new qtree with the original directory name. * Use the client application to move the contents of the directory into the new qtree. * Delete the now-empty directory. Note: You cannot delete a directory if it is associated with an existing CIFS share.