@pierrebrunet I updated and did a backup test with a smaller VM. It worked; it's no longer deleting the VMs backup. It still issues an alert about possible file corruption, but I restored it using XOCE and it restored normally.
Thank you for your help.
Best posts made by FagnerMoraes
-
RE: XO error/warning: Clean VM directory. unhandled error while checking alias.
Latest posts made by FagnerMoraes
-
RE: XO error/warning: Clean VM directory. unhandled error while checking alias.
I performed a full backup and a delta backup test.
The full backup is working, but the delta backup is not.If you look at the image, I performed 2 full backups successfully, but the first backup, which is not encrypted and is a full backup, is not here — only the .json file that generated it is present.
Where would the delta backup be located if not in the same folder as the others?
According to the log, I only saw the same location being used.
-
RE: XO error/warning: Clean VM directory. unhandled error while checking alias.
@pierrebrunet thats a metadata backup works fine:
Metadata works fine.txt -
RE: XO error/warning: Clean VM directory. unhandled error while checking alias.
@pierrebrunet
thats a metadata backup works fine, no alerts and no clean directory.
Metadata works fine.txt -
RE: XO error/warning: Clean VM directory. unhandled error while checking alias.
On the S3 storage, the backup is being saved correctly and the old files are not being deleted unexpectedly.
Using the same backup configuration, the directory cleanup process is not executed twice there.

-
RE: XO error/warning: Clean VM directory. unhandled error while checking alias.
Hello again,
When running the backup routine to the NAS, it is not saving the file anymore.
Please check the image showing:
the backup routine,
the path it points to on the NAS,
and the contents of the folder.The .XVA file was not saved.

-
RE: XO error/warning: Clean VM directory. unhandled error while checking alias.
@pierrebrunet I updated and did a backup test with a smaller VM. It worked; it's no longer deleting the VMs backup. It still issues an alert about possible file corruption, but I restored it using XOCE and it restored normally.
Thank you for your help. -
RE: XO error/warning: Clean VM directory. unhandled error while checking alias.
This is just a backup test that shows the same problem as in production.
The file is uploaded to the folder, then the verification error and file corruption alert are displayed.
Since the routine retains 3 copies, it ended up deleting the files that were working, and with the error I was left without backups.
I had to export the VMs to have at least one copy.
All packages are up to date and it is on the latest commit version.{ "data": { "mode": "full", "reportWhen": "never" }, "id": "1780237144366", "jobId": "90c1a9ac-be57-4084-a009-abea039c324e", "jobName": "Teste-BKP-RNP", "message": "backup", "scheduleId": "b603f95a-c230-4bb8-baf1-05d7b1906ae1", "start": 1780237144366, "status": "success", "tasks": [ { "id": "0mptv8soh-y67yux15fk", "start": 1780237166129, "status": "success", "tasks": [ { "id": "0mptv8u2z-z07gqebx7e8", "start": 1780237167947, "status": "success", "end": 1780237245751, "result": "7e51389c-fece-1b94-2a69-e097684f90d5", "message": "snapshot" }, { "id": "0mptvai62-dj05w24lbzp", "start": 1780237245818, "status": "success", "tasks": [ { "id": "0mptvai6g-wo1kemu62r", "start": 1780237245832, "status": "success", "end": 1780239711489, "result": { "size": 125955945472 }, "message": "transfer" } ], "end": 1780239711655, "message": "export", "data": { "id": "4e24de58-14a2-4cff-ae46-985c30831302", "type": "remote", "isFull": true } }, { "id": "0mptwroqq-oooeciwkcqg", "start": 1780239727106, "status": "success", "warnings": [ { "data": { "error": { "generatedMessage": false, "code": "ERR_ASSERTION", "actual": true, "expected": false, "operator": "strictEqual", "diff": "simple" } }, "message": "Issue while checking XVA" }, { "data": { "error": { "generatedMessage": false, "code": "ERR_ASSERTION", "actual": true, "expected": false, "operator": "strictEqual", "diff": "simple" } }, "message": "Checksum file not valid, not blocking" }, { "data": { "path": "/xo-vm-backups/695455b5-8e41-661f-d647-409620ee434e/20260501T140136Z.xva" }, "message": "XVA might be broken" }, { "data": { "error": { "generatedMessage": false, "code": "ERR_ASSERTION", "actual": true, "expected": false, "operator": "strictEqual", "diff": "simple" } }, "message": "Issue while checking XVA" }, { "data": { "error": { "generatedMessage": false, "code": "ERR_ASSERTION", "actual": true, "expected": false, "operator": "strictEqual", "diff": "simple" } }, "message": "Checksum file not valid, not blocking" }, { "data": { "path": "/xo-vm-backups/695455b5-8e41-661f-d647-409620ee434e/20260531T142045Z.xva" }, "message": "XVA might be broken" }, { "data": { "files": [ "20260501T140136Z.json", "20260501T140136Z.xva", "20260501T140136Z.xva.checksum" ] }, "message": "This files may be corrupted but not yet to be removed" }, { "data": { "files": [ "20260531T142045Z.json", "20260531T142045Z.xva", "20260531T142045Z.xva.checksum" ] }, "message": "This files may be corrupted but not yet to be removed" } ], "end": 1780239727137, "result": { "merge": false, "size": 0 }, "message": "clean-vm" } ], "end": 1780239727183, "message": "backup VM", "data": { "id": "695455b5-8e41-661f-d647-409620ee434e", "type": "VM", "name_label": "vm-giz-01" } } ], "end": 1780239727186, "infos": [ { "data": { "vms": [ "695455b5-8e41-661f-d647-409620ee434e" ] }, "message": "vms" } ] }