@skipthompson81 Hi, as you have an XOA, can you open a support tunnel to allow us to investigate further into this issue please? You can open a ticket and ask for Pierre Brunet.
This warning is a log we added to be sure we check everything in the backups but it can be alarming indeed but the checks are hard to do and can be false positive so we don't want to panic everyone.
@itservices Can you check your health dashboard where you should see " Unhealthy VDIs" ? If there are too many VDI in it, they need to be coalesced before restarting a backup.
the new code is now in master
@itservices Hi,
We did not forget you, working on it!
@MajorP93 Nice job, i'm thinking about working on an api route to have those infos without needing to go to the server console
@itservices It may be a storage or a xo issue. You can try to restart xo-server and retry the backup. If it is solved, it was an issue with xo-server not freeing your vdi. If it still happens, it will be a storage issue
Hi @DevFlint,
tasks are now correctly visible in the swagger documentation
Hi @slavavrn,
FYI, its now possible to revert a snapshot via the REST API.
POST /vms/:id/actions/revert_snapshot
And the body of the endpoint:
{
"snapshotId": <snapshot-id>
"snapshotBefore": boolean (optional)
}
@itservices Hi,
It seems the parent of the backup chain is not found (a delta backup links to another delta and another, until you have a full backup, it seems a backup on this chain is missing).
Can you restart a backup chain to have a full backup? You can do it by reducing the retention in your backup job.
@Andrew Hi, i'm the one that made the plugin, the documentation is in progress. Meanwhile, can you post the result of running
ipmitool sdr list ? You might find some leads as to which regexes should work for your particular host.
Also you can check ipmitool lan print (be carefull not to share ip's or sensitive info ).
