How To Migrate Chronicall versions 3.9.5 - 3.12.6
This article covers the new and improved way to migrate Chronicall to a new server.
- Running the backup may cause significant downtime for Chronicall. It is recommended to run it after hours.
- Please verify your current Chronicall version by going to Help > About Chronicall on the main Chronicall screen.
- Verify that your exact version of Chronicall is available on our website by visiting our downloads page. If the versions do not match, please update Chronicall to a current version before migrating (e.g. you are on version 3.8.6 but see 3.8.7 on the website).
- It is essential to make sure that the old and new server's Chronicall versions match for the database migration to succeed.
- To verify your current version, go to Help -> About Chronicall on the main Chronicall screen.
Purpose
Migration can be helpful if you want to move Chronicall to another server or want to move the Chronicall installation from one drive to another on the same machine.
Steps
- Make a backup folder on the old server to store all of the files that need to be moved.
-
In Chronicall, go to Admin (System) > Manage Backups.
- In the new menu, select Execute Backup.
- Verify Backup All Data is selected, as well as Data Only Backup. Left-click Run Backup.
- The backup will start, and you can monitor the progress at the bottom of the screen.
- The final step in 3.10 and above is the settings backup, so once that finishes you should be good to go.
- Do Not Change the name of the backup file.
- Once completed, Chronicall will create a download link for the newly created backup. Save that to the Backup folder you created in Step 1.
- If you utilize Chronicall's Recording Library, copy the 0 and Limbo folders into your backup folder.
Below are the default locations for the main recording pool.
- Windows
- 32-Bit
- C:\Program Files (x86)\Xima Software\Chronicall\recording library\0
- C:\Program Files (x86)\Xima Software\Chronicall\recording library\limbo
- 64-Bit
- C:\Program Files\Chronicall\recording library\0
- C:\Program Files\Chronicall\recording library\limbo
- 32-Bit
- Linux
- /var/lib/Xima\ Software/Chronicall/recording\ library/0
- /var/lib/Xima\ Software/Chronicall/recording\ library/limbo
- Windows
- Move the Chronicall backup folder to the new server.
- Next, unregister your Serial Key by going to Admin (System) > System Settings > Basic Settings.
- Left-click on the ellipses button for the Serial Key menu
- Left-click the Unregister Serial button
- Download the Chronicall setup file to the new server and install the software. If or when it asks you for your PBX IP address, enter 0.0.0.0.
- NOTE: This will prevent it from logging any new data before we restore the database
- NOTE: This will prevent it from logging any new data before we restore the database
- Restore the database by going to Admin(System) > Manage Backups > Restore from Backup.
- Left-click Select a zip file to import, locate the backup folder you transferred in step 8 and select it. Left-click Start Upload once the backup has been selected.
- Though this will give you updates as it progresses, keep in mind it can take a very long time to unpack larger databases
- On version 3.10 and newer you'll want to designate what kind of restore you would like to do, as the restoration is much more thorough
- After restoration, stop all Chronicall services
- Place the Recording Library folders that were backed up from the old server into the same file paths on the new server.
- Windows
- 32-Bit
- C:\Program Files (x86)\Xima Software\Chronicall\recording library\0
- C:\Program Files (x86)\Xima Software\Chronicall\recording library\limbo
- 64-bit
- C:\Program Files\Chronicall\recording library\0
- C:\Program Files\Chronicall\recording library\limbo
- 32-Bit
- Linux
- /var/lib/Xima\ Software/Chronicall/recording\ library/limbo
- /var/lib/Xima\ Software/Chronicall/recording\ library/0
- Windows
- Once those files are in place start all Chronicall related services.
- Open Chronicall and go to Reports > Cradle to Grave.
- Verify that the data from the restore is accessible. If there is no old data in Cradle to Grave you will need to restore the database again or contact Xima support.
- Verify that the data from the restore is accessible. If there is no old data in Cradle to Grave you will need to restore the database again or contact Xima support.