SQL Always On - Directory where the database is stored in the replica

Question

SQL Always On - Directory where the database is stored in the replica

Salves 501

Hi,

when I add the replicate servers to my SQL Always On AG, I don't see an option to choose where the databases will be stored. I believe that it creates the replicated bases according to the default configuration of my SQL database.

However, if I want to change the directory of a base that will be replicated in my replica, can I do this after the added replica? Or how to configure this location configuration during configuration?

Thank you.

Shashank Singh 6,251 Reputation points

2020-09-10T06:44:35.24+00:00

when I add the replicate servers to my SQL Always On AG, I don't see an option to choose where the databases will be stored

how do you add the DB instance to AG. What option do you choose ?
Cris Zhan-MSFT 6,661 Reputation points

2020-09-21T02:43:16.317+00:00

Hi @Salves ,
Is there any update on this case?
If the answer is helpful, please click "Accept Answer" and upvote it.This can be beneficial to other community members reading the thread.
Cris Zhan-MSFT 6,661 Reputation points

2020-09-24T09:55:32.883+00:00

Hi @Salves ,
Is there any update on this case?

1 answer

Your answer

Shashank Singh 6,251 Reputation points

2020-09-10T06:44:35.24+00:00

when I add the replicate servers to my SQL Always On AG, I don't see an option to choose where the databases will be stored

how do you add the DB instance to AG. What option do you choose ?
Cris Zhan-MSFT 6,661 Reputation points

2020-09-21T02:43:16.317+00:00

Hi @Salves ,
Is there any update on this case?
If the answer is helpful, please click "Accept Answer" and upvote it.This can be beneficial to other community members reading the thread.
Cris Zhan-MSFT 6,661 Reputation points

2020-09-24T09:55:32.883+00:00

Hi @Salves ,
Is there any update on this case?

Answer 1

Cris Zhan-MSFT 6,661

Hi @Salves ,

You can choose to restore the availability group database on the new replica SQL instance and specify the directory location. Then select "Join Only" ,when adding the replica to exsiting AG and initializing the database .

Or after adding the replica, suspend data movement then remove the database from Availability Group, change the file location, then rejoin the database to Availability Group. More details you can refer to this article.

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Cris Zhan-MSFT 6,661 Reputation points

2020-09-14T01:32:33.03+00:00

Hi @Salves ,
Is there any update on this case?
If the answer is helpful, please click "Accept Answer" and upvote it.This can be beneficial to other community members reading the thread.
Salves 501 Reputation points

2020-09-14T05:15:21.533+00:00

Hi,

I'm testing.

I did all BLOG procedures.

I moved the files to another location.

I copied the same permissions from where the database was located (Get-Acl | Set-Acl).

But I have this error.

Thank you.
Cris Zhan-MSFT 6,661 Reputation points

2020-09-14T06:36:50.297+00:00

Hi @Salves ,
This may be due to the long time between remove and rejoin.Now you may need to make a full backup and transaction backup on primary replica and then restore these two backups on the DB of the secondary node(WITH NORECOVERY), then join the DB to AG.
Salves 501 Reputation points

2020-09-14T16:25:36.65+00:00

Hi,

got it.

As it is an empty base and there is no information this time that you quoted worried me, because I did it simultaneously.

Yes, I did this restoration test, but I made a mistake.

I restored the backup but not in recovery and when I tried he questioned that it was not in recovery, but the error was overcome yes.

Returning to the question of time, I am concerned if the database contains a large size, the transfer time can be a problem.

Would the best procedure be to suspend the movement of data on the primary server along with the secondary one and execute the path change procedure?

Thank you.
Cris Zhan-MSFT 6,661 Reputation points

2020-09-15T02:05:31.983+00:00

Hi @Salves ,

After confirming that the AG is running well and the replicas have been synchronized, complete the file path change process as simple and fast as possible, so that it does not exceed the recovery scope of the primary database.

>Would the best procedure be to suspend the movement of data on the primary server along with the secondary one and execute the path change procedure?

Suspending the movement of data on the primary replica, you cannot rejoin the database to the AG on secondary replica.

If the answer is helpful, please click "Accept Answer" and upvote it. Thank you.

Share via

SQL Always On - Directory where the database is stored in the replica

1 answer

Your answer