9 1:Backup and Restore Functions
 Backup Overview
The following contents will guide you through the process of backing up your Project.net database and document store. The process described is considered an off-line back-up – one where the Project.net application must be taken “off-line” before the back-up procedure – and is fairly straightforward. On-line, or “hot”, backups are more involved and are not covered in this document.
The purpose of a back-up is to be able to restore data in the event of a hardware failure or accidental deletion of project data or document. This section also covers restoring a Project.net database or document vault from a back-up, in the event you need to return to a prior version.
 Options for Backing up the document vault
Please note, that backing up or restoring a Project.net database and document vault must be done in pairs. The database contains information about the document vault so it is not possible to restore the document vault without restoring its matching database, or restoring the database without its accompanying document vault.
There are three options to backing-up the document vault storage:
- Simple bulk copy of the entire document vault to another location for storage
- Continuous back-ups using rsync to “mirror” the actual document vault
- Incremental back-ups of any files that have been added or changed since the last back-up
 Copy the document storage to an archive location
The simplest approach to backing-up the document vault is to copy the entire document storage folder and its documents to another location. Restoring the vault is just as easy, copy the entire folder structure back to its original location. This approach also makes it easy to restore a single file; however it uses the most disc space because it stores every file in the document vault, regardless whether that file has changed since the last archive.
 Continuous archiving using rsync
<Description and instructions still under construction.>
 Incremental back-up
This procedure conducts an incremental back-up – only changing the files that have changed or are new since the last back-up. While this method conserves file storage it also increases the labor to restore a back-up
 Avoid Data Conversion Due to Character Sets
You must be careful when exporting and importing data into the Project.net database that the data be preserved in the same character set as the one used by the database. If not, data will be converted from one character set to the other causing loss of data or the data may not fit in the space allocated for it. Make sure to set the NLS_LANG environment variable as outlined in the instructions when saving or restoring a database.
 Overview of an Off-line Backup
The fundamental steps to perform an off-line back-up are:
- Turn off the application to prevent changes to the database during backup.
- Backup the database tables.
- Backup the document file store.
- Restart Project.net.
 Overview of Restoring From a Back-up
The fundamental steps to restoring data backed up off-line are:
- Turn off the application.
- Remove the current data from the database.
- Load data from the database back-up into the database tables.
- Remove the existing documents from the document store.
- Copy the backed-up documents to the document file store.
- Restart Project.net.
 Steps for Performing a Backup or Restore
Step-by-step instructions for backing-up and restoring a Project.net server running on: