Select the schedule option - day, weekly or monthly.
Click "Database Backup" icon under "General" section.
You can schedule database backup to be executed at any specific point of time. If you want to have the Live Backup enabled again, you need to follow the steps once again. Just delete the mysql folder in the remote machine. Note: Once you recover the data from the slave and give life to the master database, the slave database will no longer be valid. Once you do this, the data is safely recovered in the new PMP version
#WHAT A TIME TO BE ALIVE .ZIP ZIP#
Navigate to /mysql/data folder and unzip the zip created from the slave database.
Get a fresh PMP installation in the machine where the master database was running.
Go to the machine where PMP was running.
In the remote machine where slave DB is running, navigate to /data folder and create a zip of the following:.
In the rare event of master database crash, you can recover data from the slave database. Slave database is running in host: Recovering data from slave when master database crashes If the setup is proper, you will see the following:Ĭonnection Status: Alive and Live Backup is in progress now Whenever there happens a change in the master database, which runs with PMP, the same will be immediately updated to the slave databaseĪfter carrying out the above steps, you can verify if the Live Backup setup is working properly by looking at the message in "Admin > General > Database Backup" page.
Again go to the remote machine and navigate to the /bin folder and run the script startSlaveDB.bat (Windows) / startSlaveDB.sh (Linux).
Navigate to /bin directory and run the script startDB.bat (Windows) / startDB.sh (Linux)įor example, with the default the MySQL port 2345, you need to execute this as:
Now, come back to the machine where PMP is running.
The database that is bundled with PMP acts as the master database.
#WHAT A TIME TO BE ALIVE .ZIP ZIP FILE#
Unzip the zip file in the remote machine.
Move the zip file from /replication folder to the remote location where you wish to keep the slave database for live backup.
This zip with the name "Replication.zip" contains the slave database package
This will create a new directory named 'replication' under and a replication package in the form a zip file will be created under /replication folder.
Go to /bin directory and run the script replicationPack.bat (in Windows) / replicationPack.sh (in Linux).
If PMP server is already running, stop it before proceeding further.
After installation, the PMP server should have been started and stopped at least once.
In the unlikely event of any disaster to the primary database, you can rely on the slave database and recover the data. At any point of time, the data in both the databases will be in synchronization with each other. PMP achieves this live backup by leveraging the database replication feature offered by MySQL.Ī live 'slave' database could be configured in a remote location and it will get instantaneously updated whenever the 'master' database running with PMP undergoes a change. Whenever there happens an addition or modification of the entries in the PMP database, the data gets immediately backedup. To achieve this, PMP provides two features: For later versions, click here)ĭata stored in PMP database are of critical importance and in any production environment, there would be constant requirements for backing up the data for reference purposes or for disaster recovery. Database Backup (Procedure applicable only for builds prior to 6301.