Hello Andy
I was reading your support it this post.
And this caught my attention
Andy, how is that a problem?, besides not having a backup?
Isn’t this the default way to install a proxmox server? (A lot of disks, choose a zfs raid and configure external backups, and cross your fingers that never failed as a single server )
Reading twice, I think to understand that Murphy occurs here. Then, having good backups: is correct the way proxmox was installed?
By this I mean, I’m still looking for the time to create something similar to your diagrams.
- The VM/nethserver stored in a synology (nfs? or what is better?, I appreciate the advice)
- I want to have 2 proxmox : one productive (A) and other for emergencies (B)
- Both using the storage of the synology for the running VM.
I think in this aproach:
- For proxmox A & B, use the proxmox as storage for the VMs.
- 1st Reinstall/prepare the proxmox B (with enough space to host the proxmox VM and maybe some additional vm. Just in case something goes wrong with the synology).
For the proxmox B
- Put 2 big hard disk, boot the proxmox ISO, choose a RAID-1 in ZFS and that’s it, I appreciate the advice.
- Configure the storage area in the synology (nfs?)
- Move/copy that vm from promox-A to the synology share (backup first)
- Make the promox B use the VM from the synology share/storage
If this works, reinstall the proxmox A in a similar manner (It has 4 hard drives)
Create the datacenter with both proxmox (need to learn how), then migrate the running VM from proxmox B to promox A.
And I have some doubts with the interfaces, this is the configuration, this is for proxmox A
auto lo
iface lo inet loopback
iface eno1 inet manual
iface enp10s0 inet manual
iface eno2 inet manualauto vmbr0
iface vmbr0 inet static
address 192.168.16.1
netmask 255.255.248.0
# this is our fortigate
gateway 192.168.16.99
bridge_ports eno1
bridge_stp off
bridge_fd 0auto vmbr1
iface vmbr1 inet static
# I have this interface disconnected in both proxmox
address 187.xxx.yyy.25
netmask 255.255.255.240
bridge_ports eno2
bridge_stp off
bridge_fd 0
and for proxmox B this:
auto lo
iface lo inet loopback
iface enp0s31f6 inet manual
iface enp1s0 inet manualauto vmbr0
iface vmbr0 inet static
address 192.168.16.21
netmask 255.255.248.0
# this is our fortigate
gateway 192.168.16.99
bridge-ports enp0s31f6
bridge-stp off
bridge-fd 0auto vmbr1
iface vmbr1 inet static
# I have this interface disconnected in both proxmox
address 187.xxx.yyy.25
netmask 255.255.255.240
bridge-ports none
bridge-stp off
bridge-fd 0
In my tests if I turn off the VM/nethserver in promox A, and turn it on in proxmox B, nethserver works correctly. I guess that’s okay.
But I would like to know how to configure the second interface and not “burn” two static IPs (187.xxx.yyy.25); I think that using a static IP in both proxmox is wrong, in this case is the same (.25) but I don’t want to use this or a second, don’t have more IPs to spare.
This seems the right path: (I appreciate the advice)
Configure the second interface as an IP for a DMZ that is managed by my Fortigate, and when I need to publish some other external service (server: mail, dns) just create the policy to handle it (learning)
That is, if I install a server with any of these services, I could use an IP from the DMZ that will manage the fortigate. Then I suppose I should use an IP from the segment : 10.10.30.x and with this my virtual servers use IP like 10.10.30.2+
(just as an anecdote) BTW, I still have an old server with some usb storage connected, If I remove the usb, the servers goes boom every time!
Regards.