New RunLLM response generated: >>>*# Question* Question for the crowd - has anyone performed a backup / restore of Flyte blob storage from one bucket to another? As it stands, the metadata bucket is full of protobuf files which contain fully qualified paths like s3://my-data-bucket/foo to actual inputs / outputs in the data bucket. Moving to another bucket would therefore require parsing / rewriting all the protobuf files, unless I'm missing something? # Answer Yes, moving Flyte's metadata bucket to another bucket would require updating references in the metadata. According to this discussion, Flyte relies on database backups as the source of truth, and the S3 bucket contains necessary information to rebuild it. However, the metadata contains fully qualified paths that would need to be updated if the bucket changes. Would you like more detail on how to handle this process? Sources: - Is there a way to rebuild the database that flyte admin uses Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1719504891.348369 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.