Post #2817429

@kostyn@niagara.social Probably depends how/where you currently store your data. I moved climatejustice.social with about the same amount of media storage, plus 5x the database. Media was on some S3 storage, so I used rclone to sync everything to a new storage before the move. For postgres I did a dump+import shortly before the move, ran the import, shut down the servers on the old infra, then just replayed the WAL files that had accumulated in the meanwhile. (Make sure you have WAL archiving configured and set the correct WAL level). When everything was up and running on the new infra, I ran a final, incremental rclone to make sure I got all the media. Overall downtime easily below an hour. PS: don't forget to set you DNS TTL as low as possible. PPS: If you serve media from a separate domain, and this domain changes during the move, you WILL BREAK others instances image caches, and also have to manually update some strings in the database. I wrote down in detail what this means and how to fix it here: https://wiki.fediverse.foundation/books/fediverse-foundation-announcements/page/announcement-change-of-the-cdn-of-climatejusticesocial-2023-07-13