Search results

Just ran into this exact issue. Was using VirtIO drivers 0.1.229 and everything was fine and no issues until I added a 3rd virtual disk that was a local LVM mechanical HD. I did not have any issue prior to adding this virtual disk and removing it would restore stability. The virtual disks...

I just wanted to provide an update on this. We have been running a couple deployments of PVE/PBS with an local disk datastore, then added a 2nd datastore pointing to the NAS. We configured a Remotes and Sync as 'localhost' and backups and restores are working great. The dirty bitmap status for...

Our use case is a growing number of small businesses that have datasets that have begun to accelerate in size, this has begun to challenge our existing backup methods. What I want to do is have the most reliable and efficient backup that they can afford. Budgets are not big in my town, and many...

I just wanted to chime in on this. We recently began migrating to PBS from VM side backups. We have run a combination of 'internal' / 'NAS' / 'External' backups. All the SMB servers we have setup have an internal backup SSD, an onsite external NAS backup, followed by a offsite backup. The...

Thanks for the suggestion, I will try that out.

We are beginning to use Proxmox Backup Server in place of the classic PVE Backup (vzdump), and we are trying to achieve chained backups (see: https://forum.proxmox.com/threads/chained-multiple-destination-backup.88106/). Since the backups are scheduled from the PVE side of the equation, I was...

We migrating small single server setups to use the new Proxmox Backup Server as opposed to in VM backup software. Previously we used backup software within the VM to to block level backups that would do a image type backup to a local storage drive, followed by a backup to a physically separate...

I have a small 3 node Proxmox/CEPH cluster in which I had the Proxmox boot drive fail on one of the units. Despite this, all the virtual machines continued running, and the CEPH portion continued running. I have since been able to shutdown the virtual machines and migrate them to the other...

Compression is on. FIO is supposed to use random data, but I have never really looked at what the random data looks like. We are writing to a zvol created by Proxmox when we create the VM within the GUI. The reference to the record size was my mistake I mixed up the terms...

I completed another quick test using ashift=13 and 32k blocksize (recordsize), and sync=0, this should provide some indication regarding compression. fio --ioengine=libaio --rw=write --bs=4k --numjobs=1 --iodepth=1 --size=1G --buffered=1 --name XXX --filename=/dev/sdX (Write Amp ~0.28X) fio...

While I have always known about ZFS write amplification I have never really tested or investigated the exact amount that was occurring on our Proxmox server builds. I recently wrote a post investigating performance of the various local storage options...

I have quite a few servers I manage, most are for SMB clients and some are coming up on server refreshes. I have been using Proxmox since v3.4 and we use a Proxmox CEPH cluster that we use within our own network, and am reasonably familiar with the product. The main focus I have is in...

We do use ZFS on all our Proxmox hosts. We initially moved the swap off of the ZFS and to a separate partition on a different drive. I just finished moving the swap back onto a ZFS zvol a few minutes ago, and will be closely monitoring the situation now that you pointed out the potential issue...

We had looked at every log we could think of that may contain info, syslog, daemon.log, messages, kern.log. They log simply showed everything working on one line and the next was a line indicating it was booting. As the system has IPMI capability we decided to record the console, hoping to...

Well just a quick update, the Proxmox Host crashed and rebooting itself a few minutes ago. Unfortunately that means I have to rule out the Win2k8R2 as the problem.

We are in the process of migrating our last ESXi based host to Proxmox. The problem is the Proxmox host is crashing and rebooting. There are no errors in the log and the system is located at a remote server location (not hosted, our hardware and location). We have been running this system in a...