RE: Outlook 2010 questions
[2] Suggested Contacts The bane of my life currently as they broke the corrupt mailto: address fix they put in place for outlook 2007 Nick Turner This electronic message contains information from CACI International Inc or subsidiary companies, which may be confidential, proprietary, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named above. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify us immediately at postmas...@caci.co.uk Viruses: Although we have taken steps to ensure that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. CACI Limited. Registered in England Wales. Registration No. 1649776. CACI House, Avonmore Road, London, W14 8TS. --- 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
Exchange 2010 database
What is the best practice or guideline when you create/organize databases in your organization? How do you add/organize users into different databases? By location? By their size of current mailbox? By department? By users' job title? ... Thanks. Henry Shih System Administrator --- 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
RE: Exchange 2010 database
No idea about best practice but we do it by department so in the event of a DR we can restore the databases of the most important teams first. Sent from my Windows Phone -Original Message- From: Shih, Henry Sent: 14/02/2012 17:38 To: MS-Exchange Admin Issues Subject: Exchange 2010 database http://www.freebridge.org.uk http://twitter.com/Freebridge http://www.facebook.com/pages/Kings-Lynn-United-Kingdom/Freebridge-Community-Housing/192690183387?v=box_3 This e-mail (including any attachments), is confidential and intended only for the use of the addressee(s). It may contain information covered by legal, professional or other privilege. If you are not an addressee, please inform the sender immediately and destroy this e-mail. Do not copy, use or disclose this e-mail. E-mail transmission cannot be guaranteed to be secure or error free. The sender does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard copy version. Freebridge Community Housing Ltd is a Charitable Industrial and Provident Society - Reg No IP29744R Registered with the Housing Corporation - No L4463. VAT Registration Number 860762121 Freebridge Community Housing, Juniper House, Austin Street, Kings Lynn, Norfolk PE30 1DZ This email message has been scanned for viruses by Mimecast. Mimecast delivers a complete managed email solution from a single web based platform. For more information please visit http://www.mimecast.com --- 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 exchangelistinline: 112021419023401701.gifinline: 112021419023401901.gifinline: 112021419023402101.gif
RE: Exchange 2010 database
By job title/mailbox size. There seems to be a correlation between the two. From: Shih, Henry [mailto:hms...@ci.livermore.ca.us] Sent: Tuesday, February 14, 2012 11:30 AM To: MS-Exchange Admin Issues Subject: Exchange 2010 database What is the best practice or guideline when you create/organize databases in your organization? How do you add/organize users into different databases? By location? By their size of current mailbox? By department? By users' job title? ... Thanks. Henry Shih System Administrator --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto: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
RE: Exchange 2010 database
By doing it by department you're ensuring that a whole department's email is out of action should their database fail. Better to scatter people randomly. Or is it? Cheers, Phil From: Tobie Fysh [mailto:tobie.f...@freebridge.org.uk] Sent: 14 February 2012 19:03 To: MS-Exchange Admin Issues Subject: RE: Exchange 2010 database No idea about best practice but we do it by department so in the event of a DR we can restore the databases of the most important teams first. Sent from my Windows Phone -Original Message- From: Shih, Henry Sent: 14/02/2012 17:38 To: MS-Exchange Admin Issues Subject: Exchange 2010 database [Freebridge Community Housing Logo]http://www.freebridge.org.uk [twitter.com/Freebridge]http://twitter.com/Freebridge [Freebridge on Facebook]http://www.facebook.com/pages/Kings-Lynn-United-Kingdom/Freebridge-Community-Housing/192690183387?v=box_3 This e-mail (including any attachments), is confidential and intended only for the use of the addressee(s). It may contain information covered by legal, professional or other privilege. If you are not an addressee, please inform the sender immediately and destroy this e-mail. Do not copy, use or disclose this e-mail. E-mail transmission cannot be guaranteed to be secure or error free. The sender does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard copy version. Freebridge Community Housing Ltd is a Charitable Industrial and Provident Society - Reg No IP29744R Registered with the Housing Corporation - No L4463. VAT Registration Number 860762121 Freebridge Community Housing, Juniper House, Austin Street, Kings Lynn, Norfolk PE30 1DZ This email message has been scanned for viruses by Mimecast. Mimecast delivers a complete managed email solution from a single web based platform. For more information please visit http://www.mimecast.com --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it. --- 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 exchangelistinline: image001.gifinline: image002.gifinline: image003.gif
RE: Exchange 2010 database
My two cents... First, I think it depends on the organization! I usually recommend, if most mailbox limits are going to be the same, going for a balanced/random distribution based on the mailbox profile and planned users per DB rather than another factor. And, if you have an entire department on one database, or senior staff - yes you can bring them online first in the event of a total loss of all database copies, but the opposite case is also true - you could end up in a situation with just your sales force or senior staff without email. If they are spread out, then at least you don't lose them all and a part of the organization isn't totally crippled. Also when it comes to sizing you are unlikely to have departments of identical size so you could end up with complicated sizing for LUNs that are hard to manage. Of course not everyone wants a random distribution. Thinking of some customers over the last week I can give a couple of examples where that isn't the case.. Customer 1 - Has convention already in place, distributing by surname. Same mailbox limits for everyone in the organization, so analysed the surnames of the users who'll move onto these databases to determine the split of surnames per DB to tie up with the planned users per DB. Customer 2 - Has different mailbox limits for different types of users, so mailbox database and log LUNs are sized to match these limits and user numbers, with balanced distribution across mailbox databases within each tier. Finally, looking at larger environments (100,000+) and going through some of the Exchange Environment Reports people have emailed me via the blog, there is a general tendency towards a combination of location (eg large, distributed environments) and then spreading the mailboxes across DBs rather than dedicating DBs to department/roles. Steve From: Shih, Henry [mailto:hms...@ci.livermore.ca.us] Sent: 14 February 2012 17:30 To: MS-Exchange Admin Issues Subject: Exchange 2010 database What is the best practice or guideline when you create/organize databases in your organization? How do you add/organize users into different databases? By location? By their size of current mailbox? By department? By users' job title? ... Thanks. Henry Shih System Administrator --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto: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
Re: Exchange 2010 database
We go by surname with appropriate splits for DB sizing. - that spreads users pretty randomly for location, department and all that. Works well for us. Blackberry From: Steve Goodman [mailto:st...@stevieg.org] Sent: Tuesday, February 14, 2012 04:49 PM To: MS-Exchange Admin Issues exchangelist@lyris.sunbelt-software.com Subject: RE: Exchange 2010 database My two cents… First, I think it depends on the organization! I usually recommend, if most mailbox limits are going to be the same, going for a balanced/random distribution based on the mailbox profile and planned users per DB rather than another factor. And, if you have an entire department on one database, or senior staff – yes you can bring them online “first” in the event of a total loss of all database copies, but the opposite case is also true – you could end up in a situation with just your sales force or senior staff without email. If they are spread out, then at least you don’t lose them all and a part of the organization isn’t totally crippled. Also when it comes to sizing you are unlikely to have departments of identical size so you could end up with complicated sizing for LUNs that are hard to manage. Of course not everyone wants a random distribution. Thinking of some customers over the last week I can give a couple of examples where that isn’t the case.. Customer 1 – Has convention already in place, distributing by surname. Same mailbox limits for everyone in the organization, so analysed the surnames of the users who’ll move onto these databases to determine the split of surnames per DB to tie up with the planned users per DB. Customer 2 – Has different mailbox limits for different types of users, so mailbox database and log LUNs are sized to match these limits and user numbers, with balanced distribution across mailbox databases within each “tier”. Finally, looking at larger environments (100,000+) and going through some of the Exchange Environment Reports people have emailed me via the blog, there is a general tendency towards a combination of location (eg large, distributed environments) and then spreading the mailboxes across DBs rather than dedicating DBs to department/roles. Steve From: Shih, Henry [mailto:hms...@ci.livermore.ca.us] Sent: 14 February 2012 17:30 To: MS-Exchange Admin Issues Subject: Exchange 2010 database What is the best practice or guideline when you create/organize databases in your organization? How do you add/organize users into different databases? By location? By their size of current mailbox? By department? By users’ job title? … Thanks. Henry Shih System Administrator --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto: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.commailto: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
