| Audience: DocuShare administrators |
Back Up and Maintain a DocuShare Site
Overview
A recoverable DocuShare backup must keep the database and site files synchronized. Establish a recurring backup schedule, protect the backup files, and periodically test restoration on a non-production server.
Minimum Backup Requirements
1. Before starting a backup, either stop DocuShare or place the site in Read Only mode to prevent changes during the backup.
2. Back up the DocuShare database files and the document repository during the same backup cycle.
3. Locate the repository path on Admin Home > Site Management > Directory Paths. The path varies by site.
4. At minimum, include the documents directory and all DocuShare database files.
5. Verify that the backup completed and that the backup file and directory sizes are plausible compared with the source.
6. Periodically test the restore procedure on a test server.
If your site uses a database bundled with DocuShare, the Administrator Guide recommends backing up the entire DocuShare installation directory. In that scenario, stop both DocuShare and the database so files are released before copying them.
Search indexes have their own engine-specific requirements. Follow the applicable IDOL or Solr backup/restore procedure; do not assume that copying the database and documents directory also backs up the search index.
Routine Site Maintenance
- Logging: Enable site access/error logging through Site Management > Repository Log Files. Use Services and Components > Logging to set service-specific logging levels. Increase logging only as needed and monitor disk use.
- Trashcan: Enable the site trashcan if deleted objects may need recovery. Without it, deleted objects are expunged and cannot be recovered through the trashcan. Review and expunge trashcan contents regularly according to retention policy.
- Database optimization: Coordinate database optimization with your DBA. The guide recommends considering it after upgrades, migrations, or large-volume changes, and before a full index operation where appropriate. Database commands and settings are provider- and environment-specific; do not run them without DBA review.
- Account and object cleanup: Review obsolete accounts, groups, and orphaned objects using the supported administration tools and your retention policies.
Before a Maintenance or Upgrade Window
Confirm a usable backup, available disk space, the database and repository locations, an approved maintenance window, and a tested recovery plan. Keep the source backup until the site and representative content have been validated after maintenance.