Hello, Am 26.12.2016 um 15:57 schrieb Miguel Medalha via samba:> I need to free the physical machine running one of the AD DCs > for another purpose. I thought of creating a KVM Virtual > Machine running that DC as a guest to the file server, > which has more than enough hardware resources for that. > In sum, the file server would keep running as it is, > as a physical machine, with the additional role of serving > as a host to a VM running the AD DC. > > Does anyone here see any problem or disadvantage with such > a setup?One problem I see is that the client relies on a VM that might not be up when Samba on the client boots. If there are other services running on the client, that use winbind for authentication or for building a list of users, they might fail as well. Additionally the client uses the DCs DNS, so services might fail during start up if the DNS is not up. If you have only one physical machine, I would put both into a VM or at least the client and run the DC native on the machine. Regards, Marc
> One problem I see is that the client relies on a VM that might not be up > when Samba on the client boots. If there are other services running on the > client, that use winbind for authentication or for building a list of users, > they might fail as well. Additionally the client uses the DCs DNS, so services might fail during start up if the DNS is not up.As I said on my original post, I have two DCs in this setup. Only one of them would be migrated to a VM. The one having the FSMO role would still be a physical machine. Do you still see a potential problem here?
I would think running both your DC's as VM's would be a good idea - makes it easier to backup the VM's in to protect against failure of the physical host(s). Whether or not a DC is physical or virtual, you will still have the same client dependency issues. The thing to avoid would be having the KVM host machine double as anything else- you want to keep the host layer as stable as possible. I haven't used KVM. I have used VMware ESXi and Xen, so my observations may not apply to KVM. On 12/29/16 09:25, Miguel medalha via samba wrote:>> One problem I see is that the client relies on a VM that might not be up >> when Samba on the client boots. If there are other services running on the >> client, that use winbind for authentication or for building a list of users, >> they might fail as well. Additionally the client uses the DCs DNS, so services might fail during start up if the DNS is not up. > As I said on my original post, I have two DCs in this setup. Only one of them would be migrated to a VM. The one having the FSMO role would still be a physical machine. Do you still see a potential problem here? > > >
Am 29.12.2016 um 15:25 schrieb Miguel medalha via samba:>> One problem I see is that the client relies on a VM that might not be up >> when Samba on the client boots. If there are other services running on the >> client, that use winbind for authentication or for building a list of users, >> they might fail as well. Additionally the client uses the DCs DNS, so > services might fail during start up if the DNS is not up. > > As I said on my original post, I have two DCs in this setup. Only one > of them would be migrated to a VM. The one having the FSMO role would > still be a physical machine. Do you still see a potential problem > here?Only if the on-physical DC is down. Then have the same dependency problems in the described scenario. Regards, Marc