When setting up your OnBase system, be aware of the differences between the OnBase disk groups and the Gateway Caching Server's caching mechanisms. Do not attempt to use the OnBase disk groups for caching purposes, and do not attempt to use the Gateway Caching Server for backing up files.
|
Disk Groups |
Caching |
|---|---|
|
Backups: Disk groups are ideal for backup purposes. As documents are committed, they are pushed to multiple backup locations and can be burned to media at a later date. Predictable copying: The process by which data makes its way to multiple copies within a disk group is predictable. Non-distributed: Disk groups are not intended for distributed document access. Consistency of content: Each copy of a disk group is a mirror of the other copies. The content is consistent from one copy to the next for a given disk group. |
Not for backups: Caching should never be used for backup purposes. The consistency of the cache is not guaranteed and items may be flushed from the cache. The caching mechanism is internal and so the location of the cache is not published and may change from release to release. Variable copying: Items may or may not make their way into the cache, depending on the various configured rules. At any moment, there is no guarantee that an item that should be in the cache is in the cache. Distributed: Caching with the Gateway Caching Server is the recommended approach for facilitating document access at distributed locations. Application Server only: Caching works only with Application Server-based products, such as the Web Client and Unity Client. Gateway required: Caching requires the deployment of an Gateway Caching Server. |