DHIS2 Database Migration/Restoration Process

-

 

DHIS2 Database Migration/Restoration Process

This process assumes that the OS is Linux and that you have both the current DHIS2 setup (Will call it “Origin”) and a new/empty DHIS2 instance (Will call it “Destination”) where you intend to migrate data.

Actions at Origin Server [Linux]

Create a sql dump of the current/origin database:

user@origin_server$ sudo su - postgres 

postgres@origin_server$ pg_dump dhis2 -U dhis -f dhis2_origin_db.sql

 

Copy the sql dump to the destination server. You can use ssh client such as PUTTY/WinSCP or simply use the command below:

user@origin_server$ scp dhis2_origin_db.sql dhis@ destination_server:/home/dhis/

Actions at Origin Server [Windows]

Open Command Line Window

Navigate to Postgres bin folder i.e

cd C:\Program Files\PostgreSQL\9.6\bin

Dump the database using the command below

pg_dump.exe -U postgres -d dhis2 -f D:\Backup\<backup-file-name>.sql

Type password for your postgres user

You may copy the dump file over to the destination server using ssh client PUTTY or on windows command prompt /WinSCP.

Actions at Destination Server

While in destination server, create a new database by invoking:

dhis@Mydhis2$ sudo -u postgres createdb –O dhis dhis2_destination

 

Create the PostGIS extension for the newly created database

dhis@Mydhis2$ sudo -u postgres psql -c "create extension postgis;"dhis2_destination

 

Shutdown the newly created dhis2 setup by invoking the command below (this path may vary depending on your setup)

dhis@Mydhis2$ sudo -u dhis /home/dhis/tomcat-dhis/bin/shutdown.sh

 

Update the DHIS2 configuration file to reflect the newly created database.

dhis @Mydhis2$ sudo -u dhis nano /home/dhis/config/dhis.conf

 

In the dhis.conf  file, locate the following line:

# JDBC driver connection URL
connection.url = jdbc:postgresql:dhis2

 

 

Change this to the newly created database, save and exit the file edit mode.

# JDBC driver connection URL
connection.url = jdbc:postgresql:dhis2_destination

 

At this point, we are ready to migrate/restore data from the origin database to the new setup.

Invoke the following command:

dhis@Mydhis2$ sudo su - postgres 

 

Initiate the restoration of the copied database by invoking:

postgres@Mydhis2$ psql -d dhis2_destination -U dhis -f dhis2_origin_db.sql

dhis2_migration: this is the newly created and/or empty database in which we intend to restore data into.

dhis: refers to the database user.

 

Restart the dhis2 instance by invoking:

dhis@Mydhis2$ sudo -u dhis /home/dhis/tomcat-dhis/bin/startup.sh

 

You can monitor the Tomcat by viewing the log information, simply invoke the command below:

dhis@Mydhis2$ tail -f /home/dhis/tomcat-dhis/logs/catalina.out

Comments

Post a Comment

Popular posts from this blog

Building Your DHIS2 Tracker Event -Power BI Model

-
Image
 DHIS2 offers the Web API as a robust means for external systems or tools to access and manipulate data stored in your DHIS2 instance. This comes in handy whenever you want to: Push metadata in or out of the instance, Push/pull data into a DHIS2 instance i.e. MoH to Implementing Partner or into analytical tools such as PowerBI and Tableau. The focus of this document is building a Tracker/Event-based data model in PowerBI. Of importance, the tracker Web API consists of 3 endpoints (tracked entity instances, enrollments, events) with full CRUD support ( DHIS2 Documentation ), refer – Figure 1. Figure 1 : EndPoints Baseurl: https://yourdhis2.com/prod/ Essential/Core Endpoints Endpoint Sample Payload API Call TrackedEntity Instance Baseurl/api/trackedEntityInstances.json?ou=L66MANY1j43&ouMode=DESCENDANTS&program=yw0mVtYaERN&trackedEntityInstance=ydKJVwz8h3t&fields=trackedEntityInstance,tracke...
Read more

Certbot Installation and Configuration(Ubuntu)

-
1. Installation:    Begin by updating your package list and installing Certbot using the following commands:        sudo apt update    sudo apt install certbot python3-certbot-nginx   2. Configuring Certbot for Nginx:    Certbot offers automated Nginx configuration. Execute the command below to acquire and install a certificate. Certbot will seamlessly modify your Nginx configuration to enable HTTPS:        sudo certbot –nginx        Certbot will lead you through the process, prompting for the domain names you wish to secure. It will then handle the automatic configuration of your Nginx server block(s) with the new certificate.     > Note: If opting for the standalone method (not recommended if Nginx is already active), replace '--nginx' with '--standalone'.   3. Certificate Renewal:    Certificates issued by Certbot have a 90-day lifes...
Read more