From: | aarti sawant <aartisawant0(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Migration and snapshot of database |
Date: | 2013-05-30 08:49:23 |
Message-ID: | CALTiZF_CwtLg9+ieM0PE_xNMRhAF--eMS_crGXLTA2tucrxtnQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I want to migrate physical server on to virtual machine
My physical server consist of
1. Some Application.
2. PostgreSQL Database
Here the system migrated from Physical machine will be replicated into two
VM's.
- One will be act as live machine, on which live operations will be
performed.
- Second will be test VM, where I can make changes in application and test
for
new features.
Both VM need to have their own database. But two copies of database require
twice the storage.
I want to optimize for storage.
Once the database is migrated to new machine, how I can use this database
for
both VM's without two independent copies.
Test VM will have its own write operations, which will be ignored later.
My approach
Migration:
-I am thinking of using pg_basebackup for online database backup from
physical
machine to new machine.
-Is pg_barman or pg_rman is faster than pg_basebackup?
Storage optimization:
I want to use snapshot to optimize for storage.
- Will take snapshot of original database and export the snapshot with
read/write access to test VM.
Since, I could not found anything within postgres, I plan to do it using
file
system or LVM.
So with this method I can do my testing and delete the snapshot after
testing
is done without reflecting original database.
Has anyone work on such scenario? What are problem faced in writable
snapshot?
From | Date | Subject | |
---|---|---|---|
Next Message | Armand du Plessis | 2013-05-30 08:58:10 | Least intrusive way to move primary data |
Previous Message | aarti sawant | 2013-05-30 08:49:21 | Migration and snapshot of database |