SWRegistration
asked on
DFS and Event ID 13555
We have a DFS setup on Windows server 2003. We are experiencing errors with Event Id's 13506, 13555, and 13504. I've realized that the ntfrs jet database is corrupt and that the solution seems to be to delete the database and let it rebuild itself. The quesiton that I have is whether or not the data is safe while this takes place? The data is replicated across three locations and it would be disastrous to lose it. While researching this error, I've also discovered that we have far exceeded the MS recommended limits on the amount of data that the dfs and frs can handle. I wonder if anyone would be willing to discuss our setup and offer advice. Our dfs is not replicating right now and any help would be appreciated!
I'd also like to add that the errors are not on the DC's but on a member server who's role is file serving.
I'd also like to add that the errors are not on the DC's but on a member server who's role is file serving.
ASKER
Yes - step 4 would apply here. If the replica sets DO have other replicating partners, is the data safe? I've seen the dfs put file into a "pre-existing" folder before, essentially taking it offline for awhile and we can't have that happen. What exactly is in the ntfrs\jet database? Is it just replica set definitions? My main concern here is to keep my data online.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This solution made good sense and appears to have corrected this problem on my two DCs. Thank you.
One note: If you make copies of the files in the log and edb folders, I suggest moving them to another temporary folder. I left copies of the files in their respective folders and discovered that the NTfrs service deletes any files in these folders before it begins creating new ones.
One note: If you make copies of the files in the log and edb folders, I suggest moving them to another temporary folder. I left copies of the files in their respective folders and discovered that the NTfrs service deletes any files in these folders before it begins creating new ones.
Recovery Steps:
[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
net stop ntfrs
net start ntfrs
If this fails to clear up the problem then proceed as follows.
[2] For Active Directory Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
If there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
If there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.
[3] For Active Directory Domain Controllers that host DFS alternates or other replica sets with replication enabled:
(3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
(3-b) If this server is the only Active Directory Domain Controller for this domain then before going to (3-c) make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Serve
(3-c) Restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
(3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.
[4] For other Windows 2000 servers:
(4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
(4-b) net stop ntfrs
(4-c) rd /s /q g:\winnt\ntfrs\jet
(4-d) net start ntfrs
(4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members.