Hi Antoine, If you confirm the jobs are done (seems so), and the volumes do exist on primary storage, you can set the "removed" column of "volumes" table
"update volumes set removed=now() where id=<id of migrating volume>;" You'd better backup the database before the changes and start with one of the volumes. You might need some changes on the old volumes. -Wei On Thu, 30 Mar 2023 at 23:07, Antoine Boucher <[email protected]> wrote: > Hello, > > I few days ago we did 3 migrations that eventually failed because of > secondary storage issues. However, the volumes entry are duplicated on the > Web UI, one showing ready and the other one showing migrating. > > Could I edit the volume table to remove the migrating entry to remove it > from the UI? > > Regards, > Antoine > > >
