Another point you would like to take into consideration is the future growth of your data. One serious drawback to having one large volume is that in the event of a disaster, recovering one large volume is much more time consuming than recovering two smaller volumes. We try keeping our volumes under 200-250 GB. Splitting a large volume in to smaller ones is very time consuming, requires redundent resources (disks) and requires user downtime while you sync the data.
daniel@sprintlabs.com (Daniel Oxenhandler) writes:
We have an F-740 with 14 - 18GB drives (2 hot spares) configured as one large volume. OnTap version 5.3.4R2. Security style is mixed. Currently it is being used by mostly UNIX users, with some Windows users, for Home directories and Project directories. There are only about 15 total active users on the Filer currently. The plan is to move the home directories for the remaining 60 or so mostly Windows users onto the Filer.
We would like to implement quotas on the Home directories, e.g. 150MB per user. At the same time, we would like to implement quotas on the Project directories -- my thinking is we would do this via a group quota, e.g. 5GB for Group A, 15GB for Group B, etc.
My questions are as follows:
- Will we need to create separate volumes for Home dir's and Projects, so
that the quotas will work as we intend (e.g. a user can own files in his Project directory without it counting against his User quota) -- or can we get away with qtrees? My suspicion is that we will need to start from scratch and create at least two volumes to do this.
- Suggestions for the best strategy to accomplish this, maintaining all
CIFS & NFS metadata? We are currently dumping the filer as one big volume to DLT (<35GB). Does the filer's dump command support dump from a directory, so that we could restore to our new volumes or qtrees? Any other strategies?