Shulou(Shulou.com)06/01 Report--

There are many scenarios for moving database paths. A typical scenario is to move to another disk because there is not enough disk space. It is not difficult to move database paths with wizards, but if DAG is enabled, there are some precautions. The following instructions.

PS: If you need to move the database path, you must first unload the database that needs to be moved, so it is best to migrate during non-working hours.

The following is an example of an IT database, DAG enabled on MBX1 and MBX2, IT database active on MBX1, and IT database replicated on MBX2:

dismount a database

Delete the copy of IT database, because IT database only has one copy on MBX2 server, delete it directly, if there are multiple copies, delete one by one;

PS: Deleting does not actually delete database files on MBX2 servers, which are still useful.

deleted successfully

Check if the database file is still there.

6. To prepare for migration, you need to create a directory name with the same name under the same disk path on all MBX servers, such as DB-IT:

7. After all copies are deleted, go back to MBX1 and move the database path:

PS: Here we can also use the command line to migrate, command: move-DatabasePath -Identity 'IT' -EdbFilePath 'C:\DB-IT\IT.edb' -LogFolderPath 'C:\DB_IT'

8. After the migration is complete, check if the path has been updated

9. Next, you need to manually copy/move the previous database files to the new directory DB-IT on all replica servers to complete the data synchronization more quickly:

10. add replica

11. Copy addition complete

12. Restart the Microsoft Exchange Search Indexer service on all replica servers, otherwise an error will occur when activating replicas as shown below:

13. Load into database, check status

14. Migration complete.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.