Μερλιν's home

User Tools

Site Tools

You are here: Μερλιν's home » Notes » Proxmox virtualization cluster
notes:proxmox

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
notes:proxmox [2024/05/22 04:24] – Nikita Kipriyanovnotes:proxmox [2024/06/26 06:33] (current) – [ECC error notifications] Nikita Kipriyanov
Line 41: Line 41:
  
 Other COM port is used with another speed here, just for illustration. Notice also, instead of separate ''GRUB_TERMINAL_INPUT'' and ''GRUB_TERMINAL_OUTPUT'' I use a single setting for both. Other COM port is used with another speed here, just for illustration. Notice also, instead of separate ''GRUB_TERMINAL_INPUT'' and ''GRUB_TERMINAL_OUTPUT'' I use a single setting for both.
 +
 +==== Fast reboots with kexec ====
 +FIXME this needs more work
 +  * https://forum.proxmox.com/threads/tip-fast-reboots-with-kexec.35624/
 +  * https://forum.proxmox.com/threads/proxmox-7-fast-reboot-with-kexec.93422/
  
 ==== Time sync ==== ==== Time sync ====
Line 50: Line 55:
 chronyc reload sources chronyc reload sources
 </code> </code>
 +
 +==== ECC error notifications ====
 +
 +Install `rasdaemon` utility to receive reports from hardware via EDAC interface and get them into logs.
 +
 +See [[https://www.setphaserstostun.org/posts/monitoring-ecc-memory-on-linux-with-rasdaemon/]]
  
 ==== Backup ==== ==== Backup ====
Line 61: Line 72:
  
 ''0'' means "use half of available cores". If you know the number of the cores in the target system, you can use other, more tailored settings here. We set ''pigz'' too, just for the case somebody changes to gzip. ''0'' means "use half of available cores". If you know the number of the cores in the target system, you can use other, more tailored settings here. We set ''pigz'' too, just for the case somebody changes to gzip.
 +
 +**Note:** it's possible to [[https://forum.proxmox.com/threads/reading-blob-files-qemu-server-conf-blob.95551/|read blob files]] directly on the server, either with `proxmox-backup-debug` or "by hand":
 +<code>
 +proxmox-backup-debug inspect file /path/to/blob --decode -
 +dd if=/path/to/blob bs=1 skip=12 | zstdcat
 +</code>
  
 === Node backup === === Node backup ===
-Hosts may need backup, too. Theoretically we need "thin" backups as barely needed for the recovery, as explained here: https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster#Re-installing_a_cluster_node . Yet, I still find it useful to do just full host backup. It will not be very large (in my experience, 2 GB at most), it will be strongly deduplicated (between backups of same node and between nodes — they're similar), so why bother?+Hosts may need backup, too. Theoretically we need "thin" backups as barely needed for the recovery, as explained here: https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster#Re-installing_a_cluster_node . Yet, I still find it useful to do just full host backup. It will not be very large (in my experience, around 5 GB), it will be strongly deduplicated (between backups of same node and between nodes — they're similar), so why bother?
  
 It is useful to create a simple shell script and run it, say, mounthly: It is useful to create a simple shell script and run it, say, mounthly:
notes/proxmox.1716351890.txt.gz · Last modified: by Nikita Kipriyanov