https://forum.nakivo.com/index.php?/discover/NAKIVO Community Forum - All ActivityenHi @Gianluigi, Please check whether there is any disk maintenance (e.g., defragmentation) running inside the machine, as this could affect the disk system at the block level and the incremental backup size.Thu, 16 Jul 2026 16:02:57 +0000Thu, 16 Jul 2026 10:34:19 +0000Hi, I scheduled a backup on Wasabi. After the first full backup, the incrementals followed correctly. On a certain date, even though it shows the backup as incremental, they seem like full backups based on the space used. Can you help me? ThanksTue, 14 Jul 2026 10:07:17 +0000Dear @Gavino, Our development team has provided a new build (11.2.1.106615) to fix your current issue. You can update your NAKIVO to the custom build below, which includes a hotfix for the certificate issue in the QNAP App Center. + QNAP transporter x86_64: https://maglar.box.com/s/c1itcwaj3xvbk80f7uenqhuhbh5tqruy + QNAP transporter ARMx64: https://maglar.box.com/s/vgqqp8lonmyxh8a8jdaewbs0u282n1a9 + QNAP x86_64: https://maglar.box.com/s/qymklfu6na6tx97zf29out7r9t3qlu3m + QNAP ARMx64: https://maglar.box.com/s/84a4xyn95l3gggjb0s5eumwlsf4t09yj - Refer to this article to update your NAKIVO instance: https://helpcenter.nakivo.com/User-Guide/Content/Deployment/Updating-NAKIVO-Backup-and-Replication/Updating-on-QNAP-NAS.htm Before the upgrade, please ensure the SaaS/ CIFS/ NFS repository type is detached https://helpcenter.nakivo.com/User-Guide/Content/Settings/Backup-Repositories/Managing-Backup-Repositories/Detaching-Backup-Repositories.htmFri, 10 Jul 2026 11:55:34 +0000Fri, 10 Jul 2026 11:47:35 +0000Theese are info about qcow files failed to consolidate on proxmox. 043c65d6-b6f5-4f39-b27d-74ac7c31eb1a.qcow2 7f552c38-ead4-4221-b94e-760aa06f0901.qcow2 root@prxtichos:/opt/nakivo/bptmp# qemu-img info 043c65d6-b6f5-4f39-b27d-74ac7c31eb1a.qcow2 image: 043c65d6-b6f5-4f39-b27d-74ac7c31eb1a.qcow2 file format: qcow2 virtual size: 50 GiB (53687091200 bytes) disk size: 64.5 KiB cluster_size: 65536 backing file: /dev/zvol/ssd_pool/vm-100-disk-1 backing file format: raw Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false extended l2: false Child node '/file': filename: 043c65d6-b6f5-4f39-b27d-74ac7c31eb1a.qcow2 protocol type: file file length: 640 KiB (655360 bytes) disk size: 64.5 KiB root@prxtichos:/opt/nakivo/bptmp# qemu-img info 7f552c38-ead4-4221-b94e-760aa06f0901.qcow2 image: 7f552c38-ead4-4221-b94e-760aa06f0901.qcow2 file format: qcow2 virtual size: 50 GiB (53687091200 bytes) disk size: 64.5 KiB cluster_size: 65536 backing file: /dev/zvol/ssd_pool/vm-100-disk-1 backing file format: raw Format specific information: compat: 1.1 compression type: zlib lazy refcounts: false refcount bits: 16 corrupt: false extended l2: false Child node '/file': filename: 7f552c38-ead4-4221-b94e-760aa06f0901.qcow2 protocol type: file file length: 640 KiB (655360 bytes) disk size: 64.5 KiB This is the nakivo error: My question is, i have to consolidate the most recent file because the are 2 overlay file.Wed, 08 Jul 2026 08:24:31 +0000Hi @opk.giandomenico, Could you give us a bit more context on where NAKIVO is involved here? We want to make sure we can actually help! If it's a Proxmox issue, it is better to contact the Proxmox support team.Wed, 08 Jul 2026 08:10:20 +0000Hello @Gavino, We want to provide you with an update on the status of your case. Our development team is investigating the issue and working to find a resolution as quickly as possible. We expect to have another update within the next few days, and we will keep you posted on the progress. Thank you for your patience and understanding throughout this process.Tue, 07 Jul 2026 12:13:57 +0000Hello, i have a consolidation error on a proxmox environment, i have 2 overlay files to consolidate on the same vm, i think that i have to consolidate the most recent one. What i have to do with the the older overlay file? could i remove it is there a best practice to follow and avoid data corruption? Best regardsTue, 07 Jul 2026 08:57:03 +0000Mon, 06 Jul 2026 14:34:40 +0000Thu, 25 Jun 2026 15:08:59 +0000Hi @Miguel Angel, Thank you for your patience. According to information from our product team, for now there is no ETA on this improvement. Should you need any further information, please do not hesitate to contact NAKIVO support team at support@nakivo.com.Wed, 24 Jun 2026 13:11:28 +0000Hello @Gavino, Thank you for sharing your feedback. We have forwarded this information to our developer team for further investigation. We are actively working on resolving this issue and providing a solution as quickly as possible.Tue, 16 Jun 2026 07:36:24 +0000Hello @jkool, Please submit a support bundle from your environment. This will help our team verify your current deployment configuration and assist you more accurately.Mon, 15 Jun 2026 10:45:25 +0000Proxmox VE 9.1: Full backup and recovery support for workloads running on the latest Proxmox VE release The latest Proxmox VE release is actually v9.2 released 21st of May https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_9.2 - well before this June 4th announcement. Getting support is becoming very frustrating. When PVE 9.1 was out, Nakivo only supported PVE 9.0. Then PVE 9.2 comes out and only then do you support PVE 9.1. It seems like I can never get support from Nakivo if you are always behind. This is because with PVE - at least exposed in the web GUI - there is no option to pin to a particular point release. All the critical security patches and point release updates come down at the same time. If I was to just ignore the updates then sure - Nakivo would eventually catch up. But then I am vulnerable. Also I have to upgrade at some stage, and if you are always one point release behind the latest version, when I update (which would be to the latest version - again I cannot choose a point release) I would again be in front of what Nakivo supports, and again your support team would choose not to support me - a paying customer - as has happened recently when I wanted support for an issue yet because I am on PVE 9.2.2 (as I want the latest security fixes) I do not get support running the latest version of Nakivo. Another issue - "NBR_Transporter_v11.2.1_Updater_QNAP.qpkg" package which is the transporter (not director) package for x86_64 QNAP, it says that the digital signature is expired. I just checked the Nakivo download site and saw that the package there as I write this still has the expired certificate. This has happened in the past and Nakivo have eventually rectified it. That fact that it is still happening though does not speak good things about this company.Sat, 13 Jun 2026 07:08:24 +0000Need the transporter OVA fro 11.0.1.89945 We can not do a full upgrade on all components just yet, so we have to stick with the older versionSat, 13 Jun 2026 04:37:51 +0000Hello I can confirm that the file share feature is now in our NFR license and we can access the features Regards, MarkusThu, 11 Jun 2026 15:29:44 +0000Hello, We have created a feature request for our product development team for further review.Thu, 11 Jun 2026 15:26:00 +0000Hello @Markus Obermeier, Our sales team has sent you an NFR license. Could you please confirm that you have received it and let us know whether you can access the features you need for testing? We appreciate your partnership and look forward to your feedback.Thu, 11 Jun 2026 15:22:28 +0000Free version I don't see this value system.repository.remove.backups.used.by.jobTue, 09 Jun 2026 21:55:15 +0000thanx for the explanation - is it possible to create a file backup of physical machine where only necessary folders are included and create a disaster recovery for this ? and if so - how can the system files (see screenshot) be included ?Tue, 09 Jun 2026 12:15:51 +0000FILE backup for a physical machine does not allow to include OS Folders while complete backup of physical machine does not allow to exclude subfolders: it would be great if a complete backup of a physical machine could be made without e.g the "temp" or the "downloads" folder - then also a disaster recovery could be made for the physical machine without the unneccesary content of temp or download (or what folder ever)Tue, 09 Jun 2026 12:11:09 +0000Thu, 04 Jun 2026 09:45:29 +0000Hello, Thank you for your suggestion. The feature request has been submitted to our product team for review and consideration. Should you need any further information, please do not hesitate to contact NAKIVO customer support at support@nakivo.com with your ticket ID #406258.Wed, 03 Jun 2026 08:13:01 +0000Hello @Markus Obermeier, Physical backup is performed on a disk/partition level. It is not possible to exclude particular files and folders. To minimize recovery time, disks/partitions that are not required to boot may be excluded.Wed, 03 Jun 2026 08:07:22 +0000