Link to home
Create AccountLog in
Avatar of timb551
timb551Flag for United Kingdom of Great Britain and Northern Ireland

asked on

DFS Replication stopped working

Hi

I have two Server 2008 R2 servers replicating over a VPN.

The servers were working fine until a few days ago where i now get the following event.

The DFS Replication service failed to recover from an internal database error on volume E:. Replication has been stopped for all replicated folders on this volume.
 
Additional Information:
Error: 9214 (Internal database error (-1078))
Volume: BEE9E62A-4E1E-11E0-939F-00215ABC4203
Database: E:\System Volume Information\DFSR

I really done want to have to remove all the configuration and start again as there is quite a lot of data to replicate.

Any ideas?

thanks
Avatar of richardstuartpowell
richardstuartpowell
Flag of United Kingdom of Great Britain and Northern Ireland image

try deleting the staging folder - this should get things going again ...
Avatar of timb551

ASKER

Is that on the source or the destination server?
sorry i need to give you a more detailed answer ...

1) disable the dfs service on both servers
2) delete the staging folder (on both servers)
3) renable the dfs service on both server
4) restart both servers

try that and see if that works ...
ASKER CERTIFIED SOLUTION
Avatar of richardstuartpowell
richardstuartpowell
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of timb551

ASKER

Ok cannot reboot the server until tonight so will get back to you.

thanks
no worries, try all of the steps i mentioned but don't delete the staging folder unless you have to.  it's not a problem to delete this folder but you'll lose any data that wasn't replicated before dfs failed if you know what i mean, not the data itself but the bit-level replication that was outstanding prior to the failure.

so if user a made a change to a word document and you delete the staging folder he might lose the change he made before dfs failed.

good luck :-)
Avatar of timb551

ASKER

Im not worried about losing data mid transit as its a disaster recovery server with only 1 way replication.
ok, good luck!
Avatar of timb551

ASKER

Is it the staging or the staging or staging areas?

thanks
just try everything else but don't worry about deleting the staging folder(s) ...

i.e.

1) disable the dfs service on both servers
2) SKIP THIS STEP
3) renable the dfs service on both server
4) restart both servers
Avatar of timb551

ASKER

Ok will do this tonight as i missed the restart time last night.

thanks
Avatar of timb551

ASKER

Tried the disabling rebooting and enabling but nothing going
Avatar of timb551

ASKER

Any more ideas?
hi tim

try this

1) stop the dfs service on both dfs servers

2) delete the contents of the conflictanddeleted folder (dfsprivate\conflictanddeleted) - have a quick look in here and decide if you want to keep any of these files BEFORE you delete them - if you want to keep them just move them somewhere else for the time being ...

3) delete the conflictanddeletedmanifest.xml file on both dfs servers (same location as above) - you can take a quick look in this file BEFORE you delete it - it contains a list of all files that are in conflict, including their original file names

4) restart the dfs service on both dfs servers

you should also check the size of each staging folder and check that you are not exceeding your quota(s)

see if that works - good luck :-)

nb: no reboot required with this suggestion ...
Avatar of timb551

ASKER

thanks, will give this a go tonight.
Avatar of timb551

ASKER

The conflictanddeleted folder on the main server was empty.  And on the second server it wont allow me in saying that it refers to a location that is unavailable.

Any ideas?