GDS location
If 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/AEMformsserver/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:
- Log in to administration console and click Settings > Core System Settings > Configurations.
- Record the location that is specified in the Global Document Storage Directory box.
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 storage
You can enable AEM forms document storage in the AEM forms database using the administration console. Even though this option keeps all persistent documents in the database, AEM forms 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 AEM forms.
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, AEM forms does not allow snapshot backup mode and rolling backup mode. Therefore, you do not need to manage backup modes using AEM forms. If you use this option, you should back up the GDS only once after enabling the option. When you recover AEM forms from a backup, you do not need to rename the backup directory for the GDS or restore GDS.
AEM repository
AEM repository (crx-repository) is created if crx-repository is configured while installing AEM forms. The location of the crx-repository directory is determined during the AEM forms installation process. AEM repository backup and restore is required along with database and GDS for consistent AEM forms data in AEM forms. AEM repository contains data for Correspondence Management Solution, Forms manager, and AEM Forms Workspace.
Correspondence Management Solution
Correspondence Management Solution centralizes and manages the creation, assembly and delivery of secure, personalized, and interactive correspondences. It enables you to quickly assemble correspondence from both pre-approved and custom-authored content in a streamlined process from creation to archival. As a result, your customers get timely, accurate, convenient, secure, and relevant communication. Your business maximizes the value of customer interactions and minimizes cost and risk with a process that is streamlined for ease, speed, and productivity.
A simple Correspondence Management Solution setup includes an author instance and a publish instance on the same machine or on different machines
forms manager
forms manager streamlines the process of updating, managing, and retiring forms.
AEM Forms Workspace
AEM Forms Workspace matches the capabilities of the (Deprecated for AEM forms on JEE) Flex Workspace and adds new capabilities to extend and integrate Workspace and make it more user-friendly.
It allows for task management on clients without Flash Player and Adobe Reader. It facilitates rendition of HTML Forms, besides PDF forms and Flex forms.
AEM forms database
The AEM forms database stores content such as form artifacts, service configurations, process state, and database references to files in the GDS and the Content Storage Root directory (for Content Services). Database backups can be performed in real time without an interruption in service, and recovery can be to a specific point in time or to a particular change. This section describes how to configure your database so that it can be backed up in real time.
On a properly configured AEM forms system, the system administrator and the database administrator can easily collaborate to recover the system to a consistent, known state.
To back up the database in real time, you must either use snapshot mode or configure your database to run in the specified log mode. This allows your database files to be backed up while the database is open and available for use. Furthermore, the database preserves its rollback and transaction logs when it is running in these modes.
DB2
Configure your DB2 database to run in archive log mode.
IBM has a suite of tools and help systems to help database administrators manage their backup and recovery tasks:
- IBM DB2 Archive Log Accelerator
- IBM DB2 Data Archive expert (See IBM DB2 Data Archive Expert User’s Guide and Reference.)
DB2 has built-in capabilities to back up a database to Tivoli Storage Manager. By using Tivoli Storage Manager, DB2 backups can be stored on other media or the local hard drive.
For more information about DB2 database backup and recovery, see Developing a backup and recovery strategy for DB2.
Oracle
Use snapshot backups or configure your Oracle database to run in archive log mode. (See Oracle Backup: An Introduction.) For more information about backing up and recovering your Oracle database, go to these sites:
Oracle Backup and Recovery: Explains the concepts of backup and recovery and the most common techniques for using Recovery Manager (RMAN) for backup, recovery, and reporting in more detail, as well as providing more information about how to plan a backup and recovery strategy.
Oracle Database Backup and Recovery User’s Guide: Provides in-depth information about RMAN architecture, backup and recovery concepts and mechanisms, advanced recovery techniques such as point-in-time recovery and database flashback features, and backup and recovery performance tuning. It also covers user-managed backup and recovery, using host operating system facilities instead of RMAN. This volume is essential for backup and recovery of more sophisticated database deployments and for advanced recovery scenarios.
Oracle Database Backup and Recovery Reference: Provides complete information about syntax and semantics for all RMAN commands, and describes the database views that are available for reporting on backup and recovery activities.
SQL Server
Use snapshot backups or configure your SQL Server database to run in transaction log mode.
SQL Server also provides two backup and recovery tools:
- SQL Server Management Studio (GUI)
- T-SQL (command line)
For more information, see Backup and Restore.