| From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | Yambu <hyambu(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Move database |
| Date: | 2020-11-10 14:11:11 |
| Message-ID: | A631D97B-6644-4935-849A-F4E8E57C6F31@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi Yambu,
> On 10. Nov, 2020, at 14:48, Yambu <hyambu(at)gmail(dot)com> wrote:
> What is the best way to move a database from one VM to another without losing records from updating applications?
I assume you want to minimize down time? If so, set up a streaming replication on the new VM and let PostgreSQL copy the whole database over by itself as a standby database. After copying is finished and both databases are completely in sync, then shut down the old (primary) database and promote the standby database. After that, you can delete the old database.
Assuming you can afford the down time, there is always the option of shutting the database down and scp or rsync it to the new VM and start it there.
If you run it on some external storage like mounted NFS filesystems, you can shut it down, umount the NFS volume(s) on the old VM, mount the NFS volume(s) on the new VM and start it there.
It really depends on your system (storage) architecture.
Cheers,
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2020-11-10 14:12:46 | Re: Move database |
| Previous Message | Yambu | 2020-11-10 13:48:50 | Move database |