Memasang database ke dalam Grup Ketersediaan AlwaysOn SQL
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Nonaktifkan komentar:
Melakukan pemasangan ke AAG SQL Server menggunakan kumpulan snapshot
Pendekatan ini adalah cara tercepat untuk membuat grup Ketersediaan AlwaysOn SQL Server baru untuk penggunaan jangka pendek. Aplikasi yang terpasang berjalan di
kumpulan snapshot, dan mencapai performa yang sama dengan data yang diambil di
kumpulan snapshot.
Pasang database yang ditambahkan ke grup ketersediaan SQL ke setiap node
di AG, satu node dalam satu waktu. Lihat
Memasang database SQL Server.
Pilih host yang diperlukan.
Pilih instance SQL.
Tentukan waktu teruskan, pastikan untuk menentukan waktu yang sama selama pemasangan ke setiap node.
Di bagian Advanced Options, hapus centang pada Recover Database After Restore.
Masukkan nama, atau awalan atau akhiran. Gunakan nama, awalan, atau
akhiran yang sama di semua node.
Ulangi proses untuk setiap anggota grup ketersediaan.
Setelah semua database di-mount sebagai database virtual di setiap node grup ketersediaan, menggunakan SQL, pilih instance SQL yang merupakan instance utama dan pulihkan setiap database:
`recoverdatabase(name)withrecovery`
Pertahankan salinan database sekunder dalam status pemulihan.
Meng-clone ke grup ketersediaan SQL Server secara independen dari kumpulan snapshot
Untuk meng-clone ke grup Ketersediaan AlwaysOn SQL yang berada secara independen dari kumpulan snapshot, lakukan operasi clone untuk database di setiap node dalam grup Ketersediaan AlwaysOn SQL seperti yang dijelaskan dalam Meng-clone database SQL Server.
Pastikan untuk membatalkan pilihan database Pulihkan setelah pemulihan dan menentukan waktu terus maju yang sama untuk setiap operasi clone.
Menambahkan database virtual ke grup Ketersediaan AlwaysOn SQL Server baru
Setelah semua database untuk AG baru dipulihkan, gunakan SQL Studio atau T-SQL
untuk menambahkan database ke grup Ketersediaan AlwaysOn SQL:
Dari SQL Studio, pilih grup ketersediaan SQL.
Tambahkan database ke grup ketersediaan.
Klik Berikutnya. Anda akan diminta untuk memilih metode sinkronisasi.
Pilih Gabung saja; operasi Gabung saja membentuk database utama dan
sekunder menjadi grup ketersediaan.
Pantau progres operasi. Setelah operasi selesai,
database primer dan sekunder akan disinkronkan.
Jika aplikasi penemuan otomatis tidak diaktifkan, temukan aplikasi secara manual di host grup ketersediaan.
Setelah penemuan selesai, database akan muncul di Pengelola Aplikasi sebagai
anggota grup ketersediaan SQL.
Ambil anggota grup ketersediaan seperti database lainnya.
Panduan DBA SQL Server Backup and DR
Halaman ini adalah salah satu dari serangkaian halaman khusus untuk melindungi dan memulihkan database Microsoft SQL Server dengan Backup dan DR.
Anda dapat menemukan informasi tambahan di halaman berikut:
[[["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-08-25 UTC."],[[["\u003cp\u003eMounting databases to a SQL Server AlwaysOn Availability Group (AAG) using a snapshot pool is the quickest method for short-term use, providing performance comparable to data captured in the pool.\u003c/p\u003e\n"],["\u003cp\u003eWhen mounting databases to an AAG, ensure sufficient space in the snapshot pool to accommodate both the availability group and regular snapshots, as the mounted application operates within the snapshot pool.\u003c/p\u003e\n"],["\u003cp\u003eTo create an AAG independently from the snapshot pool, clone the databases on each node, deselecting "Recover database after restore" and using the same roll-forward time for each clone operation.\u003c/p\u003e\n"],["\u003cp\u003eAfter mounting or cloning, add the recovered databases to the SQL AlwaysOn Availability group via SQL Studio, selecting "Join only" as the synchronization method to form the primary and secondary databases into an availability group.\u003c/p\u003e\n"],["\u003cp\u003eOnce the operation is complete, the databases will appear as members of the SQL availability group in the App Manager and they can then be captured like any other database.\u003c/p\u003e\n"]]],[],null,["# Mount databases into SQL AlwaysOn Availability Groups\n\nDisable comment:\n\nMount to a SQL Server AAG using a snapshot pool\n-----------------------------------------------\n\nThis approach is the fastest way to create a new SQL Server AlwaysOn\nAvailability group for short-term use. The mounted application runs in\nthe snapshot pool, and achieves the same performance as data captured in the\nsnapshot pool.\n| **Note:** Be sure there is enough space in the snapshot pool for the availability group and regular snapshots.\n\n1. Mount the databases being added to the SQL availability group to each node\n in the AG, one node at a time. See\n [Mount a SQL Server database](/backup-disaster-recovery/docs/access-data/sql-access).\n\n2. Select the required host.\n\n3. Select the SQL instance.\n\n4. Specify the roll-forward time, being sure to specify the same time during\n mounts to each node.\n\n5. Under **Advanced Options** , deselect **Recover Database After Restore**.\n\n6. Enter a name, or a prefix or suffix. Use the same name, prefix, or\n suffix on all nodes.\n\n7. Repeat the process for each availability group member.\n\n8. Once all databases are mounted as virtual databases on each availability\n group node, using SQL, select the SQL instance that is the primary and for\n each database recover it:\n\n `recover database (name) with recovery`\n\n9. Keep the secondary database copies in restoring state.\n\n10. When the master database has been restored, using SQL, create the new\n availability group and join the primary and secondary databases as described\n in\n [Add virtual databases to a new SQL Server AlwaysOn Availability group](#AlwaysOn).\n\nClone to a SQL Server availability group independently from the snapshot pool\n-----------------------------------------------------------------------------\n\nTo clone to a SQL AlwaysOn Availability group that resides independently from\nthe snapshot pool, perform a clone operation for the databases on each node in\nthe SQL AlwaysOn Availability group as described in\n[Clone SQL Server databases](/backup-disaster-recovery/docs/restore-data/sql-cloning).\nBe sure to deselect **Recover** database after restore and to specify the same\nroll-forward time for each clone operation.\n\nAdd virtual databases to a new SQL Server AlwaysOn Availability group\n---------------------------------------------------------------------\n\nAfter all databases for the new AG have been recovered, use SQL Studio or T-SQL\nto add the databases to the SQL AlwaysOn Availability group:\n\n1. From SQL Studio, select the SQL availability group.\n\n2. Add the databases to the availability group.\n\n3. Click **Next** . You are prompted to select a synchronization method.\n Select **Join only** ; the **Join only** operation forms the primary and\n secondary databases into an availability group.\n\n4. Monitor the progress of the operation. When the operation is complete,\n both the primary and secondary databases are in sync.\n\n5. If autodiscover applications is not enabled, manually discover\n applications on the availability group host.\n\n6. After discovery is complete, the databases appear in the **App Manager** as\n members of the SQL availability group.\n\n7. Capture members of an availability group just like any other database.\n\nThe Backup and DR Microsoft SQL Server DBA guide\n------------------------------------------------\n\nThis page is one in a series of pages specific to protecting and recovering\nMicrosoft SQL Server databases with Backup and DR.\nYou can find additional information at:\n\n- [Backup and DR for Microsoft SQL Server Databases](/backup-disaster-recovery/docs/concepts/backupdr-for-sql-server)\n- [Prepare SQL Server databases for Backup and DR Service](/backup-disaster-recovery/docs/configuration/prepare-sql-server)\n- [Add a SQL Server database host and discover databases](/backup-disaster-recovery/docs/configuration/discover-sql-server)\n- [Configure backup plans for Microsoft SQL Server instances and databases](/backup-disaster-recovery/docs/backup/back-up-sql-server)\n- [Application details and settings for Microsoft SQL Server instances and databases](/backup-disaster-recovery/docs/backup/app-details-settings-sql-server)\n- [Mount a SQL Server database](/backup-disaster-recovery/docs/access-data/mount-sql-server)\n- [Mount databases into SQL Always On Availability Groups](/backup-disaster-recovery/docs/access-data/mount-sql-server-aag)\n- [Manage an active mount](/backup-disaster-recovery/docs/access-data/manage-active-mounts)\n- [Migrate a SQL Server database](/backup-disaster-recovery/docs/access-data/mount-and-migrate-sql-server-2)\n- [Clone SQL Server databases](/backup-disaster-recovery/docs/access-data/clone-sql-server)\n- [Recover SQL Server backups](/backup-disaster-recovery/docs/restore-data/restore-sql-server)"]]
