
So to answer the question, the servers them self can handle the virtualization but the network cannot "dont ask ive tried" as pointed out in my previous posts they are a law firm and not that interested in getting the latest i mean im running cat5 with zero fibre links and some switch's that are 10.100 in some places "bleh" and they wont let me upgrade to 1 gig with fibre links between them, not even to my NAS drive. This is where we are today single DC server "new" that has never complained since then and a fileserver "old" that is working great with a backup solution that is kida fast considering the network speed this place has. Keep in mind i was dealing with over 500k 1mil+ files at which point i brought back the old server and used it primarily as a file store, again mount an ISCSI drive and storing backups from it to NAS using filesync. The sync was stored on a relatively fast NAS drive which was configured as ISCSI and mounted directly to the server, this worked so well because my backup time was reduced to 6-18hrs. next was the size problem, this firm doesn't believe in high speed network "i know i was crying the entire time" anyways the backup time for the virtualized servers took over 2-4 days each pass this was becoming a huge problem, so again i scrapped the virtualization and opted in for a file sync method meaning i removed the sync between DC's, this took close to 4-5 days to finish the sync.

Please clarify.įor context im in South Africa, and the computer parts here are $$$ years ago when we received the new server i made the 2 servers work in unison, this worked great for a year then something happened which made the 2 dc not like each other any more, malware, hardware, software i could never find the exact problem, but i do know having them in unison was the problem so i scrapped both servers then made the new one virtualized, running both dc and dc2. Troz wrote:at one stage i had 2 server but 2nd server had to be removed, this was years ago lolSorry, can't follow which server you removed and how you do to have the only server run Windows 2012 R2 and Windows 2019. Only if both of your current Windows servers are swapping much of their time, I would believe you that you don't have the resources to run a 2nd DC controller virtualized on the second host, one headless DC per physical host.

A virtualized DC running headless does not need many resources. As you don't have the Essentials edition, your license allows you to run two VMs. You already have two Windows servers, one running currently the DC and another one running Windows Server 2019.

