Unable to add database copy in Exchange 2016

Hello Experts
I have single AD site with 3 domain controllers.
I have 2 Exchange 2016 Servers with CU6 update.
I have just created new DAG and added both servers to the DAG. I am trying to add database copy to second member but receiving the following error

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.

Open in new window


Appreciating any help.
LVL 3
cciedreamerAsked:
Who is Participating?

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

x
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.

Hemil AquinoNetwork EngineerCommented:
Are you using the console or the ECP?
Can you check if the database was added even though you have that error? If it so try updating the databse.

Try using the ECP, I had experience where using the console gets buggy configuring dag.
0
cciedreamerAuthor Commented:
I have tried using both, Powershell and ECP but facing same issue
The database is not added but some logs gets added and folder path.
0
Hemil AquinoNetwork EngineerCommented:
Do me a favor do it on the ECP and send me an screenshot if you could.
I seen this behavior before, but I wanna make sure is not different.
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

cciedreamerAuthor Commented:
Here is the screenshot
Now I receive the new error.


The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server 'EXCHANGESER2016.DOMAIN.COM'. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).
 [Database: DB02-2016, Server: EXCHANGE2016-02.DOMAIN.COM]

Open in new window

0
Hemil AquinoNetwork EngineerCommented:
OK, that's the same error I got long ago.
And I have a log of it.

Try this.

1-Login to the source server
2-Remove the 2nd copy of the database
3-Dismount the database
4-Verify database is clean shutdown by running the command eseutil /mh driveletter:\database\database.edb
5-Now rename the logs file folder to logs old.
6-Mount the database

7-Login to the destination server where we are creating the 2nd copy
8-Now rename the logs and database file folder by adding old prefix.
9-Add the 2nd database copy.

Let me know how it goes.
0

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
cciedreamerAuthor Commented:
Thanks Hemil,
I don't have logs and database file folder on destination so no need to add any old prefix

Renaming the logs file folder on source server will have any impact ?
0
Hemil AquinoNetwork EngineerCommented:
There's not impact since they're only logs.
Now careful with the files called CHK known as checkpoint. Dont rename those.
0
Hemil AquinoNetwork EngineerCommented:
By the way, as a good practice and recommendation make sure you have a backup ALWAYS before to perform any action.
You dont want any surprise.
0
cciedreamerAuthor Commented:
Thanks Hemil
My logs are saved in this folder so I would rename

F:\db01\

Rename to F:\db01.old

Correct?
0
Hemil AquinoNetwork EngineerCommented:
Question: Does your logs are where the database is? if it so, then just create a folder and move it into it.
0
cciedreamerAuthor Commented:
They are on same drive but different folders

Database
F:\databases\db01.edb

Logs
F:\db01\

I have same setup on test environment
I just rename logs folder and now i cannot mount database :(
0
Hemil AquinoNetwork EngineerCommented:
Did you follow the steps I wrote to you? Is not going to work because the DB is dirty, you need to clean it then you would be able to mount it.
Verify database is clean shutdown by running the command eseutil /mh driveletter:\database\database.edb
0
cciedreamerAuthor Commented:
I followed your steps

Even I ran eseutil to make sure clean shutdown and it was clean

Then i rename the db01 folder for log files to db01.old and tried mounting the database but receiving error
0
Hemil AquinoNetwork EngineerCommented:
Could you please show me the error?
Also show me the status of the database as well whether is clean or dirty
0
cciedreamerAuthor Commented:
Sure I will post them now
As soon as I return the folder name as before I was able to mount the database successfully
0
cciedreamerAuthor Commented:
I will do the following again during non-working hours and will see

- Dismount the active database first.
- check the database is in the clean shutdown with the help of eseutil tool by using the parameter eseutil /mh "path of the database"
- Rename existing log file folder. Create a new folder, copy the .chk file (s) only to the new folder.
- Mount the database and it will create the fresh log files.
- I will try again to add the passive copy on remote mailbox server in DAG.

I will update once done with above steps.
0
cciedreamerAuthor Commented:
Hi,
I did all above steps but no luck, please any further help.
0
Hemil AquinoNetwork EngineerCommented:
Sorry for the delay, I've been really busy.
Try this, create a new mailbox database and see if you can copy the database to the next hop server. If it worked, please let me know.
0
cciedreamerAuthor Commented:
Hi
Even the new database is failing.
0
Hemil AquinoNetwork EngineerCommented:
Try deleting dag an re-creating it again? make sure both server dont have anything.
With the solution I have gave you you should get that up and running. the problem might be on the second server.

Do you still experiencing the same error above?
0
cciedreamerAuthor Commented:
Hi Hemil,
Sorry for the delay in response.
I did the following and it is resolved now but still no clue why I need to do all of these steps for each database.

Firstly, I repeated the steps as you mentioned above for resetting the log files however when adding adding database copy I still received the error message. But then I need ran the following to seed the copy and it worked.

Update-MailboxDatabaseCopy -Identity DB01\ex02 -DatabaseOnly

Open in new window

0
cciedreamerAuthor Commented:
The cause of the problem has been identified and fixed. Now all is fine and healthy.

he value of the ConfigurationDomainController parameter and the value of the PreferredGlobalCatalog parameter are different. I set those parameters statically using the following powershell cmdlet

[code]Set-ExchangeServer –Identity <mailboxserver_name> -StaticDomainControllers  <DC FQDN> -StaticGlobalCatalogs <DC FQDN> –StaticConfigDomainController <DC FQDN>.

Open in new window

[/code]
0
Hemil AquinoNetwork EngineerCommented:
Hi pal, glad you solved it. But I remember I asked you for you to do that in my first comment and you said "it didn't work for some reason"

Are you using the console or the ECP?
Can you check if the database was added even though you have that error? If it so try updating the databse.

Try using the ECP, I had experience where using the console gets buggy configuring dag.
0
cciedreamerAuthor Commented:
Thanks Hemil,
But your comment was if I am using Powershell or ECP However, the solution that worked for me is completely different, its about AD replication and preferred DC/GC.

Please correct me if misunderstood.
0
Hemil AquinoNetwork EngineerCommented:
I see, that's good.

I was formulating my commend based on your second response above

But then I need ran the following to seed the copy and it worked.
Update-MailboxDatabaseCopy -Identity DB01\ex02 -DatabaseOnly
0
cciedreamerAuthor Commented:
Aha..Sorry.
Thanks Hemil for your support.
0
cciedreamerAuthor Commented:
Thanks Hemil.
To help others, please also see the comment 42367932 which was one of main cause of this problem.
0
cciedreamerAuthor Commented:
Hi Hemil,

Just a small concern here,

When I renamed logs files folder then a new folder was created with a fresh files.
however there are some files in folder, do you I need to copy them to new folder? Will there be any lost of messages ?
0
Hemil AquinoNetwork EngineerCommented:
You don't need to, those files are created automatically by exchange.
Once you have cleaned and mounted the database those files comes automatically.

But as always say, keep a backup just in case.
0
cciedreamerAuthor Commented:
Thanks Hemil for the clarification.  I appreciate that.
Lets assume if I delete any log file from original folder and refresh the files by renaming the same folder. Do the does files comes automatically including the deleted one ?
0
Hemil AquinoNetwork EngineerCommented:
If you delete any logs from the database, it wouldn't impact anything on exchange.
Those logs are there to tell you what is going on with the database. If you look closely those logs will increment from time to time and you might have to delete some to free space in your HDD

But remember there's some files that AREN"T logs. Those files are E00.CHK
Check this sample below.
logs.png
0
cciedreamerAuthor Commented:
Thanks Hemil.
0
Hemil AquinoNetwork EngineerCommented:
You're welcome Pal,
0
cciedreamerAuthor Commented:
Hi Mate,
I read on internet that log files are not regenerated at any time. Once log files are deleted, they are gone for good unless restored from backup.
0
Hemil AquinoNetwork EngineerCommented:
Hey dude,

Like I've mentioned before, logs file tells you the status of the database and helps for recovery checkpoint.

Now, like we talked before, let say your database crashed and you need to perform recovery, for some reason your logs are not concurrent and therefore won't let you to mount the database.

In this case you would need to use exeutil to clean the database and generate logs that will help you to bring the database from dirty shutdown to clean shutdown.
The only thing is you can't bring the database at certain checkpoint for recovery. Logs will be automatically generated with the time stamp of the day date.

Here is what I do as a good practice in my scenario. Those logs will increment as I stated from time to time. You have to make sure your backups are on point as I mentioned too. So if you need to troubleshoot you can delete logs without worry about anything.

It wouldn't harm anything, those logs are only for database checkpoint.
0
cciedreamerAuthor Commented:
Thanks Hemil for excellent clarification. Let me just breakdown by dates to determine that there will be no issue. We are using Veritas backup solution

13/11 0200 am - Full Backup
13/11 2300 - Logs folder rename and new files were generated.
14/11 - 15/11 - No backup
16/11 - 0900 - Full Backup.

Will there be any issue ? I still copy of logs in the folder that renamed
0
Hemil AquinoNetwork EngineerCommented:
If you are performing backups everyday you shouldn't have any issue restoring your logs back to your server.

But like I've said, dont worry about those logs. If your database still in good condition an no one is having trouble accessing to their mailbox you dont need to recover those things. It generate lots of space in your hard drive until it reach the full capacity of it. In fact you did to yourself a good favor.

Maybe you dont feel comfortable not having them because may be you haven't dealt with them logs before and I understand.
But, it's just logs, make sure you always have your backup and test it, I had experience where at the moment of recovery all my backups was screwed dont ask me how, it's just one of those days as an IT  that everything turns upside down.

I hope this clears it up :)
0
cciedreamerAuthor Commented:
Thanks once again.
Why was worried because I received complaints from some end users ( 4-5 ) at the same time saying that we are missing some emails from the specific dates.
0
Hemil AquinoNetwork EngineerCommented:
That's odd, because as I remember you put everything back to normal copying back the logs and database. And all you wanted to do is  add database copy to a second exchange right? but anyways let say it's missing and you think that happened after you did some changes, all you have to do it's recover that specific user email from a backup and you should be all set.
0
cciedreamerAuthor Commented:
Hi Hemil,
I did not copy back the logs. The logs were just created after mounting the database and then I add database copy.
0
Hemil AquinoNetwork EngineerCommented:
At the moment you mounted the database it creates a checkpoint logs which is normal, but that has nothing to do with the user missing emails. If you think about it emails are embedded into a database that can't be deleted unless the database its damaged, or the user itself deleted by mistake, and still can be recoverable.
0
cciedreamerAuthor Commented:
Yes, the database was mounted successfully and no errors were occurred, and full backup was ran after 2 days.
Anyways, I suppose this might be a different issue not related with logs.

Thanks once again brother for your good support.
0
Hemil AquinoNetwork EngineerCommented:
Not a problem dude anytime, by the way are you working in your CCIE, I will be starting working next year. I bought a lot of equipment to get it done.
0
cciedreamerAuthor Commented:
Hi,
I send you private message.
0
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
Exchange

From novice to tech pro — start learning today.