 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Backing up Exchange database</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/backing-up-exchange-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/backing-up-exchange-database/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 07:52:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: vnoome</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/backing-up-exchange-database/#comment-63554</link>
		<dc:creator>vnoome</dc:creator>
		<pubDate>Thu, 14 May 2009 04:06:21 +0000</pubDate>
		<guid isPermaLink="false">#comment-63554</guid>
		<description><![CDATA[Hey Daddy1268,

I would have to agree with Vishalvasu....
309G is quite a bit of space your are sucking up....part and partial one of your biggest challenges you will face is to comply with local governance.  As a rule, e-mail communication should be kept for a 5 year period...this could be different from country to country.

Your problem is not backing up that storage....the fact is that when you are going to restore is going to really be a problem.  Exchange is a bit of a two sided coin...what to do and what not to do.
In my opinion I would first start by enforcing a storage limit as it might be that users are really going nuts.
You have to have mail policy that outlines your objective in how mail storage will be managed.
My policy that I enforce is that I will only allow MS office docs.  Limitation per mail is set to 10 MB.
Further more, I also focus on archiving.  Any mail older than 1 year is archived and then removed from the mail server.

My total storage went from 200G to 34G after enforcing that policy.  My backup time is currently 45min.

I do a full backup every evening of my exchange server with GRT.  My reason for doing this is that I am able to do single mail restoration per user and do not have to restore the entire database which will affect all other users.

I am not too jacked up on your application that you are using... I am using Veritas.

What is your typical throughput that you are getting on your backup job?
Pending on your kit.....2GB/min should be more or less what you can be happy about...

Hope this helps you a bit...

Cheers.


Vince]]></description>
		<content:encoded><![CDATA[<p>Hey Daddy1268,</p>
<p>I would have to agree with Vishalvasu&#8230;.<br />
309G is quite a bit of space your are sucking up&#8230;.part and partial one of your biggest challenges you will face is to comply with local governance.  As a rule, e-mail communication should be kept for a 5 year period&#8230;this could be different from country to country.</p>
<p>Your problem is not backing up that storage&#8230;.the fact is that when you are going to restore is going to really be a problem.  Exchange is a bit of a two sided coin&#8230;what to do and what not to do.<br />
In my opinion I would first start by enforcing a storage limit as it might be that users are really going nuts.<br />
You have to have mail policy that outlines your objective in how mail storage will be managed.<br />
My policy that I enforce is that I will only allow MS office docs.  Limitation per mail is set to 10 MB.<br />
Further more, I also focus on archiving.  Any mail older than 1 year is archived and then removed from the mail server.</p>
<p>My total storage went from 200G to 34G after enforcing that policy.  My backup time is currently 45min.</p>
<p>I do a full backup every evening of my exchange server with GRT.  My reason for doing this is that I am able to do single mail restoration per user and do not have to restore the entire database which will affect all other users.</p>
<p>I am not too jacked up on your application that you are using&#8230; I am using Veritas.</p>
<p>What is your typical throughput that you are getting on your backup job?<br />
Pending on your kit&#8230;..2GB/min should be more or less what you can be happy about&#8230;</p>
<p>Hope this helps you a bit&#8230;</p>
<p>Cheers.</p>
<p>Vince</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.039 seconds using memcached
Object Caching 266/272 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-18 09:30:17 -->