# Devops # EMR Deployment # Point of Care EMR deployment This describes the processes in which the Point of Care # Deployment using Clonezilla Installing Clonezilla On Server Purpose This document is a guide for how to install Clonezilla on Server Audience This document is applicable for Baobab Health Trust staff (Operations Department) The process described below assumes that the server to carry clonezilla has access to the Internet during the whole of the process. Installing Clonezilla On Server The process described below assumes that the server to carry clonezilla has access to the Internet during the whole of the process. It also assumes the server is on the IP Address of 192.168.5.200. If what is described in this document, then please do make changes to suit your system configuration. I am also using nano as my text editor, but you can use any text editor e.g. vim, vi ... 1. Install TFTP server This is the application/server that enables the J2s or any other computer to be able to boot from the server. - Option A - sudo apt-get install tftpd-hpa sudo start tftpd-hpa Ensure /var/lib/tftpboot exists. If it does not: mkdir -p /var/lib/tftpboot Ensure that the values in /etc/defaults/tftpd-hpa match. Option B sudo apt-get install atftpd atftp sudo start atftp NOTE: if you are using the latest ubuntu/ubuntu server you should have the file /etc/default/tftpd-hpa, looking like this: else, Ensure that the values in /etc/default/tftpd.conf match. Make sure that that the line which says “use daemon is changed fro “no” to “yes” and make # Deployment using a server image Step By Step Guide on Deployment of New Server Image Backing up databases Backup Procedure
1. Backup All Databases on the Old Server
Execute the provided script to back up all necessary databases.
2. Synchronize couchdb Database
For nlims\_db, sync it to your local machine.
3. Blis Drivers
Copy iBlis Drivers that are found in the Server PM2 Show PM2 List
4. Backup all iblis drivers available on the server
----------------------------------------------------- Recloning/restoring image
- Reclone server with new image using your clonezilla bootable device. Refer to the document on setting up clonezilla
NB: Make sure you have a copy of any old image to revert to in case the new image fails
- Test the server, test all applications and services
----------------------------------------------------- Restoration of New image
1. Change Server Name to Site Name in /etc/hostname . This sets the system's hostname and contains only the hostname of the machine.
![](https://bookstack.hismalawi.org/uploads/images/gallery/2025-11/embedded-image-mutopyot.png) 2. Add site name in /etc/hosts. This file is used for hostname-to-IP address mapping and helps in local name resolution. ![](https://bookstack.hismalawi.org/uploads/images/gallery/2025-11/embedded-image-6xkacuyb.png) 3. Change IP Address to Facility’s IP address in /etc/netplan/. See example below: ![](https://bookstack.hismalawi.org/uploads/images/gallery/2025-11/embedded-image-7iz36eze.png)Apply changes by running netplan apply Restore all databases
- Nlims\_db sync to server from local machine
- Restore configurations
- Restore Databases (Use tmux to manage your sessions and it will also allow you to remotely monitor)
- Before you restore your databases, make sure you make changes to mysql configuration in /etc/mysql/mysql.conf.d/mysqld.cnf
Set “innodb\_strict\_mode = 0” ![](https://bookstack.hismalawi.org/uploads/images/gallery/2025-11/embedded-image-nybjwziv.png) NB: Skipping the step above may result in encountering the error below: ERROR 1118 (42000) at line 3483: Row size too large (> 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.
- Load metadata in the fresh database before restoring the new database
- Run ./bin/update\_art\_metadata.sh production
Testing
- Ensure all applications are functioning properly.
- Verify that all syncing cron jobs are operating correctly.
- Confirm remote accessibility via VPN.
- Test all EBNs and J2s to ensure they are working properly and can pull the application
Things to Note
- Most apps running using services and the service files are in /etc/systemd/system
- Emr-api.service
- Nlims-controller.service
- Nlims-data-syncronizer.service
- Mlab-api.service
- Lims-websocket
- BHT-EMR-API in /var/www directory has been changed to just EMR-API.
- Database for EMR-API is running in Production mode.
- This means that you need to specify production mode when running initialization script, migration/metadata scripts
- Old Iblis DB still uses mysql 5.6 is running on docker and can be accesses on port 3307
If other implementing partners are using the server make sure you contact them for them to do their backups.