Note: This solution applies to DocuShare 3.x, 4.x, 5.x, 6.x, and 7.
To ensure the security of your DocuShare site data, you should backup daily. Ideally, you should backup the entire contents of the \Xerox\Docushare directory. Follow the database vendor’s instructions to backup the DocuShare database files.
Note: The backup of the database files and the documents directory must be done at the same time so that the information contained is in sync, otherwise there will be inconsistencies between the documents and the database information. To prevent inconsistencies between the documents and the database, you will need to stop DocuShare or place DocuShare in Read Only mode so that no new data is written during the backup period.
Tech Note:
-
Always follow the instruction from your database vendor or server backup application.
-
If you are using the bundled MSDE database, we recommend that you always backup and restore the entire DocuShare directory. For this, you will need to stop both docushare and mssql in order to release all the necessary files from running processes.
To Backup DocuShare you will need a copy of the following files:
Required
· DocuShare documents directory
NOTE: The location of the documents directory may vary depending on your installation environment. The location of the documents directory in your environment can be found in Admin Home | Site Management | Directory Paths | Document Repository.
· DocuShare database files
NOTE: The default DocuShare database files in SQL are called docushare.mdf and docushare_log.ldf.
Recommended
· Xerox\DocuShare directory
NOTE: Backing up the Xerox\Docushare directory structure will allow to backup your config files and any customizations you might have done to your site. At a minimum you should backup your Xerox\Docushare\config directory and any customizations.
Note: Verify backup file sizes for both the documents directory and database files to ensure that your backup file sizes match the original size.
Note: You should test your restore procedure on a test server occasionally just to be sure that everything restores successfully.
Solution Updated: September 4, 2018
Solution ID: 321