Good morning.  I am new to Exchange 2013, as we are in the midst of migrating from Lotus Domino.  I need to familiarize myself with and test recovery features of Exchange before we can continue with migrating users and I am at the stage where I am testing accidental mailbox deletion.  So, I go to the recipients and I delete one of the mailboxes (Test Email9).  I verify the mailbox and AD account have been deleted, which I expected.  So I go into the Exchange Shell to try to restore and the first thing it asks me to do is see if it is soft deleted or deleted.  I run the following command:

Get-MailboxDatabase | Get-MailboxStatistics | Where { $_.DisplayName -eq "<display name>" } | fl DisplayName,Database,DisconnectReason

Here is what I see:

The DiconnectReason is blank.  What does this mean, and how do I continue my restore process?

Thanks,
Brian

Thank You, Brian Nytch

I am getting the event id 1018 in the exchange 2013 crismon channel

please help to resolve this issue

thnks 

rajesh

Hello,

I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for"Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

Hi

(apology in advance if my English is not so great)

I really need some advice what will be the best course of action.

I have Virtual Windows Server 2008 R2 Enterprise running my Exchange 2010.

I want to setup a second Exchange that just replicates the Exchange data to my second Virtual Server to have a replacement if my first Server fails I want to be able to use my second Server with close to no data loss as possible.

so i have the following questions .

Will I need a second Exchange license to do this setup?

What will be the simplest method of actively replicating my exchange data?

Will the second exchange intervene with any of the current exchange functions?

What secondary backups will you recommend to backup my exchange ? 

Any other information or explanation on this matter will be appreciated.

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.

I have installed two Exchange 2013 SP1 servers on Windows Server 2008 R2 SP1 Enterprise, called mail01 & mail02, both have CAS & Mailbox roles installed, and configured DAG. There are four active mailbox database copies on mail01 server, and four passive copies on mail02.

I have read that I should backup the active database copies with Windows Backup, so I setup Windows Backup on mail01, and backup the volume D: where all database and log files are located with VSS Full Backup selected, the backup destination is a network shared folder on another server. I scheduled the backup running in every night.

Next day when I check the database status, I noticed that all databases were activitied on mail02. Then I check the event logs on mail01, and found that the server was crashed and automatically restarted at about 1 hour after the backup started.

The BugCheck event ID 1001 shows the error code: 0x000000f4 (0x0000000000000003, 0xfffffa8013a9c390, 0xfffffa8013a9c670, 0xfffff8000277f270).

In addition, there were some Exchange services stopped unexpectedly before the server crash, such as MSExchangeRepl, MSExchangeDelivery, and Cluster Service.

I also noticed that if I run the backup on mail01 when it holds only passive database copies, the backup will finish without any error, and the server will not crash.

I also tested the backup on mail02 when it holds all active database copies, mail02 crashed and restarted with the same blue screen error.

The hardware of two servers are not identical, one is IBM x3650, and the other is IBM x3250. The two servers are all running fine except for this one issue.

What may cause this issue, and what should I do to troubleshoot? Any help will be greatly appreciated.

-Steven

I have a two node (node1 & node2) exchange 2013 DAG with FSW quorum on a 'non' exchange server (server), all within the same site.  All databases are mounted on the first node which is working with database copies on the second node which is 'down'.

A few times I have experienced, one of the DAG node goes 'offline' in failover cluster manager, in the past it has resolved itself, or I have taken various steps to resolve it.  This time however it will not come online again and I cannot find any method to fix this.

Windows event errors include (repeatedly);

1564

1573

C:\Windows\system32>cluster node (from the 'working node')
Listing status for all available nodes:

Node           Node ID Status
-------------- ------- ---------------------
NODE1        1 Up
NODE2        2 Down

C:\Windows\system32>cluster node (from the not working node)
Listing status for all available nodes:

Node           Node ID Status
-------------- ------- ---------------------
NODE1        1 Down
NODE2        2 Joining

The above shows me two different results depending on which exchange node I run it from.. interesting...

My DC and exchange server's time are all in sync.
I can access the FWS, and confirm the share is present, and being updated by the working node. The share has the Trusted Subsystem full control permission on the share and ntfs security.
Internally we do not use a firewall, and can confirm there are not any firewall issues.
I do not have any Antivirus running, so nothing is being blocked or interfered with here.
I can ping all hosts involved from all machines (both nodes, fws, dc, dag dns name, everything).
I have restarted the failed node, and also the working node.

It was all fine until an unexpected host/VM failure and restart.

I figure I can remove all the database copies from the failed node, then evict it from the cluster, and start it again, but if I can just get it joined again properly I would much prefer that.

Andrew Huddleston |  Sydney, Australia

Hello.  I have 2 Exchange 2013 servers running in the data center.  A virtual appliance does the load balance.  A device does the spam filter and also holds the MX record.  A DAG is already implemented.  This configuration seems to be working well.  Now the company will like to add an additional exchange 2013 server in a remote site, connected to the data center via a Tunnel, and move the mailboxes of some users, physically close to the remote site.  At this moment, only the mailbox database of the remote site will be added to the DAG.

Since the tunnel will be used for email and replication traffic, between the data center and the remote site, adding the 3rd Exchange server and setting it up the same as the other 2, should basically take care of any email redirection for the user's mailboxes that will be move to that remote site database.  Am I right here?

More importatn, is there a way to make those users access the remote site directly, without going through the data center?  Maybe adding an additional MX record that will point to the remote site?

Replay Queue Length is too high is this normal?

Hello,

I have already pre-staged my CNO in active directory. I also have created my DAG in exchange 2013. When I try to add my mailbox servers to my DAG, I receive the following error. I also tried to install the Failover Clustering feature manually, but I received the same following error. Could you please assist me with this?

Pooriya Aghaalitari

Hi guys,

we have 3 major sites - North America, Europe and Asia.
All sites are interconnected with an 8Mbit/s MPLS line.
Also every site has a "normal" internet connection with 10-50Mbit/s.

Our goal is this:
- Have 2 Exchange 2013 servers with all roles in each site
- Have multiple DAGs, so each site will have one active and one passive DB for their local users mailboxes and each site
  should have 1 DB copy from a remote site in addition
- Users should be able to work when 1, or even both local Exchange Server go down

- Users should be able to use their Active Sync Device, OWA and Outlook Anywhere (which is used both internal/external) in case of a failover as described above within a downtime window of maybe 1 minute. We would like to keep our 3 external addresses like na.domain.com, eu.domain.com and as.domain.com as we can't utilize a geo-dns solution.

- External connections are currently configured like this: (na/eu/as).domain.com -> Sophos UTM Firewall -> NAT rule to the internal Exchange Server; What needs to be done to avoid connection issues in case a Sophos UTM goes down in one region?

Many thanks for your input and help!

Hi All,

I have a Hybrid org (office 365 , on premises exchange 2013)

The on premises Exchange 2013 server on which the hybrid wizard was run does not host mailbox data that needs to be recovered.

Can anyone confirm that in the event of a server level failure

 Setup /m:RecoverServer  will also recover the hybrid configuration ?

Thanks !

Dear All,

I have few questions regarding how to configure the Exchange 2013 DAG on hyper-v cluster

1) whether the Exchange DAG can be configured as fully HA on a hyper-v 2012 cluster or it should be removed from HA?

2) Does it required to create anti-affinity rule for the Exchange DAG servers?

regards,

sarma

Is it supported to take offline backups of a lagged database copy and restore it like 6 months later?

Thanks

Peter

Hi there, I'm trying to move the maibox from exchange 2007 to 2013 and i'm receiving this kind of error:

Error: Move for mailbox '/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=EXC' is stalled because DataMoveReplicationConstraint is not satisfied for the database 'Supervisors-DB' (agent MailboxDatabaseReplication). Failure Reason: Database 1541069d-2976-4f40-afb1-569ed323de0b does not satisfy constraint SecondCopy. There are no available healthy database copies.

I tried to to run this command

Set-MailboxDatabase <DB_Name>-DataMoveReplicationConstraint none 
and it works well, i didn't received that error again but when i run this command Get-MailboxDatabase | Get-MailboxDatabaseCopyStatus i found out that the Replay Queue length for the particular database where i did the migration becomes too high. i try to fix it using the below commands and it works well but whats the best solution or procedure to migrate users without having this errors? 
Suspend-MailboxDatabaseCopy Supervisors-DB\MAIL1
Update-MailboxDatabaseCopy Supervisors-DB\MAIL1 -DeleteExistingFiles
Resume-MailboxDatabaseCopy -Identity Supervisors-DB\MAIL1
*************************************************************************
[PS] C:\Windows\system32>Get-MailboxDatabase | Get-MailboxDatabaseCopyStatus

Name                              Status      CopyQueue   ReplayQueue   LastInspected    LogTime   ContentIndex
                                                       Length           Length           State
----                                          ------          --------- ----------- --------------------   ------------
CEOLevel-DB\MAIL1         Healthy         0                  1423        8/27/2014 9:02:04 AM   Healthy
CEOLevel-DB\MAIL2         Mounted       0                  0                                                Healthy
EXCSystem-DB\MAIL2      Mounted       0                 0                                                 Healthy
EXCSystem-DB\MAIL1      Healthy         0                 7474        8/27/2014 8:59:42 AM   Healthy
Business-DB\MAIL1          Healthy         0                1633        8/27/2014 9:04:12 AM   Healthy
Business-DB\MAIL2          Mounted       0                 0                                                 Healthy
Franchise-DB\MAIL2         Mounted       0                 0                                                  Healthy
Franchise-DB\MAIL1         Healthy         0                1412        8/27/2014 9:05:13 AM    Healthy
ICT-DB\MAIL1                 Healthy         0                4217        8/27/2014 9:07:11 AM    Healthy
ICT-DB\MAIL2                 Mounted       0                0                                                   Healthy
MGMTLevel-DB\MAIL1       Healthy        0                5           8/27/2014 9:05:36 AM       Healthy
MGMTLevel-DB\MAIL2       Mounted      0                0                                                    Healthy
Supervisors-DB\MAIL2     Mounted       0                0                                                  Healthy
Supervisors-DB\MAIL1     Healthy        0                239         8/27/2014 9:09:00 AM       Healthy
Users-DB\MAIL2              Mounted      0                 0                                                   Healthy
Users-DB\MAIL1              Healthy        0               15          8/27/2014 9:09:25 AM          Healthy

How to fix this issue and whats the possible reason why DatabaseAvailability Failed?

[PS] C:\Windows\system32>Test-ReplicationHealth

Server          Check                     Result    Error
------          -----                      ------     -----
MAIL2           ClusterService          Passed
MAIL2           ReplayService              Passed
MAIL2           ActiveManager              Passed
MAIL2           TasksRpcListener          Passed
MAIL2           TcpListener                Passed
MAIL2           ServerLocatorService      Passed
MAIL2           DagMembersUp              Passed
MAIL2           ClusterNetwork            Passed
MAIL2           QuorumGroup                Passed
MAIL2           FileShareQuorum            Passed
MAIL2           DatabaseRedundancy        Passed
MAIL2           DatabaseAvailability      *FAILED*   Failures:...

I have two exchange 2010 multirole  (CAS, HUB, Mailbox) servers which already implemented with DAG.

and I would like to deploy CAS HA in these servers.

but I've read some articles that WNBL does not support CAS array when exchange 2010 implemented with DAG. And I don't have enough budget to purchase hardware load balancer or new server.

done it has any method I can do the CAS HA or reduce the down time when my primary CAS Server down?

Thank you  

Hi,

I'm having issues with enabling SSL Health check for my CAS VMs, works fine when I select TCP however doesn't work when I change health check to SSL.  This relates to a previous issue I've raised (http://social.technet.microsoft.com/Forums/office/en-US/0b3e2573-99ed-49a0-9fbb-c46a629dcc50/exchange-2013-load-balancing-owaecp?forum=exchangesvravailabilityandisasterrecovery )

TCP is great but would much prefer to do an SSL check instead;

Tests servers using SSLv3 client hello messages. The server is considered valid only when the response contains server hello messages.

This url helps, http://blogs.vmware.com/vsphere/2012/11/load-balancing-using-vcloud-networking-and-security-5-1-edge.html

The only other issue is I have a redirect at root mail.domain.com => mail.domain.com/owa  Could that be the issue because of the re-direct!

Thanks ;)

Hi,

I have been having this issues for a while now, I have two physical exchange servers in a DAG, both on Exchange 2013 CU1. Randomly, every few days and various times, Server1 will fail all of it's databases over to Server2. I'll redistribute them, and again, say Server2 will fail all databases to Server1. In short, both servers at times have failed their databases over.

I started with this: http://technet.microsoft.com/en-us/library/dd351258(v=exchg.150).aspx which led me to setup monitoring of the Microsoft-Exchange-ManagedAvailability logs. I can tell you that replication tests work fine, and the health of all the databases are fine.

My monitoring turned up the following errors, in this example "EX0001" was the server that failed all of it's databases over to "EX0002".  It seems pretty clear to me, that Exchange Managed Availability, is finding an issue with EWS, attempting to restart the MSExchangeServicesApp pool and cannot due to "Throttling" so ti fails the DB's over, that's my  best guess...the problem is I dont know how to fix this...I've run through troubleshooting EWS Healthset, nothing really turns up... http://technet.microsoft.com/en-us/library/ms.exch.scom.ews.protocol(v=exchg.150).aspx