Restoring from backup

KB Home   |   Restoring from backup

Main.RestoringDataFiles History

Hide minor edits - Show changes to output

September 16, 2019, at 04:39 AM by Mel Zouzoulas - Mentioned Print Deploy
Added lines 50-51:
!!How about back up with Print Deploy?
We have this documented in the Print Deploy Help Center which you can find over [[https://www.papercut.com/support/resources/manuals/print-deploy/manage-print-deploy/topics/maintain-print-deploy.html|here.]]
Changed lines 21-26 from:
# Run the import process by executing the following:
@@db-tools import-db -f "C:\path\to\backup\backup-file-name.zip"@@

As above with macOS and Linux, don't forget to prefix the command with '''dot slash'''.

The process warns that an import deletes the existing database data before proceeding, so choose yes to continue.
to:
# Run the import process by executing the following: @@db-tools import-db -f "C:\path\to\backup\backup-file-name.zip"@@. As above with macOS and Linux, don't forget to prefix the command with '''dot slash'''.
->The process warns that an import deletes the existing database data before proceeding, so choose yes to continue.
Changed line 20 from:
#Re-initialize the database back to an empty state by typing the following: @@db-tools init-db -f@@. On macOS and Linux, run the command like any executable file:  @@./db-tools init-db -f@@.
to:
#Re-initialize the database to an empty state by typing the following: @@db-tools init-db -f@@. On macOS and Linux, run the command like any executable file:  @@./db-tools init-db -f@@.
October 17, 2018, at 06:51 PM by 82 - grammar and adding export restore steps to prevent unnecessary clicking.
Changed lines 3-8 from:
Q: How do I restore a PaperCut database file?

A: '''PaperCut (Internal Database):'''

A: The PaperCut data (stored
in the internal database) can be restored either by restoring the contents of the directory:
to:
!!How do I restore a PaperCut database file?
''Note: To make sure the files are not in use at the time of restoration, remember [[https://www.papercut.com/kb/Main/StoppingAndStartingPaperCutServices|to stop the ''PaperCut Application Server'' service]] before getting started.''

!!!PaperCut (Internal Database):
*Copy and paste (yes, really).
-->Replace the existing contents of the directory below with the contents of the same folder from your latest off-disk backup (e.g., your backup software):
Changed lines 11-14 from:
A: from your latest off-disk backup (e.g. your backup software).  Remember to stop the ''PaperCut Application Server'' service before restoring (so the files are not in use at the time of restoration).

Or, alternatively (a secondary option), PaperCut has an inbuilt database export feature at the application-level which is a form of backup.  It is possible to restore a point-in-time export file created by PaperCut.  These are stored in the
directory:
to:
*Restore from PaperCut's automatic DB export
-->Alternatively, PaperCut performs an automatic weekly database export, which is a form of backup. You can leverage these weekly exports to restore to a specific a point-in-time. The exports are in the following
directory:
Changed lines 15-16 from:
A: Again, you may need to restore your latest point-in-time database export file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the date and time allowing you to select the most recent export. Database exports can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
to:
-->Again, you may need to restore your latest point-in-time database export file from your system's off-disk backup system. In any case, the files all end in a ''zip'' extension and have names that include the date and time to help you select the most recent export. Use the [@db-tools@] binary to restore the files as described in the excerpt from the manual below:

#Locate the most recent DB export file by browsing to @@[app-path]/server/data/backups@@.
#Since the database cannot be in use when performing the restore, [[https://www.papercut.com/kb/Main/StoppingAndStartingPaperCutServices|stop the Application Server service]].
#On a Windows print server, open an elevated command prompt the change to the server binaries directory @@C:\Program Files\PaperCut NG or MF\server\bin\win\@@. On macOS, the server binaries are in @@[=/Applications/PaperCut NG or MF/server/bin/mac/=]@@ and on Linux in @@/home/papercut/server/bin/linux-x64/@@.
#Re-initialize the database back to an empty state by typing the following: @@db-tools init-db -f@@. On macOS and Linux, run the command like any executable file:  @@./db-tools init-db -f@@.
# Run the import process by executing the following:
@@db-tools import-db -f "C:\path\to\backup\backup-file-name.zip"@@

As above with macOS and Linux, don't forget to prefix the command with '''dot slash'''.

The process warns that an import deletes the existing database data before proceeding, so choose yes to continue.

I used the following manual pages to adapt the instructions above:
Changed lines 33-35 from:
A: '''PaperCut (External Database):'''

A: All data is stored in the external database with the exception of:
to:
!!!PaperCut (External Database):

A: An externalized database stores all PaperCut data except for the following items:
Changed lines 40-41 from:
Instead, these settings are stored in the ~/server/server.properties file.  If the Application Server fails, all data is still safe in the external database.  Simply re-installing PaperCut, complete the configuration wizard, then pointing it to the existing external database will restore all settings and data.
to:
Instead, these settings are in the @@[app-path]/server/server.properties file@@.  If the Application Server fails, all data is still safe in the external database. Merely re-installing PaperCut, completing the configuration wizard, then pointing the @@server.properties@@ file to the existing external database restores all settings and data.
Changed lines 46-49 from:
Q: How do I restore a PaperCut Print Archives?

A: PaperCut by default stores the Print Archive data in:
to:
!!How do I restore PaperCut Print Archives?

!!!PaperCut by default stores the Print Archive data in:
Changed line 52 from:
A: This location can be backed up using your existing backup processes and due to designed resilience can be restored fully or in-part allowing for partial backups of these files e.g. one or two months worth. The [@README.txt@] in the archive directory that explains more about partial backups and the directory structure layout.
to:
-->Your existing backup processes can help to restore this directory, and, due to designed resilience, you can do this wholly or in-part allowing for backups of one or two months worth, for example. The [@README.txt@] in the archive directory explains more about partial backups and the directory structure layout.
August 15, 2018, at 10:27 AM by Chris King - Corrected the Print Archive folder location
Changed line 40 from:
--> [@[app-path]/server/data/backups@]
to:
--> [@[app-path]/server/data/archive@]
July 21, 2016, at 01:51 AM by Shane Higgins - Updated Links to the new manual pages
Changed line 19 from:
-->https://www.papercut.com/products/ng/manual/ch-sys-mgmt-backups.html
to:
-->https://www.papercut.com/products/ng/manual/common/topics/sys-backups.html
Changed line 21 from:
-->https://www.papercut.com/products/ng/manual/apdx-tools-db-tools.html
to:
-->https://www.papercut.com/products/ng/manual/common/topics/tools-db-tools.html
Changed line 49 from:
[- keywords: crash, restoration, back-up, point-in-time, snapshot, image, storage -]
to:
[- keywords: crash, restoration, back-up, point-in-time, export, image, storage -]
October 01, 2013, at 06:35 AM by Kelby - Database Exports
Changed lines 13-14 from:
Or, alternatively (a secondary option), PaperCut has an inbuilt snapshot feature at the application-level which is a form of backup.  It is possible to restore a point-in-time backup file as created by PaperCut.  These are stored in the directory:
to:
Or, alternatively (a secondary option), PaperCut has an inbuilt database export feature at the application-level which is a form of backup.  It is possible to restore a point-in-time export file created by PaperCut.  These are stored in the directory:
Changed lines 17-18 from:
A: Again, you may need to restore your latest point-in-time snapshot backup file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the date and time allowing you to select the most recent backup. Snapshot backups can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
to:
A: Again, you may need to restore your latest point-in-time database export file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the date and time allowing you to select the most recent export. Database exports can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
Changed lines 32-33 from:
A: If your database crashes, follow your database's recommended restore procedure.  Again, PaperCut does maintain it's own point-in-time backups (see above) in the directory:
to:
A: If your database crashes, follow your database's recommended restore procedure.  Again, PaperCut does maintain it's own point-in-time database exports (see above) in the directory:
Changed lines 17-18 from:
A: Again, you may need to restore your latest point-in-time snapshot backup file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the date and time allowing you to select the most recent backup.  Point-in-time backups can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
to:
A: Again, you may need to restore your latest point-in-time snapshot backup file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the date and time allowing you to select the most recent backup. Snapshot backups can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
Changed lines 44-65 from:
A: '''PaperCut Quota: [Legacy Software]'''

A: PaperCut stores data such as the user list, account balances, and activity logs in files labeled with an MDB file extension (*.mdb).  PaperCut will automatically take backups of these important files during key operations such as a database “tune up”.  Backups are placed in the directory:

--> @@C:\Program Files\PaperCut\Backups@@

->In addition to PaperCut’s automated backup we strongly recommend that all PaperCut files (files under the PaperCut program folder) be included in a ''regular'' system-wide backup process.

->If a database files needs to be restored from backup, use the following process:

-->'''1.''' Open ''Start->Settings->Control Panel->Administration Tools->Services''

-->'''2.''' Select the "PaperCut" service(s) and press the stop button.

-->'''3.''' Copy the @@*.mdb@@ file intended to be overwritten to a safe place on the hard drive.

-->'''4.''' Manually copy the @@*.mdb@@ file from the backup pool over the top of the existing file.  Ensure the file name is consistent with the original file name.

-->'''5.''' Restart the PaperCut services stopped in step 2.

-->'''6.''' Test PaperCut by instigating printing and/or internet use and ensure tracking continues as expected and no error messages existing in the PaperCut application event log.

to:
Changed line 49 from:
[- keywords: crash, restoration, back-up -]
to:
[- keywords: crash, restoration, back-up, point-in-time, snapshot, image, storage -]
Changed lines 11-14 from:
A: from your latest off-disk backup.  Remember to stop the ''PaperCut Application Server'' service before restoring (so the files are not in use at the time of restoration).

Or, alternatively it is possible to restore a point-in-time backup file as created by PaperCut's own backup procedure.  These are stored in the directory:
to:
A: from your latest off-disk backup (e.g. your backup software).  Remember to stop the ''PaperCut Application Server'' service before restoring (so the files are not in use at the time of restoration).

Or, alternatively (a secondary option), PaperCut has an inbuilt snapshot feature at the application-level which is a form of backup.  It is possible to restore a point-in-time backup file as created by PaperCut.  These are stored in the directory:
Changed lines 17-18 from:
A: Again, you may need to restore your latest point-in-time backup file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the date and time allowing you to select the most recent backup.  Point-in-time backups can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
to:
A: Again, you may need to restore your latest point-in-time snapshot backup file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the date and time allowing you to select the most recent backup.  Point-in-time backups can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
January 24, 2013, at 10:10 AM by Jason - backing up print archive.
Added line 26:
* The Print Archive data (see below)
Changed lines 28-29 from:
* The database connection details
to:
* The database connection details
Added lines 36-43:
Q: How do I restore a PaperCut Print Archives?

A: PaperCut by default stores the Print Archive data in:

--> [@[app-path]/server/data/backups@]

A: This location can be backed up using your existing backup processes and due to designed resilience can be restored fully or in-part allowing for partial backups of these files e.g. one or two months worth. The [@README.txt@] in the archive directory that explains more about partial backups and the directory structure layout.

Changed lines 5-8 from:
A: '''PaperCut NG & PaperCut ChargeBack (Internal Database):'''

A: The PaperCut NG data (stored in the internal database) can be restored either by restoring the contents of the directory:
to:
A: '''PaperCut (Internal Database):'''

A: The PaperCut data (stored in the internal database) can be restored either by restoring the contents of the directory:
Changed lines 23-24 from:
A: '''PaperCut NG & PaperCut ChargeBack (External Database):'''
to:
A: '''PaperCut (External Database):'''
Changed lines 34-35 from:
A: '''PaperCut Quota:'''
to:
A: '''PaperCut Quota: [Legacy Software]'''
Changed lines 32-33 from:
-->[@[app-path]/Program Files/PaperCut NG/server/data/backups@]
to:
-->[@[app-path]/server/data/backups@]
Changed lines 9-10 from:
--> [@[app-path]/Program Files/PaperCut NG/server/data@]
to:
--> [@[app-path]/server/data@]
Changed lines 15-16 from:
--> [@[app-path]/Program Files/PaperCut NG/server/data/backups@]
to:
--> [@[app-path]/server/data/backups@]
Changed lines 15-16 from:
--> [@[app-path]/Program Files/PaperCut NG/server/backups@]
to:
--> [@[app-path]/Program Files/PaperCut NG/server/data/backups@]
Changed lines 32-33 from:
-->[@[app-path]/Program Files/PaperCut NG/server/backups@]
to:
-->[@[app-path]/Program Files/PaperCut NG/server/data/backups@]
Changed lines 17-18 from:
A: Again, you may need to restore your latest point-in-time backup file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the data and time allowing you to select the most recent backup.  Point-in-time backups can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
to:
A: Again, you may need to restore your latest point-in-time backup file from your system's off-disk backup system.  The files all end in a ''zip'' extension and are named with the date and time allowing you to select the most recent backup.  Point-in-time backups can be imported into the system using the [@db-tools@] program as detailed in the user guide here:
Added lines 19-20:
-->https://www.papercut.com/products/ng/manual/ch-sys-mgmt-backups.html
and
Changed lines 28-29 from:
A: If your database crashes, follow your database's recommended restore procedure.  Again, PaperCut does maintain it's own backups in the directory:
to:
A: If your database crashes, follow your database's recommended restore procedure.  Again, PaperCut does maintain it's own point-in-time backups (see above) in the directory:
Changed lines 7-8 from:
A: The PaperCut NG data can be restored either by restoring the contents of the directory:
to:
A: The PaperCut NG data (stored in the internal database) can be restored either by restoring the contents of the directory:
Changed lines 13-14 from:
Or, alternatively it is possible to restore a point-in-time backup file from the directory:
to:
Or, alternatively it is possible to restore a point-in-time backup file as created by PaperCut's own backup procedure.  These are stored in the directory:
Added line 29:

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on September 16, 2019, at 04:39 AM
Printable View   |   Article History   |   Edit Article