Errors seeding Exchange 2010 DAG

I just setup a DAG last night and attempted to add database copies this morning.  When I did this I got the following error:

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:11


2010_DB2
Failed

Error:
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 'EXCHANGE.domain.local'. Hresult: 0xfffffae7. Error: The database was either not found or was not replicated.. [Database: 2010_DB2, Server: EXCHANGE2.domain.local]

In the event log:

[Seed Manager] The seed request for database '2010_DB1' encountered an error during seeding. Error: Failed to open a log truncation context to source server 'CUNJ-EXCHANGE.cunj.local'. Hresult: 0xfffffae7. Error: The database was either not found or was not replicated

When I run get-mailboxdatabasecopystatus -identity 2010_db1 | fl here are the results:

RunspaceId                       : 1a886a6a-cb32-496d-80e6-a34a09d19cfc
Identity                         : 2010_DB1\EXCHANGE2
Name                             : 2010_DB1\EXCHANGE2
DatabaseName                     : 2010_DB1
Status                           : Suspended
MailboxServer                    : EXCHANGE2
ActiveDatabaseCopy               : exchange
ActivationSuspended              : True
ActionInitiator                  : Service
ErrorMessage                     :
ErrorEventId                     :
ExtendedErrorInfo                :
SuspendComment                   : The Microsoft Exchange Replication service has suspended database copy '2010_DB1'
                                   as part of the initial seeding operation.
SinglePageRestore                : 0
ContentIndexState                : Failed
ContentIndexErrorMessage         : Catalog is dismounted externally for database
                                   {485a0702-41c4-48e3-890f-3bc66ab2e3cb}.
CopyQueueLength                  : 101470
ReplayQueueLength                : 0
LatestAvailableLogTime           :
LastCopyNotificationedLogTime    :
LastCopiedLogTime                :
LastInspectedLogTime             :
LastReplayedLogTime              :
LastLogGenerated                 : 101470
LastLogCopyNotified              : 0
LastLogCopied                    : 0
LastLogInspected                 : 0
LastLogReplayed                  : 0
LogsReplayedSinceInstanceStart   : 0
LogsCopiedSinceInstanceStart     : 0
LatestFullBackupTime             :
LatestIncrementalBackupTime      :
LatestDifferentialBackupTime     :
LatestCopyBackupTime             :
SnapshotBackup                   :
SnapshotLatestFullBackup         :
SnapshotLatestIncrementalBackup  :
SnapshotLatestDifferentialBackup :
SnapshotLatestCopyBackup         :
LogReplayQueueIncreasing         : False
LogCopyQueueIncreasing           : False
OutstandingDumpsterRequests      : {}
OutgoingConnections              :
IncomingLogCopyingNetwork        :
SeedingNetwork                   :
ActiveCopy                       : False
IsValid                          : True
ObjectState                      : Unchanged

RunspaceId                       : 1a886a6a-cb32-496d-80e6-a34a09d19cfc
Identity                         : 2010_DB1\EXCHANGE
Name                             : 2010_DB1\EXCHANGE
DatabaseName                     : 2010_DB1
Status                           : Mounted
MailboxServer                    : EXCHANGE
ActiveDatabaseCopy               : exchange
ActivationSuspended              : False
ActionInitiator                  : Unknown
ErrorMessage                     :
ErrorEventId                     :
ExtendedErrorInfo                :
SuspendComment                   :
SinglePageRestore                : 0
ContentIndexState                : Healthy
ContentIndexErrorMessage         :
CopyQueueLength                  : 0
ReplayQueueLength                : 0
LatestAvailableLogTime           :
LastCopyNotificationedLogTime    :
LastCopiedLogTime                :
LastInspectedLogTime             :
LastReplayedLogTime              :
LastLogGenerated                 : 0
LastLogCopyNotified              : 0
LastLogCopied                    : 0
LastLogInspected                 : 0
LastLogReplayed                  : 0
LogsReplayedSinceInstanceStart   : 0
LogsCopiedSinceInstanceStart     : 0
LatestFullBackupTime             :
LatestIncrementalBackupTime      :
LatestDifferentialBackupTime     :
LatestCopyBackupTime             :
SnapshotBackup                   :
SnapshotLatestFullBackup         :
SnapshotLatestIncrementalBackup  :
SnapshotLatestDifferentialBackup :
SnapshotLatestCopyBackup         :
LogReplayQueueIncreasing         : False
LogCopyQueueIncreasing           : False
OutstandingDumpsterRequests      : {}
OutgoingConnections              :
IncomingLogCopyingNetwork        :
SeedingNetwork                   :
ActiveCopy                       : True
IsValid                          : True
ObjectState                      : Unchanged

If I attempt to resume the copy I get the following pop up:

The Microsoft Exchange Replication service has suspended database copy '2010_DB1' as part of the initial seeding operation.

I'm not certain why the seed attempt failed (it did the same on database 2) or if its actually seeding now and just needs some more time...would very much appreciate any assistance on this one.
LVL 1
First LastAsked:
Who is Participating?
 
First LastConnect With a Mentor Author Commented:
Wound up being backup software (Veeam) causing problems during the seed.  Stopping the backups allowed the full seed to recover using this commands:

Suspend-MailboxDatabaseCopy -Identity "2010_DB1\cunj-exchange2"

Update-MailboxDatabaseCopy -Identity "2010_DB1\cunj-exchange2" -DeleteExistingFiles

Sync resumes shortly after the seed is complete
0
 
imkotteesSenior Messaging EngineerCommented:
Hi,

if you are not able to resume the copy then try to update it.
http://exchangeserverpro.com/how-to-reseed-a-failed-mailbox-database-copy-in-exchange-server-2010
0
 
imkotteesSenior Messaging EngineerCommented:
status should be healthy to seed the copy successfully..
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
First LastAuthor Commented:
Ok, the resume seems to be running well.  I did it from powershell instead of the EMC this time, not sure if that makes a difference.  I'll report back here once the seed completes, thanks for the tip!
0
 
imkotteesSenior Messaging EngineerCommented:
glad to hear that.. good luck :)
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
If anytime some issues do suspend all DB copies and then Recycle Replication Services on both or affected nodes and Resume and check if still not Update

- Rancy
0
 
First LastAuthor Commented:
Found own answer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.