@cbaguzman Thank you! unfortunately, I can't reproduce that. After the update backups were not working at all. Even those that "worked" when trying to restore it failed to do so. So we decided to reinstall 8.2 and don't do updates. But in the process, we think we configure things differently. Now we can't reproduce what we did before even with the documentation we have. The moral of the story? don't create backup systems too complicated
F
Posts
-
RE: VDI_IO_ERROR(Device I/O errors) when you run scheduled backup
-
RE: VDI_IO_ERROR(Device I/O errors) when you run scheduled backup
@stormi There is really nothing there. I've checked but nothing related to this problem. Now let me explain my setup, maybe I am doing something wrong.
- XCP-ng 8.2 with a VM (Debian, XOA)
- I've created a LV storage and attached it to the XOA machine.
- I backup "locally". The remote is a "local" storage on the XOA machine but it is indeed a LVM which is located in another disk. I hope I make sense.
- The VMs to be backed up are in another xcp-ng servers.
The problem appears to be that it does not have permission or it cannot written into that LV partition.
The weird thing is that it worked before, and after we updated all our hypervisors, it stopped working.
To test out, I've created a VM in the same hypervisor where the XOA is located and try to backup that very machine and I've got the same error.
-
RE: VDI_IO_ERROR(Device I/O errors) when you run scheduled backup
@olivierlambert no more feedback on this problem. We reinstall the whole server, XCP-ng 8.2 and we are still experiencing this problem. We are unable to do Delta backups.
-
RE: VDI_IO_ERROR(Device I/O errors) when you run scheduled backup
@stormi The problem continues. I decided to reinstall and not do updates and we are experiencing the same problem.
-
RE: Introduce yourself!
@olivierlambert Thank you so much for your hard work! XCP-ng is incredible!
-
RE: VDI_IO_ERROR(Device I/O errors) when you run scheduled backup
Having the same issue after the latest update in 8.2. It was working fine before. I am not sure what caused the issue. Is there a way to revert the latest update?