Search results

ZFS RAID1 Mirror is a very common for Proxmox OS drives. For actual wear of SSD/NVMe, kind of RAID does not really causes any more wear than non-RAID. If anything else, wear might be lower on a full RAID such as RAIDZ2/RAIDZ3 etc because bits of data are scattered across multiple drives instead...

Multi tenancy never has been a focal point for PMG..... yet. For this reason some of the needed feature to operate a multi-tenant environment simply does not exist. As of PMG latest, no way to search quarantine other than Email and Sender as you know already. We tried to dig deep to have a way...

This seems to happen time to time due to Browser. Try a different browser and it should work. Using same browser from a different machine also seems to work. I have seen this happening more on Chrome browser than others.

Adding the Incoming/Sender email address in the Configuration > Mail Proxy > Whitelist is enough to prevent any block. One reason it could be that the email is not always coming from same specific sender but perhaps an array of possible email address. Try to add the whole domain and see if it...

If you regularly create similar configuration of VMs, you can create a blank VM with or without disk image and turn it into a template. Then whenever you need a VM, just clone it. Use full cloning instead of linked ones. This is much faster than creating new VM even if you could change the...

Very true. You can also mitigate issues due to power failure, by using safer Cache mode such as WriteThrough or DirectSync at the cost of performance. Raw disk image will also shield you from some of the power or abrupt shutdown related issues. XFS file system is notorious when it comes to...

First question is, how were you cleaning up Snapshots? From the Proxmox GUI? If this is the case, Proxmox will never delete the VM disk image. Because from the Datacenter > Node > VM > Snapshot interface, you simply do not have access into the VM disk image itself. If you were cleaning up...

As @cwt mentioned, you can bind SSH daemon to a specific ListenAddress. This is the IPv4 that the interface is configured with. Binding to a the Proxmox node management IP will not break anything. As @cwt also pointed out, firewall rules is also an option. In most cases this is probably...

The isc-dhcp-client is responsible on the Debian side to receive correct IP based on MAC. It is installed by default. But for some odd reason it is not: apt install isc-dhcp-client Tried to forcefully release and renew IP?: dhclient -r <interface> dhclient <interface> Also check the content...

The Assigned to LV percentage that you see, it just shows how much of the physical drive is used for that LV. That is not the actual usage of the data stored. Also this question is not really the Proxmox Datacenter Manager related. It should be in the Proxmox VE section.

That is correct. It is not a concrete number. Only the administrator of the environment can tell how much new data is being written on day to day basis. 5% in my opinion is a safer overall figure for the sake of calculation with little bit of overestimation. There are some environment which does...

I agree with what @UdoB said in the previous post. In addition to that, here is a scenario that should help you understand slightly better and size your PBS: In this scenario, the space used by all VM is 50TB. It is a rough estimate. Hope this helps. Retention is 3 daily, 2 weekly, 6...

I upgraded one of my test Proxmox node to 8.2.2 and since then I am seeing the following error on Ceph > Monitor dashboard. malformed UTF-8 character in JSON string, at character offset 1093 (before "\x{fffd}/\x{64f}\x{fffd}...") at /usr/share/perl5/PVE/RADOS.pm line 277, <DATA> line 960...

Did the issue start recently? Are you using backup Fleecing feature?

If your Synology NAS sitting useless and you cannot use it for anything else, it makes sense to use it to store your backups via a NFS or iSCSI mountpoint. Yes it wont be the best performing backup server but your scenario looks like you dont have very large backup needs into several terabytes...

Since this is a backup server, I would go with the first option with Intel E5-1650 CPU. Put the other one for heavier load such as VM node. Better use of hardware in my opinion. That also has 256GB RAM. So use of ZFS storage in Raid-Z3 would give you much more usable space while tolerating 3...

Another option perhaps would be to create a new PBS datastore, that way each backup job will backup to each datastore with own pruning and schedule. If you are using ZFS storage, its just a matter of creating a new dataset and use that for the new datastore.

I am unclear what you are meaning by 2 hosts. Do you intend to create 2 separate PBS nodes? Easiest thing would be of course to replace the PSU. I am assuming it is not possible in your current scenario. If your original ZFS drives are intact from the PBS, you can simply transfer all the drives...

No, it does not matter, if that's the specific setup you are looking for. I will give you my version to make this work. It comes down to if the hardware supports it or not, really. - First thing to check if the CPU and Mboard supports IOMMU (Inet VT-d for intel, AMD-VI for AMD). - Also have...

@Dariusz Is there any particular reason you don't want to use bridges? That will be the simplest and cleanest configuration without extra layers. This sort of passthrough setup will always depend on the hardware itself. If the NIC goes, you will be down till you find another suitable replacement.