Hi Mevludin, Just curious about how you are migrating the secondary storage. Are you using the CloudStack feature to migrate data across secondary storage? So you added a new secondary storage and cloudstack already started syncing the public templates from URLs?
-Jithin From: Pearl d'Silva <pearl.dsi...@shapeblue.com> Date: Friday, 26 April 2024 at 3:11 AM To: users <users@cloudstack.apache.org> Subject: Re: Avoid re-redownloading URLs when migrating secondary storage Hi Mevludin, When migrating data to another secondary store, it only considers private templates and public templates with no url - those which are created from snapshots or volumes. Public templates with URLs are automatically synced(downloaded) on to the newly added secondary store. So, they aren't ideally getting duplicated on the new secondary store. Regards, Pearl ________________________________ From: Mevludin Blazevic <mblaze...@uni-koblenz.de> Sent: April 25, 2024 4:51 AM To: users <users@cloudstack.apache.org> Subject: Avoid re-redownloading URLs when migrating secondary storage Hi all, it looks like with every secondary storage migration Cloudstack tries to re-download all templates with URLs instead of simply grabbing the already downloaded template from the old image store. If that's true, how to avoid that behaviour? Mevludin
