dfs replication
6 TopicsDFS Folder Replication DB Import Error code: 0x00000005
Hello, I have a server 2016 file server I am trying to setup with DFS folder replication. The volume that I am stuck on has 15.4TB of data and I have already done the preseeding to the downstream server which is within the same network. I have done the dfrs clone export both with basic validation and no validation, the basic validation seems to timeout and error out saying it wasnt able to read the config.xml file in the directory, however when I do no validation it goes right through but then the downstream server on the import gives me a Error code: 0x00000005. I have done my own validation on the preseeded folders and files on the downstream server so I am not worried about doing the validation and just need the downstream server to import it.332Views0likes0CommentsStop DFS replication and remove data from one server
0 Hi, two servers, both servers on the same domain. DFS is setup to replicate between both servers. How do I stop the replication and delete the files from one of the servers, while keeping the data intact on the other server, without causing a mess and potentially making the shares unavailable or experiencing data loss? DFS can stay, just the replication needs to stop. I'm aware how to stop DFS: Open the DFS Management console. Expand the Replication. Select your replication group(s). Right-click on each member server and select Disable. But this will still leave me with the data on both servers, won't it? I want to reclaim the space by deleting the data off of one of the servers because it's quite a lot and the space is needed elsewhere. Thanks!29KViews0likes6CommentsDFS Replication is Not Compatible with NTS Deduplication
The documentation claims that data deduplication is compatible with DFS Replication, but that is not correct. I have several systems with both enabled, some Windows Server 2012 R2 and some Windows Server 2019 systems. If a user interacts with a file that has been deduplicated, such as moving it from one folder to another, DFS-R may log a 4406 error (The DFS Replication service encountered an unsupported reparse point in a replicated folder. This reparse point will not be replicated because the replication of this type of reparse point is not supported by the DFS Replication service.) and delete the file from the partner. Data deduplication uses reparse points and DFS Replication doesn't like them. I thought that since the documentation says both technologies are compatible that DFS Replication would have been updated to work correctly with reparse points when they are related to data deduplication.Solved1.7KViews0likes4CommentsDFS and DFSR failover
Hi, I'm looking at setting up DFS Namespace and DFSR for some remote branches and just wanted to get some expert advice: I understand that if a local server at a branch office fails then the users will be auto-redirected to another server (according to the sites configuration). But when happens is a network link fails? I know DFSR will fail, but will the namespace still stay at the local server? In that case what happens when the link comes backup? secondly, am I right in thinking that there is no awareness in the Namespace that would stop 2 users trying to open/save the same file from 2 different branch offices. If that was to happen how would DFSR deal with the 2 modified files. Thanks.1.3KViews0likes2CommentsReplicación DFS entre sedes
Buenas tardes, Tenemos configurado un servidor DFS en la sede principal con Windows Server 2019 y hemos creado una replicación DFS de algunas carpetas a otra sede. La idea es que en cada sede se trabaje contra los documentos de su servidor y entre ellos se repliquen los datos. El problema es que si un usuario de la sede principal abre un documento el lunes por ejemplo y hasta el viernes no lo guarda y cierra, todos los cambios que hayan realizado sobre ese mismo documento en la sede secundaria al replicar se pierden. Es decir, en caso de que se edite el mismo documento en las dos sedes a la vez, solo se guardan los cambios del último que le ha dado a guardar. Que se puede hacer para que se bloquee el documento en uso, salga algún mensaje o que no permita abrirlo al menos en la segunda sede? Queremos evitar que se pierdan los datos modificados de alguna de las dos sedes en caso de que coincidan. Muchas gracias1.2KViews0likes3CommentsActive Directory DFSR headache
We have 23 DC's, all but one of which are 2012R2. The one-off, I upgraded a couple weeks ago directly from 2012R2 to 2019. For the past year or two we've had 2 DC's that weren't doing SYSVOL replication. I thought I had fixed that before I started with the process of getting them upgraded to 2019, but now that I've done one server, it looks like I was incorrect. So here's what's driving me nuts. Using the "status" tab of the Group Policy Management MMC, things are either horribly FUBAR, or humming along perfectly, depending (apparently) on the OS of the computer I'm running the MMC from. If I run it from a Windows 10 workstation or the Server 2019 DC, things look bad. I show 15 servers with replication "in progress", of which 13 show a status under the SYSVOL column of "Inaccessible", and 2 show a "Contents" issue with a single GPO. If I run the MMC from the 2012R2 DCs or from a Win 8.1 VM I spun up on a hunch, I show all 22 DCs in perfect sync (both AD and SYSVOL) with the baseline DC. When I use a file/folder comparison tool on the contents of the SYSVOL folder for each DC, not one of them matches the contents on the PDC. Although there are no "orphaned" files or folders, the date modified doesn't match on a varying number of files and/or folders for each DC (sometimes off by years). The closest is actually the 2019 DC, which only shows mismatches on the contents of 3 GPOs. The DFSR event logs don't show any regularly occurring errors other than losing replication for a bit between DCs when one goes down for system state backup. I ran a dcdiag /a /c, and didn't see any errors in there aside from the DFS test failing due to the above-mentioned errors caused by backups, some system event log errors due to a deleted computer account, and one DC had a typo in the secondary DNS entry on its network adapter settings. There are also no errors when I run repadmin /showrepl. I've tried running both non-authoritative and authoritative replications using the instructions here, and neither made any difference at all. Any suggestions?Solved1.6KViews1like3Comments