Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Setelah rencana pencadangan dikonfigurasi seperti yang dijelaskan dalam
Mengelola template pencadangan, Anda dapat mengonfigurasi metode pencadangan
untuk database atau instance.
Microsoft SQL Server,
Oracle, dan
database SAP HANA
masing-masing memiliki dokumentasinya sendiri. Jenis database lain yang didukung ini memiliki
banyak prosedur yang sama.
Perlindungan instance database Db2 dapat dilakukan dari node
utama atau dari node HADR. Untuk melindungi dari node HADR Db2, node harus
dapat dibaca. Pastikan parameter DB2_HADR_ROS=ON ditetapkan.
Jika database SAP ASE dilindungi dengan pencadangan berbasis Full+Incremental,
database sumber dan target harus menggunakan set karakter atau urutan pengurutan yang sama
agar pemulihan berhasil. Untuk mengetahui detailnya, lihat
SAP Note: 1860413 - How to change character set or sort order of SAP ASE.
Untuk melindungi database atau instance database, selesaikan langkah-langkah berikut:
Di halaman Kelola Rencana Cadangan, pilih template dan profil resource,
lalu klik Terapkan Rencana Cadangan.
Jika Anda mencadangkan beban kerja ke appliance pencadangan/pemulihan yang akan melampaui kapasitas penyimpanan atau batas snapshot yang direkomendasikan, Anda akan melihat notifikasi dengan rekomendasi untuk mencadangkan data ke appliance pencadangan/pemulihan yang berbeda.
Klik Detail & Setelan dan pastikan metode pengambilan cadangan
cocok dengan jenis cadangan yang ditetapkan di Kelola template cadangan.
Klik Terapkan paket pencadangan atau Simpan Perubahan. Instance muncul di
App Manager dengan ikon perisai.
Instance dilindungi saat tugas snapshot berhasil sesuai dengan
jadwal dalam template.
Jika Anda melindungi instance, Anda dapat menyertakan atau mengecualikan database tertentu selama pencadangan. Dari Pengelola Aplikasi, pilih instance. Gunakan kotak centang untuk memfilter daftar.
Pilih Kelola paket pencadangan.
Di bagian Aturan Penyertaan Database, klik Edit. Jika Anda tidak
melihat setelan Pencantuman Database, Anda telah memilih database,
bukan instance.
Pilih Aturan Penyertaan—Sertakan Semua, Sertakan yang Dipilih,
atau Kecualikan yang Dipilih—lalu pilih database yang akan disertakan
atau dikecualikan, lalu klik Simpan.
Melindungi log database
Untuk mengaktifkan dan menyiapkan pencadangan log database, ikuti langkah-langkah berikut:
Dari halaman Template Paket Pencadangan, klik kanan template yang akan digunakan untuk melindungi instance, lalu klik Edit.
Klik panah di samping kebijakan snapshot untuk membuka detailnya,
lalu klik Edit Kebijakan.
Di dekat bagian bawah, pilih Setelan Kebijakan Lanjutan.
Tetapkan opsi kebijakan log—Anda harus men-scroll untuk melihat semuanya:
Aktifkan Pangkas/Hapus log setelah pencadangan.
Setel Enable Database Log Backup ke Yes.
Untuk RPO (Menit), jika Aktifkan Pencadangan Log Database disetel ke
Ya, RPO menentukan frekuensi pencadangan log database. Frekuensi ditetapkan dalam menit dan tidak boleh melebihi interval pencadangan database. Nilai terkecil yang dapat disetel adalah 15 menit.
Tetapkan Periode Retensi Cadangan Log (dalam Hari) untuk pemulihan point-in-time.
Setel Replicate Logs (Uses StreamSnap Technology) ke Yes jika
Anda ingin mengaktifkan replikasi StreamSnap dari pencadangan log ke situs DR.
Tetapkan Send Logs to OnVault Pool ke Yes jika Anda ingin log database dikirim ke kumpulan OnVault, sehingga memungkinkan pemulihan point-in-time dari OnVault di situs lain.
Klik Simpan Perubahan.
Dari daftar Aplikasi Pengelola Aplikasi, pilih instance.
Anda dapat menggunakan kotak centang di sebelah kiri untuk memfilter daftar.
Klik kanan, lalu pilih Kelola Rencana Cadangan.
Di bagian atas layar, pilih Detail & Setelan.
Tetapkan Retensi Log DB Produksi dalam jam. Nilai ini digunakan untuk menghapus log dari tujuan produksi. Berdasarkan setelan ini,
log akan dihapus jika sudah lebih lama dari jumlah jam yang ditentukan.
Jika nilai default tidak ditentukan, nilai defaultnya adalah 24 jam.
Klik Simpan.
Langkah berikutnya
Database dan instance Anda dicadangkan sesuai jadwal yang ditetapkan dalam rencana pencadangannya. Untuk meninjau dan melaporkan aktivitas Backup and DR, Anda dapat melihat dasbor konsol pengelolaan dan memeriksa laporan di pengelola laporan.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis page provides instructions on how to configure backup methods for various database types and instances, including Microsoft SQL Server, Oracle, SAP HANA, IBM Db2, MariaDB, MySQL, PostgreSQL, SAP ASE, SAP IQ, and SAP MaxDB.\u003c/p\u003e\n"],["\u003cp\u003eDatabase or instance protection is generally set for the entire instance, with the exception that virtual databases can be protected separately, and you can use inclusion rules to include or exclude specific databases during the process.\u003c/p\u003e\n"],["\u003cp\u003eYou can enable and configure database log backups, including settings for log truncation, RPO, retention period, log replication to a DR site, and sending logs to an OnVault pool.\u003c/p\u003e\n"],["\u003cp\u003eAfter setting up a backup plan you can monitor the success of backup and recovery by viewing the management console dashboard and reports.\u003c/p\u003e\n"],["\u003cp\u003eWhen protecting SAP ASE databases, only user database transaction logs are backed up, so to prevent production backup jobs failing, system database logs need to be cleared manually.\u003c/p\u003e\n"]]],[],null,["After the backup plan is configured as detailed in [Manage backup templates](/backup-disaster-recovery/docs/create-plan/create-template), you can configure a backup method for the database or instance.\n\n\u003cbr /\u003e\n\n[Microsoft SQL Server](/backup-disaster-recovery/docs/backup/sql-protect),\n[Oracle](/backup-disaster-recovery/docs/backup/oracle-db-protect), and\n[SAP HANA](/backup-disaster-recovery/docs/backup/protect-sap-db) databases\neach have their own documentation. These other supported database types share\nmany procedures.\n\nThe following are the other supported database types:\n\n- [IBM Db2](/backup-disaster-recovery/docs/concepts/db2-intro)\n\n- [MariaDB](/backup-disaster-recovery/docs/concepts/mariadb-intro)\n\n- [MySQL](/backup-disaster-recovery/docs/concepts/mysql-intro)\n\n- [PostgreSQL](/backup-disaster-recovery/docs/concepts/postgresql-intro)\n\n- [SAP ASE](/backup-disaster-recovery/docs/concepts/sap-ase-intro)\n\n- [SAP IQ](/backup-disaster-recovery/docs/concepts/sap-iq-intro)\n\n- [SAP MaxDB](/backup-disaster-recovery/docs/concepts/maxdb-intro)\n\n| **Note:** With one exception, protection is set for the entire instance. You can include or exclude specific databases during the process using a database inclusion rule from the **Manage Backup Plan** page. The exception is that virtual databases can be protected separately from the instance when created.\n\nProtect a database or a database instance\n\nDb2 database instance protection can be done from either the primary\nnode or from HADR nodes. To protect from a Db2 HADR node, the node must\nbe read-enabled. Ensure that the parameter `DB2_HADR_ROS=ON` is set.\n\nWhen an SAP ASE database is protected with Full+Incremental based backup,\nthe source and target databases must use the same character set or sort order\nfor a successful restore. For details refer to\n[SAP Note: 1860413 - How to change character set or sort order of SAP ASE](https://userapps.support.sap.com/sap/support/knowledge/en/1860413).\n\nTo protect the database or database instance, complete the following:\n\n1. Click **App Manager** \\\u003e **Applications** , right-click the instance\n and select **Manage Backup Plan**.\n\n2. On the **Manage Backup Plan** page, select a template and a resource profile,\n then click **Apply Backup Plan**.\n\n If you back up a workload to a backup/recovery appliance that would exceed its\n recommended storage capacity or snapshot limit, you will see a notification\n with a recommendation to back up the data to a different backup/recovery appliance.\n | **Caution:** Exceeding the capacity of a backup/recovery appliance can lead to failed jobs and unprotected data and failed restore operations.\n3. Click **Details \\& Settings** and ensure that the backup capture method\n matches the type of backup set in [Manage backup templates](/backup-disaster-recovery/docs/create-plan/create-template).\n Click **Apply backup plan** or **Save Changes** . The instance appears in\n the **App Manager** with a shield icon.\n\n The instance is protected when the snapshot job succeeds according to the\n schedule in the template.\n4. If you are protecting an instance, then you can include or exclude\n specific databases during backup. From the **App Manager** , select the\n instance. Use the checkboxes to filter the list.\n Select **Manage backup plan**.\n\n5. Under **Database Inclusion Rule** , click **Edit** . If you do not\n see the **Database Inclusion** settings, you have selected a database,\n not an instance.\n\n6. Select an **Inclusion Rule** ---**Include All** , **Include Selected** ,\n or **Exclude Selected** ---and then select the databases to include\n or exclude, then click **Save**.\n\nProtect database logs\n\nTo enable and set up database log backup, follow these steps:\n\n1. From the **Backup Plans Templates** page, right-click the template\n that will be used for protecting the instance and click **Edit**.\n\n2. Click the arrow beside the snapshot policy to open up the details,\n then click **Edit Policy**.\n\n3. Near the bottom, select **Advanced Policy Settings**.\n\n4. Set the log policy options---you have to scroll to see them all:\n\n - Enable **Truncate/Purge log after backup**.\n\n - Set **Enable Database Log Backup** to **Yes**.\n\n - For **RPO (Minutes)** , when **Enable Database Log Backup** is set to\n **Yes**, RPO defines the frequency for database log backup. Frequency is set\n in minutes and must not exceed the database backup interval. The smallest\n value that can be set is 15 minutes.\n\n - Set **Log Backup Retention Period (in Days)** for point in time recovery.\n\n - Set **Replicate Logs (Uses StreamSnap Technology)** to **Yes** if\n you want to enable StreamSnap replication of log backup to a DR site.\n\n - Set **Send Logs to OnVault Pool** to **Yes** if you want the database\n logs to be sent to an OnVault pool, enabling for point-in-time\n recoveries from OnVault on another site.\n\n5. Click **Save Changes**.\n\n6. From the **App Manager Applications** list, select the instance.\n You can use checkboxes on the left to filter the list.\n Right-click it and select **Manage Backup Plans**.\n\n7. At the top of the screen, select **Details \\& Settings**.\n\n8. Set the **Retention of Production DB Logs** in hours. This value is\n used to purge the logs from the production destination. Based on this setting,\n the logs are purged if they are older then the number of hours specified.\n If the default value is not specified, then the default value is 24 hours.\n\n9. Click **Save**.\n\n| **Note:** (SAP ASE only) Only user database transaction logs are backed up; System database transaction logs (including master database transaction logs) are not backed up and so they are not truncated. This means that the system database archive log can get full and cause production user database backup jobs to fail. To prevent this, manually clear the system database logs by running the command `dump tran master with no_log`.\n\nWhat's next\n\nYour databases and instances back up on the schedules set in their backup\nplans. To review and report on Backup and DR activity, you can view the\n[management console dashboard](/backup-disaster-recovery/docs/concepts/dashboard)\nand examine the reports in the report manager."]]
