Search results

This morning we had some power outage issue on our server room, all nodes recovered except one. This node is part of (one of three) ceph cluster , (pools are set to replication 3) so the data is safe and the cluster is stable, (excluding ceph warning) Any idea how i can fix it?

the proxmox host had the same ram usage as before: the max ram available to the vm was marked as used, even when the vm used around 1% of the ram

i installed virtio and enable the flag, but the system still uses all ram and it is not shared i see "BalloonService " running on windows

I assume that this is impossible, but ill ask this anyway. i need to put one lxc (ubuntu) and one vm on each host (for large computational tasks) somtiems we need windows and sometimes we need linux the problem that the VM need to have all the ram prealocation and not freed when not in use...

nfs (qnap based) over 40GB network. tmp dir is default (what come pre configured with proxmox)

how i can pull only the relevant file ? libpve-common-perl >= 6.2-3 i did not see instructions

proxmox 6.2-12 any idea? INFO: starting new backup job: vzdump 140 --storage vqfiler1-lxc --remove 0 --node pve-srv1 --compress zstd --mode snapshot INFO: Starting Backup of VM 140 (lxc) INFO: Backup started at 2020-10-02 15:37:29 INFO: status = running INFO: CT Name: grid-master INFO...

i have lxc containers hostes on ceph storage (with speed over 5GBs ) when making backup using zstd the speed is between 20-90MBs the storage i am writing to store the backup have read/write speed around 1GB proxmox 6.2.12

my mistake, repository was on strech insted of buster . updating .. upgrade fixes the issue, thanks

most nodes are 6.2-11 (oldest is 6.1-2) (upgraded but did not rebooted yet)

on some hosts the ZSTD backup compression is not working? any idea why ? this is the error? Parameter verification failed. (400) compress: value 'zstd' does not have a value in the enumeration '0, 1, gzip, lzo' solution: upgrade proxmox to latest version on all nodes.

i think i found something that cause it, hope you can recreate it: i just run manual back on lxc container (Ubuntu 18.04 ) with multiple nfs mount points, but one of the nfs mounts is unavailing (down) once the backup failed with the following error: INFO: excluding bind mount point mp7...

Nope, i guess i missed it, I thought this relatively basic and that that is already implemented.. * we did not change the ID or the name Ill probably wait for a beta of PBS to end..

We usually got for enterprise refurbished hardware (dell\supermicro 1-5 years) and used (but relatively new sas ssds 1-2 years old)) I guess our top budget for this is 1500$ (including storage) We dont need high (around 5-10TB redundant , with some scale options in the future) The question if...

this is for our work,currently all our CT's are ceph based (3 replication), it should be solid enough, but a bug in the ceph core can cause a issue that is beyond my capabilities to fix. so i am looking for something to feel safe ( another backup off site will be added later) what are the best...

Does the PBS require same storage as the normal proxmox servers? Currently have mainly lsi cards in IT mode. Will it work the pbs? Any suggestions on minimal requirements?, all i could find is 8GB ram, and high grade boot drive

i have a scheduled backup. on a nfs VZDUMP backup file that configured for 2 backups. the script files withe the following reason :ERROR: Backup of VM 112 failed - There is a max backup limit of (2) enforced by the target storage or the vzdump parameters. Either increase the limit or delete...

only solution i found so far is to delete the binds (nfs mount) clone and then remake them any other solutions ? example for bind that fails: mp3: /mnt/pve/docs,mp=/mnt/docs,backup=0,shared=1,replicate=0

i gave up. ill find another use for this server. thanks everyone

the first step i took is to upgrade all hardware, ipmi, bios .... yes same error on 6.2. running upgrade and dist-upgrade now