Exchange Add Mailbox Database Copy fails.

I'm recovering from a server failure on my Exchange System and while I've been able to rebuild the server an integrate it into the Exchange System and the DAG. When I attempt to replicate any of the databases, it fails. It creates a directory on the new Exchange server in the right place, but the database isn't there and I get the following error:--------------------------------------------Summary: 1 item(s). 0 succeeded, 1 failed.Elapsed time: 00:00:23AM.ScottFailedError:A source-side operation failed. Error An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'FRANKLIN2.domain.com'. Hresult: 0x80070057. Error: An unexpected error occurred. Error (0x80070057).. [Database: AM.Scott, Server: FRANKLIN0C.domain.com]Failed to open a log truncation context to source server...
This topic first appeared in the Spiceworks Community

Hi Belinda,
Thanks for the response. I am holding off on using Eseutil or Isinteg for now as I may have finally found the problem.
I was reading another forum yesterday where someone else was getting many of the same errors and everyone responding was telling them the same thing, to check the database as it seemed to have some corruption. Then there was one post at the very bottom where
a guy said he had the same problems but found it was an incompatibility with Exchange 2010 and the Windows Serve Backup Command-line Tools for Server 2008. He removed the Command-line Tools and the problem was resolved. Since we do not use the Windows Serve
Backup, we use Backup Exec, I decided to give it a try. I removed the Command-line Tools and reseeded the database. It has been running since about 12:30 PM yesterday with no errors at all. I'm not claiming victory yet as I stated in my original post that
it has at times run for up to 5 days before failing. I will monitor it for the next week and  keep my fingers crossed that the issue has been resolved. I will report back if it fails before then and if not I will consider the issue resolved and post to
the thread. 
If this does in fact turn out to be the solution it is just another instance of Microsoft dropping the ball as I was only able to find this mentioned once on their website in a thread about Exchange logs not truncating. I would find it rather annoying their
Server backup software is incompatible with their Mail program and even more annoying that they have not acknowledged the issue. I have been fighting this for months and only found the solution by a stroke of luck. I will update accordingly.
Many thanks,
Gerard

Similar Messages

  • Fail to add mailbox database copy

    Hello,
    When I am trying to add a mailbox database copy in DAG, I receive the following error:
    error
    The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to notify source server 'mbx1.domain.local' about the local truncation point. Hresult: 0xc8000713. Error: Unable to find the file.
    when viewing details of the passiv, error message shows:
    The database file wasn't found after log replay. The copy will be set to failed
    Please help. Thanks

    Hi,
    Please use the Get-MailboxDatabaseCopyStatus cmdlet to check the health and status of mailbox database copy.
    Please dismount and remount the active mailbox database, remove the failed passive database copy and then add it again to check the result.
    Besides, please check the application log to see if there is any related events.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Cannot add mailbox database copy to DR site - .edb file not getting created

    I have a DR site setup that I want copies of 4 of my mailbox databases.  3 of the mailbox databases copied over successfully but the last and largest one which is really not that large 69Gbs keeps failing when i Update the database copy.  Seems
    to not be creating the .edb file.  Is there another way to get the .edb file over to the server, possibly manually copying it then doing and update database copy?  I have my backups turned off on all the servers that have the mailbox role on it now
    thinking that was causing some issues with the database copy?  Any suggestions is appreciated, thanks.
    Michael Duhon

    Yes manually copy the edb file and paste them in the DR server . Then try to update with for the incremental of database copy. Verify the database is clean shutdown that you are moving to the DR site.
    What error message it throws when you performing update the database copy
    Exchange Queries

  • Microsoft Exchange Server/Exchange 2010/Mailbox/Database Copy Mounted

    Good Morning everyone!!!
    I Have SCOM 2007 R2 CU5 Envoirnment and i am monitoring Microsoft Exchange 2010 SP1 Messaging infrastracture,
    I have Microsoft Exchange  2010 SP1 Monitoring MP, MP version is 14.2.71.0.
    Case:-
    When exchange is having issue with DAG, SCOM monitoring rule:- KHI: The database copy is not mounted on the local server. Another database copy may be mounted on a different server.
    is generating the alert but alert Description is only "    _ef4a8515_1cc0_48a9_aa12_92ba059a6eae_ " and rest of the things are blank
    and because of this ticketing team is unable to process these alerts,
    Impact:-
    Whenever DAG is unavailable, messaging team is not getting notification and because of this. Exchange services are failing down,
    Does anyone having this kind of issues on their exchange environment?
    I am looking solution for this issue, please let me know if anyone is aware about this.
    Regards, Ganesh M <!> Microsoft MPN - Member =========================================================== 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.

    Does anyone has updated information regarding Exchange 2010 DAG monitoring fix, <o:p></o:p>
    As i see there was exchange MP release on 31st Aug 2012
    ID
    Name
    Targets
    _ef4a8515_1cc0_48a9_aa12_92ba059a6eae_
    KHI: The   database copy is not mounted on the local server. Another database copy may   be mounted on a different server.
    Root   Management Server
    _EF51D339_22C5_49b3_8B6B_25002BE31D4A_
    KHI: Retry   Mailbox Delivery Queue Length - sustained for 90 minutes - Red(>1) - Hub   Transport.
    Root   Management Server
    _93558cf0_e063_45b1_b57a_0d4b53e0d615_
    KHI: The   Microsoft Exchange Information Store service (MSExchangeIS) isn't running.
    Root   Management Server
    My monitoring is affected for these rules which i mentioned below, here alerts
    information is shown as rule ID instead of Rule name. and we don’t get alert description
    for above rules when the generate alerts.<o:p></o:p>
    Response would be appreciated <o:p></o:p>
    Regards, Ganesh M <!> Microsoft MPN - Member =========================================================== 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.

  • Failed to Manually Seed the Mailbox Database Copy on Exchange 2013

    Hi,
    I tried to manually seed the mailbox database copy via exchange shell by run this command
    Update-MailboxDatabaseCopy –Identity “DB_name\Server” -sourceserver "Name Server" –DeleteExistingFiles.
    However, i got the error message whereas shown below.
    A parameter cannot be found that matches parameter name 'identity'.
        + CategoryInfo          : InvalidArgument: (:) [Update-MailboxDatabaseCopy], ParameterBindingException
        + FullyQualifiedErrorId : NamedParameterNotFound,Update-MailboxDatabaseCopy
        + PSComputerName        : XXXX.abc.XXX
    Any ideas?

    I hope database is in suspended state and not in failed state.
    Make sure EMS is running As Administrator.
    http://technet.microsoft.com/en-us/library/dd335201(v=exchg.150).aspx
    Cheers,
    Gulab Prasad,
    Technology Consultant
    Blog:
    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.

  • Moving the mailbox database copy from one exchange server to another exchange server 2010 DAG

    Hello Team
    is it possible to the move the passive copy of database and logs from one server to another exchange server in the same DAG with out removing  and deleting the mailbox database copies in exchange 2010
    normaly procedure is
    Remove the mailbox database copies and manually delete the .edb files and logs from the physical location and re-add the mailbox database copy to the new server in the DAG.
    is that any way to achieve to move the passive database copy to another exchange 2010 server in the same DAG ?

    From your note, you appear to have a two-member DAG (with a server hosting your active database, and a second hosting the passive copy), and you want to move your passive database copy from the current passive server to another.  Your note
    about what "the normal procedure is" isn't 100% correct - there are many ways to handle this task, and all can be considered "normal". Why not just add the third server to the DAG and
    add a database copy on that third server?  Once it is fully seeded, you can remove the current passive copy.  This way, you never lose your redundancy.
    Yes i can add the third and fourth  serve in DAG , but i cannot add the mailbox database copies to the 3rd and 4th mailbox server in DAG as am using RTM version of exchange 2010 which is allowing to have only 5 database inclding mailbox datbase copies
    and also currently my lab setup is  two member dag (with a server hosting your active database,
    and a second hosting the passive copy) in the same site named SITE A
    and recently i have created new SITE B and included the 3rd and 4th DAG members in the same DAG
    i want the  mailbox database copies from the mailbox server  database  in SITE A  to
    Mailbox server database in  SITE B as  passive copy
    That is why i want to move the mailbox database without deleting / removing it manually
    Hope you understand my situation!

  • Remove mailbox database copy from DAG

    Hi There,
    We would like to remove the mailbox database copy from our exchange server as we are lack of the space on our fixed vhd and we hope to be able to free about 100GB from the passive database copies as we have deployed DAG. is there any guidelines or procedures
    to safely remove the database copies? currently, we have 4 mailbox servers, HQMB01, HQMB02, SSMB01, and SSMB02. HQMB01 and HQMB02 is already part of DAG members by itself. however, on ssmb01 and ssmb02, we also add in HQMB01 and HQMB02 as the DAG member,
    thus they can fail over to HQMB01 or HQMB02 if their server have issue. in this situation, SSMB01 and SSMB02 passive copies is also inside our HQMB01 and HQMB02. As the our HQMB01 and HQMB02 is lack of the disk space and we would like to remove SSMB01
    and SSMB02 from the DAG, thus we could remove the passive database copies. The following is the picture of the activation preference for all servers. what is the procedures and the guidelines to remove mailbox database copy and also remove the server from
    the DAG members? we are quite confuse and worry that after we are removing wrongly and cause the active database to lost as we understand that there is replication happening between them. as we have 4 mailbox servers from which server we should perform
    the task? Wish to get some advises from the exchange guru from this forum. we are on exchange server 2010 sp1 and windows server 2008 R2.Thanks so much.
    Name                 : HQDB01
    Servers              : {HQMB01, HQMB02}
    ActivationPreference : {[HQMB01, 1], [HQMB02, 2]}
    ReplayLagTimes       : {[HQMB01, 00:00:00], [HQMB02, 00:00:00]}
    TruncationLagTimes   : {[HQMB01, 00:00:00], [HQMB02, 00:00:00]}
    Name                 : HQDB02
    Servers              : {HQMB02, HQMB01}
    ActivationPreference : {[HQMB02, 1], [HQMB01, 2]}
    ReplayLagTimes       : {[HQMB02, 00:00:00], [HQMB01, 00:00:00]}
    TruncationLagTimes   : {[HQMB02, 00:00:00], [HQMB01, 00:00:00]}
    Name                 : SSDB01
    Servers              : {SSMB01, SSMB02, HQMB01, HQMB02}
    ActivationPreference : {[SSMB01, 1], [SSMB02, 2], [HQMB01, 3], [HQMB02, 4]}
    ReplayLagTimes       : {[SSMB01, 00:00:00], [SSMB02, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
    TruncationLagTimes   : {[SSMB01, 00:00:00], [SSMB02, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
    Name                 : SSDB02
    Servers              : {SSMB02, SSMB01, HQMB01, HQMB02}
    ActivationPreference : {[SSMB02, 1], [SSMB01, 2], [HQMB01, 3], [HQMB02, 4]}
    ReplayLagTimes       : {[SSMB02, 00:00:00], [SSMB01, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
    TruncationLagTimes   : {[SSMB02, 00:00:00], [SSMB01, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}

    Hi Exchange Guru,
    thanks so much for the prompt response..i have few queries to ask following your guidelines above:
    1. from the show result above, I am still confuse which server that I should go to remove as this is involving 4 database copies. from what I understand from the truncation or replay lag times of SSDB01 and SSDB02, I can see that HQMB01 and HQMB02 are on
    the third and fourth preference, which means that SSDB01 and SSDB02 will be able to failover to each of them when there is a failure and it cause the passive copies of both of SSDB01 and SSDB02 to be stored in the HQMB01 and HQMB02. what my purpose
    is to remove both SSDB01 and SSDB02 passive copies in HQMB01 and HQMB02. in this case, should I login to SSDB01 or SSDB02 mailbox servers to perform the removal with your guidelines above?
    2. is the command as below:
    Remove-MailboxDatabaseCopy -Identity SSDB01\HQMB01 -Confirm:$False
    Remove-MailboxDatabaseCopy -Identity SSDB01HQMB02 -Confirm:$False
    Remove-MailboxDatabaseCopy -Identity SSDB02\HQMB01 -Confirm:$False
    Remove-MailboxDatabaseCopy -Identity SSDB02\HQMB02 -Confirm:$False 
    will this cause the risk either of my HQDB01, HQDB02, SSDB01, and SSDB02 active copies accidentally  being removed? I am sorry that I am a bit naggy and always want a confirmation as this is very critical and I must be super careful.
    3. If after the removal successful, when is the best time to go to the drive where the passive copies stored and remove them so I can clear some space on  my disk? and is it just as simple by going to the drive and do a folder file deletion manually?
    because I just worry when I delete the file and the server is still replicating between each other, which will cause even corruption to the active database.
    4. From point 3, you mention about when the server is empty. what do you mean by that? do you mean that when the passive copies are no more there? and what command that I used to check?
    5. From point 4, is removing the server from DAG the last step to be performed? yes, I want to remove them from DAG, thus will left only HQMB01 and HQMB02 as one DAG and SSMB01 and SSMB02 as one DAG.
    Thank so so much for your patient and attention.
    Regards,
    Henry

  • Seed mailbox database copy through replication network (DAG members on different subnets in different sites)

    Good afternoon
    I currently operate a two node DAG in our primary site supporting one mailbox database. I plan to introduce a third DAG node in our datacenter which is in a different Active Directory site. Both current DAG members replicate over a dedicated replication
    network to keep the traffic separate from the MAPI traffic. The third DAG member will also have a dedicated replication network adapter (of course, on a different subnet). Ideally I would like to seed the database at a time of my choosing, rather than at the
    moment I add the mailbox database copy (I know how to achieve this), but I would like to specify which network the data replicates over.
    According to the following (see below link) under the 'Seeding and Networks' section as my two DAG members will be on different subnets in different sites Exchange will make the decision to use the MAPI network adapters of the target and source server.
    'If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.'
    http://technet.microsoft.com/en-us/library/dd335158%28v=exchg.150%29.aspx
    Am I able to force Exchange to use the replication network adapters of both source and target server when I initiate the seeding process? I have a 200+ GB mailbox database that will need to replicate over a 100Mbps internet connection to our secondary
    site and I would like to keep that traffic to the replication network I have configured.
    Any insight would be helpful.

    Hi,
    If you want to specify the networks for seeding, you can use the
    Network parameter when running the
    Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use.
     If you don't use the Network parameter, then the system uses the following default behavior for selecting a network to use for the seeding operation:
    If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
    If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
    If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
    So please use the Update-MailboxDatabaseCopy cmdlet with
    NetWork parameter to specify which DAG network should be used for seeding.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • I can't either mount for remove Exchange 2010 mailbox database file

    Yesterday I proceeded with moving Exchange 2010 database file to a newly installed hard drive because my "C" drive was running out of space. After dismouting both the mailbox database and the public folder database, I used EMC's  "move
    data path" wizard to move both the mailbox database and public folder database to "mailbox" folder in "D" drive.  The move was successful without an error, but when I opened "mailbox" folder in "D" drive, both
    the database file and public folder database files weren't there.  All the other files were moved, but the mailbox database file was gone.  
    Luckily I manually copied entire mailbox folder to another folder in "D" drive.  So I manually copied mailbox database file (it is about 20GB) to "d:\mailbox".  When I try to mount, I received the following error message.
    Microsoft Exchange Error
    Failed to mount database 'Mailbox Database 1658107303'.
    Mailbox Database 1658107303
    Failed
    Error:
    Couldn't mount the database that you specified. Specified database: Mailbox Database 1658107303; Error code: An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC
    error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3..
    An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3.
    Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3
    When I try to move the database path back to the original path, I received the following error message.
    Mailbox Database 1658107303
    Failed
    Error:
    There are no source files under the path:d:\emailbox\Mailbox Database 1658107303. Use the command Move-DatabasePath -ConfigurationOnly in the Exchange Management Shell to set the new path in Active Directory only.
    Exchange Management Shell command attempted:
    move-DatabasePath -Identity 'Mailbox Database 1658107303' -EdbFilePath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox database 1658107303\Mailbox Database 1658107303.edb' -LogFolderPath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox
    database 1658107303'
    EMC would not even delete the database file.
    I need help.  I need to mount my mailbox database file.  Please help.

    If the database was fine pre move I doubt it needs a repair, however if you want to validate do an eseutil /mh ReplaceWithYourDatabaseName.edb and post the results here
    did you move the logs as well or are they still in same location
    I have seen this before if everything is where its supposed to bea restart fixed it so I would recommend that you put the DB back into the  NEW D path and do a restart to see if that resolves the issue
    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

  • Exchange User Mailbox Database Group Lookup Reconciliation-parameters

    Hi everyone,
    I want to execute Exchange User Mailbox Database Group Lookup Reconciliation.
    Parameters :
    Code Key Attribute : __NAME__ (default)
    Decode Attribute : __NAME__ (default)
    IT Resource Name : Exchange IT Resource
    Lookup Name : Lookup.Exchange.MailboxDatabase (default)
    Object Type : __MAILBOXDATABASE__ (default)
    Resource Object Name : Exchange User
    Is there any incorrect parameter?
    Thanks.
    Best Regards.

    Everything looks correct, all parameters have been provided correctly. Check values in "Exchange IT Resource" before executing scheduler.

  • Mailbox Database Copy Status Failed

    We have 2 Exchange 2010 servers.  We run a DAG.  Recently I have noticed that database copy DB2 which is located on Exch-1 is showing "Failed".  Database copy DB1 which is located on Exch-2 is showing Healthy.  I searched online
    for information regarding the issue with the failed database copy.  I found information that led me to run these commands.
    Suspend-MailboxDatabaseCopy -Identity “Mailbox Database XXXXX\Server Name”
    Update-MailboxDatabaseCopy -Identity “Mailbox Database XXXXX\Server Name” -DeleteExistingFiles
    It went thru the seeding process and completed but the database copy still shows "Failed".  Copy Q Length is 19.  I have refreshed the console.  What else do I need to do to correct this?  I did recently shut down Exch-2 server
    for maintenance.  thanks

    Hi,
    It's glade to hear the good news. Thanks for your updating.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Windows 2008 R2 - Exchange 2010 Mailbox Role Install Failed

    Hi,
    I have been trying to install Exchange 2010 on my Win Server 2008 R2.
    I have an error when  i try to install mailbox role :
    The following error was generated when "$error.Clear(); $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
    $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1; if( $dismbx -ne $null) { $srvname = $dismbx.ServerName; if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" ) { Write-ExchangeSetupLog -info "Setup
    DiscoverySearchMailbox Permission."; $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; if( $mountedMdb -eq $null ) { Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
    mount-database $dismbx.Database; } $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; if( $mountedMdb -ne $null ) { $dmRoleGroupName = "Discovery Management"; $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupName
    -DomainController $RoleDomainController -ErrorAction:SilentlyContinue; if( $dmRoleGroup -ne $null ) { Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
    } } } }" was run: "Couldn't mount the database that you specified. Specified database: Mailbox Database 1527275860; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred
    during discovery of the database availability group topology. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005,
    ec=-1011)
     [Database: Mailbox Database 1527275860, Server: serveur.domain.fr].".
    Couldn't mount the database that you specified. Specified database: Mailbox Database 1527275860; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database
    availability group topology. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
     [Database: Mailbox Database 1527275860, Server: serveur.domain.fr].
    An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database availability group topology. Error: Database action failed with transient error. Error: A transient error
    occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
     [Database: Mailbox Database 1527275860, Server: serveur.domain.fr]
    An Active Manager operation failed with a transient error. Please retry the operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
     [Server: serveur.domain.fr]
    MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
    /prepareschema  ->OK
    /preparead  ->OK
    /preparedomain  -> OK
    The Account rights seems good : Domain Admins - Enterprise Admins - Schema Admins
    I tried to use another installation media but no change.
    I tried this : http://support.microsoft.com/kb/978776/fr
    but at step 2 i have the sameerror again.
    Can you help me Please  :-)
    tkx

    Hi,
    Thanks for your sharing. It's great to hear the good news.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Adding Database copy failed

    Dear Exchange 2013 users,
    We have exchange environment of version in 2013.
    We have main site and DR site. Adding database copy has failed in DR site.
    The following getting.
    error
    EMPDB3
    The seeding operation failed. Error: An error occurred while running prerequisite checks. Error: The specified database isn't configured for replication and therefore cannot be used to perform seed operations. [Database: EMPDB3, Server: SRVINFDRMBX01.x.x.x]
    Kindly help how can resolve this issue.
    Ashraf

    Hi Ashraf,
    Thank you for your question.
    This issue may occur because the Add-MailboxDatabaseCopy cmdlet utilizes different DC’s (Domain Controllers) in different parts of the task and the DC’s may inconsistent due to site replication delay.
    We could refer to Hinte's advice to force AD replication. We could refer to the following link:
    http://support.microsoft.com/en-us/kb/2464273
    Notice: although this is link about Exchange 2010, it is adapt for Exchange 2013.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • Powershell command to migrate Exchange 2007 mailbox databases with a legacy name, & import them into a new 2007 instance, with a new name.

    Hi All. I am currently at the later stage of provisioning a new CCR Exchange 2007 migration (to
    virtualise old Exchange 2007 hardware) for 5,000 users & have a quick question.
    I have created around 15 newly named storage groups, & have named 1 new DB per group, with the same name (let's say New-DB-1), residing within them.  The problem I have, is the old legacy DB's have different names (let's say Old-DB-1) & I need
    to import them into the new storage groups, to match the new names. So far I can import/export between old & new OK if both old & new DB names\folders etc. names marry up perfectly, but are unable to if there not the same. Does anyone have any thoughts
    on how best to tackle this, as this is one of the final hurdles stopping the migration? Many Thanks, John 

    Hi All
    Many Thanks for the feedback.
    The terminology 'migrate' was used based around the fact I will be decommissioning the old 2007 physical environment. This is after moving all DB's over to the new newly created Virtual environment that will host all roles.
    The solution I ended up using yesterday, was the following:
    1) Dismounted the relevant named DB (NEWDB) in the new environment.
    2) I then ticked the 'This database can be overwritten by a restore option' box.
    3) Copied over the old named DB (OLDDB) to the same location, & overwrote using the new name (NEWDB).
    4) Re-mounted the (NEWDB).
    5) Ran the following 2 PowerShell commands:
     Get-mailbox –database OLDDB | move-mailbox –targetdatabase NEWDB -configurationonly:$true
     Get-MailboxDatabase NEWDB | ResetSearchIndex.ps1 -force
    6) Checked to make sure the clients were working ok, in the now the new (NEWDB) environment.
    Rich: Many thanks for your PS script, which I will test with future DB moves & provide feedback
    J
    John.

  • Exchange 2010 - mailbox database in a DAG different sizes

    HI
    After a recent health check on our Exchange 2010 (SP3) environment I noticed that our mailboxes databases in the DAG, which consists of 4 Exchange Servers, had used
     different capacity.
    Could someone why the mounted database and the 3 healthy copies are not the same size?
    Many thanks

    Hi,
    Based on your description, the active database and passive database have different size.
    Apart from Willard Martin's suggestions, please update database copy using the following command and then check result.
    Update-MailboxDatabaseCopy -Identity DB -SourceServer activeserver
    Please make sure the passive databae copy has healthy state.
    Best regards,
    Belinda Ma
    TechNet Community Support

Maybe you are looking for