<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
Aren't you better off dropping $1,500 on a Synology/Netgear NAS with
a bunch of RAID5/6 7500RPM 2.5TB SATA3's in it and just giving them
7TB to duke it out over? Surely spending a couple of days screwing
about squabbling over a couple of TB is more costly than just buying
some storage.<br>
<br>
2c<br>
<br>
<br>
<br>
<br>
T.<br>
<br>
<div class="moz-cite-prefix">On 13/02/13 2:11 PM, Shane Bryan wrote:<br>
</div>
<blockquote
cite="mid:4C4323531BCB544D98ECD3FA06D22B7D83E7DB83@RC-EX02.msl.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
<font face="Calibri" size="2"><span style="font-size:11pt;">
<div>Hi all – hope you’re all enjoying a pleasant afternoon.</div>
<div> </div>
<div>I’m looking to put Home Share quotas in place from our
2008 R2 file server. At least now you can do them down to
the folder level (rather than volume level) but as I’m
implementing them – in many cases, years – after they were
first setup and given to
the user, a ‘one size fits all’ solution won’t cut it.</div>
<div> </div>
<div>Has anyone else attempted this? We have some users with
0kb in their Home Shares, all the way up to some people with
5, 8 or even 9Gb of files.<br>
</div>
<div>Currently we have all Home Share folders under one common
folder shared out. What I’m contemplating doing is having
some sub folders, eg;</div>
<div> </div>
<div><i>Home Shares Root\</i><i>Regular Home Shares (<1Gb)</i></div>
<div><i>Home Shares Root\</i><i>Medium Home Shares (1Gb to
2Gb)</i></div>
<div><i>Home Shares Root\</i><i>Large Home Shares</i><i> (2Gb
+)<br>
<br>
</i>(or some other naming structure, tbd) Of course this
means we would have to update each users AD profile with the
new share path(s) – not ideal.</div>
<div> </div>
<div>Having a blanket\inheritable quota policy for the Home
Shares under 1Gb meets the needs of about 400 of our users,
leaving 40 or so with larger ones. For these heavier users I
was contemplating having another 3 quota policies for the
people up to 1.2Gb,
1.5Gb then 2Gb and on top of that for the final 20, having
custom quota policies giving them an extra 100Mb or so on
top of what they currently have.<br>
<br>
It’s a bit of work, but the policies don’t take long to
create. I also can’t create a 9Gb quota policy and apply it
to a user that only has 5Gb of files, that would defeat the
whole purpose of this so custom ones might just be the only
option.</div>
<div> </div>
<div>What this would do is give the light users plenty of
space, but the heavy users at each level will start getting
alerts and prompt them to clean unwanted stuff out.</div>
<div><br>
If anyone of you learned ladies and gentlemen have
implemented File Quotas into an existing setup, I’d love to
hear any tips or war stories from the challenges you
encoutered <font face="Wingdings">J<br>
<br>
</font>Cheers, Shane.</div>
<div> </div>
<div><font face="Times New Roman" size="3"><span
style="font-size:12pt;"><a moz-do-not-send="true"
href="http://www.msmelbournecycle.org.au"><img
moz-do-not-send="true"
src="http://www.mssociety.org.au/images/emailbanners/staff-join-me-signature-low.gif"
height="170" width="650"></a> </span></font></div>
</span></font>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
AusNOG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a>
<a class="moz-txt-link-freetext" href="http://lists.ausnog.net/mailman/listinfo/ausnog">http://lists.ausnog.net/mailman/listinfo/ausnog</a>
</pre>
</blockquote>
<br>
</body>
</html>