Search results

I have gotten a few week without error. However, for a particulat VM I am getting Blob too small error again. I went back to the last VM backup without errors and deleted the ones with errors. Ran a backup using Stopped, still got an error. Odd behaviour since another Node I am backing up had...

I was having the same issue. Memory was hovering around 90%, after uninstalling Virtio Balloon it dropped to around 20-30% which is inline with another server VM I have running. Main difference is the other server has more physical RAM allocated to the node with 64GB vs. 16GB. However, the 64GB...

Is there a way to schedule verification of each backup after it's completed? It doesn't have to be done right after the backup is done, but in some timely manner. I found a script to run a verification, but it will verify every single image of every backup which I think can be redundant unless...

This may not be the correct place to post, but I am trying to find a solution to this issue. I just started using rclone to backup my files from a Proxmox node to a remote location on a Synology NAS. However, I realized that partial backups could complicate things using rclone alone. I saw...

An update. I did a backup from my local network with the downloaded remote backup and the verification passed. Now I am going to try and complete and incremental backup from the remote location. The image I had is a couple days old so this may take while to sync up. So to the external USB passed...

@fabian My setup is almost like @luphi I have made a vzdump and brought it local to make a backup to PBS as well, however I got the same error of the blob being too small. My other non vm backups work, but not the Windows Server 2016 one. I'm wondering if it could be my disks which are VM...

@fabian This is the logs from my email notification after the backup was complete. The PBS is running as a VM on PVE 6.2-10 and the store1 is a vmdisk ext4 I believe. I have another vm that backed up to that store and the restore was successful. Albeit the VM was only 32GB total about. I am...

Thank you @fabian This was the latest output from a verification I just ran. verify store1:vm/107/2020-08-08T22:45:02Z 2020-08-11T05:54:07-04:00: check qemu-server.conf.blob 2020-08-11T05:54:07-04:00: check drive-efidisk0.img.fidx 2020-08-11T05:54:07-04:00: check drive-scsi0.img.fidx...

Sorry for the late reply. I am just coming around to this idea. Am I able to do a local backup. Restore it on a remote server, back it up to PBS and then continue my backups from the original server to the PBS backup image made from the local backup to remote server? Essentially...

Any developments? If the verification fails, is there any way to repair it? Or remove those backups and start new? Does it matter whether backups are Snapshot, Suspend or Stop for the incremental VMs? Thanks.

I am having this blob issue as well. I am having trouble restoring a Windows Server 2019 Standard VM backup wich shows as 1.17 TiB. On ther other hand, I have a 32 GiB Debian VM wich restores fine. I am running a verify task on the PBS server as well.

Could this somehow be related? I was perusing the BIOS settings and noticed a SMEE setting which is disabled, Found a link https://developer.amd.com/sev/ and this https://www.supermicro.com/support/faqs/faq.cfm?faq=30017 Should I turn it on?

Good morning everybody. Since last week, whenever I reboot or shutdown then power on my Proxmox server I get this error. Can anybody help me decipher it? Not entirely sure what it is, but last week I upgrade the BIOS on my Supermicro Motherboard M11SDV-8C-LN4F AMD Epyc 3251 SOC with 2 dimms...

I thought the Server VM was running normally, but I got a call from the office that it was not serving up its SQL Express database, in which case I had restart the node since I could not start the VM itself anymore. Here is my pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.44-2-pve)...

thank you @harry700 It is not part of a cluster. These are stand a lone nodes. I tried pvestatd status which shows it is running. Did a pvestatd restart and it’s the same question mark remaining.

I have had some weird behaviour. A couple times I have gottent Exclamation Marks on the Node and VMs the Proxmox Node which my PBS was running from. I think this had to do with exceeding the Hard drive space allocated, hence resulting in an I/O Error. I freed up some space on that particular...

I am getting Question Marks and Greyed out Nodes and VMs. The servers keep running, but not sure what is really happening. It happened yesterday as well to another node. When I restated it, it seemed to work. Any help or atleast pointers in the right direction to find out what is happening would...

MY Smart version is: smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.44-2-pve] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org I didn't manually update it, but I am running PVE version 6.2-9 atleast. The last time I manually updated smartctl was when...

I am trying to figure a few things out. I am following up on this drive. We took it out at one location, but the other location wanted to downsize, and didn't have the funds to build a new server so I put this in temporarily. They tell me for a few months, but who knows. Anyways this is my...

@RobFantini Didn't you just give me instructions on how to do that? Or do you mean, how do you connect an existing store to a PBS Server? I followed your instructions, but I eventually crashed all my VMs with an I/O error probably since I exceeded my VM Drive space. I had to clean things up...