Backing up the LiveCycle data

This section describes the steps that are required to complete a hot, or online, backup of the LiveCycle database, the GDS, and Content Storage Root directories.

After LiveCycle is installed and deployed to production areas, the database administrator should perform an initial full, or cold, backup of the database. The database must be shut down for this backup. Then, differential or incremental (or hot) backups of the database should be done regularly.

To ensure a successful backup and recovery, a system image backup must be available at all times. Then, if a loss occurs, you can recover your entire environment to a consistent state.

Backing up the database at the same time as the GDS, AEM repository, and Content Storage Root directory backups helps keep these systems synchronized if recovery is ever required.

The backup procedure described in this section requires you to enter safe backup mode before you back up the LiveCycle database, AEM repository, GDS, and Content Storage Root directories. When backup is complete, you must exit safe backup mode. Safe backup mode is used to mark long-lived and persistent documents that reside in the GDS. This mode ensures that the automated file cleanup mechanism (the file collector) does not delete expired files until the safe backup mode is released. It is necessary to keep a GDS backup in synchronization with a database backup.

How often the GDS location must be backed up depends on how LiveCycle is used and the backup windows available. The backup window can be affected by long-lived processes because they can run for several days. If you are continually changing, adding, and removing files in this directory, you should back up the GDS location more often.

If the database is running in a logging mode, as described in the previous section, the database logs also must be backed up frequently so that they can be used to restore the database in case of media failure.

Note: Files that are not referenced may persist in the GDS directory after the recovery process. This is a known limitation at this time.

    Back up the database, GDS, AEM repository, and Content Storage Root directories

    You must put LiveCycle in either the safe backup (snapshot) mode or the rolling backup (continuous coverage) mode. Before you set LiveCycle to enter either of the backup modes, ensure the following:

    • Verify the system version and record the patches or updates that were applied since the last complete system image backup was performed.

    • If you are using either rolling or snapshot mode backups, ensure that your database is configured with the correct log settings to allow for hot backups of the database. (See LiveCycle database.)

    In addition to these, observe the following guidelines for the backup/restore process.

    • Back up the GDS directory by using an available operating system or a third-party backup utility. (See GDS location.)

    • (Optional) Back up the Content Storage Root directory by using an available operating system or a third-party backup and utility. (See Content Storage Root location (stand-alone environment) or Content Storage Root location (clustered environment).)

    • Back up author and publish instances (crx-repository backup).

      To back up the Correspondence Management Solution environment, perform the steps on the author and publish instances as described in Backup and Restore.

      Consider the following points when backing up the author and publish instances:

      • Ensure that backup for author and publish instances are synchronized to start at the same time.Although you can continue to use author and publish instances while the backup is being performed, it is recommended not to publish any asset during the backupto avoid any uncaptured changes. Wait for the backup of both author and publish instances to end before publishing new assets.

      • The complete backup of Author node includes backup of Forms Manager and HTML Workspace data.

      • Workbench developers can continue to work on their processes locally. They should not deploy any new processes during the backup phase.

      • The decision about the length of each backup session (for rolling backup mode) should be based on the total time taken to back up all the data in LiveCycle (DB,GDS, AEM repository, and any other additional custom data).

    You should back up the LiveCycle database, including any transaction logs. (See LiveCycle database.) For more information, see the appropriate knowledge base article for your database:

    These articles provide guidance to basic database features for the backup and recovery of data. They are not intended as all-inclusive technical guides of a specific vendor's database backup and recovery feature. They outline commands that are required to create a reliable database backup strategy for your LiveCycle application data.

    Note: The database backup must be complete before you begin backing up the GDS. If the database backup is not complete, your data will be out of sync.

    Entering the backup modes

    You can use either Administration Console, the LCBackupMode command, or the API available with the LiveCycle installation to enter and leave backup modes. Note that for rolling backup (continuous coverage), the Administration Console option is not available; you should use either the command line option or the API. For information about using the API to enter and leave backup modes, see LiveCycle API Reference.

    Note: If you configured SSL on the LiveCycle server, then you cannot place the LiveCycle server in back up mode using LCBackupMode.CMD script.

    Using the Administration Console to enter safe backup mode

    1. Log in to Administration Console.

    2. Click Settings > Core System Settings > Backup Utilities.

    3. Select Operate In Safe Backup Mode and click OK.

      This method puts LiveCycle into backup mode indefinitely (no time out), and it enters snapshot mode rather than rolling backup mode.

    Using the command line option to enter safe backup mode

    You can use the command line interface LCBackupMode scripts to put LiveCycle in safe backup mode.

    1. Set ADOBE_LIVECYCLE and start the application server.

    2. Go to the [LiveCycle root]/sdk/misc/Foundation/BackupRestoreCommandline folder.

    3. Depending on your operating system, edit the LCBackupMode.cmd or LCBackupMode.sh script to provide default values that are appropriate for your system.

    4. At the command prompt, run the following command on a single line:

      • (Windows) LCBackupMode.cmd enter [-Host=hostname] [-port=portnumber] [-user=username] [-password=password] [-label=labelname] [-timeout=seconds]

      • (Linux, UNIX) LCBackupMode.sh enter [-host=hostname] [-port=portnumber] [-user=username] [-password=password] [-label=labelname]

      In the previous commands, the placeholders are defined as follows:

      Host is the name of the host where LiveCycle is running.

      port is the WebServices port of the application server on which LiveCycle is running.

      user is the user name of the LiveCycle administrator.

      password is the password of the LiveCycle administrator.

      label is the text label, which can be any string, for this backup.

      timeout is the number of seconds after which the backup mode is automatically left. It can be 0 to 10,080. If it is 0, which is the default, the backup mode never times out.

      For more information about the command line interface to the backup mode, see the Readme file in the BackupRestoreCommandline directory.

    Leaving backup modes

    You can use either the Administration Console or the command line option to leave backup modes.

    Leave safe backup mode (snapshot mode)

    To use Administration Console to take LiveCycle out of safe backup mode (snapshot mode), perform the following tasks.

    1. Log in to Administration Console.

    2. Click Settings > Core System Settings > Backup Utilities.

    3. Deselect Operate In Safe Backup Mode and click OK.

    Leave all backup modes

    You can use the command line interface to take LiveCycle out of safe backup mode (snapshot mode) or to end the current backup mode session (rolling mode). Note that you cannot use the Administration Console to leave rolling backup mode. While in rolling backup mode, the Backup Utilities controls on the Administration Console are disabled. You must use either API call or use the LCBackupMode command.

    1. Go to the [LiveCycle root]/sdk/misc/Foundation/BackupRestoreCommandline folder.

    2. Depending on your operating system, edit the LCBackupMode.cmd or LCBackupMode.sh script to provide default values that are appropriate for your system.

      Note: You must set the JAVA_HOME directory as described in the appropriate chapter for your application server in Preparing to Install LiveCycle.

    3. Run the following command on a single line:

      • (Windows) LCBackupMode.cmd leaveContinuousCoverage [-Host=hostname] [-port=portnumber] [-user=username] [-password=password]

      • (Linux, UNIX) LCBackupMode.sh leaveContinuousCoverage [-Host=hostname] [-port=portnumber] [-user=username] [-password=password]

        In the previous commands, the placeholders are defined as follows:

        Host is the name of the host where LiveCycle is running.

        port is the port on which LiveCycle is running on the application server.

        user is the user name of the LiveCycle administrator.

        password is the password of the LiveCycle administrator.

        leaveContinuousCoverage Use this option to disable rolling backup mode completely.

      Important: For the time that backup mode is off, continuous coverage cannot be reestablished. Any changes during that time are not protected.
      Note: If you enabled document storage in database, the snapshot backup mode and rolling backup modes are not applicable.

      For more information about the command line interface to the backup mode, see the readme file in the BackupRestoreCommandline directory.

    // Ethnio survey code removed