데이터 복구의 경우 백업 및 DR은 재기록 가능한 스테이징 디스크를 즉시 마운트하고 데이터베이스를 온라인으로 가져옵니다.
작동 방식: 파일 기반 백업
파일 기반 백업 이미지를 사용한 데이터 백업 및 복구는 다음 단계를 따릅니다.
백업 및 DR 에이전트가 데이터베이스 서버에 배포됩니다.
데이터베이스 서버에 스테이징 디스크를 마운트합니다.
백업 이미지를 마운트된 디스크에 쓰면서 백업 덤프 명령어를 사용하여 전체+증분 백업을 호출합니다.
백업 및 DR은 내부 스냅샷을 사용합니다.
로그 백업은 구성된 일정에 따라 파일 시스템에서 직접 비슷한 방식으로 실행됩니다.
데이터 복구의 경우 백업 및 DR은 스테이징 디스크를 데이터베이스 서버에 즉시 마운트하고 데이터베이스 복원 작업을 시작합니다.
데이터베이스가 복원된 후 로그를 원하는 지점까지 재생할 수 있습니다.
복구의 경우 백업 및 DR은 스테이징 디스크를 데이터베이스 서버에 즉시 마운트하고 데이터베이스 복원 작업을 시작합니다.
데이터베이스가 복원된 후 로그를 원하는 지점까지 재생할 수 있습니다.
SAP MaxDB API
백업 및 DR은 다음 SAP MaxDB 백업 API를 사용합니다.
Linux CBT 및 LVM 스냅샷: Linux CBT 및 LVM 스냅샷이 포함된 MaxDB UTIL_EXECUTE SUSPEND LOGWRITER 및 UTIL_EXECUTE RESUME LOGWRITER API
파일 기반 백업: MaxDB
dbmcli -d <dbsid> -u <dbm_username>,<dbm_password>backup_start
파일 기반 백업 API
이렇게 하면 백업 형식으로 데이터베이스의 전체 백업이 제공됩니다. 데이터 백업의 기본 요건은 먼저 백업 템플릿을 정의하는 것입니다.
복구 API 복원 db는 데이터 영역을 물리적으로 덮어써서 데이터베이스를 복구합니다.
MaxDB 로그 백업: 애플리케이션 측에서 MaxDB 자동 로그 백업을 사용 설정해야 합니다. 백업 및 DR은 cp 명령어를 사용하여 로그 백업 파일을 스테이징 디스크에 복사합니다. 자동 로그 백업이 사용 설정되어 있으므로 os 명령어를 사용하여 로그 백업을 삭제합니다.
[[["이해하기 쉬움","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\u003eSAP MaxDB, a database management system by SAP SE, is compatible with Microsoft Windows, Linux, Unix, and major hardware platforms.\u003c/p\u003e\n"],["\u003cp\u003eBackup and DR utilizes Linux Changed Block Tracking (CBT) and Logical Volume Manager (LVM) snapshots for efficient volume-based backups of SAP MaxDB, minimizing I/O overhead by tracking only changed blocks.\u003c/p\u003e\n"],["\u003cp\u003eFile-based backups in SAP MaxDB involve deploying a Backup and DR agent, mounting a staging disk, and using the \u003ccode\u003edump backup\u003c/code\u003e command to create backup images, followed by internal snapshots for point-in-time recovery.\u003c/p\u003e\n"],["\u003cp\u003eSAP MaxDB offers specific APIs for both volume-based (CBT/LVM snapshots) and file-based backups, including APIs for suspending/resuming log writers and initiating backup processes, along with log backups.\u003c/p\u003e\n"],["\u003cp\u003eBackup and DR provides a full suite of tools and processes for protecting and recovering SAP MaxDB databases, ranging from preparing the database and defining policies to performing backups, mounts, and restores.\u003c/p\u003e\n"]]],[],null,["# Backup and DR Service for SAP MaxDB\n\nSAP MaxDB is the database management system developed and supported by SAP SE.\nSAP MaxDB is available on Microsoft Windows, Linux, and Unix, and for the most\nprominent hardware platforms.\n\nHow it works: Backup and DR volume-based backup with Linux CBT\n--------------------------------------------------------------\n\nOnly changed blocks are tracked in the bitmap---no copy-on-writes or\nI/O-intensive operations.\n\nData backup and recovery with volume-based backup images and CBT 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\nsteps:\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\nSAP MaxDB APIs\n--------------\n\nBackup and DR uses the following SAP MaxDB backup APIs:\n\n- **Linux CBT and LVM snapshot** : MaxDB `UTIL_EXECUTE SUSPEND LOGWRITER` and\n `UTIL_EXECUTE RESUME LOGWRITER` API with Linux CBT and LVM snapshot\n\n- **File-based backups** : MaxDB\n `dbmcli -d <dbsid> -u <dbm_username>,<dbm_password>backup_start`\n file-based backups API\n\n This provides the full backup of the database in backup format. The\n prerequisite for data backup is to define the backup template first.\n Recovery API restore db recovers the database by physically overwriting the\n data area.\n- **MaxDB log backup**: MaxDB autolog backup must be enabled on the\n application side. Backup and DR copies the log backup files to staging disk\n with cp command. As Autolog Backup is enabled we use os command to purge the\n log backup.\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 MaxDB\n-----------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nMaxDB databases with Backup and DR.\nYou can find additional information at the following pages:\n\n- [Backup and DR for SAP MaxDB](/backup-disaster-recovery/docs/concepts/maxdb-intro)\n- [Prepare the database for Backup and DR](/backup-disaster-recovery/docs/configuration/otherdb-prep-database)\n- [Add a MaxDB 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 MaxDB database and its logs](/backup-disaster-recovery/docs/backup/otherdb-protect)\n- [Mount a MaxDB database](/backup-disaster-recovery/docs/access-data/otherdb-mounts)\n- [Recover MaxDB Backups](/backup-disaster-recovery/docs/restore-data/otherdb-restore)\n- [Create a MaxDB Backup and DR Workflow](/backup-disaster-recovery/docs/access-data/otherdb-workflow)"]]
