I think I should include "System Volume Information" because it stores:
The contents of Indexing Service database used for fast file search
Distributed Link Tracking Service database
NTFS disk quota settings
DFS Replication database
And it's size is acceptable (40GB)
Migrating data to new disk - Windows server 2012
Hi all,
My environment : Windows server 2012 standard as File server for head site : FileServer-Head
I want to migrate data (including shares and permissions) from D drive (local disk) to G drive (new SCSI LUN) using robocopy.
I have concern : FileServer-Head has DFSR replication with a branch site file server
FileServer-Head\D\somefolders <------> FileServer-Branch\D\somefolders
Here are steps I plan to do on FileServer-Head
Stop the Server service, DFS namespace, DFS replication service to prevent anyone from accessing files on the server during this migration
Run ROBOCOPY D: G: /E /COPYALL /R:3 /W:10 /XD "System Volume Information" (exclude DFS "System Volume Information" from being copied)
When data is copied over, Switch drive letters : D to K , G to D, reboot server
Start the Server service, DFS namespace, DFS replication service and check if it works.
Should I exclude or include "System Volume Information" folder for DFSR keeps working after migration ? Please give me some advice thank you very much.
1 answer
Sort by: Most helpful
-
Jack Chuong 856 Reputation points
2021-10-29T23:38:51.987+00:00