Klik Enable.
Wizard Setup Backup and DR akan terbuka.
Di bagian Aktifkan konsol pengelolaan, selesaikan langkah-langkah berikut:
Pilih Lokasi tempat Anda ingin menempatkan
konsol pengelolaan. Ini adalah Google Cloud
region, lihat
Region yang didukung.
Klik Lanjutkan.
Di bagian Deploy your first backup/recovery appliance, selesaikan langkah-langkah berikut:
Di Nama alat, masukkan nama untuk alat. Nama harus
dimulai dengan huruf kecil dan dapat berisi hingga 23 karakter. Nama
perangkat hanya boleh berisi huruf kecil, karakter numerik, dan tanda hubung (-). Tidak diperbolehkan ada spasi.
Pilih VPC network. Anda dapat memilih jaringan dalam project yang sama atau dari project VPC Bersama.
Pilih Target project tempat Anda ingin men-deploy appliance pencadangan/pemulihan.
Pilih Region dan Zone tempat Anda ingin menempatkan alat backup/pemulihan. Ini adalah Google Cloud region dan zona, lihat
Region yang didukung.
Pilih Subnetwork. Ini ditampilkan berdasarkan wilayah dan zona yang dipilih.
Pilih Jenis penyimpanan untuk menyimpan cadangan. Opsi ini hanya muncul
jika Anda memilih Dasar untuk database, VM VMware, & resource lainnya untuk
Jenis appliance pencadangan/pemulihan.
Klik Siapkan.
Anda akan dialihkan ke halaman status. Proses ini dapat memakan waktu sekitar satu jam.
Setelah deployment selesai, klik Log in to the management console
dan management console akan terbuka di jendela baru.
Jika Anda ingin men-deploy appliance kedua, klik
Deploy another backup/recovery appliance. Anda dapat menambahkan hingga 30 peralatan ke konsol pengelolaan. Jika Anda perlu menambahkan lebih dari 30 peralatan,
buat project baru, deploy konsol pengelolaan baru, lalu deploy peralatan.
gcloud
Anda dapat menggunakan Google Cloud CLI untuk membuat konsol pengelolaan. Pembuatan appliance pencadangan/pemulihan menggunakan gcloud CLI tidak didukung.
Anda harus menggunakan konsol Google Cloud untuk membuat appliance pencadangan/pemulihan.
Gunakan perintah berikut untuk membuat konsol pengelolaan.
MANAGEMENT_SERVER_NAME: nama untuk konsol
pengelolaan, misalnya, test name. Setelah server pengelolaan di-deploy, nama ini tidak dapat diubah. Nama harus unik untuk project dan lokasi.
LOCATION_ID: masukkan lokasi yang didukung konsol pengelolaan.
Dapatkan daftar lokasi yang didukung menggunakan
gcloud backup-dr locations list.
PROJECT_ID: nama project Anda, misalnya,
test-project. Gunakan flag ini jika Anda ingin menentukan project
lain.
FULL_OPERATION_ID: ID operasi yang ditampilkan untuk konsol pengelolaan. Formatnya adalah:
projects/test-project/locations/us-central1/operations/operationID
Output ditampilkan sebagai:
```none
Create in progress for management server [projects/test-project/locations/us-central1/operations/test-operation] \
Run the [gcloud backup-dr operations describe] command to check the status of this operation.
```
Terraform
Anda dapat menggunakan link resource Terraform berikut untuk men-deploy konsol pengelolaan dan appliance pencadangan/pemulihan:
[[["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-11 UTC."],[[["\u003cp\u003eBefore deploying, users should plan their Backup and DR deployment and prepare accordingly, as outlined in the provided links.\u003c/p\u003e\n"],["\u003cp\u003eThe Backup and DR management console can be enabled via the Google Cloud console by selecting a location, setting up an appliance name, choosing a VPC network, selecting a target project, region, zone, and subnetwork.\u003c/p\u003e\n"],["\u003cp\u003eThe Google Cloud CLI can be used to create a management console, but creating backup/recovery appliances requires the use of the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eTerraform resources are available for deploying both a management console and a backup/recovery appliance, which can be linked directly from the documentation provided.\u003c/p\u003e\n"],["\u003cp\u003eAfter enabling the Backup and DR Service, users can protect Compute Engine instances and other workloads by configuring cloud credentials, roles, permissions, backup plans, and by discovering and adding hosts.\u003c/p\u003e\n"]]],[],null,["# Deploy Backup and DR Service\n\nBefore you begin\n----------------\n\nUse the following procedures to prepare for the deployment:\n\n- [Plan a Backup and DR deployment](/backup-disaster-recovery/docs/configuration/deployment-plan)\n\n- [Prepare to deploy Backup and DR](/backup-disaster-recovery/docs/configuration/deployment-prep)\n\nEnable Backup and DR\n--------------------\n\n### Console\n\n1. In the Google Cloud console, click\n menu **Menu**.\n\n2. Select **Operations** \\\u003e **Backup and DR**.\n\n3. Click **Enable** .\n The **Setup Backup and DR** wizard opens.\n\n4. In the **Activate the management console** section, complete\n the following:\n\n 1. Select the **Location** where you want the\n management console to be located. This is the Google Cloud\n region, see\n [Supported regions](/backup-disaster-recovery/docs/configuration/deployment-plan#regions).\n\n 2. Click **Continue**.\n\n5. In the **Deploy your first backup/recovery appliance** section, complete\n the following:\n\n 1. In **Appliance name**, enter a name for the appliance. The name must\n start with a lowercase letter and can contain up to 23 characters. The\n appliance name can only contain lowercase letters, numeric characters,\n and dashes (-). Spaces are not allowed.\n\n 2. Select a **VPC network**. You can select the network within the same\n project or from the Shared VPC project.\n\n 3. Select the **Target project** where you want to deploy your\n backup/recovery appliance to.\n\n 4. Select the **Region** and **Zone** where you want your backup/recovery appliances\n to be located. This is the Google Cloud region and zone, see\n [Supported regions](/backup-disaster-recovery/docs/configuration/deployment-plan#regions).\n\n 5. Select **Subnetwork**. This is displayed based on the selected region\n and zone.\n\n | **Caution:** Don't use the subnetwork with IP range of 172.17.0.0/16. This subnet IP is used for Backup and DR internal purposes. Using this IP range might fail the backup/recovery appliance deployment.\n 6. Select the [**Backup/recovery appliance type**](/backup-disaster-recovery/docs/configuration/deployment-plan#appliance)\n based on the workload that you want to back up.\n\n 7. Select a **Storage type** to store backups. This option only appears\n if you select **Basic for databases, VMware VMs, \\& other resources** for\n the **Backup/recovery appliance type**.\n\n 8. Click **Set up**.\n\n You are redirected to the status page. This can take about an hour to\n complete.\n6. When the deployment is complete, click **Log in to the management console**\n and the [management console](/backup-disaster-recovery/docs/concepts/introduction) will open in a new window.\n\n7. If you want to deploy a second appliance, click\n **Deploy another backup/recovery appliance**. You can add up to 30 appliances\n to a management console. If you need to add more than 30 appliances,\n create a new project, deploy a new management console, and\n then deploy the appliances.\n\n | **Warning:** After the backup/recovery appliance has been deployed, the Compute Engine VM instances listing page shows a recommendation to save money by resizing the instance. Don't do this. Resizing the appliance or changing its machine configuration---changing the series, CPU, memory---can make the backup/recovery appliance unusable.\n\n### gcloud\n\nYou can use Google Cloud CLI to create a management console. Creating\nbackup/recovery appliances using gcloud CLI is not supported.\nYou must use Google Cloud console to create backup/recovery appliances.\n\nUse the following commands to create a management console.\n\n1. Create a management console:\n\n gcloud backup-dr management-servers create \u003cvar translate=\"no\"\u003eMANAGEMENT_SERVER_NAME\u003c/var\u003e \\\n --location=\u003cvar translate=\"no\"\u003eLOCATION_ID\u003c/var\u003e \\\n\n | **Note:** By default, the project set in your Google Cloud CLI config is used. To specify a different project, use the `--project` flag.\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eMANAGEMENT_SERVER_NAME\u003c/var\u003e: a name for the management console, for example, `test name`. Once the management server is deployed, this name can't be changed. The name must be unique for a project and location.\n - \u003cvar translate=\"no\"\u003eLOCATION_ID\u003c/var\u003e: enter a management console supported [location](/backup-disaster-recovery/docs/deployment/deployment-plan#management_console_supported_regions). Get the list of supported locations by using `gcloud backup-dr locations list`.\n - \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the name of your project, for example, `test-project`. Use this flag, if you want to specify a different project.\n2. You can check the status of the operation:\n\n gcloud backup-dr operations describe \u003cvar translate=\"no\"\u003eFULL_OPERATION_ID\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eFULL_OPERATION_ID\u003c/var\u003e: the operation ID that is displayed for the management console. It is in this format: `projects/test-project/locations/us-central1/operations/operationID`\n\n The output is displayed as: \n\n ```none\n Create in progress for management server [projects/test-project/locations/us-central1/operations/test-operation] \\\n Run the [gcloud backup-dr operations describe] command to check the status of this operation.\n ```\n\n### Terraform\n\nYou can use the following Terraform resource links to deploy a management\nconsole and backup/recovery appliance:\n\n- [Deploy a management console using Terraform resource](https://registry.terraform.io/providers/hashicorp/google-beta/latest/docs/resources/backup_dr_management_server)\n- [Deploy a backup/recovery appliance using Terraform resource](https://github.com/GoogleCloudPlatform/terraform-google-backup-dr)\n| **Note:** For debugging purposes, the Backup and DR Service collects appliance logs and sends them to Cloud Logging. Standard Cloud Logging pricing applies to this log collection. For pricing information, see [Cloud Logging pricing](/stackdriver/pricing). To reduce the cost of logging service, contact [customer support](/backup-disaster-recovery/docs/support) to disable the optional logs.\n\nWhat's next\n-----------\n\nAfter enabling Backup and DR Service, you can start exploring the\n[management console](/backup-disaster-recovery/docs/concepts/introduction) and protect workloads.\n\n### Protect workloads\n\nUse these instructions to protect Compute Engine instances:\n\n1. Learn about [Cloud credentials](/backup-disaster-recovery/docs/configuration/create-cloud-credentials).\n\n2. Assign required [roles and permission](/backup-disaster-recovery/docs/access-data/permissions).\n\n3. Define a [backup plan](/backup-disaster-recovery/docs/concepts/backup-plan).\n\n4. [Discover and protect Compute Engine instances](/backup-disaster-recovery/docs/configuration/discover-and-protect-ce-inst)\n\n### Protect databases and file systems within VMs\n\n1. [Add your hosts](/backup-disaster-recovery/docs/configuration/manage-hosts-and-their-connected-applications) and [discover applications on your hosts](/backup-disaster-recovery/docs/configuration/onboarding-wizard).\n\n2. [Install the Backup and DR agent on the hosts](/backup-disaster-recovery/docs/concepts/about-connector).\n\n3. Ensure [firewall rules](/backup-disaster-recovery/docs/configuration/deployment-plan#firewall_configurations) are set.\n\n4. Define a [backup plan](/backup-disaster-recovery/docs/concepts/backup-plan).\n\n5. [Apply a backup plan to the discovered applications](/backup-disaster-recovery/docs/create-plan/apply-backup-temp-overview)"]]
