...
| Warning | ||
|---|---|---|
| ||
Do not put your data at risk by overlooking a comprehensive backup strategy that includes both indexing data and document image files. Failure to adopt a regimented backup plan may result in incomplete data or days’ worth of re-scanning and indexing documents because a backup plan was overlooked. Square 9 Softworks® strongly urges our customers to implement a backup plan that will deliver an appropriate amount of protection from data loss. Please contact Technical Support if you have any questions or concerns related to backup procedures. |
Archives and Inboxes
It is essential to back up the directory that contains your Archives and Inboxes. In the event of data loss, restoring this directory will recover your documents (minus indexing data). By default, the Archives and Inboxes files are located in C:\GlobalSearch (the directory may be called SmartSearch in older versions or upgrades from older versions). If you are backing up from a custom installation, they may be in another location.
...
- Archive – Contains Archive folders for the default database and any additional databases within GlobalSearch. If you have a Content Search license and Content Search is enabled on an Archive, the
ContentSearchfolder will also be located here.
Note that the target destination of an Archive may be modified in GlobalSearch. It is possible for a single Archive to store documents in multiple locations and on multiple servers. It is important to back up document at all your Archive locations. - Inboxes – Contains any Inbox folders that you have created within GlobalSearch.
Workflows, OCR Templates, Web Form Mappings, and Custom Development
By default, the GlobalSearch main application exists within the C:\GetSmart directory. Inside this directory are key folders that are specific to each individual installation. It is highly recommended that you back up the entire GetSmart directory.
Process History and GlobalAction & GlobalCapture Workflows
The mongoDB folder (found in the C:\GetSmart directory by default) contains the database objects that store Workflow layouts and processing data for both active and historical document operations. As MongoDB is a separate database engine technology that runs as a service on the server, files will be in use when the MongoDB engine is running. It is important to note that this can impact a traditional file system backup’s ability to access the files. Additional backup steps may be needed.
...
| Warning | ||
|---|---|---|
| ||
If you do not backup MongoDB, you can lose Workflow definitions that may have taken hours, days, or even weeks to build. Additionally, you could lose days, months, or years of processing history that may or may not be needed. Consult with your network administrator on how best to back up in-use files in the file system. Refer to the MongoDB documentation for specific backup recommendations from the database vendor: https://docs.mongodb.com/. MongoDB offers backup and restore commands that can be configured as a batch job. Refer to MongoDB documentation found at https://docs.mongodb.com/manual/tutorial/backup-and-restore-tools/ for details. |
Databases
Backing up all your GlobalSearch databases is critical to a successful recovery in the event of data loss. If you already have a backup routine for SQL Server, you may simply incorporate the GlobalSearch databases into that routine.
...
| Tip | ||
|---|---|---|
| ||
By default, the GlobalSearch databases are created in Simple Recovery mode. Please visit http://msdn.microsoft.com/en-us/library/ms189275.aspx to select the recovery mode that is right for you. |
SQL Database Backup
How you back up your SQL databases will depend up on your chosen backup procedure, but backups must include SmartSearch, SSMaster, SSProcessing, Square9Users, and SSCapture. This section contains a simple, manual procedure for backing up your databases. For more information about automated backups, please consult your organization’s database or network administrator.
...