Exchange 2010 DB maintenance

Hello,
Environment : Exchange 2010 sp3 ru3 in DAG
We have a exchange database which is having about 300GB of whitespace.
The database is having about 200 mailboxes and the avaerage mailbox size is 1GB.
We ensured that online maintenance was run completely for 48 hours.We have checked the support sites and see that defrag should not be run on databases which are in DAG.
Last option is to move the mailboxes to another new mailbox.
Any other suggestions?
Regards, Ajit

Agreed with above suggestion.
You can follow the prequisites given at this technet blog and can gather more information while preparing to move mailbox to anoth new mailbox : http://technet.microsoft.com/en-in/library/dd298174%28v=exchg.141%29.aspx
Lepide - Simplifying IT Management

Similar Messages

Appointments from Exchange 2010 show as Mail in Mailbox

I have a very frustrating issue with a single user on one of our post offices. For reasons unknown appointments sent to the user from Exchange 2010 appear as mail items instead of appointments within the mailbox. Other users on the same post office do not get the same issue. I have tried resetting the user's views and a full client reset via maintenance. I have set the user's client settings to be the same as another user who does not get the issue without any luck either. Maintenance checks on the account does not flag any errors. I'm pretty certain I'm missing something very simple, but alas I can not think what.
Software wise we're running client 8.0.1 on post office agent version 8.0.2. We seem to get the same results regardless of the Client version of outlook, (we have tried the web version and 2003 and 2010 of the client). Anything else I could try would be greatly appreciated.
Kind Regards
Rob

In article <[email protected]>, Rob naylor
wrote:
> Software wise we're running client 8.0.1 on post office agent version
> 8.0.2.
>
How about updating those as they are a bit old.
Try looking at that user's account from another machine and from
WebAccess (if installed).
It is good to separate the PC from the user account as sometimes an odd
problem can be from some funky issue on the PC.
I'm not surprised that different versions of the Exchange 2010 client
doesn't make a difference as there is the formatting is set when
Exchange formats the outgoing to the internet.
A thought there, is your user setup as a contact on the Exchange
system, there have been settings in the past that caused invalid
formatting of internet messages. Something to the effect that 'this
user is on OutLook/Exchange vs regular internet standards'.
Has there been a single appointment sent from a user on that Exchange
system to two of your users?
Andy Konecny
Konecny Consulting Inc. in Toronto
"Give more than others think is wise
Challenge yourself beyond what others think is right"
Michael 'Pinball' Clemens

Exchange 2010 /hosting shared mailbox issue

Hello everyone.
I had an issue come up in our Exchange 2010 with /hosting switch deployment (currently at SP2).
We have several organizations and shared mailboxes configured and working on some. We add Full access permissions via Powershell + Send as rights and it auto configures and works just fine.
Last week though, one of several people that uses a specific shared mailbox started getting the error: "Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the
Microsoft Exchange Server computer is down for maintenance." (Error ID: 300)
The other users can still work just fine. Configuring the account in another PC shows the same problem (so it's not the local profile).
Creating 2 users, giving nr1 full access to nr2 generates the same error.
In another org though, i was able to give full access to another acount to an existing user and it worked (although the auto-mapping didn't, had to add it manually)
I'm out of ideias. Any sugestions?
EDIT: Did a couple more tests on another Org. On this one everything works with the shared folder access with old and new accounts but strangely the auto-mapping doesn't.
It seems that this is an issue with the mapping.

Hi,
From your description, I recommend you manually update or create your Outlook profile with RPC encryption and check the result. Here is the steps on Outlook 2007 for your reference:
1. Select your profile, and then click Properties, click E-mail Accounts.
2. Select the Microsoft Exchange Server account, and then click Change.
3. In the dialog box that contains your mailbox server and user name, click More Settings.
4. In the Microsoft Exchange Server dialog box, click the Security tab.
5. Click to select the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box, and then click OK.
6. Click Next, and then click Finish.
For more information, here is a kb for your reference.
Connection issues and error messages in Outlook for a mailbox on a server that is running Exchange Server 2010
http://support.microsoft.com/kb/2735060
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2010 Rollup 2 SP3 update cannot find installation package exchangeserver.msi file on SBS 2011... NEED HELP!!!

Hello,
I am running a windows SBS 2011 standard system and there was currently an update for Exchange 2010 Rollup 2 Service Pack 3 and it keeps failing. It says that it cannot find the installation package (exchangeserver.msi) and it is looking for it
in E:\Software\Exchange2010-SP3-x64\ folder but there never was this folder. There is only an Exchange2010-SP3-x64.exe file.
The only exchangeserver.msi file that I find on the server any where is in C:\ProgramFiles\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1 but it won't accept it (says not authorized for this update or something alike).
Please help. It is currently causing issues with email. Some of the features are not working because it says exchange is currently under maintenance.
Any suggestions would be greatly appreciated. Thank you.

Susan you are correct: After I installed Exchange 2010 SP3, I deleted the msi just to "clean up' my hard disk... While trying to install Rollup 2 for SP3, the installer is trying to find it. I downloaded the installer, used 7-zip to get
the msi and I pointed the installer to it when asked.
The installation failed 3 times...
NOTE: I was using WSUS to install the Rollup: I downloaded the Rollup installer and I executed: I could see where the installer was hanging up! First it asked me to stop an SBS service and something else (sorry I do not remember), I stopped
the services and installation continued. Then it asked me for more files from the SP3 installation which I found on the installation folder that I created with 7-zip. I copied to the path that the installer was looking and installation finished
(finally!)...
NOTE 2: If you have any firewall appliance that denies Internet access to un-authenticated requests, you better turn that rule off because the installer accesses the internet (not sure why - probably for Dot Net assemblies)...
Susan THANKS for all your help to the community! You have helped so much!
All the Best
Constantine

Problems with archive mailbox in Outlook, with exchange 2010+2013 co-existence

Hi!
We have an Exchange 2010 environment plus one Exchange 2013 MBX server meant for archive mailbox purpose. (We are going to upgrade to 2013 but with over 20.000 mailboxes it will take som time. Therefore we need to co-exist with primary mbx on 2010 and archive
mbx on 2013 for some time.)
My primary mailbox is on a 2010 MBX server, and I have today given myself an archive mbx on 2013 MBX server.
When I use OWA, both my primary mailbox and my archive shows up and everything works 100% fine!
But when I try Outlook 2010 or Outlook 2013, only my primary mailbox works. The archive mailbox shows up, but generates an error when accessing it:
"The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance"
Anyone who knows about this issue? Would we nice to know why it works in OWA but not in Outlook.
Thanks!
Trond Jenssen

Hi，
Please try to recreate a profile to access archieve mailbox.
If it doesn't make sense, also try Uncheck “Download shared folders” and check it again.
If you have any feedback on our support, please click
here
Wendy Liu
TechNet Community Support

Exchange 2010 mailbox not able to access auto-mapped Exchange 2013 CU3 mailbox

Hi,
We are in co-existence with Exchange 2010 SP3 and Exchange 2013 CU3.
Outlook Anywhere and Autodiscover pointed towards Exchange 2013 CAS servers. Everything works fine irrespective where is mailbox is located Exchange 2010 or 2013.
When I tried to access auto-mapped mailbox from Exchange 2010 as primary mailbox accessing auto-mapped Exchange 2013 mailbox "Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network
problems or the Exchange server is down for maintenance".
Exchange 2013 OutlookAnywhere "Externalclientauthenticationmethod" is Basic and "Internalclientauthencitcationmethod" is NTLM. Everything is setup as per the Tech-net recommendations.
Checked both these articles but still it is not working:
http://support.microsoft.com/kb/2839517
http://support.microsoft.com/kb/2834139
Please let me know if there are any other ideas.
Raman

Hi,
I recommend you refer to the following articles to troubleshoot the issue:
Troubleshooting Mailbox Auto-Mapping : Autodiscover
Details about the shared mailbox that is to be accessed will be returned to the Outlook client by the autodiscover process. This is really handy to know if you are ever in the position where you need to troubleshoot why the auto-mapping feature isn’t working
correctly
Troubleshooting Mailbox Auto-Mapping : Permissions
When you use either the Exchange Management Console or the Exchange Management Shell to grant a user with full access permission against another mailbox, permissions changes are made to allow this as you might expect. Certain Active Directory attributes
are also updated to reflect both the Active Directory account of the mailbox being accessed as well as the Active Directory account of the accessing mailbox. Specifically, you can check the contents of the msExchDelegateListLink and msExchDelegateListBL Active
Directory attributes to see these details and it is worth checking these if you have any suspicions that things aren’t working correctly.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Unity 5.0 compatibility with Exchange 2010 SP2?

Has anyone out there tested Unity 5.0 (1) with Exchange 2010 SP2? Did you have any problems? I understand that Unity 5.x has gone end of maintenance, and it has not been officially been tested for compatibility with Exchange 2010 SP2 for unified messaging. I don't anticipate being able to upgrade Unity until next year, but the sytem admins want to upgrade from Exchange SP1 to SP2 sooner. Thanks.

Has anyone out there tested Unity 5.0 (1) with Exchange 2010 SP2? Did you have any problems? I understand that Unity 5.x has gone end of maintenance, and it has not been officially been tested for compatibility with Exchange 2010 SP2 for unified messaging. I don't anticipate being able to upgrade Unity until next year, but the sytem admins want to upgrade from Exchange SP1 to SP2 sooner. Thanks.

Questions about upgrading from Exchange 2010 RTM to Exchange 2010 Service Pack 3

I am preparing to perform an maintenance upgrade on our current Exchange 2010 Server, to Service Pack 3 (and any post-SP3 roll ups), but I have a couple questions about the process.
Current Exchange Server details:
Exchange 2010 Standard
Version: 14.0 (Build 639.21) - from Exchange Management Console
Version: 14.0.702.4000 - from Outook client
Active Directory forest and domain levels: Windows 2008 R2 native
The questions I have are:
1. Can I assume that because it's version 10.0.702.4000 I am on Exchange Server 2010 RTM Update Rollup 4?
2. Can Exchange 2010 Standard RTM be patched directly to Service Pack 3, or would I need to perform incremental patches (i.e. SP1, SP2, etc.) before going to SP3?
3. Do I need to manually perform the AD domain schema prep before applying Service Pack 3, or will the Service Pack 3 update process automatically handle the modifications of the AD schema?

Hi,
Here are my answers you can refer to:
1. Firstly, I’d like to explain , we can use connection status to check our Exchange server version from Outlook client:
http://office.microsoft.com/en-in/outlook-help/determine-the-version-of-microsoft-exchange-server-my-account-connects-to-HA010117038.aspx
And I check my version from both EMC and Outlook client. It’s same.
2. We can directly update RTM version to SP3 , and the update will take an additional 30 minutes or longer per database.
3. Since Exchange 2010 SP3 makes updates to the Active Directory schema, we need prepare AD domain schema. However, it will automatically prepare AD and the domain when you install the update.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/jj965774(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela
Angela Shi
TechNet Community Support

Upgrading domain controller from Server 2003 to Server 2012 R2, how will this affect Exchange 2010?

Hi All,
Below is an AD and Server related post that I had submitted last week. While I did receive valid responses for the post, I was advised to check with the Exchange forums for the Exchange related question in
bold. All responses are welcomed, thank you!
===========================================================
Hi All,
I am hoping that someone could perhaps provide some insight on this topic as I apparently can't seem to google the best answer.
I have recently acquired an AD domain that is running on a 2003 domain controller. I have been tasked with upgrading our existing domain structure with 2012 R2 domain controllers for our main office and remote offices.
The domain name is company.mynetwork.com, and it is the default first site name. We have multiple offices throughout the US with their own domain controllers (i.e. FL.mynetwork.com, NY.mynetwork.com, DC.mynetwork.com, etc.).
Our main office, and default first site has one domain controller (mynetdc1) running Server 2003 R2. It is also our only DNS server for the main office. It also has an additional domain controller called mynetmaster3 which is running Server 2003.
Both mynetdc1 & mynetmaster3 NTDS settings show them as global catalogs under AD Sites & Services. Both servers are also in the AD Domain Controllers OU, along with all of the other satellite office domain controllers.
Additionally, our main office is running Exchange 2010 with the latest service pack. My questions are:
Can we demote and retire mynetmaster3, then replace mynetdc1 with a newly promoted 2012 R2 global catalog domain controller without harming anything in the domain tree and interrupting connectivity to the other offices (this of course goes without saying
after a 4 hour maintenance window to get the task completed has passed)?
Should we upgrade the satellite offices first after raising the functional level for mynetdc1, or should we do the opposite (upgrade main office, then satellite offices)?
MS Exchange 2010 is heavily dependent on AD, what effect will this entire project have on our email server? What steps should we take beforehand to ensure email continuity?
Finally, is there any shame for a Net Admin to suggest that we hire an implementation specialist for this task? :)
Any advice would be greatly appreciated!

As long as the operating system on your Exchange servers isn't upgraded, and as long as you do the Active Directory domain and forest updates in the supported manner (the following link is a good example -
http://blogs.msmvps.com/mweber/2012/07/30/upgrading-an-active-directory-domain-from-windows-server-2003-or-windows-server-2003-r2-to-windows-server-2012/), Exchange will happily operate behind the scenes. Exchange 2010 is supported in the Windows
forests (domain controllers, domain functional level and forest functional level) mentioned in the following TechNet article, which includes both Windows 2003 and Windows 2012.
http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx
Due to this, you should be good as long as you do the domain controller, domain, and forest upgrades carefully. Oh, and before you start each step, get a nice backup.

Prepare Exchange 2010 for a Major Network Outage

We are planning to replace our Core networking switch in our production environment. I am looking for a best practice option for Exchange to be placed into during this outage. This will be an approximate four hour outage.
Our current environment for Exchange is this:
Exchange 2010 SP3 rollup 8v2 two CAS servers and Three MBX/HT servers.
I read a few articles and they recommended different things, one was to just power down all of the exchange servers before the outage and then bring them back up after the outage. To me this just seems like a bad idea. The other was to put the MBX servers
into maintenance mode prior to shutting them down. This seemed more practical.
Can anyone provide feedback, insight, and guidance in this case? Has anyone gone through this type of outage and if so how did you handle your exchange environment and what was your success or failures with the scenario you used?
Thank you

When the server is in maintenance mode it moves all the active databases to other DAG members. It pauses the node in the cluster, and sets the DatabaseCopyAutoActivationPolicy mailbox server setting to Blocked. The Suspend-MailboxDatabaseCopy cmdlet is run
for each database hosted by the DAG member, and the cluster core resources will be moved to another server in the DAG if needed. This prevents data bases from auto activating in the case of a server failure. Just powering down an exchange MBX server would
cause the active data bases to failover to the alternate server, but once Quorum is lost due to more than half of the servers being shut down, I am not sure how the data bases would react after being brought back on line. Based on
this it seems to me that putting the servers in maintenance mode prior to powering them down would be the safest bet.
TL;DR What I am really looking for is advice or experience from an Admin who has already gone through a similar exercise.
Thanks for your input.

Exchange 2010 Unable to create new mailboxes through provisioning

Recently I started noticing that when attempting to create a new mailbox in Exchange 2010 I was receiving the error "Load balancing failed to find a valid mailbox database". I checked the provisioning by running the command "Get-MailboxDatabase
| ft Name,IsExcludedFromProvisioning". All my databases are set to "true". All I would have to do is run the command "get-mailboxdatabase | set-mailboxdatabase -isexcludedfromprovisioning $false" to enable the provisioning again. My
question is here, does this require any kind of reboot or setting the DAG into maintenance mode? These are prod servers and I would hate to run a command that might cause an unplanned downtime of any sort. I got a feeling that this is probably a quick simple
command and wont cause any issues, just want to confirm that this won't require any sort of planning before running.

No, you don;t have to restart the server or make any changes in DAG.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Circular Logging in exchange 2010

1.
How to enable circular logging in Exchange 2010 while is in DAG in place.
2.
When enable it will it clear my Transaction Log automatically?
Regards

The Exchange Management Shell can be used to determine which mailbox databases are enabled for circular logging by running the following command.
[PS] C:\>Get-MailboxDatabase | where {$_.CircularLoggingEnabled -eq $true}
Name Server Recovery ReplicationType
Mailbox Database 02 EX1 False Remote
Mailbox Database 04 EX2 False None
Another technique is to list all mailbox database sorted by their circular logging settings.
[PS] C:\>Get-MailboxDatabase | select name, circularloggingenabled | sort circularloggingenabled -desc | ft -AutoSize
Name CircularLoggingEnabled
Mailbox Database 04 True
Mailbox Database 02 True
Mailbox Database 01 False
Mailbox Database 03 False
Here is a method that can be used to disabled circular logging on each of the mailbox databases. Because the change doesn’t take effect until the mailbox database is dismounted and mounted again, this method also performs that task.
Caution: this may cause a disruption to mailbox access for your end users, so I do not recommend running this outside of maintenance windows.
Firstly, read the mailbox databases that have circular logging enabled into an array.
[PS] C:\>$dbs = Get-MailboxDatabase | where {$_.CircularLoggingEnabled -eq $true}
You can see now that the two mailbox databases are in the array.
[PS] C:\>$dbs
Name Server Recovery ReplicationType
Mailbox Database 02 EX1 False Remote
Mailbox Database 04 EX2 False None

Sequence for shutting down Exchange 2010 Servers

I have 3 mailbox servers, 3 CAS servers, 3 hubtransport servers, in active production, and I have 3 mailbox servers, 3 cas servers, and 3 hubtransport servers, as a DR. I have a DAG between them and a Cassarray
These Servers are virtualized using vmware.
I need to know microsoft's BPA for shutting down these servers to move to another location.

Follow these- are you completely shutting down the server or planning to do the maintenance.?
http://exchangeserverpro.com/forums/exchange-server-2010/3186-datacenter-power-shutdown-need-shutdown-all-exchange-servers.html
http://www.kreslavsky.com/2011/04/shut-down-exchange-2010-dag-member.html
The correct way to perform any maintenance is to run first StartDagServerMaintenance.ps1 script that is located under “C:Program FilesMicrosoftExchange ServerV14scripts”
This script moves all the active databases to next preferred DAG server and prevents active databases from moving to that server during the maintenance.
In addition the script ensures that all critical DAG support functionality that may be on this server has been moved to next proffered server
Once the DR site servers are in maintenance mode you can bring the serves down in DR site first, CAS and then Hub.
And then on the Primary Site shutdown the CAS and HUB, Dismount the DB and shutdown the servers.
Where Technology Meets Talent

Moving/rebooting Exchange 2010 server

So we have 2 Exchange 2010 SP3 servers- 1 east coast and 1 west coast which are in a 2 member replicated DAG (plus one quorum node). Both are MBX/CAS/HUB servers. We need to physically move the east coast server which will require about 4 hours downtime.
We also figured this would be a good time to upgrade the latest MSFT patches as we are a bit out of date. What is the proper procedure "step by step" for gracefully relocating a server and restoring DAG replication? Maintenance mode? Relocate each
database?
-John

Hi,
If you want to update patches, you need to place this DAG member into maintenance mode before updating.
Then you can install update and move mailbox databases. After that, you can take this DAG member out of maintenance mode.
Here is an article about how to install update rollups on DAG members for your reference.(This process can also be used to install operating system updates.)
http://technet.microsoft.com/en-us/library/ee861125(v=exchg.141).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

CLUSTER(DAG) EXCHANGE 2010 - Updates

Hello
I want apply Updates in Exchange 2010 with Cluster
What is the procedure?? ( step by step please )
Thanks and regards
MCITP

If its Exchange 2010 with SP1 and above, you only need to run the maintenance script.
The script will automatically do the following tasks for you:
Calls Suspend-MailboxDatabaseCopy on the database copies.
Pauses the node in Failover Clustering so that it can not become the
Primary Active Manager.
Suspends database activation on each mailbox database.
Sets the DatabaseCopyAutoActivationPolicy to Blocked on the server.
Moves databases and cluster group off of the designated server.
Exchange services will be stopped automatically if necessary, but it is recommended to stop AV services.
Please flow the steps provided above.
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Exchange 2010 DB maintenance

Similar Messages

Maybe you are looking for