I know what si needed in order to move a database and a log file path to another drive but what I have not been able to find is how si this done when you have passive copy (DAG) for the database you want to move. Will I need to remove the database copies then move the active database to where I need it ansd then recreate the database copy? I will also be moving the log files for the database to another drive.
Not knowing the official answer, I will give you the answer I use...
DAG requires that the members servers have identical pathing for DB/Log per database. Therefore, if you want to move the database path, the active database and all passives must have access to identical paths for the new location.
FWIW, I also remove all passive copies before moving the active, then recreate the passives.
I did finally find an official article that outlines what needs to be done but when I read this I do not see much difference in following their recommendation compared to removing the copies and then recreating them after the move. I was aware of idential structure needed to exit for the database copies but good info to know for those contemplating this as well.
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
Don't remove the copies. Just suspend the replication and copy the data from old place to new place. Then change the drive letter or mount point paths of the hardware. Then resume replication.
1. dismount and suspend replication for the db copies on the DAG nodes
2. copy the db files to the new location
3. use the move-databasepath cmdlet with the -configurationonly switch. this will just update AD. make sure your db paths are consistent across all nodes example - Move-DatabasePath –Identity 'my db' –EDBFilePath 'd:\DAG\Data\mydb.db -ConfigurationOnly
Posts: 6812
Joined: 9.Jun.2004
From: Philadelphia PA
Status: offline
No. Sorry. That's wrong. If you dismount you're taking people offline. So, 1. is wrong. Item 2 is ok. Item 3 is wrong because that updates the path for all copies.
The OP wants to move the passive from one drive to another. The path in the active is not at issue.
Mark so if I understand correctly I suspend the database copy, Move the data base copy's log and database files to the new location , then when done follow the procedure for moving the database to another drive, then once done unsuspend and resume replication. The path will be identical on both severs. If I understand the process there is no way to do this without access being lost to users during this proces or is there a way to limit down time?