Move postgresql database to separate machine

looks good to me. Just make sure we have proper working backups before starting the migration.

:thumbsup: And we should do it quickly too.

@isaagar make a plan, list out the steps, then schedule a down time. We should announce it to our users. We can review the steps.

@praveenarimbrathod @noteness Yes, amar already provided one machine with 40 GB disk space.

Should we start replicating the database on that VM then? ( according to https://gitlab.com/piratemovin/diasp.in/wikis/setting_up_backup )

Then, decide a time, stop all services and promote the slave to master and make the services use the new database?

Yes, i thought of that and interesting to see how slave becomes master :)

New machine has public IP which I'll share and add the others ssh keys
Following are the steps for setup.
1. Find the configuration of all web services dependent on the postgresql where we need to change it according to our new setup. (Adding it in the wiki will be helpful before starting the setup)
2. Encrypt the 40 GB disk of the new machine.
3. Setup the postgrsql on new machine (replica ? new version 9.6?).
4. Shutdown all services and Sync the database to the new machine. (~12G and will be faster locally)
5. Make changes in the configuration of services and start the services.

Shutdown all services and Sync the database to the new machine. (~12G and will be faster locally)

Do we need to shutdown all the services while replicating? Can't we just use pg_basebackup?

Not needed while replicating but we haven't decided with the approach. Whether it is replica setup or just manual moving of database to the new machine.And, to keep the new instance in sync with existing we have stop services from committing in the database before syncing to the new machine.

@praveenarimbrathod @noteness @devraj Lets finalize the steps.