Migrating or Moving your PaperCut Database Server
on 10 August 2020 03:51 PM
“I need to move my PaperCut database to a different server - how do I do that?”
If you’re running PaperCut on an external database like Microsoft SQL, PostgreSQL, MySQL or Oracle, chances are that at some point you’ll need to move it. If you’re looking to migrate your external PaperCut database to a new server, this is the guide for you!
If you’re currently running on the default PaperCut ‘Derby’ database (check under About → Systems Info, in the PaperCut admin interface to check what you’re using currently), and you want to upsize to an external DB, head on over to the Upsize to an external database help center article.
Note: This article is not describing how to move or migrate your PaperCut Application server. That is described over on the article: Migrating PaperCut to a new server (when using an external database)
The PaperCut App Server doesn’t really mind where the data is that it’s using - as long as it knows the host of the database, and connection details. So when it comes to migrating your database, it’s pretty forgiving as to how you want to do it.
There are two main options:
In this method, you’ll use the PaperCut ‘db-tools’ utility to move the data from the old database to the new database.
Follow the steps in the Upsize to an external database checklist. The summary of the steps is below:
Hang on, that seems too simple - why does that work?
In the same way that when you moved from the internal derby database to an external database, you’re doing exactly the same thing moving from one external database to another - so the steps are identical.
If you have a large set of databases running across multiple SQL servers, chances are that you have a database team looking after them. They’ll want to use their own processes and tools to move data around - just like any other database that they’re maintaining.
Again, you can follow the steps in the Upsize to an external database checklist. However - some of the steps will effectively get performed by your database team. The summary of the steps is below: