Mover o gerenciamento de VM entre dois dispositivos de backup/recuperação
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Com o console de gerenciamento, é possível mover o gerenciamento de uma VM de um
dispositivo de backup/recuperação para um dispositivo de destino. Esse processo move o gerenciamento
dessa VM para o dispositivo de backup/recuperação de destino especificado, conforme definido na janela
Mover plano de backup.
A movimentação do gerenciamento de VMs entre dois dispositivos é limitada a VMs localizadas
no mesmo host vCenter ou ESX. Somente dispositivos que gerenciam VMs no
mesmo host vCenter ou ESX podem ser dispositivos de destino para movimentação de planos de backup.
Esses aparelhos aparecem na lista de possíveis aparelhos de destino.
Mover o gerenciamento de VMs para outro dispositivo
Use estas instruções para mover uma VM de um dispositivo para outro:
No console de gerenciamento do serviço de backup e DR, clique em
Gerenciador de apps e selecione Aplicativos na lista suspensa.
A página Aplicativos é aberta.
Selecione a VM que você quer mover e escolha Mover plano de backup na lista suspensa no canto inferior direito da janela.
A janela Mover plano de backup será aberta. A VM selecionada pode ser gerenciada ou
não gerenciada. É possível mover uma VM sem aplicar um plano de backup para gerenciá-la.
Escolha o dispositivo de destino, o perfil de recurso e o modelo de política.
Clique em Mover plano de backup.
A mensagem de backup em movimento é aberta durante a transferência.
Quando a migração for concluída, a mensagem "Migração concluída" vai aparecer.
Renomear um vCenter
Se você mudar o nome de um vCenter, renomeie-o no console de gerenciamento.
Use estas instruções para renomear um vCenter no console de gerenciamento:
Clique em Gerenciar e selecione Hosts.
Encontre o host do vCenter e selecione a opção Editar.
Atualize o campo Nome e selecione Salvar.
Efeito da mudança do UUID de uma VM.
Se o UUID de uma VM gerenciada mudar, uma nova cópia completa será feita na
próxima tarefa de backup. Isso acontece porque o UUID é um identificador de chave, e um UUID
alterado pode significar que é uma VM totalmente nova.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-18 UTC."],[[["\u003cp\u003eVM management can be moved between backup/recovery appliances within the same vCenter or ESX host using the \u003cstrong\u003eMove Backup Plan\u003c/strong\u003e feature in the management console.\u003c/p\u003e\n"],["\u003cp\u003eThe process of moving VM management involves selecting a target appliance, resource profile, and policy template, and then initiating the move from the \u003cstrong\u003eApplications\u003c/strong\u003e page.\u003c/p\u003e\n"],["\u003cp\u003eIf a VM is managed with a StreamSnap replication policy, and the replicated VM exists on the target appliance, the management console will prevent the backup plan move and display an error message.\u003c/p\u003e\n"],["\u003cp\u003eIf a vCenter's name is changed, it must also be updated in the management console by editing the host details within the \u003cstrong\u003eManage\u003c/strong\u003e section.\u003c/p\u003e\n"],["\u003cp\u003eChanging the UUID of a managed VM will result in a new full backup on the next job, since the changed UUID is interpreted as a new VM.\u003c/p\u003e\n"]]],[],null,["# Move VM management between two backup/recovery appliances\n\nThe management console lets you move the management of a VM from one\nbackup/recovery appliance to a target appliance. This process moves management\nof that VM to the specified target backup/recovery appliance as defined in the\n**Move Backup Plan** window.\n\nThe movement of VM management between two appliances is limited to VMs located\nwithin the same vCenter or ESX host. Only appliances that manage VMs in the\nsame vCenter or ESX host can be target appliances for backup plan movement.\nThose appliances are shown in the list of possible target appliances.\n\nMove VM management to another appliance\n---------------------------------------\n\nUse these instructions to move a VM from one appliance to another appliance:\n\n1. From the Backup and DR Service management console, click\n **App Manager** and select **Applications** from the drop-down list.\n\n The **Applications** page opens.\n2. Select the VM that you want to move, then choose **Move Backup Plan** from\n the drop-down list at the bottom right corner of the window.\n\n The **Move Backup Plan** window opens. The VM you select can be managed or\n unmanaged. You can move a VM without first applying a backup plan to manage it.\n3. Choose the target appliance, resource profile, and policy template.\n\n4. Click **Move Backup Plan**.\n\n The moving backup message opens during the move.\n | **Note:** If the VM on the source appliance is managed with a StreamSnap replication policy, and the replication target---including the VM to move---exists on the target appliance, then management console prevents the backup plan move and generates an error message. This occurs because the VM already exists on the target appliance as part of the replication process, where a full copy of data is created at the remote site.\n\n Once migration is complete, the migration complete message displays.\n | **Note:** If the move is not successful, the management console displays a **Move Backup Plan Failed** message along with an explanation of the failure as related to the target appliance. If possible, resolve the issue and attempt to move the backup plan again.\n\nRename a vCenter\n----------------\n\nIf you change the name of a vCenter, then remember to rename the vCenter within\nthe management console.\n\nUse these instructions to rename a vCenter in management console:\n\n1. Click **Manage** and select **Hosts**.\n2. Find your vCenter host and select the **Edit** option.\n3. Update the **Name** field, and select **Save**.\n\n### Effect of changing the UUID of a VM.\n\nIf the UUID of a managed VM changes, then a new full copy occurs on the\nnext backup job. This is because the UUID is a key identifier and a changed\nUUID could mean this is a totally new VM.\n\nThe VMware administrator's guide\n--------------------------------\n\n- [Configure VMware Engine for Backup and DR protection](/backup-disaster-recovery/docs/configuration/prepare-vmware)\n- [Add vCenter and ESX server hosts to the management console](/backup-disaster-recovery/docs/configuration/add-vcenter-host)\n- [Discover and protect VMware VMs](/backup-disaster-recovery/docs/configuration/discover-and-protect-vms)\n- [Apply a backup template to protect a VM](/backup-disaster-recovery/docs/create-plan/apply-backup-template-to-manage-a-VM)\n- [Configure Application settings for VMware VMs](/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm)\n- [Restore a VMware VM](/backup-disaster-recovery/docs/restore-data/restore-vm)\n- [Mount a VMware image](/backup-disaster-recovery/docs/access-data/mount-vmware-image)\n- [Clone an image of a VMware VM](/backup-disaster-recovery/docs/access-data/clone-image-of-a-vm)\n- [Create LiveClone workflows](/backup-disaster-recovery/docs/access-data/create-liveclone-workflows)\n- [Move VM management between two backup/recovery appliances](/backup-disaster-recovery/docs/configuration/supported-vmware)"]]
