Howard Marks

Network Computing Blogger


Upcoming Events

Interop NY
Oct. 1-5

Interop is the only event to give you a comprehensive and unbiased understanding of all the latest innovations-including cloud computing, virtualization, security, mobility and data center advances-that help position your company for growth.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

Tags: , , ,

Channel: Data Protection, Backup & Recovery, E-discovery

See more from this blogger

Quotas Are Evil, Or At Least Counterproductive

I, like most of you, spend much of my time managing ever growing piles of data, so I was intrigued when an email with the subject "Five ways to manage data growth" arrived in my inbox, along with the usual press releases and spam. I was appalled when I saw that the first suggestion was to impose strict quotas on user mailboxes and home directories.

I understand how quotas are attractive. Users never delete anything and as a poor system administrator, you have to deal with it. We shouldn’t be surprised that we’re drowning in data, we live in a nation of packrats. An estimated 10% of US households have held on to so much garbage that it has overflowed their attics and garages into over 40,000 self-storage facilities. Packratism is so rampant in America that we make reality TV shows about the people that buy the junk in abandoned storage lockers.

Now don't get me wrong, I'm sure your mail servers, NAS systems and file servers are full of obsolete messages and files that your users should have deleted years ago, along with vacation snapshots, iTunes libraries and gigabytes of other stuff that never should have been there in the first place. I’ve just seen the ugly side of quotas and I think that there are better solutions. In fact, after seeing several attempts to impose quotas on users backfire badly, I've come to the conclusion that quotas are evil.

The first problem is the general resentment that users who have a gigabyte of personal mail in their Gmail account will feel when they get a message from their exchange server that they can't send the quote your best customer is waiting for because their mailbox has exceeded the puny 200MB quota you've imposed. Soon that resentment leads the users to believe you're incompetent, since they can get better service from free services on the internet than you provide.

I'd be all for quotas if users actually cleaned their acts up when they got the first message that they were approaching their quotas and selectively deleted the old useless stuff from their mailboxes and folders. What they actually do is call the helpdesk and demand that their quotas be extended. When you say no, they complain to their bosses and some vice president calls your boss to complain that they really do have 4GB of important email or that their time is too important to spend making your life easier.

If you manage to withstand the political battle and keep enforcing the quota, most users won’t actually carefully look over their data and delete the unimportant stuff, they'll just copy some data at random to the C: drive or create archive.pst files there.

While moving the data to a local drive gets it out of the data center, and out of your backup cycle, the story doesn't end there. When an e-discovery request comes for all messages between user A and customer Q, you have to produce those messages or files, you don't get to produce just the data in your data center. If you know, or could know, that the .PST files exist on C: drives, you have to search them for the data as well.

Finally, when the hard drive dies or you replace the user's desktop with a new model, that data will become your problem once again.

Related Reading


More Insights




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Research and Reports

Storage Virtualization Guide
May 2012

Network Computing: May 2012

TechWeb Careers