|
Home > Archive > PostgreSQL Discussion > May 2005 > Question: migrate
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Hrishikesh Deshmukh 2005-05-27, 11:23 am |
| Hi All,
I have a huge database working on a debian linux machine, this machine
is going to get a hard drive wipe and new OS. I have another debian
linux machine (exact hardware + software). Is there a way to get
database "migrated" from machine 1 to machine 2 without much work?
Anxiously waiting for reply. Kindly advice.
Thanks in advance.
Hrishi
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
| |
| Jeff Trout 2005-05-27, 1:23 pm |
|
On May 27, 2005, at 12:10 PM, Hrishikesh Deshmukh wrote:
> Hi All,
>
> I have a huge database working on a debian linux machine, this machine
> is going to get a hard drive wipe and new OS. I have another debian
> linux machine (exact hardware + software). Is there a way to get
> database "migrated" from machine 1 to machine 2 without much work?
>
2 methods
1. since it is the same kind of hardware you can shut down PG on
machine1 and tar up $PGDATA move to machine2, untar and fire up PG.
2. pg_dump on machine 1, copy the dump, load up on machine2. (this
will take longer)
--
Jeff Trout <jeff@jefftrout.com>
http://www.jefftrout.com/
http://www.stuarthamm.net/
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql
.org
| |
| Robert Treat 2005-05-27, 1:23 pm |
| On Friday 27 May 2005 12:52, Jeff Trout wrote:
> On May 27, 2005, at 12:10 PM, Hrishikesh Deshmukh wrote:
>
> 2 methods
>
> 1. since it is the same kind of hardware you can shut down PG on
> machine1 and tar up $PGDATA move to machine2, untar and fire up PG.
>
Depending on your systems, it might be quicker to just mount one of the drives
on the other machine and copy it directly over, bypassing the tar step.
> 2. pg_dump on machine 1, copy the dump, load up on machine2. (this
> will take longer)
>
Option 3 would be to use slony, which would minimise the down time, but might
not fall into the "without much work" constraint.
--
Robert Treat
Build A Brighter Lamp :: Linux apache {middleware} PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend
|
|
|
|
|