이 페이지에서는 백업 및 DR 개념과 데이터베이스를 캡처하고 액세스하는 데 사용되는 절차를 소개합니다.
백업 및 DR 데이터 가상화
백업/복구 어플라이언스는 애플리케이션 데이터를 가상화하여 비즈니스의 복원력, 민첩성, 클라우드 이동성을 개선하는 확장성이 뛰어난 사본 데이터 관리 플랫폼입니다. 다른 기술에서 서버와 네트워크를 가상화하는 것과 거의 동일한 방식으로 데이터를 가상화하여 작동합니다. 이를 통해 프로덕션 시스템에서 데이터를 캡처하고, 최대한 효율적인 방식으로 관리하고, 필요에 따라 데이터의 가상 사본을 사용할 수 있습니다.
SAP ASE (이전 명칭: Sybase ASE)는 SAP 정보 관리 부서 내의 관계형 데이터베이스 관리 시스템 제품군으로, 여러 관계형 데이터베이스 관리 시스템 제품을 중심으로 합니다.
이 DBA 가이드에서는 Linux 환경에서 백업 및 DR을 사용하여 SAP ASE 애플리케이션 일관성 데이터베이스 데이터를 보호하는 방법을 설명합니다.
백업 및 DR은 다음 SAP ASE 백업 API를 사용합니다.
Linux 변경 블록 추적 및 LVM 스냅샷: Linux 변경 블록 추적 및 LVM 스냅샷을 사용한 SAP ASE 데이터베이스 퀴에스 처리 보류 및 데이터베이스 퀴에스 처리 출시 API
파일 기반 백업: SAP ASE 덤프 데이터베이스 파일 기반 백업 API
이렇게 하면 백업 형식으로 데이터베이스의 전체 및 증분 백업이 제공됩니다. 복구 시 restore DB API는 데이터 영역을 물리적으로 덮어써서 데이터베이스를 복구합니다.
로그 백업: 로그 백업 중에 백업 및 DR 로그 스테이징 디스크에 로그를 덤프하기 위해 호출된 덤프 트랜잭션 API
작동 방식: Linux CBT를 사용한 백업 및 DR 볼륨 기반 백업
데이터 백업 및 복구는 다음 단계를 따릅니다.
백업 및 DR 에이전트에는 데이터베이스 데이터 영역에서 변경된 블록을 추적하는 CBT가 있습니다.
에이전트는 데이터 백업을 위해 데이터베이스 API를 호출하여 데이터베이스를 정지하거나 일시중지합니다.
[[["이해하기 쉬움","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\u003eBackup and DR virtualizes application data to enhance business resilience, agility, and cloud mobility.\u003c/p\u003e\n"],["\u003cp\u003eThis guide details how to protect SAP ASE databases using Backup and DR in a Linux environment, utilizing both Linux change block tracking (CBT) with LVM snapshots and file-based backup APIs.\u003c/p\u003e\n"],["\u003cp\u003eBackup and DR captures data by adding servers, discovering databases, defining backup policies, and assigning those policies to the discovered databases.\u003c/p\u003e\n"],["\u003cp\u003eData backup and recovery with volume-based backups involve using CBT to track changes, creating LVM snapshots, and copying changed blocks to a backup appliance.\u003c/p\u003e\n"],["\u003cp\u003eFile-based backups utilize the dump backup command to write backup images to a mounted disk, and log backups are handled directly from the file system.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service for SAP ASE\n\nThis page introduces Backup and DR concepts and the procedures\nused to capture and access databases.\n\nBackup and DR data virtualization\n---------------------------------\n\nA backup/recovery appliance is a highly scalable copy data management platform\nthat virtualizes application data to improve the resiliency, agility, and cloud\nmobility of your business. It works by virtualizing data in much the same way\nother technologies have virtualized servers and networks. This lets you\ncapture data from production systems, manage it in the most efficient way\npossible, and use virtual copies of the data however they are needed.\n\nSAP ASE (formerly Sybase ASE) is a is a family of relational database\nmanagement systems within SAP Information Management division that\nis centered on several relational database management system offerings.\nThis DBA guide explains how to protect SAP ASE application consistent database\ndata with Backup and DR in a Linux environment.\n\nBackup and DR uses these SAP ASE backup APIs:\n\n- **Linux change block tracking and LVM snapshot**: SAP ASE quiesce database\n hold and quiesce database release API with Linux change block tracking and\n LVM snapshot.\n\n- **File-based backups**: SAP ASE dump database file-based backups API.\n This provides the Full+Incremental backups of the database\n in backup format. On recovery, the restore DB API recovers\n the database by physically overwriting the data area.\n\n- **Log backup**: During a log backup the dump transaction API\n called to dump logs to a Backup and DR log staging disk.\n\nHow it works: Backup and DR volume-based backup with Linux CBT\n--------------------------------------------------------------\n\nData backup and recovery follows these steps:\n\n1. The Backup and DR agent has CBT to track changed blocks in the database data\n area.\n\n2. The agent calls the database API to freeze or pause database for data backup.\n\n3. Agent creates LVM snapshot of database data area and synthesizes a bitmap.\n\n4. Agent call to database API to unfreeze database.\n\n5. Agent copies changed blocks to backup/recovery appliance, which then deletes\n the snapshot and catalogs the backup.\n\n6. The appliance issues an internal snapshot and synthesizes a point-in-time\n virtual full backup.\n\n7. For data recovery, Backup and DR instantly mounts a rewritable staging disk\n and brings the database online.\n\nHow it works: file-based backup\n-------------------------------\n\nData backup and recovery with file-based backup images follows these steps:\n\n1. Backup and DR agent is deployed in the database server.\n\n2. Mount staging disk on the database server.\n\n3. Invoke Full + Incremental backup using the dump backup command,\n writing the backup image to the mounted disk.\n\n4. Backup and DR takes an internal snapshot.\n Log backups are done in a similar fashion directly from the file-system at\n any schedule that you configure.\n\n5. For data recovery, Backup and DR instantly mounts the staging disk to the\n database server and initiates the database restore operation.\n Logs can be played to any point in time after the database is restored.\n\n6. For recovery, Backup and DR instantly mounts the staging disk to the database\n server and initiates the database restore operation.\n Logs can be played to any point in time after the database is restored.\n\nCapture data\n------------\n\nCapturing data consists of four steps:\n\n1. Add servers that host databases.\n\n2. Discover the databases.\n\n3. Define Backup and DR policy templates and resource profiles according to\n your RPOs and RTOs.\n\n4. Assign Backup and DR policy templates and resource profiles to discovered\n databases. The jobs runs on schedule defined in the policy template.\n\nSAP ASE configurations support\n------------------------------\n\nSAP ASE primary and standby protection can be set from primary or the standby.\nProtection is at the instance level residing on protected LVM. Transaction log\nprotection is from the primary instance only.\n\nWhat's next\n-----------\n\n[Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/otherdb-prep-database)\n\nOther documentation for Backup and DR for SAP ASE\n-------------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nSAP ASE databases with Backup and DR.\nYou can find additional information at:\n\n- [Backup and DR for SAP ASE](/backup-disaster-recovery/docs/concepts/sap-ase-intro)\n- [Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/otherdb-prep-database)\n- [Add a SAP ASE database host and discover databases](/backup-disaster-recovery/docs/configuration/otherdb-add-host)\n- [Define policy templates and resource profiles](/backup-disaster-recovery/docs/create-plan/create-template)\n- [Set application details and settings](/backup-disaster-recovery/docs/backup/app-details-settings-otherdb)\n- [Check staging disk format and backup method](/backup-disaster-recovery/docs/backup/backup-method-staging-disk-otherdb)\n- [Protect the SAP ASE database and its logs](/backup-disaster-recovery/docs/backup/otherdb-protect)\n- [Mount a SAP ASE database](/backup-disaster-recovery/docs/access-data/otherdb-mounts)\n- [Recover SAP ASE Backups](/backup-disaster-recovery/docs/restore-data/otherdb-restore)\n- [Create a SAP ASE Backup and DR Workflow](/backup-disaster-recovery/docs/access-data/otherdb-workflow)"]]
