Search results

That's what I said. You will not be able to use borg with a dataset using raw files. When specifying zfs send/receive, I was talking about sending the dataset to another remote server using ZFS and ditching borg. Borg is fantastic but in your case you won't be able to use it. You could try to...

Unfortunately, you don't have access to the files directly in the snapshot like an LXC container dataset. This will not work with borg since you are trying to backup 1 giant raw file (like an archive). Incremental will not work since the whole file as changed therefore it will be backed again...

Normal. Read here: https://docs.oracle.com/cd/E23824_01/html/821-1448/gbchp.html

Now you can just enable NFS/CIFS mounting from the webui under Options-Feature instead of enabling nesting

Sure. Take a look at my post here where I show the procedure.

Unfortunately I don't have any existing scrips that does that but it's pretty easy. Depending on the file system you are using on your host you can use curl to probe the site and if it returns a certain code then restore the snapshot. I found this link maybe it can help. The automatic snapshot...

You can easily create bash scripts that do all this stuff and run them on your host using the crontab

Check out borg for your backups assuming you don't have another node for ZFS send/receive. We are using it in production and it's awesome. This is one of the best option if you want compression/incremental backups. The easiest way to go would be to use the Proxmox webui built-in backup option...

Your hostname in the DNS tab of your container should be the hostname and not the FQDN. It should be like this: Container hostname: production-1 Host search domain: example.com Which would set the FQDN in your container to example-1.example.com There is no need to mess with /etc/hostname and...

Set the hostname in the DNS tab in the webui. The search domain of your host will then be happened to form the FQDN wich will be persistent when rebooting.

Here's a simple script I wrote for our Nagios that monitor errors with the replications #!/bin/bash # Script to check Proxmox storage replication # ExitCode: # 0 = Ok # 1 = Warning # 2 = Critical # 4 = Ok (No replicatons configured) RESULTS=($(/usr/bin/pvesr status | awk 'NR>1 {print $7}'))...

ZFS snapshot and borgbackup of the snapshot to a NAS

I also recommend this. We have a custom made backup script that creates a ZFS snapshot and using borgbackup backup the snapshot at the file system to a NAS. With this we can restore a single file or a whole container if needed. The whole thing is made while the container is online. Even if you...

Yeah this is weird, maybe a bug in the version of Proxmox I use. Thanks for your help anyway

Here's the ouput: vm.swappiness = 0

As mentionned in my OP, I did reboot to apply the changes but to no avail.

Will do ! Thanks for your help

I'm using Nagios with a custom script that reads /proc/meminfo of the container. The Nagios report is consistent with what I'm seeing in the Proxmox webui. Here's free -m from a container total used free shared buff/cache available Mem: 1024...

After reading the 6 pages of the thread, I'm still not sure if upgrading from the no-sub repo to the entreprise repo will overwrite the packages with the more stable version if they are a version behind. For example, let's says on the no-sub repo (and currently installed on the host) there is...

Yes I'm aware of that but based on what I've posted originally it's like the container is swapping even if the swappinness is 0 and there is plenty of ram available. We have some monitoring software in place to monitor the ram so it should never be full and if it even gets high we can act...