Apply a backup plan to a generic application (LVM)

Before you can manage a generic application, you must copy scripts to a specific folder on the database server. For details on those scripts, consult the database administrator's guide for the database to be protected.

Use these instructions to apply a backup template and manage:

  1. Click the App Manager menu and select Applications from the drop-down menu. The Applications page opens.

  2. Select the Generic application (LVM) that you want to manage, and then Manage Backup Plan from the drop-down list at the bottom right corner of the page. The Manage Backup Plan page opens.

  3. From the Manage Backup Plan page, choose from the Template and Profile drop-down lists:

    • Template. An existing backup template that includes policies to define the snapshot or replication of the application data.

    • Profile. An existing resource profile that defines the resources used to store the data of the application as snapshot or replicated images.

      The Manage Backup Plan page shows a view of the policies assigned to the selected applications in the backup plan policy map. Data capture management comes from the template policies and profiles that you designed in the backup plans.

  4. Click Apply Backup Plan. The Apply backup plan page opens.

  5. Configure the database or instance's details and settings or policy overrides settings.

  6. Click Manage Volumes to open the Manage Volumes dialog.

    1. Select the eligible volumes to protect.

    2. In case there are a large number of volumes, use the search box to look up a specific volume.

    3. Verify that the Generic LVM script name is the genlvmscript.sh script.

    4. For LVM snapshot reserve space, change the reserve space as needed. By default it is 20%.

    5. Click Save to save the manage membership configuration.

  7. Click Apply Backup Plan to apply the backup template and resource profile. A success message opens.

  8. Click Okay.

    The application may not get backed up until the scheduled job runs according to the hours of operations defined in the backup template. For example, if at 10:00 (UTC) you assign a template that has hours of operation from 02:00 to 05:00 (UTC), then the first job will not start until the appliance has an available job slot at 02:00 (UTC) of the following day. To run a job immediately, see perform an on-demand capture.