Migrate PostgreSQL Database to another Server Toolkit

The procedure of PostgreSQL migration to new server (presumably, using PostgreSQL as a destination DBMS) consists with two simple, completely automated steps:

1. Backup PostgreSQL database to some place.
2. Migrate PostgreSQL to another server using a copy of database from backup.

Here we put a short instruction describing programming the sequence for these actions in Handy Backup. Please read the appropriate sections of the User Manual for more detailed instructions about each step mentioned here.

Taking a PostgreSQL Backup

To create a PostgreSQL migration tool sequence, firstly make a PostgreSQL backup task. Note that you may need a data storage (such as an FTP server or an external USB drive) of an appropriate capacity to put your PostgreSQL backup data into (at least temporarily!).

1. In Handy Backup, create a new backup task. Use either simple or advanced mode, as you wish.

2. Select PostgreSQL from the Database group on Step 2.

3. If you still do not have a PostgreSQL configuration for migrating server, create a new.
4. Click "Create a connection" and enter your PostgreSQL connection parameters in the dialog.

5. Now you have a configuration to back up PostgreSQL. Select it and choose migrating databases.
6. Go to Step 3 and select storage where you will place your Postgres migration data.
7. Proceed continuing creating a task with default parameters, according to your backup strategy. Here you can use such advanced parameters as differential and versioned backup on Step 4, scheduling and triggering a task on Step 6, and starting external software on Step 7.

Caveat: To take a snapshot for PostgreSQL migration, you must have a sufficient user privileges to use a PostgreSQL SELECT statement freely for creating a backup dump.

Using a Backup Dump to Migrate PostgreSQL to New Server

Next, you will need to create a new PostgreSQL restoration task to migrate Postgres database to another server. Please follow the instruction below:

1. Create a new task and select restoration as a task type. Use advanced mode.
2. On Step 2, select a backup location where you have saved your Postgres snapshot.
3. Find a file backup.hbi, containing all data related to this particular backup. Click "Next".

4. Click on the "Change Location" button. Select a new server to migrate PostgreSQL database.
5. Click OK. Continue creating a task with default restoration parameters.

Note: Network solutions of Handy Backup (particularly the Server Network edition) can perform both backup and restore operations needed for PostgreSQL migration on remote machines in the local network! In addition, single-machine editions like Small Server can also access remote databases.

Implementing a PostgreSQL Migration Tool

Finally, you may migrate PostgreSQL to another server. To do it, start a backup task created in a previous instruction. After finishing this task, start a second part of the job – a restoration task. That is all! Your PostgreSQL migration will complete in fully automated mode!

An advice: Using the scheduling on the Step 6 of backup task (and the Step 4 or Step 5 of restore task), you can schedule your tasks to run automatically in an appropriate time (e.g. at evening after finishing workhours). This can save you some time and efforts, although may feel a bit uncontrollable (or no?).

How to Migrate PostgreSQL Database to New Server with Different DBMS?

Despite Handy Backup has no direct PostgreSQL migration tool for other database engines, you can always do a modest quantity of manual operations to migrate from PostgreSQL to MySQL or another DBMS architecture. The method of PostgreSQL migration has a base on native SQL dump format.

• Handy Backup saves unencrypted, uncompressed PostgreSQL files as a sequence of SQL commands to re-create an original dataset when executing this sequence. You can always make necessary changes in this dump file to ensure PostgreSQL migration to new server DBMS.