To restore a specific document into Project Portal 2015, it is necessary to identify the document records from the database backup. After that, the backup information is used to recreate the document manually in Project Portal 2015, in the same way as a new document is created.
Note: Do not restore individual database records manually. This may corrupt the Project Portal database beyond repair.
To find the correct records in the backup, you must have some information on the document to be restored, such as the document number, document title, author, or description. The internal database storage id can be used to identify the correct document immediately.
Note that if you need to start the recovery process by looking for the files attached to a deleted document first, you can use the internal document record id to find the correct document quickly.
The common search keys for locating documents in the backup are summarized in Table 1. The keys are columns in the DOCUMENTS table. Use standard tools to locate the correct document records.
|
Key/column name |
Value |
Description |
|---|---|---|
|
ID |
Integer |
Internal storage id, unique for every Project Portal document. Can be used for identifying document versions. |
|
DOCUMENT_CODE |
String |
Document number visible to end-users. Identifies a document, including all versions. A query in the document code returns all versions of the specified document. When looking for a specific version, you need to look at the document version key as well (column ‘VERSION’). Version is always an integer, starting from 1. |
|
DOCUMENT_NAME |
String |
Document name specified by the user. |
|
AUTHORS |
String |
Document author specified by the user |
Table 1.Search keys for locating documents in backup
Note that the DOCUMENTS table contains the document property data across all workspaces.