Re: 75 GB limit in Windows Server 2003 R2
- From: - Michel <Michel@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 2 Jan 2008 15:15:01 -0800
Funny that there are quite a few serious responds to this posting.
Basically Harold, you sound your CEO who doesn't understand IT or your
neighbour I-hate-Microsoft-by-definition-please-give-me-open-source-kid.
Email is NOT a file archiving tool.
If your users can mail themselves mails with attachments of a particular
size, review your mail gateway software and harden policies. Let them bring a
(of course encrypted) memory stick to the IT department that will place the
data on the network if that is actually business related and necessary (of
course USB ports are locked down if you did your job well, so your users need
the iT dept for that).
Second, buy a arching tool like Enterprise Vault that will nicely archive
email and attachments out of the Exchange databases into an external
"database".
Third, if your Exchange server is really that heavy used it must be quite
mission critical. I wonder what your Recovery Time Objectives and Recovery
Point Objectives are for the server. Wish you good luck restoring a database
(or parts of that) from 75GB in a reasonable timeframe...
Last: perhaps you should talk to some real experts before you start posting
messages like you did...
Kind regards,
Michel
"Terry Drewes" wrote:
Maybe a 3rd party tool, to auto save attachments?.
http://www.techhit.com/ezdetach/
BTW... we use their MessageSave product for archiving, and it works great!
Ciao!
~Terry
Harold Naparst wrote:
I can see how if the company set, say a 2 GB limit on mail,
then when they run out of space they would ask for an increase.
Then, what are you suggesting? How exactly would a user upload
their pictures to the company extranet for public access?
Or perhaps you mean they would upload to an intranet, but then
the external recipient could not access it.
I think that what would happen is this: They would use their
personal hotmail account to send the mail with the attachment.
In fact, they would probably abandon Exchange altogether because
they don't understand this upload/link process you are talking about.
I don't even understand it.
We are in the marketing business, not in the business of
training users to modify their behavior so it fits the limits of the
software.
It actually is not that easy to find out what the limits on
Exchange Standard are, by the way. If you go through the
product sheets, it just has a lot of statements about how it is appropriate
for SMEs, but no real description of what the limits are. That you
find out when you install the product.
But, that having been said, if there is in fact a way to make the
product work for us, I'm all ears. Maybe attachments can be automatically
stripped out, uploaded to a public web service, and replaced by links.
- References:
- RE: 75 GB limit in Windows Server 2003 R2
- From: Leythos
- Re: 75 GB limit in Windows Server 2003 R2
- From: Terry Drewes
- RE: 75 GB limit in Windows Server 2003 R2
- Prev by Date: Re: Event ID:3719 Source: Netlogon
- Next by Date: Strange Problem with Authentication Has anyone ever run across thi
- Previous by thread: Re: 75 GB limit in Windows Server 2003 R2
- Next by thread: Re: 75 GB limit in Windows Server 2003 R2
- Index(es):