정책 재정의. 선택한 백업 템플릿에서 이전에 구성된 특정 정책 설정을 재정의합니다. 고급 설정은 특정 상황에서 유용하거나 필요할 수 있습니다. 자세한 내용은 고급 설정 구성하기를 참고하세요.
볼륨 관리를 클릭하여 볼륨 관리 대화상자를 엽니다.
보호할 수 있는 볼륨을 선택합니다.
볼륨이 많은 경우 검색창을 사용하여 특정 볼륨을 찾습니다.
일반 LVM 스크립트 이름이 genlvmscript.sh 스크립트인지 확인합니다.
LVM 스냅샷 예약 공간의 경우 필요에 따라 예약 공간을 변경합니다.
기본값은 20%입니다.
저장을 클릭하여 멤버십 관리 구성을 저장합니다.
백업 계획 적용을 클릭하여 백업 템플릿과 리소스 프로필을 적용합니다.
성공 메시지가 열립니다.
확인을 클릭합니다.
권장 스토리지 용량 또는 스냅샷 한도를 초과하는 백업/복구 어플라이언스에 워크로드를 백업하면 데이터를 다른 백업/복구 어플라이언스에 백업하라는 추천이 포함된 알림이 표시됩니다.
백업 템플릿에 정의된 운영 시간에 따라 예약된 작업이 실행될 때까지 애플리케이션이 백업되지 않을 수 있습니다.
예를 들어 10:00 (UTC)에 02:00~05:00 (UTC)의 영업시간이 있는 템플릿을 할당하면 다음 날 02:00 (UTC)에 어플라이언스에 사용 가능한 작업 슬롯이 있을 때까지 첫 번째 작업이 시작되지 않습니다.
작업을 즉시 실행하려면 주문형 캡처 실행을 참고하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eBefore managing a generic application, scripts must be copied to a specific folder on the database server, as detailed in the database administrator's guide.\u003c/p\u003e\n"],["\u003cp\u003eManaging a backup plan for a generic application involves selecting a template and profile from the respective drop-down lists on the "Manage Backup Plan" page.\u003c/p\u003e\n"],["\u003cp\u003eApplication-specific settings, such as the backup data capture method, and policy override settings can be configured on the "Apply backup plan" page.\u003c/p\u003e\n"],["\u003cp\u003eThe "Manage Volumes" dialog allows for the selection of volumes to protect and verification of the Generic LVM script, with the option to adjust LVM snapshot reserve space.\u003c/p\u003e\n"],["\u003cp\u003eAfter applying the backup plan, the application backup will occur according to the defined schedule, which is determined by the hours of operation specified in the backup template, or you can perform an on-demand capture.\u003c/p\u003e\n"]]],[],null,["# Apply a backup plan to a generic application (LVM)\n\nBefore you can manage a generic application, you must copy\nscripts to a specific folder on the database server. For details on those\nscripts, consult the database administrator's guide for the database to be\nprotected.\n\nUse these instructions to apply a backup template and manage:\n\n1. Click the **App Manager** menu and select **Applications** from the\n drop-down menu. The **Applications** page opens.\n\n2. Select the **Generic** application (LVM) that you want to manage, and then\n **Manage Backup Plan** from the drop-down list at the bottom right corner of\n the page. The **Manage Backup Plan** page opens.\n\n3. From the **Manage Backup Plan** page, choose from the **Template** and\n **Profile** drop-down lists:\n\n - **Template.** An existing backup template that includes policies to define\n the snapshot or replication of the application data.\n\n - **Profile.** An existing resource profile that defines the resources used\n to store the data of the application as snapshot or replicated images.\n\n The **Manage Backup Plan** page shows a view of the policies assigned to the\n selected applications in the backup plan policy map. Data capture management\n comes from the template policies and profiles that you designed in the backup\n plans.\n4. Click **Apply Backup Plan** . The **Apply backup plan** page opens.\n\n5. Configure the database or instance details and settings or policy\n overrides settings.\n\n - **Application Settings.** Configure application-specific settings like\n backup data capture method (required). See\n [Configure application settings for generic application (LVM)](/backup-disaster-recovery/docs/backup/configure-app-settings-generic-apps) for\n details.\n\n - **Policy Override.** Override specific policy settings previously configured\n in the selected backup template. Advanced settings can be useful or\n required in certain circumstances. See [Configure advanced settings](/backup-disaster-recovery/docs/create-plan/policy-settings)\n for details.\n\n | **Note:** You can override policy settings only if the policy template **Allow Overrides on Policy Settings** parameter has been set to **Yes**.\n6. Click **Manage Volumes** to open the **Manage Volumes** dialog.\n\n | **Note:** The settings in the **Manage Volumes** dialog reflect the settings selected when the **Generic** application was created. In most cases you won't need to make any changes.\n 1. Select the eligible volumes to protect.\n\n 2. In case there are a large number of volumes, use the search box to\n find a specific volume.\n\n 3. Verify that the **Generic LVM script name** is the `genlvmscript.sh`\n script.\n\n 4. For **LVM snapshot reserve space**, change the reserve space as needed.\n By default it is 20%.\n\n | **Note:** **Generic Application** (LVM) leverages LVM snapshots along with the LVM script to achieve application consistency. This is the space LVM will consume to track changes to production volumes when an LVM snapshot is in effect. By default it is 20%.\n 5. Click **Save** to save the manage membership configuration.\n\n7. Click **Apply Backup Plan** to apply the backup template and resource profile.\n A success message opens.\n\n8. Click **Okay**.\n\n The application might not get backed up until the scheduled job runs\n according to the hours of operations defined in the backup template.\n For example, if at 10:00 (UTC) you assign a template that has hours of\n operation from 02:00 to 05:00 (UTC), then the first job won't start\n until the appliance has an available job slot at 02:00 (UTC) of the following day.\n To run a job immediately, see [perform an on-demand capture](/backup-disaster-recovery/docs/monitor-reports/monitor-jobs#run).\n | **Note:** All policies start and end times are in UTC time zone.\n\n| **Note:** To reset one or more application settings back to its default state, click the **Reset to Default** checkbox to the right of the selection you want to reset, or click **Reset All to Default** to reset all application selections back to their default state."]]
