|
The GDS is a directory used to store long-lived files that
are used within a process. The lifetime of long-lived files is intended
to span one or more launches of a LiveCycle system, and can span
days and even years. These long-lived files can include PDFs, policies,
and form templates. Long-lived files are a critical part of the
overall state of many LiveCycle deployments. If some or all long-lived documents
are lost or corrupted, the LiveCycle server may become unstable.
Input documents for asynchronous job invocation are also stored
in the GDS and must be available to process requests. Therefore,
it is important that you consider the reliability of the file system
that hosts the GDS and employ a redundant array of independent disks
(RAID) or other technology as appropriate for your quality and level
of service requirements.
The location of the GDS is determined during the LiveCycle installation
process or later by using Administration Console. In addition to
keeping a high-availability location for GDS, you can also enable
database storage for documents. See Backup options when database is used for document storage.
GDS locationIf you leave the location setting empty during installation,
the location defaults to a directory under the application server
installation. You must back up the following directory for your
application server:
(JBoss) [appserver root]/server/[server]/svcnative/DocumentStorage
(WebLogic) [appserverdomain]/[server]/adobe/LiveCycleServer/DocumentStorage
(WebSphere) [appserver root]/installedApps/adobe/[server]/DocumentStorage
If
you changed the GDS location to a non-default location, you can
determine it as follows:
In a clustered environment, the GDS typically points to a directory
that is shared on the network and is read/write accessible for every
cluster node.
The location of the GDS may be changed during a recovery if the
original location is no longer available. (See Changing the GDS location during recovery.)
Backup options when database is used for document storageYou can enable LiveCycle document storage in the LiveCycle
database using the Administration Console. Even though this option
keeps all persistent documents in the database, LiveCycle still
requires the file system-based GDS directory because it is used
to store permanent and temporary files and resources related to
sessions and invocations of LiveCycle.
When you select the “Enable document storage in the database”
option in the Core System Settings in the Administration Console
or by using Configuration Manager, LiveCycle does not allow snapshot
backup mode and rolling backup mode. Therefore, you do not need
to manage backup modes using LiveCycle. If you use this option,
you should back up the GDS only once after enabling the option.
When you recover LiveCycle from a backup, you do not need to rename the
backup directory for the GDS or restore GDS.
|
|
|
