Habilitar Copia de seguridad y recuperación ante desastres
Consola
En la consola Google Cloud , haz clic en
menuMenú.
Selecciona Operaciones>Backup y DR.
Haz clic en Enable (Habilitar).
Se abre el asistente Configurar copia de seguridad y recuperación ante desastres.
En la sección Activar la consola de gestión, sigue estos pasos:
Selecciona la ubicación en la que quieras que se encuentre la consola de gestión. Esta es la Google Cloud
región. Consulta las
regiones admitidas.
Haz clic en Continuar.
En la sección Despliega tu primer dispositivo de copia de seguridad o recuperación, haz lo siguiente:
En Nombre del aparato, escribe el nombre del aparato. El nombre debe empezar por una letra minúscula y puede contener hasta 23 caracteres. El nombre del dispositivo solo puede contener letras minúsculas, caracteres numéricos y guiones (-). No se permiten espacios.
Selecciona una red de VPC. Puedes seleccionar la red del mismo proyecto o del proyecto de VPC compartida.
Selecciona el proyecto de destino en el que quieras implementar tu dispositivo de copia de seguridad o recuperación.
Selecciona la región y la zona en las que quieras que se ubiquen tus dispositivos de copia de seguridad o recuperación. Esta es la Google Cloud región y la zona. Consulta las regiones admitidas.
Selecciona Subred. Se muestra en función de la región y la zona seleccionadas.
Selecciona un tipo de almacenamiento para guardar las copias de seguridad. Esta opción solo aparece si seleccionas Básico para bases de datos, máquinas virtuales de VMware y otros recursos en Tipo de dispositivo de copia de seguridad o recuperación.
Haz clic en Configurar.
Se te redirigirá a la página de estado. Este proceso puede tardar aproximadamente una hora.
Cuando se haya completado la implementación, haz clic en Iniciar sesión en la consola de gestión y la consola de gestión se abrirá en una ventana nueva.
Si quieres implementar un segundo dispositivo, haz clic en Implementar otro dispositivo de copia de seguridad o recuperación. Puedes añadir hasta 30 electrodomésticos a una consola de gestión. Si necesitas añadir más de 30 dispositivos, crea un proyecto, implementa una consola de gestión y, a continuación, implementa los dispositivos.
gcloud
Puedes usar la CLI de Google Cloud para crear una consola de gestión. No se admite la creación de dispositivos de copia de seguridad o recuperación con la CLI de gcloud.
Debes usar la consola de Google Cloud para crear dispositivos de copia de seguridad o recuperación.
Usa los siguientes comandos para crear una consola de gestión.
MANAGEMENT_SERVER_NAME: un nombre para la consola de gestión, por ejemplo, test name. Una vez que se haya implementado el servidor de gestión, no se podrá cambiar este nombre. El nombre debe ser único para un proyecto y una ubicación.
LOCATION_ID: introduce una ubicación compatible con la consola de gestión.
Consulta la lista de ubicaciones admitidas mediante gcloud backup-dr locations list.
PROJECT_ID: el nombre de tu proyecto, por ejemplo, test-project. Usa esta marca si quieres especificar otro proyecto.
FULL_OPERATION_ID: el ID de operación que se muestra en la consola de gestión. Tiene este formato:
projects/test-project/locations/us-central1/operations/operationID
El resultado se muestra de la siguiente manera:
```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
Puedes usar los siguientes enlaces de recursos de Terraform para implementar una consola de gestión y un dispositivo de copia de seguridad y recuperación:
[[["Es fácil de entender","easyToUnderstand","thumb-up"],["Me ofreció una solución al problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Es difícil de entender","hardToUnderstand","thumb-down"],["La información o el código de muestra no son correctos","incorrectInformationOrSampleCode","thumb-down"],["Me faltan las muestras o la información que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-08-21 (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)"]]
