Skip to main content

Restore a Backup- Export/Import documents to production site

Updated

NOTE: This procedure requires a test server environment for DocuShare and may require a test server for the database. You must restore, from your backup, the [ds3home]\documents directory and the database/tablespace containing the DocuShare Meta data. For MSDE or SQL Server this would be the Docushare.mdf and Docushare.ldf files.

  1. If using an external database restore the necessary database / tablespace to the database server.
  2. Install a clean instance of DocuShare 3.1 on to a test server. During installation configure DocuShare to connect to the database by providing the appropriate database information to use the restored database / tablespace.

    NOTE: An existing instance of DocuShare can be configured to use the restored database/tablespace. Edit the [ds3home]\config\JDBCPropertyBean.properties file. Change the database property values for url, user, password, and database name to the correct values for connecting to the database/tablespace. For Oracle make sure you use the correct SID and database user for the restored tablespace.

  3. Stop DocuShare.
  4. Restore the [ds3home]\documents directory from your backup.
  5. Restart DocuShare.
  6. Run dsindex index_all to recreate the Verity indexes.
  7. Locate the Collections and Documents objects to be restored to your production server. Note the object handles, for example: Collection-2322 or Document-224.
  8. Use the dsexport utility found in the [ds3home]\bin directory to export the desired object. For example the command string dsexport r d c:\myexport Collection-2322 will export the entire contents of Collection 2322. In the c:\myexport destination directory, a directory with the same name as the handle being extracted is created. Collection 2322 in this example. Within the c:\myexport\Collection-2322 directory, an XML file called Collection-2322.xml and a directory called documents are created. All extracted documents (the original end-user documents associated with a document object) end up in the documents directory.
  9. Copy the contents of the destination directory (c:\myexport in this example) to the target DocuShare server.
  10. At the target server use the dsimport utility found in the [ds3home]\bin directory to import the object(s) to the production server. This will be completed in two steps.
    1. Run dsimport with the w option. The w option is a simulation and does not alter data on the server. The w option will report all dsimport actions and errors. For example the command string dsimport w n must_exist r d Collection-12 add c:\myexport\Collection-2322\Collection-2322.xml uses the Collection-2322.xml file and the c:\myexport\Collection2322\document directory (both created in the dsexport example above) as the source for importing into Collection-12. The w option will report every object being imported and any errors, Changes will not be committed to repository.
    2. The second time use the same command as in step a, except without the w option. Run this after you have corrected any errors and validated there are no error messages reported by dsimport when run with the w option.
  11. After completing the import your imported objects will be available on DocuShare.

    NOTE: Imported objects will have a new handle number. Hyperlinks and URLs to these objects will need to be updated to use the new object handle number.

Related articles