I have a poweredge R440 xeon silver server as a master running as an AD DC which has accommodated 1000 users, my boss will buy a new server with a poweredge R450 xeon silver type as a AD DC backup.
can i apply for hotsync?
I only use 1 network card that is embedded in the server by default.
I’m from Indonesia, I’ve been using this netserver for 4 years, and I had to make a decision to buy a new server for backup.
It’s good that you mention it, I just have uncertainty at the moment haha. I want to implement an active directory, I have two somewhat old servers, an nx430 and a poweredge R310, both with 8 gigs of ram.But precisely I want to have a backup server, so I don’t know whether to install NS7 Baremetal or install proxmos on each server and from there install virtual machines with NS7.
What really makes me doubt is the RAM of each server, because obviously proxmox consumes ram, and I consider that apart from that it would be the ram of the nethserver, so I don’t know how good or how bad the performance would be, there are approximately 200 users and 600 computers.
@uebmaster hi, I don’t know the arrangement and the detailed configuration among your servers. What comes next is my personal opinion…
If both servers are RHEL 7.0 compatible and have less than 16gb of ram, use bare metal might have some performances and overhead advantages compared with Type 1 Virtualization (ESX, Virtualbox, Proxmox, whatever). When you fail enough times for bare metal recovery (try several times for write down the dumb/hurry/sleepness-proof instruction and notes), NethServer works quite well as a startup from the dead end.
Advantages for the virtualization (even the one so proudly sponsored and profit-gaining for @Andy_Wismer) is that the migration among hardware is quite easier. You can start your cluster on your old server than move the machines on newer hardware (well supported by Proxmox or ESX) with less problems, because you can “configure” the hardware you want to interface for NethServer.
But it’s not necessary: I mean… with enough time and try, you can start NethServer on VirtualBox, then go physical, than go ESX, than came back to phyisical with the same path:
Backup old server, install new server, update, shutdown old server, restore config, restore data (adapting network adapters). This path can lead to longer downtime, but they are viable (I have personal experience about that).
It’s something wrong in Proxmox? Absolutely no.
Is necessary have a type 1 virtualizator (like ESX or proxmox)? Depends on goals, needs, hardware configuration.
my uncertainty was if i could do it with proxmox instead of bare metal. But when I read that what I have didn’t work, I understood that it didn’t work to run NS7 directly on the server either.
I don’t really have anything implemented yet, so based on your comment I’ll do the test.
I will install NS7 directly on a server (R310) and I will make the backup server virtual on a desktop computer only for emergencies, because I already remembered that one of the servers (NX430) only supports windows.
In fact, that’s why I entered the forum, because I remember that someone said that NS7 could be used as a secondary domain server in windows server.
But when I entered I saw this thread and that’s why I asked hehe.
This procedure is experimental and incomplete. It is not designed to work on production environments. It does not integrate with NethServer backup/restore procedure.
Using a bandaid instead of proper fixing device like clamps or welding, is calling for troubles on pipes.
Use an unsupported way to get around nethserver for “make windows believe” to have some buddy can lead to exciting while danger and unstable places…
Procedure was written as proof of concept in october 2016. I think that at least two versions of Windows server came to market after that. And some more revisions of Samba, Microsoft SMB and many others patches…