I can think of a couple of possible suggestions... First, could you not split the data up and NOT backup all that (largely static, unchanged?) data every time?... Implement exchange archiving, give all users an archive mailbox on a different server, and have an arching policy that moves items to the archive automatically after x months... Then backup the archives with a separate backup job, that can run concurrently with the main job, thus reducing the overall backup window required, and, you can backup the archives on a less frequent schedule... The main mailboxes will then shrink hugely, thus reducing your backup overhead there...
Secondly, I'd think about maintaining an additional, LAGGED copy of the databases... The issue with going backupless and relying purely on replication for your data security is that a logical corruption will replicate to all your copies just like any other data would... (exchange won't replicate corrupted log files) but say a virus gets into an email and wreaks havoc amongst your databases... A lagged copy gives you time to detect and respond to any such problems before that copy of the data becomes similarly damaged... You can of course do both of the above... They're not mutually exclusive... You could, if you are concerned enough, (and wealthy enough!) have multiple lagged database replicas with different delays on them... Copies can be lagged up to a maximum of 14 days IIRC... So you could for example have a 24 hour lagged copy, and then say a 7 day lagged copy as well... You can have as many lagged copies as you like, subject to the DAG design rules of 16 databases maximum in the DAG. Hth Paul g Sent from my iPad On 3 Feb 2012, at 18:18, "Anthony Goraczko" <anth...@fiu.edu> wrote: > We are pretty much in the same boat. We have had very bad results with > Tivoli and 2010 (YMMV; 2007 was fine), so we are looking to move to MS DPM > for backup purposes. So far, the plan is to mirror a local copy of the DPM > data to our DR site and hopefully that will meet the off-site backup > requirement we have. We currently use Iron Mountain as well, so if that > doesn't work out, hopefully we can leverage Iron Mountain's CloudRecovery for > long-term off-site backup, which integrates with DPM. > > --Anthony > > Anthony Goraczko > University Technology Services > Division of Information Technology > Florida International University > https://mysites.fiu.edu/sites/anthony/ > From: Pfefferkorn, Pete (pfeffepe) [pfeff...@ucmail.uc.edu] > Sent: Friday, February 03, 2012 10:43 AM > To: MS-Exchange Admin Issues > Subject: Exchange 2010 backup/DAGs question. > > We are in the process of finalizing our Exchange 2010 deployment. We will be > setting up Database Availability Groups for replication to two sites. The > current 2007 deployment is over 4 terabytes in size and we anticipate that > growing substantially since we are going from 2 gig quotas to 10 gig quotas > right off the bat. We currently use Tivoli to backup information using > lanfree backups and then those backups get written to tape. Backup times are > going 8 to 10 hours at times for full backups. For 2010 we would like to go > tapeless and just use replication, but we are getting pushback from upper > management on this and the requirement to dump data to tape for offsite > storage seems to be a pressing issue. > > My question is with 2010 what other backup solutions are available for the > amount of data we are speaking about. If push comes to shove I would like to > at least give upper management a few options so they get the warm/fuzzy and > costs associated to the solutions. We would like to create a third site off > campus and replicate data to the third site as well for DR purposes and > possibly make that a lag copy. Management has the mindset that they would > like data dumped to physical media that could then be sent to Iron Mountain > which is where our mainframe tapes go for storage. If we lose both sites on > campus…bring back the media….then rebuild. > > Sorry if this has been hashed through before. > > Pete Pfefferkorn > University of Cincinnati Information Technology Services > Operating Systems Analyst/Messaging Administrator > Phone: (513) 556-9076 > Fax: (513) 556-2042 > Email: pete.pfefferk...@uc.edu > > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to listmana...@lyris.sunbeltsoftware.com > with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
