ubu's latest activity
-
Uubu replied to the thread I recommend between 2 solutions.With Ceph, you need fast networking for your Storage, 10 Gbit should be the absolute minimum, better 25 or 40 Gbit. Your data will be on all 3 nodes for redundancy, if one node fails you can still work, if 2 Nodes fail your ceph is no longer...
-
Uubu replied to the thread Change zfs boot pool name.zpool-rename.md: rpool is the original, zp_pve the new pool name # Rescue System booten zpool import rpool zp_pve -R /mnt -f for i in proc sys dev run; do mount -o bind /$i /mnt/$i ; done chroot /mnt rm /etc/default/grub.d/zfs.cfg sed -i...
-
Uubu replied to the thread Change zfs boot pool name.You can change the pool name afterwards, but it is a bit of work
-
Uubu replied to the thread Change zfs boot pool name.You can of course do this, but unless you have a specific reason, it might not be such a good idea. When you want to build a cluster, the pools must have the same name for migration to work.
-
Uubu reacted to tom's post in the thread Kritischer Ausfall – gleichzeitiger Reboot aller Nodes nach iSCSI-Verbindungsverlust (Proxmox + HA + Softdog) with
Like.
Bei aktivierten HA bitte unbedingt einen zweiten (oder mehr) Corosync Link konfigurieren, sonst passiert genau das was hier beschrieben ist. Und auf keinen Fall Corosysn und Storagenetz auf derselben NIC. Siehe auch... -
Uubu replied to the thread Kritischer Ausfall – gleichzeitiger Reboot aller Nodes nach iSCSI-Verbindungsverlust (Proxmox + HA + Softdog).forum.proxmox.com/threads/adding-a-secondary-corosync-network-for-failover-setting-the-priority-when-adding-a-2nd-corosync-network-to-upgrade-to-a-redundant-ring-network.99688/
-
Uubu replied to the thread Kritischer Ausfall – gleichzeitiger Reboot aller Nodes nach iSCSI-Verbindungsverlust (Proxmox + HA + Softdog).Haben Sie mehrere redundante Ringe im Corosnc konfiguriert? in /etc/corosync/corosync.conf