nbctcp
asked on
DFS Replication Health Report status Uninitialized
INFO:
2x Win2003 X64 (FileServer1 and FileServer2)
Located in same Site and subnet
When I ran "DFS Replication Health Report", in FileServer2 DFS INFORMATIONAL status shown Uninitalized.
QUESTIONS:
INFO:
2x Win2003R2 X64 (FileServer1 and FileServer2)
Located in same Site and subnet
When I ran "DFS Replication Health Report", in FileServer2 DFS INFORMATIONAL status shown Uninitalized.
QUESTIONS:
-what Uninitialized mean
-how to change it to Normal
thanks
2x Win2003 X64 (FileServer1 and FileServer2)
Located in same Site and subnet
When I ran "DFS Replication Health Report", in FileServer2 DFS INFORMATIONAL status shown Uninitalized.
QUESTIONS:
INFO:
2x Win2003R2 X64 (FileServer1 and FileServer2)
Located in same Site and subnet
When I ran "DFS Replication Health Report", in FileServer2 DFS INFORMATIONAL status shown Uninitalized.
QUESTIONS:
-what Uninitialized mean
-how to change it to Normal
thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This is in all likelihood related to the unavailability of the failed DC.
Restarting the service DFS Replication will force it to link to an available DC.
It will probably take 30 - 60 minutes before running a diagnostic report will show that replication has initialised.
Restarting the service DFS Replication will force it to link to an available DC.
It will probably take 30 - 60 minutes before running a diagnostic report will show that replication has initialised.
ASKER
I got this error code in FS2.
I think that also causing DFS problem
Do you have any idea how to fix chkdsk error?
Maybe need to off System Restore. I haven't check whether System Restore enable or not
thanks
18-Mar-11-10.47.25.jpg
I think that also causing DFS problem
Do you have any idea how to fix chkdsk error?
Maybe need to off System Restore. I haven't check whether System Restore enable or not
thanks
18-Mar-11-10.47.25.jpg
Definitely turn off system restore.
When you have a time when you can reboot the server, run chkdsk C: /R.
When you have a time when you can reboot the server, run chkdsk C: /R.
ASKER
I delete failed DC in "Site and Services", in DNS nic of every servers
FS2 hard disk of data is corrupted and can'be trusted after replacing disk of Dell MD3000i. We decide to recreate the disk later
thanks
FS2 hard disk of data is corrupted and can'be trusted after replacing disk of Dell MD3000i. We decide to recreate the disk later
thanks
ASKER
My client have 2 sites. HQ sites have 3 ADs. Branch site have 1 AD
Between site connected through 512KB link
recently AD2 in HQ site corrupted because of HD failed. so I need to off it.
AD1-AD4 all are GC. AD4 in Branch site
because of AD2 off, then I migrate all FSMO that previously in AD2 to AD1.
I haven't cleanup AD2 info in SIte and Services, User and Computer/Domain Controller and DNS site
All DNS setting in NIC in AD1-AD4, 3xFileServer in HQ and 1xFileServer in Branch still have AD2 ip address
FS1, FS2, FS3 in HQ site, FS4 in BRANCH site
FS2 and AD2 connected to the same iSCSI disk that recently 1 disk has faulty.
Replication folder that has status Uninitalized happen in FS2 that has same connected disk as AD2
Same connected disk means: I have Dell MD3000i using iSCSI mount the disk to esx vm of FS2 and AD2. That Dell MD3000i recently has 1 disk failure and the hot spare disk not kick in base on the report
1. How soon after creating the replication group did you run the report?
We create replication last 2 yrs.
just recently AD2 has problem, then I off it
2. How much data is there to replicate?
160GB
3. Can both file servers contact the domain controller without problems?
1 of AD is down, other 3x DC are ok
4. Have you tried restarting the DFS service?
-haven't
-what service name exactly in Services do I need to restart or do I need to restart the server itself