SAP ASE（旧 Sybase ASE）は、SAP 情報管理部門のリレーショナル データベース管理システム ファミリーであり、複数のリレーショナル データベース管理システム プロダクトを中心にしています。この DBA ガイドでは、Linux 環境でバックアップと DR を使用して SAP ASE アプリケーションの整合性のあるデータベース データを保護する方法について説明します。
バックアップと DR では、次の SAP ASE バックアップ API が使用されます。
Linux 変更ブロック トラッキングと LVM スナップショット: Linux 変更ブロック トラッキングと LVM スナップショットを使用する SAP ASE quiesce database hold と quiesce database release API。
ファイルベースのバックアップ: SAP ASE ダンプ データベース ファイルベースのバックアップ API。これにより、バックアップ形式でデータベースの完全バックアップと増分バックアップが提供されます。復元時に、restore DB API はデータ領域を物理的に上書きしてデータベースを復元します。
ログ バックアップ: ログ バックアップ中に、ダンプ トランザクション API が呼び出され、バックアップと DR ログのステージング ディスクにログがダンプされます。
仕組み: 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)"]]
