Difference between revisions of "Retain Maintenance"
From GWAVA Technologies Training
(→Maintenance/Caching) |
(→Maintenance/Caching) |
||
Line 11: | Line 11: | ||
<b>Note:</b> | <b>Note:</b> | ||
− | This maintenance section does | + | This maintenance section does <b>not</b> involve backup or maintenance of the data store. You must back that up yourself. See KB article, [http://support2.gwava.com/kb/?View=entry&EntryID=371 "Backing Up Retain"], for more details. |
===Ignore Domains=== | ===Ignore Domains=== |
Revision as of 23:52, 4 March 2014
Maintaining a Retain system involves many tasks:
- Backup Configuration (Embedded) Database
- Compress Configuration Database
- Indexing (All Indexes)
Contents |
Level 1
Maintenance/Caching
The maintenance is controlled here. This configuration database – the “Embedded” database - contains your system address book and key information used by Retain; thus, it should be backed up regularly.
Configure how often it gets backed up. You can also configure how often indexes get backed up and how often the indexes are optimized for speed. Retain also lists a history of backups and maintenance.
Note: This maintenance section does not involve backup or maintenance of the data store. You must back that up yourself. See KB article, "Backing Up Retain", for more details.