[[["わかりやすい","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\u003eThis guide explains the process of backing up Microsoft SQL Server databases to a backup vault, which offers immutability and indelibility to protect against data modification and deletion.\u003c/p\u003e\n"],["\u003cp\u003eTo store backups in a single region you need to create a backup vault, or for multi-region backups you can either use multiple backup vaults in different regions, or a multi-regional Cloud Storage bucket that won't offer the same immutability and indelibility protection.\u003c/p\u003e\n"],["\u003cp\u003eSetting up the backup process involves creating a backup vault, registering a backup/recovery appliance as an authorized accessor, creating an associated OnVault pool, building a resource profile, creating a backup template, and finally applying a backup plan.\u003c/p\u003e\n"],["\u003cp\u003eBefore protecting SQL Server databases, you need to add the hosts and discover their databases using the SQL Server wizard in the management console.\u003c/p\u003e\n"],["\u003cp\u003eOnVault pools associated with backup vaults provide enforced retention periods, preventing deletion of backups until the specified duration is met, adding an extra layer of security to your backups.\u003c/p\u003e\n"]]],[],null,["This page describes how to back up Microsoft SQL Server database into a backup vault.\n\nMicrosoft SQL Server database backups can be stored in regional\nbackup vaults. Sending backups to a backup vault provides\nprotection against modification (immutability) and deletion (indelibility).\nFor more information about backup vault, see [backup vault for immutable and indelible backups](/backup-disaster-recovery/docs/concepts/backup-vault).\n\nWith a backup vault, you can store backups in a single region. If you\nneed backups in multiple regions, consider the following options:\n\n- You can define a backup plan and resource profile that sends backups to two or more OnVault pools with two or more backup vaults. Create these backup vaults in different regions, which provides dual-region protection for your backups. Note that you will be charged for the storage in each backup vault separately.\n- Define an OnVault pool that uses a multi-regional Cloud Storage bucket. Note that this option doesn't provide the protection against modification and deletion that a backup vault provides.\n\nBefore you begin\n\nBefore you protect SQL server databases into a backup vault, you must\nadd the hosts and discover their databases using the management console\nSQL Server wizard as detailed in\n[Add a SQL Server database host and discover databases](/backup-disaster-recovery/docs/configuration/discover-sql-server).\n\nBack up Microsoft SQL Server into a backup vault\n\nBacking up Microsoft SQL Server into a backup vault involves the following steps.\n\n1. [Create a backup vault](#vault)\n\n2. [Register a backup/recovery appliance as an authorized accessor for a backup vault](#register)\n\n3. [Create an OnVault pool associated with backup vault](#onvault)\n\n4. [Create a profile associated with the backup vault](#profile)\n\n5. [Create a template](#template)\n\n6. [Apply a backup plan to protect a Microsoft SQL server](#server-plan)\n\nCreate a backup vault\n\n\u003cbr /\u003e\n\nA Backup vault is a container to store backups. To back up\nMicrosoft SQL server to a backup vault, you need to create a\n[backup vault](/backup-disaster-recovery/docs/concepts/backup-vault).\nFor instructions, see [Create and manage a backup vault in the Google Cloud console](/backup-disaster-recovery/docs/cloud-console/backup-vault-create).\n\n\nRegister a backup/recovery appliance as an authorized accessor for a backup vault\n\nYou can access a backup vault from the backup/recovery appliance project only\nafter the appliance service account is granted with the\nBackup and DR Backup Vault Accessor (`roles/backupdr.backupvaultAccessor`)\nIAM role in the backup vault project. Without this role,\nyou cannot access the backup vault to complete the setup to enable\nbackup creation. For instructions, see\n[Grant roles to the backup/recovery appliance service account](/backup-disaster-recovery/docs/cloud-console/backup-vault-create#service-account).\n| **Note:** The backup/recovery appliance and the backup vault don't need to be in the same project.\n\nCreate an OnVault pool associated with a backup vault\n\nOnVault pools created with the backup vault type store data\nin the backup vault. A backup vault with a minimum enforced retention period\nprevents the deletion of backups before the enforced retention period is met.\n\nBackup/recovery appliances that are registered with the backup vault pool type\nand updated to the version 11.0.12 or later are displayed for selection.\nTo upgrade your appliances to the latest version, see\n[Update backup/recovery appliances](/backup-disaster-recovery/docs/configuration/update-appliance).\n\nUse the following instructions to create an OnVault pool which points to a\nbackup vault.\n\n1. Click **Manage** and select **Storage pools** from the menu.\n2. Click **Add OnVault pool**.\n3. Enter a name for the pool. Valid characters are letters, numbers, spaces, hyphens (-), and underscores (_).\n4. Check that the **Pool type** is set to **Backup vault**.\n5. From the **Appliance** list, select the appliance you want to add the OnVault pool to. If your appliance is not available to select, you will need to [updated the appliance](/backup-disaster-recovery/docs/configuration/update-appliance) to the latest version.\n6. In the **Project ID** field, enter the Google Cloud project that contains your backup vault.\n7. From the **Region** list, select the region that contains your backup vault.\n8. From the **Choose a backup vault** section, select a backup vault.\n9. Click **Save**.\n\nCreate a profile associated with a backup vault based OnVault pool\n\n\u003cbr /\u003e\n\nA resource profile specifies the storage medium for Microsoft SQL server\nbackups. You can use a backup vault, a specialized storage for\nBackup and DR Service backups, designed with features that support resilience\nagainst malicious or accidental deletion of backups. After the profile is\ncreated and designated for use with backup vaults, the profile cannot\nbe edited to use a different storage pool type and a backup vault must\nalways be specified. Also, if the resource profile is in use to protect an\napplication, the specified backup vaults cannot be changed.\n\n\nUse the following instructions to create a resource profile which points to\na backup vault.\n\n1. Click **Backup plans** and select **Profiles** from the menu.\n2. Click **Create profile**.\n3. Enter a name and optional description for the resource profile.\n4. Select **Use OnVault pools that point to backup vaults (Recommended)**.\n5. In the **Primary appliance** section, from the **Appliance** list, select the appliance type that the backup pool type is associated with.\n6. From the **Snapshot pool** list, select a snapshot pool type.\n7. From the **OnVault pool 1** list, select the OnVault pool associated with your backup vault.\n8. Optional. From the **OnVault pool 2** list, select the OnVault pool associated with your backup vault that is created in a different region.\n9. Click **Save profile**.\n\nCreate a template with the backup policies\n\nA backup plan template defines backup creation and management details, such as\nthe backup schedule and the timeline for backup deletion. Backup plan\ntemplates are created within the management console. Create a backup template\nusing the instructions in the [Manage backup templates](/backup-disaster-recovery/docs/create-plan/create-template).\n\nApply a backup plan to protect a Microsoft SQL server\n\nUse the following instructions to apply a backup plan to protect Microsoft SQL server database.\n\n1. From the management console, go to **App Manager** \\\u003e **Applications** .\n The **Applications** page opens.\n\n2. Select the Microsoft SQL server database, instance, AG, or\n consistency group that you want to back up and in the lower right corner\n of the page select **Manage Backup Plan**.\n\n3. From the **Manage Backup Plan** window, choose a **Template** and **Profile**\n from the drop-down lists:\n\n - **Template.** An existing backup template that includes policies to define\n the snapshot and replication of the application data.\n\n - **Profile.** An existing resource profile that defines the resources\n used to store the data of the application as snapshot and\n replicated images.\n\n4. From the **Manage Backup Plan Template** window make the following changes\n prior to applying a backup plan:\n\n - **Application Settings.** Settings specific to Microsoft SQL such as\n application type, hostname, host IP address, path, operating system,\n backup/recovery appliance, and appliance IP address.\n\n - **Policy Overrides.** Override specific policy settings previously\n configured in the selected backup template. Policy overrides can be useful\n or required in certain circumstances. You can only override policy\n settings if the policy's template has been configured to allow\n policy settings overrides.\n\n5. To select databases, under **Database Inclusion Rule** , click **Edit** .\n The **Manage Membership** dialog opens.\n\n - From the **Manage Membership** dialog, select the databases to back up\n by assigning an inclusion rule (**All** , **System Databases** ,\n **User Databases** ), and then select whether the rule should\n **Include Selected** or **Exclude Selected**.\n\n - Click **Save** and the **Manage Membership** dialog closes.\n\n6. Click **Apply** to apply the backup template and resource profile and\n the success message box appears.\n\n The first time the selected database is discovered, an on-demand job runs as\n soon as possible to protect the data. Afterward, new data is backed up when the\n scheduled job runs according to the hours of operations defined in the backup\n template. For example, if at 10:00 (UTC) you assign a template that has hours of\n operation from 02:00 to 05:00 (UTC), then the first job won't start until the\n appliance has an available job slot after 02:00 (UTC).\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."]]
