Hi Richard

Would you recommend a cloud archiving solution such as MS EHA ?

Regards
[cid:image001.jpg@01CB2F0B.BA61FA00]

Peter Johnson
I.T Architect
United Kingdom: +44 1285 658542
South Africa: +27 11 252 1100
Swaziland: +268 442 7000
Fax:+27 11 974 7130
Mobile: +2783 306 0019
peter.john...@peterstow.com


This email message (including attachments) contains information which may be 
confidential and/or legally privileged. Unless you are the intended recipient, 
you may not use, copy or disclose to anyone the message or any information 
contained in the message or from any attachments that were sent with this 
email, and If you have received this email message in error, please advise the 
sender by email, and delete the message. Unauthorised disclosure and/or use of 
information contained in this email may result in civil and criminal liability. 
Everything in this e-mail and attachments relating to the official business of 
Peterstow Aquapower is proprietary to the company.

Caution should be observed in placing any reliance upon any information 
contained in this e-mail, which is not intended to be a representation or 
inducement to make any decision in relation to Peterstow Aquapower. Any 
decision taken based on the information provided in this e-mail, should only be 
made after consultation with appropriate legal, regulatory, tax, technical, 
business, investment, financial, and accounting advisors. Neither the sender of 
the e-mail, nor Peterstow Aquapower shall be liable to any party for any 
direct, indirect or consequential damages, including, without limitation, loss 
of profit, interruption of business or loss of information, data or software or 
otherwise.

The e-mail address of the sender may not be used, copied, sold, disclosed or 
incorporated into any database or mailing list for spamming and/or other 
marketing purposes without the prior consent of Peterstow Aquapower.
No warranties are created or implied that an employee of Peterstow Aquapower 
and/or a contractor of Peterstow Aquapower is authorized to create and send 
this e-mail.
 [cid:image002.jpg@01CB2F0B.BA61FA00]
From: Sobey, Richard A [mailto:r.so...@imperial.ac.uk]
Sent: 29 July 2010 10:49
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 DAG and backup options/recommendations.

That would be my biggest concern: the absence of a backup to restore someone's 
mailbox from two to three months ago. There's backup for disaster recovery, 
then there's backup for user stupidity.

From: bounce-9036114-8066...@lyris.sunbelt-software.com 
[mailto:bounce-9036114-8066...@lyris.sunbelt-software.com] On Behalf Of Neil 
Hobson
Sent: 29 July 2010 09:44
To: MS-Exchange Admin Issues
Subject: RE: Exchange 2010 DAG and backup options/recommendations.

In addition to what has already been said, let's talk a little about your 
statement "a backup system isn't really required".  What you're referring to 
there is Exchange native data protection and if you go down this route there 
are some very clear things that you need to consider.

For example, the MS recommendation is that you have at least 3 database copies 
if you implement native data protection; you've said 2 copies per database in 
your statement.  I don't know your environment, and I know it's extremely 
unlikely to happen, but could your 2 on-site buildings be taken out at the same 
time?  Consider a 3rd copy somewhere completely remote.  You say you're worried 
about database corruption - that's where lagged database copies come in, so 
you'd need to consider those (which will take your design to 3 database copies 
anyway).  Also, what are you planning to do regarding single item recovery?  
That affects the users and your ability to restore in the absence of a backup.

From: Pfefferkorn, Pete (pfeffepe) [mailto:pfeff...@ucmail.uc.edu]
Sent: 28 July 2010 21:02
To: MS-Exchange Admin Issues
Subject: Exchange 2010 DAG and backup options/recommendations.

We are going to be moving to Exchange 2010.  Basically we will have 14,000 
users and will allow users to go up to 4 gig mailboxes.  We will have 4 
backends distributed between 2 on-site buildings for redundancy 
(power/network).  We will also be deploying a DAG configuration with 2 copies 
per database.   We are talking a ton of storage and the question keeps arising 
about backups.  I've heard with the DAG deployment, a backup system isn't 
really required because of the database replication, but my mind keeps going 
back to the possibility of database corruption.  Total data to be backed up 
could be 192 terabytes, so it's a large amount of data.  I was wondering what 
other large shops are using for that type of data.  Comments on backup 
strategies for 2010?

Pete Pfefferkorn
University of Cincinnati
Email Services-Systems Engineer
pete.pfefferk...@uc.edu<mailto:pete.pfefferk...@uc.edu>
(513)556-9076


<<inline: image001.jpg>>

<<inline: image002.jpg>>

Reply via email to