Search results

by the way, I did try to do qm migrate 3382 pve3 --with-local-disks —online and still got the same exact errors so, I emailed the users on that VM for a 15 minute window to test .. I shut the vm down, and did the qm migrate 302 vm3 --with-local-disks —online and it worked, it migrated in just...

I have a cluster with 5.3, all ZFS. For some reason (no idea) one of the nodes rebooted, how can I find out why?) The VMS that were on that node migrated to the assigned rotation on the HA, a few hours later (when I do my daily check up) I see some VMS errors on the tasks list Upon...

Well, I have created 2 backup jobs to compare. One no compression, the other with LZO compression. I am no expert at compression algorithms, but I do not think that a saving of 15gb is worth it 1 hour and 30 minutes of time wasted that makes other backups timeout. But, another VMs do get...

It was rhetorical, in theory anything you do inside the VM has not repercussions on a proxmox level activity, unless the filesystem is in constant change. This is actually one that has very little workload, 4 times a day. 15 minutes. Last activity is around 5 pm, backups start at midnight...

Thanks. How do I ls inside a windows vm? :) I have other backups that are way faster.

Sorry, I changed the replication times, the only real problem was the FIRST time, after that it is just seconds.

Working with Proxmox since summer 2017, everyday I realized how little I know about this big platform.

Hi, I have a USB attached to one of the nodes , for a dedicated backup of a few VMs (on the same host, so no network here, just plain USB connection) it was taking over 2 and half hours to backup 46 GB, so I changed the backup to the local hard drives and still takes a long time Actually...

In case this helps somehow.

Hi, I have done resizes many time with qm resize <vmid> <disk> <size> , always growing disks, now I have a situation with a VM (win 2012r2) that is behaving very slow, so I moved a lot of pieces to another VM and now I am left with a hard drive that used to be 400GB+ used to be only 25GB. I...

Thanks.. I do not understand then why sometimes it tells me either timed out of could not get lock.. I am quite sure the next time around it syncs, but it is scary to have to check daily .

So, basically you imply that there is no way to 'stager' the replications? Does not matter if you put 12 min, 15 or 17, eventually at the 00 they will all be at the same time? that seems to create a lot of work at the same time.

Has anyone realized that does not matter the 'timing' you setup for the replication, it ends up falling out of its expected schedule to SYNC with round time? This one shows next sync will be in both at 13:00 even that it is NOT supposed to happen at that time for the bottom one. 12:37 + 00:37...

Yes, I can bring the servers down, one at the time without impact, but still do not see HOW to add the other drives as a different pool ,, and maybe use a different type of zraid (like mirror) to make it faster

Not sure what the number tells, where can I read about that? That would mean losing what I thought was the advantage of raidz2, best of both worlds passing the divers directlyu to proxmox and let zfs deal, instead of using a hardware raid, which I was told many times is not good since zfs does...

Finally restore finished That is a little over one hour to restore ..

Hi, I have a new Cluster, setup to what I understood was best practices each node with 2*6 cpu, 4*1tb sas disk on raidz2, 128 gb ram, separate bond network for corosync, etc.. everything that I have learned and put together over the last year. But, this new cluster is VERY SLOW, much slower...

Great , thanks , I was not aware of this tool .. I have put all 3 nodes on a 75% load for 2 hours.. Let's see.

Can you point to any tool in particular? I have run this server already with a few VMs and has not happened again but of course, cpu usage never got over 25%. With the import that it rebooted, cpu only got to 4%. And with all the new attempts also to about 4% and did not reboot.

This way worked perfectly fine. The imported machine works fine. I am concerned with the importdisk tool .. etc.. but I can't fix it.