Exchange 2013 unable to seed database when adding copy

When running the command Add-MailboxDatabaseCopy, the following error is received;

[Seed Manager] The seed request for database 'Database' encountered an error during seeding. Error: Failed to open a log truncation context to source server 'server2'. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).

Open in new window

The database copy status is then set to "FailedAndSuspended".

When trying to force the reseed, I get the following error;

The Microsoft Exchange Replication service was unable to perform an incremental reseed of database copy 'Database\SERVER1' due to a network error. The database copy status will be set to Disconnected. Error An error occurred while processing a request on server 'SERVER2'. Error: Database 'fd81f7fc-a37a-4438-95f0-d566c07c334a' was not active on source server 'SERVER2'.

Open in new window

Any help would be appreciated.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
Are the servers in the same site?
Have they been backed up recently?
Size of the databases?

FunktopusAuthor Commented:
Hi Simon, yes, same site.

Yes, the database is backed up nightly, and the actual server weekly.

SIze is approx 120GB.

Simon Butler (Sembee)ConsultantCommented:
"Yes, the database is backed up nightly, and the actual server weekly."

What do you mean by the server weekly?
You shouldn't be doing any kind of snapshots etc on the server.
Any kind of imaging is completely useless to you, because in the event of a failure of the server you would follow the guidance on recovery - which is a fresh build of Windows and then Exchange installed with the recovery switches. ANy image backup of an Exchange server is useless the second the backup is complete.

Does the Exchange database report that it is backed up correctly?

Personally I would suspect the database has a problem. In that scenario I would suggest a new database is created, added to the DAG while empty. Once confirmed working, move the mailboxes in to the new database. Once complete, drop the original.

FunktopusAuthor Commented:
Thanks Simon, yes you are correct, its using a VM backup weekly.

I can't find any guidance on VM backups not being supported, are you able to point me in the right direction?

Yes, the database reports that its backed up correctly each night.

Regarding the suspect DB, I was on the same line of thought.

Simon Butler (Sembee)ConsultantCommented:
Snapshots are covered in the VM guidelines.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.