broken backup in XOA 6.5 ? orphan VDI Directory, not referenced by any backup

Pilow

did a full VM restoration on an "N/D" backup point, was successful

so it seems backup is backuping buuuuut not reporting correct transfer size

halp

olivierlambert

Interesting Ping @florent and @julienxovates

acebmxer

Just notice similar for me with only 2 vms. Both vms are on main pool with xoa. pools connected via proxy dont show this error..

I have support tunnel open already for active support ticket still. Home lab does not seem to have this issue. currently.

Pilow

@acebmxer but you have SIZE and SPEED

same error but I do not even have these infos.

acebmxer

@Pilow

Maybe because my backup was a full vs delta?

Pilow

@acebmxer had a combo error on some VMs "fell back to full" and "not referenced by any backup" but no tranfer size either.

can't screenshot it anymore, I did a rollback to XOA 6.3 for the time being, snapshoted just before the upgrade

Bastien Nollet

Hi @Pilow,

Can you send the full log of one of your backups that don't display any size? We recently had some changes on backup logs, so we need to make sure it's not just a UI issue. (please send the logs of a regular backup, a delta backup or a replication, and not the log of a metadata backup)

pierrebrunet

@pilow @acebmxer This should be fixed in 6.5.1 but you will need to run again your backups.

Pilow

@Bastien-Nollet Sorry, I had to revert back to 6.3.3, and didnt save the logs...
but as far as I remember, it was not an UI issue, even in the logs it didnt put any transfer informations

@pierrebrunet i'll report back as soon as we test 6.5.1 on this same client infrastructure

acebmxer

@pierrebrunet

I have updated my XOA and Proxies... It seems i did not see the warning on the next round of backups. Will continue to monitor now patches are installed.