Hi There, I am currently working in a test environment with a copy of our 2 main Exchange server's, Primary DC, a new additional Exchange HT server and a Windows 7 client. My aim is to test the use of Database Availability Groups as a solution for our organisation in the case of losing an Exchange server. However I have hit a snag. All 3 Exchange servers have been upgraded to Exchange 2010 SP2 Rollup 1 and I've tested to ensure email's are working within the Windows 7 client. My problem is, I have created a DAG and added 2 of the 3 servers as members, but after a Database copy completes for a database that already exists, I find that although the Content Index State is "Healthy", the Copy Status is "Failed". I have checked the other member of the DAG and the file directories both for the mailbox and logs are created. I then performed an "Update-MailboxDatabaseCopy" with the "-CatalogOnly" parameter in order to reseed the copy. The Content Index State is still "Healthy" but the Copy Status has now changed to "Resynchronizing", however it has been like this for a while now and the only thing that seems to be changing is the "Copy Queue Length" which began at 5010 and has risen to 5012 now. Should this be reducing? I have tested creating a brand new mailbox database and the moving some existing databases to it. I've then created mailbox database copies for this new database, which were successfully and the status was healthy too. I was also able to mount this copy on the other Exchange server without any issues. It just seems to be a problem with the existing mailbox databases! Any thoughts or ideas would be greatfully received, as i'm on my 3rd test now and had this problem each time with ALL existing databases. Thanks

Hi, Can you provide some additional info: the copy queue length on which database does it occurare there any event logs createdopen the EMS and run the following cmdlet: get-databaseavailabilitygroup dagfqdn -status |fl Regards, JohanExchange-blog: www.johanveldhuis.nl

The number will go up, and then it will go down again. That is normal, because it is synchronising the data. If it continues to cause a problem, then creating a new database (within the DAG) and then moving the mailboxes is the only solution. I have had to do that more than once. Do you have an RPC CAS Array in place? If not then I suggest that you create one so that clients can be updated. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi Johan, The copy queue length is rising on the non-active copy of the database. I've looked through the event logs for Exchange with DAGs but there is nothing being listed. Here are the results of the cmdlet you asked me to run: RunspaceId : 557ab2c8-8e83-4ec4-85bf-184c5413a391 Name : DAG1 Servers : {exch001, exch002} WitnessServer : exch003.mydomain.org.uk WitnessDirectory : C:\DAGFileShareWitnesses\DAG1.mydomain.org.uk AlternateWitnessServer : AlternateWitnessDirectory : NetworkCompression : InterSubnetOnly NetworkEncryption : InterSubnetOnly DatacenterActivationMode : Off StoppedMailboxServers : {} StartedMailboxServers : {} DatabaseAvailabilityGroupIpv4Addresses : {} DatabaseAvailabilityGroupIpAddresses : {} AllowCrossSiteRpcClientAccess : False OperationalServers : {exch002, exch001} PrimaryActiveManager : exch002 ServersInMaintenance : {} ThirdPartyReplication : Disabled ReplicationPort : 64327 NetworkNames : {DAGNetwork01} WitnessShareInUse : Primary AdminDisplayName : ExchangeVersion : 0.10 (14.0.100.0) DistinguishedName : CN=DAG1,CN=Database Availability Groups,CN=Exchange Administrative Group (FYDI BOHF23SPDLT),CN=Administrative Groups,CN=mydomain,CN=Microsoft Exchange,CN=Servic es,CN=Configuration,DC=mydomain,DC=org,DC=uk Identity : DAG1 Guid : 7dba3e93-6d55-4160-b386-6580ff088170 ObjectCategory : mydomain.org.uk/Configuration/Schema/ms-Exch-MDB-Availability-Group ObjectClass : {top, msExchMDBAvailabilityGroup} WhenChanged : 09/03/2012 10:43:07 WhenCreated : 09/03/2012 10:43:07 WhenChangedUTC : 09/03/2012 10:43:07 WhenCreatedUTC : 09/03/2012 10:43:07 OrganizationId : OriginatingServer : AD0001.mydomain.org.uk IsValid : True Thanks, Scott

Scott, Well what I am missing is an DatabaseAvailabilityGroupIpv4Addresses address. Did you configure an IP-address fot the DAG? Regards, JohanExchange-blog: www.johanveldhuis.nl

No I didn't configure it with an IP address, I left it blank as it provides it with a DHCP address in this case doesn't it? Thanks, Scott

Scott, That's true but I recommend to configure a static IP. Regards, JohanExchange-blog: www.johanveldhuis.nl

OK, I shall change it to a static address from the EMC. I can ping the dag from all Exchange servers, so there doesn't appear to be any issues with communication with the DAG. Scott

Scott, OK if that doesn't fix the only solution left is to move the users to a new database in the DAG as recommend by Simon. Regards, JohanExchange-blog: www.johanveldhuis.nl

The number will go up, and then it will go down again. That is normal, because it is synchronising the data. If it continues to cause a problem, then creating a new database (within the DAG) and then moving the mailboxes is the only solution. I have had to do that more than once. Do you have an RPC CAS Array in place? If not then I suggest that you create one so that clients can be updated. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi Scott, Any update?Xiu Zhang TechNet Community Support

Scott, OK if that doesn't fix the only solution left is to move the users to a new database in the DAG as recommend by Simon. Regards, Johan Exchange-blog: www.johanveldhuis.nl I have got back in the office today after setting the IP address for the DAG Network as static on Friday afternoon, and I've tried updating a database copy which was in a "failed and suspended" state, but it has failed again. Looks like I'll need to create new DB's and move all the mailboxes over to them, before adding them to the DAG. Do you have any idea of the reason why these existing database's will not copy correctly?

No unfortunatly I don't have an answer on that question. Maybe someone from MS can answer that question Regards, JohanExchange-blog: www.johanveldhuis.nl

During my testing I have noticed some inconsistencies with my existing mailbox databases and these are: When creating a mailbox database copy, some fail and some complete successfully according to the EMCThe status of the copies either appears as "Failed" or "Failed and Suspended"Some of these copies become "Healthy" following a CatalogOnly reseed from the EMS, whereas other remain in a "Failed" or "Failed and Suspended" state Due to these inconsistencies I will probably have to revert to the solution of creating new Mailbox databases and moving the data to them from the existing databases, and then adding them to the DAG. Thanks for all of your help on this one though, Scott