Exchange 2010 Dirty Shutdown

hi ,
We have DAG implemented Server A & Server B , Server A is on production enviroment & server B is holding passive database when I am checking health of Server B database it is showing database is dirty shutdown . How can I fix that please help

How you check exchange health which likely to show as "database is dirty shutdown" ?
Though, you can run with Eseutil.Exe tool to repair corrupt database and recover the mailbox again.
Check-out this
link for detail information and step-wise process.
However, sometimes Eseutil does not correct the problems at the application level. In such scenario, you can have try this
utility which would a best approach and good solution in order to repair corrupt exchange database and restore all the data content in previous used values.

Similar Messages

Exchange DataBase is in Dirty ShutDown State

Hi ALL,
I am not able to mount the Data Base in Exchange Server 2010, I have run “Eseutil /mh” and confirm that Data base is in Dirty shutdown state.
Now, can any buddy tell me the step by step procedure to make it in Clean shutdown state.
Subs

HI Shubi,
Zahir have provided very good article to make clean shutdown your DB. Please try to run "eseutil /mk" swicth against check point file and see if any remain log files is not commited. In this case you can use "eseutil /r /e01" (Base file can be change) and
try to recover it.
Some more information.
Exchange Database Recovery – Using eseutil commands:
http://msexchangeguru.com/2009/07/12/exchange-database-recovery-using-eseutil-commands/
http://smtp25.blogspot.com/2007/05/eseutil-in-exchange-2007-and-lost-log.html
Anil MCC 2011,ITIL V3,MCSA 2003,MCTS 2010, My Blog : http://messagingschool.wordpress.com

Exchange 2010 mount database after dirty shut down

I have exchange 2010 where is all roles located on , i have only 1 database , this database is dismounted & unable to b re-mounted again with the following error
Microsoft Exchange Error
Failed to mount database 'Mailbox Database 0173462073'.
Mailbox Database 0173462073
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database 0173462073; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount
database. (hr=0x80004005, ec=-550)
[Database: Mailbox Database 0173462073, Server: Exchange2010.Egytrav.local].
An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)
[Database: Mailbox Database 0173462073, Server: Exchange2010.Egytrav.local]
An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)
[Server: Exchange2010.Egytrav.local]
MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-550)
OK
all services is started correctly , i can stop & start normally , i could create new database & mounted ok
any help?

You said the database is definitely NOT mounted correct?
the -1032 means something has a lock on the EDB file which would make sense if its locked
If its not mounted then do you have another session open somewhere trying to take action on the EDB, copy it etc?
Sometimes backup jobs can put a hold on a file, i.e. I have seen BUE do this and its quit aggravating because the job doesn't even have to be running
If you cant find what has a lock on the file and your are absolutely sure its not mounted then use this file unlocker utility
http://download.cnet.com/Unlocker/3000-2248_4-10493998.html
Troy Werelius
http://www.lucid8.com/

External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
the Exchange 2010 all incoming external mails were not received. What could be the cause?

Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
Sniff the traffic to ensure that it is hitting 2013 directly.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
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.

Exchange crash during move request, new DB in dirty shutdown

I had a hardware failure (storage controller in VM environment) during a mailbox move request to a new DB. After fixing that and rebooting, the old database came up and is fine which is great. The new database is in a dirty shutdown state right now with a few completed but most are still queued or in progress. If I try to remove the request on the completed mailboxes it has a message along the lines of, couldn't connect to mailbox database, it could be dismounted. Do you want to orphan the move request for user XYZ?
Will this cause any problems? I would like to remove the move requests and proceed recovery and repair of the dismounted DB. Thoughts?
Thanks,
Josh
This topic first appeared in the Spiceworks Community

Hi,
Thank you for sharing the resolution.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Replay only particular logs (before a certain date) to restored Exchange 2010 database?

Hello,
I'm doing Exchange 2010 database full backup using windows server backup (windows 2008 R2) every weekend. I have a Mac user which Mac Outlook 2011 which somehow managed to corrupt his mailbox. I.e. on Wednesday many messages and contacts disappeared (all
contact gone) after his Outlook told his something about "corrupted database". I'm not sure what Mac Outlook did, but fact is that his mailbox has zero contacts and many inbox message are gone. Hard deleted items don't contain lost messages.
So I have DB backup from weekend before and weekend after. No circular logging, so all logs in place.
Is there a way how I can restore his mailbox back to the point in time? I want to restore his mailbox how it was on Wednesday morning. For it looks obvious that since I have log files from Monday to Friday, it should be possible to replay logs until certain
time.
I tried to did thick trick by removing Friday and Thursday logs and doing soft recovery, but got Operation terminated with error -543 (JET_errRequiredLogFilesMissing, The required log files for recovery is missing.) They indeed missing:
dbtime: 2221857861 (0x846edc45)
State: Dirty Shutdown
Log Required: 2895446-2895464 (0x2c2e56-0x2c2e68)
Log Committed: 0-2895465 (0x0-0x2c2e69)
Log Recovering: 2838005 (0x2b4df5)
Log required are logs from they day of backup, so they are really missed in that case, but that's what I want - restore DB with less/older logs to get back in time, when mailbox was not corrupted.
Is that possible?
Thanks

ok so the problem is you have the dreaded -1018 error and this is a very serious issue. -1018 is not a good deal at all, in short your DB has corruption within it
and it is usually caused by a hardware or firmware related issue. Most of the time these occur somewhere within the storage subsystem, i.e. firmware upgrade or lack of firmware upgrade, Controller issue, cabling, disk, disk arrays, etc, however they can
also be caused by memory upgrades or failures, Motherboard issues etc.   The -1018 tells you the DB is already damaged and if you see these its very bad and needs to be addressed ASAP else the DB's are sure to fail and the more stress you put on
them the faster the chance of failure, i.e. database backups, defrag;s and repairs etc are not recommended at all until you solve the hardware issue. So here is what I would recommend:
A: Lets try to ensure the box is stable and whatever caused the DB to get the -1018's is solved before we do anything else.
General Review: Whats changed recently? i.e. any hardware, memory, motherboard, any firmware updates on anything at all?
Event Log Review: Look at your Application Log, how long have these 1018's been occurring?   Look at your System event log for errors and pay close attention to any errors regarding disk, memory or MB and report back
Protect: I would dismount the database & copy it and any others off to a secure, safe drive that is NOT connected to this system
Action: Depending on what you find in your review there are really two options
     i: If you had a recent change that is easily identifiable you may be able to correct it and then we can look at finding a clean copy of the EDB and rolling up the logs OR we opt to repair the DB you have
     ii: if you cannot find the issue in short order then I would suggest that you build a new Exchange Server on new hardware and migrate your mailboxes immediately.
B: Once you have addressed the -1018 issue then;
1. We need to find a database from your backups that does NOT have the -1018 result code when attempting a rollup.
2. Once you have a non -1018 result you can then grab a fresh copy of the EDB along with all logs from that point forward and make a consistent DB via rollup up to the 18th as desired.
3. If you cannot find a good copy of the EDB then you are stuck with the latest data you have and should either move all mailboxes to a new EDB on that server but ONLY IF the source of the -1018 is found and resolved, else you will just be making thing s
worse. IF you CANNOT resolve the issue that causes the -1018 then build a brand new server and move all users over to it ASAP, else you are headed for a major failure on all users.
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Can't Restore Exchange 2010 Mailbox DB from HP Data Protector backup

I'm trying to implement Exchange 2010, but I won't feel comfortable moving many users to it until I've successfully restored a mail database from tape backup. So far, this hasn't worked out so well. I'm using HP Data Protector for my backup solution.
Here's what I've done:
1. In DP's "Restore" GUI, navigated down to the MS Volume Shadow Copy Writers entry, then selected both "Files" and "Logs" from the DB's entry under Microsoft Information Store. I'm not restoring any of the other Writers. So that I don't have to take down Exchange, I'm restoring them to a temporary restore location.
2. After the restore completes, I go to the temporary restore location on the server and run eseutil /mh on the database, which returns a "Dirty Shutdown" db status.
3. Since I have the log files, I attempt to repair using eseutil /r E01 in the log files' path. This generates "Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after 10.608 seconds."
Can anyone suggest what I'm doing wrong with this recovery? If my steps are incorrect I'd love to know, as HP's documentation for restoring Exchange 2010 is very young and not terribly useful. My ultimate goal is to be able to restore a database from DP's tapes and bring it back online on the Exchange 2010 server.
Thanks!
Thanks!

Hi Ben,
We backup our primary database (Ex Writer) and always with full backup (DB+LOGS). When we restore we restore to alternate location, then manualy copy db file and everything from restored log directory to one folder (for example: d:\restore_DB1). At this
stage DB is in dirty shutdown state. Then we run (in folder where we copied db file and log files)
Eseutil.exe /R E00 /D
it takes a couple of seconds (160GB file) and the db is in clean shutdown state. Then we do:
New-MailboxDatabase -Name “Restored DB” -Server MBOX1 -EDBFilePath “D:\Restore_DB1\DB1.edb”
-Logfolderpath “D:\Restore_DB1” -Recovery
and
Mount-Database “Restored DB”
now we can restore single mailbox or even single item from mailbox with:
1: whole mailbox with overite the destination
Restore-Mailbox –Identity “USERNAME” –RecoveryDatabase “Restored DB”
2. whole mailbox to alternate location (new folder in another mailbox)
Restore-Mailbox –Identity “EXISTING MAILBOX TO RESOTRE TO” –RecoveryDatabase “Restored DB” –RecoveryMailbox “MAILBOX DO BE RESTORED
FROM BACKUP” –TargetFolder “NEW FOLDER IN EXISTING MAILBOX”
3. the same as 2 but single item with MEETING in email subject
Restore-Mailbox –Identity “EXISTING MAILBOX TO RESOTRE TO” –RecoveryDatabase “Restored DB” –RecoveryMailbox “MAILBOX DO BE RESTORED
FROM BACKUP” -SubjectKeywords "MEETING" –TargetFolder “NEW FOLDER IN EXISTING MAILBOX”
Best Regards,
Alex

How to reset logs on Exchange 2010 after Event 518 stops backups from completing?

I'm only able to find references to resetting logs Exchange 2000 and 2003. I'm looking for info for Exchange 2010.
There appears to be some kind of corrupt logs issue with one of our mailbox databases. The corrupt logs cause the full backup to fail and because the full backup fails, the logs just get worse and keep growing.
The server has event ID 518 that says a log is "is missing (error -528) and cannot be used. If this log file is required for recovery, a good copy of the log file will be needed for recovery to complete successfully. "
How do e get past this and stop the backup job from trying to look for this log file and start over? I know that a full backup is supposed to clear the logs, but it will not happen because the backup never completes due to this log error.

its still same for 2010
Stop all the databases in the storage group.
Verify the state of each database file in the particular storage group. For information about how to verify the state of each database file, see the "Database states" section.
Perform one of the following actions:
If one or more of the databases are in a Dirty Shutdown or Inconsistent state, determine which transaction log files can be removed without affecting database consistency.
For more information, see the "Log files" section.
If all the databases are in a Clean Shutdown or Consistent state, you may remove all the transaction log files except for the current transaction log file. Removing the
current log file when all databases are in a Clean Shutdown state will cause a reset of the log file sequence. This does not prevent databases from starting. However, a reset of the log file sequence affects the ability to roll a
database forward from a previous backup if the situation occurs.
Copy all the transaction log files that you want to remove to a different location before you permanently remove them from the transaction log hard disk. Do not permanently delete the transaction log files until you have
successfully completed a full online backup of all the databases in the storage group.

Exchange 2010 - Database issues

Good morning everyone!
I have an exchange database problem. It was first caught when implementing exchange backups with Acronis backup software.
(EXCHANGE 2010 v 14.01.0218.013)
So the backups fail one night and succeed the next. But each time it fails we get 4 errors (Consistency related). Also the database size is growing rapidly. Here are the errors:
Then a couple more:
EVENT ID 9782
Exchange VSS Writer (instance b1bfbf43-9594-4cee-980f-50d84b0ee4eb:76) has completed the backup of database 'xxxxxxxxx' with errors. The backup did not complete successfully, and no log files were truncated for this database.
Then finally:
EVENT ID 2007
Information Store (2136) Shadow copy instance 76 aborted.
For more information, click http://www.microsoft.com/contentredirect.asp.
EDIT:
SO my DB is not growing because the issue...I had forgotten that we enabled LEGAL HOLD. But my backups fail / succeed / fail / succeed.
Any ideas on this?
Kevin

Hi,
Please use Windows Server backup to backup the Exchange database to check result.
If Windows Server backup works well, I recommend you contact the third party support to confirm this issue.
If the issue persists, please check whether your database is dirty shutdown. If it's dirty, please bring to clean state and backup agian to check result.
Best regards,
Belinda Ma
TechNet Community Support

Dirty Shutdown: 0

Hi. Sorry if this is a silly question, but I'll ask it anyway.
Does "Dirty Shutdown: 0" in an ESE event 327 mean "Dirty Shutdown: No", i.e. the database shut down cleanly? I'm guessing "0" means "No"; and that "1" would mean "Yes, it *was* a dirty shutdown",
but I can't find this explicitly stated anyahere.
Reason I ask is that I dismounted a mailbox database in order to move EDB and log paths, the move failed, and the database then wouldn't mount for an hour. (After 30 auto-retries it succeeded.)
In looking for the cause of the problem, I found, among other Application Log entries:
"Information DD/MM/YYY HH:MM:SS ESE 103 General Information Store (3720) <Database-Name>: The database engine stopped the instance (4). Dirty Shutdown: 0"
and I'm trying to establish whether this means the shutdown was or wasn't dirty. Thanks.

Those are normal events and are to be expected when activating another store (1) versus dismounting and remounting a store (0).
Also the DB when mounted is ALWAYS in a dirty state and upon completion of a proper dismount it should be clean.
before you do a move I would take a look at the # of transaction logs since the more there are the longer it will take to complete the move. if there are an excessive # of logs you may want to do a full backup first to truncate the logs and then do
the move
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

ACE20 Module with Exchange 2010 Configuration

Hello all,
I have deployed the following configuration for Exchange 2010, if all services are up on the two servers it functions good but if a service goes down on one server (especially outlook) some clients are disconnected (stickiness) ...
Stickiness is needed for all services by ip source sticky and by coockies for OWA.
Because all services are on the same server (ip address) the configured sticky causes problems !!! when a service is down the ACE usually forwards requests to it !!!! Any help please.
Configuration :
XXXXX-ACE1/CTXT-EXCHANGE(config)# do sh run
Generating configuration....
access-list BPDU-Allow ethertype permit bpdu
access-list EXCH-LB line 10 extended permit ip any any
probe http HTTP-GET
interval 10
passdetect interval 10
request method get url /iisstart.htm
expect status 200 202
probe icmp PING
interval 3
probe tcp abport
port 7575
interval 2
faildetect 2
passdetect interval 10
passdetect count 1
connection term forced
probe tcp epmap
port 135
interval 2
faildetect 2
passdetect interval 10
passdetect count 1
connection term forced
probe tcp http
interval 2
passdetect interval 2
passdetect count 1
connection term forced
probe http http-probe
interval 60
passdetect interval 60
passdetect count 2
request method get url /exchweb/bin/auth/owalogon.asp
expect status 400 404
probe tcp https
port 443
interval 2
passdetect interval 2
passdetect count 1
connection term forced
probe http https-probe
interval 60
passdetect interval 60
passdetect count 2
request method get url /owa/auth/login.aspx
expect status 400 404
probe tcp imap
port 143
interval 2
passdetect interval 2
passdetect count 1
connection term forced
probe tcp imaps
port 993
interval 2
passdetect interval 2
passdetect count 1
connection term forced
probe udp ipsec
port 500
interval 2
passdetect interval 2
passdetect count 1
probe icmp ping
interval 2
passdetect interval 2
passdetect count 1
probe tcp pop3
port 110
interval 2
passdetect interval 2
passdetect count 1
connection term forced
probe tcp pop3s
port 995
interval 2
passdetect interval 2
passdetect count 1
connection term forced
probe tcp rpcport
port 7576
interval 2
faildetect 2
passdetect interval 10
passdetect count 5
connection term forced
probe tcp smtp
port 25
interval 2
passdetect interval 2
passdetect count 1
connection term forced
rserver host CAS1
ip address 172.22.101.74
inservice
rserver host CAS2
ip address 172.22.101.76
inservice
rserver host HUB1
ip address 172.22.101.75
inservice
rserver host HUB2
ip address 172.22.101.77
inservice
rserver redirect RPC-REDIRECT
rserver redirect SSLREDIRECT
webhost-redirection https://mail.tunisiana.com/owa 302
inservice
serverfarm host CAS-Outlook
probe PING
probe abport
probe epmap
probe rpcport
fail-on-all
rserver CAS1 135
    inservice
rserver CAS1 7575
    inservice
rserver CAS1 7576
    inservice
rserver CAS2 135
    inservice
rserver CAS2 7575
    inservice
rserver CAS2 7576
    inservice
serverfarm host CAS-http
probe HTTP-GET
probe PING
rserver CAS1 80
    inservice
rserver CAS2 80
    inservice
serverfarm host CAS-https
probe https
probe ping
rserver CAS1 443
    inservice
rserver CAS2 443
    inservice
serverfarm host CAS-imap
probe PING
probe imap
rserver CAS1 143
    inservice
rserver CAS2 143
    inservice
serverfarm host CAS-imaps
probe imaps
probe ping
rserver CAS1 993
    inservice
rserver CAS2 993
    inservice
serverfarm host CAS-ipsec
probe ipsec
probe ping
rserver CAS1
    inservice
rserver CAS2
    inservice
serverfarm host CAS-pop3
probe ping
probe pop3
rserver CAS1 110
    inservice
rserver CAS2 110
    inservice
serverfarm host CAS-pop3s
probe ping
probe pop3s
rserver CAS1 995
    inservice
rserver CAS2 995
    inservice
serverfarm host CAS-smtp
probe ping
probe smtp
fail-on-all
rserver CAS1 25
    inservice
rserver CAS2 25
    inservice
serverfarm host HUB
probe ping
probe smtp
rserver HUB1
    inservice
rserver HUB2
    inservice
serverfarm redirect RPC-REDIRECT
serverfarm redirect SSLREDIRECT
rserver SSLREDIRECT
    inservice
parameter-map type http STICKY
persistence-rebalance
parameter-map type connection TCP_IDLE_30min
set timeout inactivity 1800
sticky ip-netmask 255.255.255.255 address source HUB-ST
timeout 30
replicate sticky
serverfarm HUB
sticky ip-netmask 255.255.255.255 address source CAS-http-ST
timeout 30
replicate sticky
serverfarm CAS-http
sticky ip-netmask 255.255.255.255 address source CAS-https-ST
timeout 30
replicate sticky
serverfarm CAS-https
sticky ip-netmask 255.255.255.255 address source CAS-imap-ST
timeout 30
replicate sticky
serverfarm CAS-imap
sticky ip-netmask 255.255.255.255 address source CAS-imaps-ST
timeout 30
replicate sticky
serverfarm CAS-imaps
sticky ip-netmask 255.255.255.255 address source CAS-smtp-ST
timeout 30
replicate sticky
serverfarm CAS-smtp
sticky ip-netmask 255.255.255.255 address source CAS-pop3-ST
timeout 30
replicate sticky
serverfarm CAS-pop3
sticky ip-netmask 255.255.255.255 address source CAS-pop3s-ST
timeout 30
replicate sticky
serverfarm CAS-pop3s
sticky ip-netmask 255.255.255.255 address source CAS-ipsec-ST
timeout 30
replicate sticky
serverfarm CAS-ipsec
sticky ip-netmask 255.255.255.255 address source CAS-Outlook-ST
timeout 30
replicate sticky
serverfarm CAS-Outlook
sticky http-cookie sessionid exchange-sticky-sessionid-grp
timeout 20
serverfarm CAS-http
sticky http-cookie cookie OWA-STICKY
cookie insert browser-expire
timeout 60
replicate sticky
serverfarm CAS-http
sticky http-header Authorization CAS-RPC-HTTP
serverfarm CAS-http
class-map match-any CAS-OUTL-MAPI-VIP
2 match virtual-address 172.22.101.69 tcp any
class-map match-any CAS-Outlook-VIP
2 match virtual-address 172.22.101.69 tcp eq 135
3 match virtual-address 172.22.101.69 tcp eq 7575
4 match virtual-address 172.22.101.69 tcp eq 7576
class-map match-any CAS-http-VIP
2 match virtual-address 172.22.101.69 tcp eq www
class-map match-any CAS-https-VIP
2 match virtual-address 172.22.101.69 tcp eq https
class-map match-any CAS-imap-VIP
2 match virtual-address 172.22.101.69 tcp eq 143
class-map match-any CAS-imaps-VIP
2 match virtual-address 172.22.101.69 tcp eq 993
class-map match-any CAS-ipsec-VIP
2 match virtual-address 172.22.101.69 udp eq 500
class-map match-any CAS-pop3-VIP
2 match virtual-address 172.22.101.69 tcp eq pop3
class-map match-any CAS-pop3s-VIP
2 match virtual-address 172.22.101.69 tcp eq 995
class-map match-any CAS-smtp-VIP
2 match virtual-address 172.22.101.69 tcp eq smtp
class-map match-all CAS_SERVERS
2 match source-address 172.22.101.64 255.255.255.192
class-map match-any HUB-VIP
2 match virtual-address 172.22.101.80 any
class-map match-all HUB_SERVERS
2 match source-address 172.22.101.64 255.255.255.192
class-map match-all OWA-OUTLOOKANYWHERE-SSL
2 match virtual-address 172.22.101.69 tcp eq https
class-map match-all OWA-SSL-CM
2 match virtual-address 172.22.101.69 tcp eq https
class-map match-all OWAREDIRECT
2 match virtual-address 172.22.101.69 tcp eq www
class-map type management match-any REMOTE-MGT
201 match protocol snmp any
202 match protocol http any
203 match protocol https any
204 match protocol icmp any
205 match protocol ssh any
206 match protocol telnet any
policy-map type management first-match REMOTE-MGT
class REMOTE-MGT
    permit
policy-map type loadbalance first-match CAS-Outlook-policy
class class-default
    sticky-serverfarm CAS-Outlook-ST
policy-map type loadbalance first-match CAS-http-policy
class class-default
    sticky-serverfarm CAS-http-ST
policy-map type loadbalance first-match CAS-https-policy
class class-default
    sticky-serverfarm CAS-https-ST
policy-map type loadbalance first-match CAS-imap-policy
class class-default
    sticky-serverfarm CAS-imap-ST
policy-map type loadbalance first-match CAS-imaps-policy
class class-default
    sticky-serverfarm CAS-imaps-ST
policy-map type loadbalance first-match CAS-ipsec-policy
class class-default
    serverfarm CAS-ipsec
policy-map type loadbalance first-match CAS-pop3-policy
class class-default
    sticky-serverfarm CAS-pop3-ST
policy-map type loadbalance first-match CAS-pop3s-policy
class class-default
    sticky-serverfarm CAS-pop3s-ST
policy-map type loadbalance first-match CAS-smtp-policy
class class-default
    serverfarm CAS-smtp
policy-map type loadbalance first-match HUB-policy
class class-default
    serverfarm HUB
policy-map type loadbalance first-match OWA-OUTLOOKANYWHERE
match OUTLOOK_ANYWHERE http header User-Agent header-value "MSRPC"
policy-map type loadbalance first-match OWA-SSL-PM
class class-default
    sticky-serverfarm OWA-STICKY
policy-map type loadbalance http first-match SSLREDIRECT
class class-default
    serverfarm SSLREDIRECT
policy-map multi-match CAS-Outlook-POLICY-MAP
class CAS-Outlook-VIP
    loadbalance vip inservice
    loadbalance policy CAS-Outlook-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match CAS-http-POLICY-MAP
class CAS-http-VIP
    loadbalance vip inservice
    loadbalance policy CAS-http-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match CAS-https-POLICY-MAP
class CAS-https-VIP
    loadbalance vip inservice
    loadbalance policy CAS-https-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match CAS-imap-POLICY-MAP
class CAS-imap-VIP
    loadbalance vip inservice
    loadbalance policy CAS-imap-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match CAS-imaps-POLICY-MAP
class CAS-imaps-VIP
    loadbalance vip inservice
    loadbalance policy CAS-imaps-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match CAS-ipsec-POLICY-MAP
class CAS-ipsec-VIP
    loadbalance vip inservice
    loadbalance policy CAS-ipsec-policy
    loadbalance vip icmp-reply
policy-map multi-match CAS-pop3-POLICY-MAP
class CAS-pop3-VIP
    loadbalance vip inservice
    loadbalance policy CAS-pop3-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match CAS-pop3s-POLICY-MAP
class CAS-pop3s-VIP
    loadbalance vip inservice
    loadbalance policy CAS-pop3s-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match CAS-smtp-POLICY-MAP
class CAS-smtp-VIP
    loadbalance vip inservice
    loadbalance policy CAS-smtp-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match EXCH-POLICY
class CAS-imap-VIP
    loadbalance vip inservice
    loadbalance policy CAS-imap-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
class CAS-imaps-VIP
    loadbalance vip inservice
    loadbalance policy CAS-imaps-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
class CAS-pop3-VIP
    loadbalance vip inservice
    loadbalance policy CAS-pop3-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
class CAS-pop3s-VIP
    loadbalance vip inservice
    loadbalance policy CAS-pop3s-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
class CAS-smtp-VIP
    loadbalance vip inservice
    loadbalance policy CAS-smtp-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
class CAS-http-VIP
    loadbalance vip inservice
    loadbalance policy CAS-http-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
class CAS-https-VIP
    loadbalance vip inservice
    loadbalance policy CAS-https-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
class CAS-OUTL-MAPI-VIP
    loadbalance vip inservice
    loadbalance policy CAS-Outlook-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
policy-map multi-match HUB-POLICY-MAP
class HUB-VIP
    loadbalance vip inservice
    loadbalance policy HUB-policy
    loadbalance vip icmp-reply
    connection advanced-options TCP_IDLE_30min
interface vlan 52
description #### vlan client side EXCHANGE ####
bridge-group 1
access-group input BPDU-Allow
access-group input EXCH-LB
service-policy input REMOTE-MGT
service-policy input HUB-POLICY-MAP
service-policy input EXCH-POLICY
no shutdown
interface vlan 54
description #### vlan client side ACE_EXCHANGE ####
bridge-group 1
access-group input BPDU-Allow
access-group input EXCH-LB
service-policy input REMOTE-MGT
service-policy input HUB-POLICY-MAP
service-policy input EXCH-POLICY
no shutdown
interface bvi 1
ip address 172.22.101.123 255.255.255.192
peer ip address 172.22.101.122 255.255.255.192
description EXCHANGE-Bridged-vlans
no shutdown
ip route 0.0.0.0 0.0.0.0 172.22.101.126
Best Regards

Thank you for your email. I am out of the office until March 25th, I will have limited access to my e-mail during this period.
In my absence, please feel free to contact Mr Akram Allani : [email protected]
Thank you for your understanding.
Best regards,
Youssef Boukari

Removing Exchange 2010 from AD

Hi
We have moved all our mail into Office 365 Exchange. We still need to run AD locally and will keep the DC's I need to shutdown the Exchange server, however if I do I need to understand how this may effect the Active Directory in the respect of setting
up users etc. I guess I am guessing that AD will complain that it can not find the Exchange Server when we add or remove users fro the AD?
Kind regards

Hi,
As far as I know, after upgrading to on-premise Exchange server and working well for a period of time in coexistence, we can remove the legacy Exchange server.
The Exchange users in AD still have mailbox since we move mailboxes to new server. In this case, it doesn’t have any difference through AD.
For more information about removing Exchange 2010, you can refer to the following article:
http://technet.microsoft.com/en-us/library/ee332361(v=exchg.141).aspx
However, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum:
http://social.technet.microsoft.com/Forums/msonline/en-us/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2010: Virtualized Exchange 2010 Datacenter Migration

We have a virtualized Exchange 2010 production implementation that needs to be relocated to a new datacenter. We will be leveraging SAN based replication and VMWare to cutover.
Some background info:
3 CAS/HUB servers
4 Node DAG across 2 sites (3 production Mailbox servers in the site to be migrated, 1 mailbox server will not move and be left in DR)
Since I need to shutdown 3 mailbox servers in a 4 node DAG, the cluster will go offline and the databases will dismount. I could run a datacenter switchover to preserve service, but I have the OK to take Exchange completely down.
Knowing that:
1) What are the best practices to shutdown and start up all the CAS servers and Mailbox servers (both in prod and DR)?
2) Should I suspend replication or dismount the databases in advance and prevent them from automatically mounting on boot up? Is the StartDagServerMaintenance script relevant in this situation?
Any suggestions on the proper way to go about this is much appreciated. Thanks for reading.

-->1) During the shutdown...would it make sense to turn off the 4th mailbox server in the DAG which is located in our DR site? I'm thinking that leaving the DR mailbox server powered off and powering it up last among the DAG members would prevent
any database copies from being activated in DR.
You already have a planned outage. I suggest you shut down the server in DR and start that after starting
all the 3.
2) To be able to mount a database in a 4 node DAG, I need to have the file share witness and two mailbox servers available first...correct?
Your fileshare witness should be online first otherwise none of your databases will get mounted.
If your DAG contains odd number of members filesharewitness will be ignored, (even number of DAG members will use filesharewitness)http://blog.credera.com/technology-insights/microsoft-solutions/when-do-dags-need-a-file-share-witness/
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

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

Exchange 2010 Slow Database Mount Time - Almost 1 Hour

Hello -
We have 2 DAG nodes on the production site running EX2010 SP3 RU6
In preparation for Windows patching I moved the active copy of DB2 active from EX2 to EX1, this took approx 20 seconds as per usual
Patching happened, and EX2 got a reboot
Later that evening I moved the active copy of DB2 back from EX1 to EX2
The move took 59 minutes and 32 seconds
During which time the DB status showed as mounting on EX2 and mailboxes where inaccessible [luckily this was out of hours]
The DB is 185 GB with 4 GB of logs at that time
There weren't ESE events related to playing transaction logs
There have been ESE 629 events in the log for a while showing... "While attempting to move to the next or previous node in a B-Tree, the database skipped over 25583 non-visible nodes in 73 pages... The database may benefit from widening the online maintenance
window..." but these warnings show up really quickly on our site even with a new database
We also have a problem that emerged approx 2 weeks ago where CPU runs at 100% for prolonged periods [mainly store.exe for 10/20/30 mins] and people get slow response times in Outlook, it's running on 4 x vCPU's and 18 GB RAM
Could the really slow mount time be related to DB corruption?
Thanks

Thanks for the feedback
This is not related to a dirty shutdown
According to Get-MailboxDatabaseCopyStatus etc all DB copies are healthy
I tested the DB activation again last night
Mailbox Database 2 is normally active on EX2
So we made the copy on EX1 active [server is on the same network] and this took 3 secs
When it came to making the same DB active on EX2 again it took 1 hr 46 mins 34 seconds!
We ran the task from EMC and the GUI did not hang, all the while it kept counting the hours, minutes & seconds
During this time mailboxes were unavailable, and the DB status showed as Mounting in EMC
From the Event Log, when ESE event 326 is finally logged there are some timings…
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.031, [4] 0.000, [5] 0.000, [6] 0.094, [7] 0.000, [8] 6386.578,
[9] 0.016, [10] 0.000, [11] 0.000, [12] 0.047.
And step 8 [whatever that is] took 6386 seconds while everything else flew
Of the 2 other Mailbox DB’s… DB1 took 7 seconds to activate on EX2 and DB3 took 32 minutes 41 seconds
Any ideas what is going on?
Thanks
Log Name:      Application
Source:        MSExchangeRepl
Date:          12/08/2014 21:02:02
Event ID:      2090
Task Category: Action
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Database: Mailbox Database 2\EX2
Mailbox server:
EX2.company.com
A failover or switchover occurred. Database Mailbox Database 2\EX2 will be
mounted with no data loss.
Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          12/08/2014 21:02:05
Event ID:      9539
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
The Microsoft Exchange Information Store database "c21e43b5-feb8-4bde-a993-aca830cd71a3: /o=Company X/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=xxx.company.com/cn=Microsoft
Private MDB" was stopped.
Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          12/08/2014 21:02:05
Event ID:      1000
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Attempting to start the Information Store "Mailbox Database 2".
Log Name:      Application
Source:        ESE
Date:          12/08/2014 21:02:05
Event ID:      102
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2: The database engine (14.03.0162.0000) is starting a new instance (4).
Log Name:      Application
Source:        ESE
Date:          12/08/2014 21:02:06
Event ID:      105
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2: The database engine started a new instance (4). (Time=0 seconds)
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.109, [4] 0.079, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.219, [10] 0.000, [11] 0.000.
Log Name:      Application
Source:        ESE
Date:          12/08/2014 22:48:33
Event ID:      326
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2: The database engine attached a database (4, X:\Database\Mailbox Database 2\Mailbox Database 2.edb). (Time=6386 seconds)
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.031, [4] 0.000, [5] 0.000, [6] 0.094, [7] 0.000, [8] 6386.578, [9] 0.016, [10] 0.000, [11] 0.000, [12] 0.047.
Saved Cache: 1

Exchange 2010 Dirty Shutdown

Similar Messages

Maybe you are looking for