Windows 10: Server 2019 replication error 6408

I am getting error 6408 on my domain controllers. I have tried shutting of dfsr and re-syncing everything following the common posts about replication errors. Everything completes with no error but I keep getting 6408 when i restart the service. In DFS Management I have an invalid item showing up from an old domain controller that I have no idea how to get rid of. It shows the member name in the details but it's Member column is <unknown> and no local path.ERROR:The DFS Replication service failed to initialize replicated folder C:\Windows\SYSVOL because the service detected that one of i

:)

 

Server A --- to --- Server B / Replication

Situation
I've got a very simple network, providing data in a SOHO environment to just 3 users.

SERVER A (W2K3)
+
3 users


SERVER A has recently been upgraded to RAID 1, with scheduled Cobian backups. All good so far.

Now, for the next 6 months, we've got a project in a far-far away land. Connecting to SERVER A is not going to be very efficient on consumer based internet connections. I also want a level of redundancy in case SERVER A, for any reason, goes down. (This includes power cuts, internet interruptions, not just hardware failure of the machine).

Enter SERVER B

Server B will be a mirror copy of SERVER A, but without the RAID and backup. It will be a SFF Atom box that can go on the road to the project site, and will have all data available locally providing fast access as well as "insurance" should SERVER A become unavailable for any reason.

Note that during this time away, there will be nobody at site A to fix/repair anything so why I need to find a maintenance free solution to the whole affair. Although I can Dameware Remote Control (remote desktop) into SERVER A assuming it is up and running, if it goes down, then it will stay down.

Note further than SERVER A and SERVER B will not be permanently connected over WAN. SERVER A has permanent internet access, but SERVER B will travel and therefore will be connected some days, and some days not.

QUESTION
What is the best way to keep SERVER A and SERVER B synchronised? (Or multi-server replication, depending on your preferred terminology)?

Something that seems to do this job perfectly is DFS Replication, a service in Windows Server products. However, it does not operate unless DNS and Active Directory are installed. It refuses to work on in a "workgroup" but only in a "domain". Setting up a domain, DNS and Active Directory seem to be overkill for a SOHO environment, plus I'm not sure how to do that properly given our usage topology. All instructions seem to be for enterprise fixed infrastructure/LANs and talk about heirarchy's, forests, domain servers, active directory servers, replicating between these. This all seems like a lot of work to do even BEFORE doing the simple DFS replication (Keeping the data on SERVER A shares and SERVER B shares in sync).

Are there any other solutions? Limited budget. Free, opensource or cheap. No suggestions for ArcServe Replication at $5000+ thank you!

If you made it this far down the post, thanks for listening and any suggestions you might have are very welcome *Pimp imp:

 

Problem with data replication from win server 2019 to server 2012 R2

Can I do data replication from win server 2019 with Active Directory to server 2012 R2 without Active Directoriy?

Or I must install Active Directory on device with win server 2012 R2 first

Zdravkovic Nebojsa

*** Email address is removed for privacy ***

 

Office 2019

Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

Microsoft Office 2019 will only work on Windows 10

https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

Spoiler Office 2019
Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

• Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
• Office 2019 apps will be supported on:
  • Any supported Windows 10 SAC release
  • Windows 10 Enterprise LTSC 2018
  • The next LTSC release of Windows Server
• The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.