# Postgresql problem on moving discourse with rsync **URL:** https://meta.discourse.org/t/postgresql-problem-on-moving-discourse-with-rsync/318771 **Category:** Self-hosting **Created:** [July 27, 2024, 2:27pm UTC](https://meta.discourse.org/t/postgresql-problem-on-moving-discourse-with-rsync/318771 "2024-07-27T14:27:22Z") **Posts on this page:** 1 **Showing post:** 12
### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman) #### Post date: [December 19, 2025, 7:20pm UTC](https://meta.discourse.org/t/postgresql-problem-on-moving-discourse-with-rsync/318771/12 "2025-12-19T19:20:52Z")
> [@sandra.mccollum](#): > > I want to create a 2nd instance of my self-hosted discourse site on another VPS, with a different domain name. Why? Do you want a staging site for testing? If so, the easiest way to do it is set up the new site, have both sites share an S3-compatible bucket for backups and just restore the backup on the other site. > [@sandra.mccollum](#): > > That should work to basically clone the site from one VPS to another, right? Some other topics were doing so via rsync, which feels like that should not be necessary, to me anyway. You can do that if you want, but there are a bunch of steps in changing hostnames, and restoring a backup is much easier. The rsync way involves moving less data around (in some ways) and lets you move to a an up-to-date OS (which you presumably don’t need to do). So, sure, you can do that (if the host was shut down when the image was made), then edit the hostname in your `app.yml` and rebuild. It’ll still be easier to restore the most recent backup, but if you prefer, you can follow these steps [Change the domain name or rename your Discourse](https://meta.discourse.org/t/change-the-domain-name-or-rename-your-discourse/16098) --- _[View the full topic](https://meta.discourse.org/t/postgresql-problem-on-moving-discourse-with-rsync/318771)._