Mombu the Microsoft Forum sponsored links

Go Back   Mombu the Microsoft Forum > Microsoft > FILE SERVICES (TECHNET) > Multiple DFSR issues
User Name
Password
REGISTER NOW! Mark Forums Read

sponsored links


Reply
 
1 30th March 14:00
richard
External User
 
Posts: 1
Default Multiple DFSR issues


Hi,

I posted a few days ago regarding an issue I had with DFSR, unfortunately
its now apparent that there are several problems. They all seem to relate
back to a faulting application that produced a 130GB file a few weeks ago,
prior to this there were no issues. This large file has now been deleted
however DFSR does not seem to have settled down since. The DFS topology
includes two servers at different sides of a WAN link. Effectively the data
is replicated from one to the other for backup purposes, people very rarely
use the other replica since users of the data are at the other site.

DFSR has failed to replicate a number of highly important large files
reporting sharing violations when the files are not locked or otherwise being
accessed, i.e. one of the files was created on Tuesday night by NTBackup and
was being reported as having sharing violation this morning.

DFSR does seem to be replicating user data files in another folder, things
like Excel spreadsheets etc. However, when it replicates to the folder target
the namespace EventID 4412 is reported - a file was changed on multiple
servers - and the ****nal file is removed from the source server.

In respect of the server with the large files, I have deleted the files on
the target server, pre-staged them and completely recreated the folder
structure under a new namespace with new folder targets, tried turning of RDC
and rebooting the server etc. None of this has worked and DFSR still reports
the same errors and no data is replicated. It seems to be being staged at
some point as the staging area is large (~20GB - its set with a maximum of
30GB). dfsrdiag reports the files as backlogged.

As for the user data folders, I can't remove the namespace as the namespace
is used across the company in login scripts and must remain in use. I can
remove the replica at the other end of the WAN link and start replication
again, but I am not convinced this will work in the light of what happened
when I created the other namespace as referred to above.

As I said earlier, there were no issues before the creation of this 130GB
file, is there any way to completely reset DFSR and force a complete resync
without having to delete the whole folder structure for example? What else
can I try to get this working?
  Reply With Quote


  sponsored links


2 4th April 23:10
rpost@online.microsoft.com (robert a post, jr
External User
 
Posts: 1
Default Multiple DFSR issues


can you use dfsrdiag to see what the filenames of the backlogged files are?
Seems odd that dfsr would be trying to stage this rogue 130GB file still.

Cycling the service should reset the what each machine thinks that it needs
(as far as files are concerned.) so if it was trying to replicate the big
file it should stop.

You can retrieve the conflicting files whenever you get the 4412 event.
The file should be in the DfsrPrivate\conflicts&deleted Folder on the same
machine.

Something else you may want to try on the machine that generated the nasty
file is to delete the dfsr database. Stop the service, delete the db, and
then start the service again. DFSR will recognize the db is lost / corrupt
and rebuild a new one. When it rebuilds it will walk the filesystem in the
replicated folder. This may take some time if you have a large amount of
files, but It should remove any reference to the rogue file.

The DB is in the <replicated folder volume>:\System Volume
Information\DFSR\DB folder.

Thanks,

Robert A Post, Jr [MSFT]
Distributed File Service Replication Test
This posting is provided "AS IS" with no warranties, and confers no rights.
  Reply With Quote
3 14th April 17:47
richard
External User
 
Posts: 1
Default Multiple DFSR issues


Hi,

I posted a few days ago regarding an issue I had with DFSR, unfortunately
its now apparent that there are several problems. They all seem to relate
back to a faulting application that produced a 130GB file a few weeks ago,
prior to this there were no issues. This large file has now been deleted
however DFSR does not seem to have settled down since. The DFS topology
includes two servers at different sides of a WAN link. Effectively the data
is replicated from one to the other for backup purposes, people very rarely
use the other replica since users of the data are at the other site.

DFSR has failed to replicate a number of highly important large files
reporting sharing violations when the files are not locked or otherwise being
accessed, i.e. one of the files was created on Tuesday night by NTBackup and
was being reported as having sharing violation this morning.

DFSR does seem to be replicating user data files in another folder, things
like Excel spreadsheets etc. However, when it replicates to the folder target
the namespace EventID 4412 is reported - a file was changed on multiple
servers - and the ****nal file is removed from the source server.

In respect of the server with the large files, I have deleted the files on
the target server, pre-staged them and completely recreated the folder
structure under a new namespace with new folder targets, tried turning of RDC
and rebooting the server etc. None of this has worked and DFSR still reports
the same errors and no data is replicated. It seems to be being staged at
some point as the staging area is large (~20GB - its set with a maximum of
30GB). dfsrdiag reports the files as backlogged.

As for the user data folders, I can't remove the namespace as the namespace
is used across the company in login scripts and must remain in use. I can
remove the replica at the other end of the WAN link and start replication
again, but I am not convinced this will work in the light of what happened
when I created the other namespace as referred to above.

As I said earlier, there were no issues before the creation of this 130GB
file, is there any way to completely reset DFSR and force a complete resync
without having to delete the whole folder structure for example? What else
can I try to get this working?
  Reply With Quote
4 20th April 13:31
rpost
External User
 
Posts: 1
Default Multiple DFSR issues


can you use dfsrdiag to see what the filenames of the backlogged files are?
Seems odd that dfsr would be trying to stage this rogue 130GB file still.

Cycling the service should reset the what each machine thinks that it needs
(as far as files are concerned.) so if it was trying to replicate the big
file it should stop.

You can retrieve the conflicting files whenever you get the 4412 event.
The file should be in the DfsrPrivate\conflicts&deleted Folder on the same
machine.

Something else you may want to try on the machine that generated the nasty
file is to delete the dfsr database. Stop the service, delete the db, and
then start the service again. DFSR will recognize the db is lost / corrupt
and rebuild a new one. When it rebuilds it will walk the filesystem in the
replicated folder. This may take some time if you have a large amount of
files, but It should remove any reference to the rogue file.

The DB is in the <replicated folder volume>:\System Volume
Information\DFSR\DB folder.

Thanks,

Robert A Post, Jr [MSFT]
Distributed File Service Replication Test
This posting is provided "AS IS" with no warranties, and confers no rights.
  Reply With Quote


  sponsored links


Reply


Thread Tools
Display Modes




Copyright 2006 SmartyDevil.com - Dies Mies Jeschet Boenedoesef Douvema Enitemaus -
666