Menambahkan host server vCenter dan ESX ke konsol pengelolaan
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Layanan Pencadangan dan DR menggunakan perlindungan data VMware vSphere storage API untuk
membuat cadangan VM VMware, dengan menempatkan cadangan di kumpulan snapshot
perangkat pencadangan/pemulihan atau di kumpulan OnVault.
Untuk melakukan panggilan API, appliance pencadangan/pemulihan harus terhubung ke
host server vCenter atau ESX dengan nama pengguna dan sandi yang memiliki otorisasi untuk
melakukan tindakan yang diperlukan. Halaman ini menjelaskan cara menambahkan host server vCenter atau
ESX di konsol pengelolaan.
Layanan Pencadangan dan DR membuat koneksi aman dengan vCenter. Jika
koneksi aman tidak dibuat, tugas pencadangan dan pemulihan akan gagal.
Koneksi ke vCenter gagal dalam salah satu skenario berikut:
Jika ada ketidakcocokan antara nama vCenter dan nama dalam
sertifikat vCenter.
Jika sertifikat vCenter tidak dipercaya oleh anchor kepercayaan OS atau jika vCenter memiliki sertifikat yang ditandatangani sendiri.
Menambahkan host vCenter atau ESX Server baru
Gunakan petunjuk ini untuk menambahkan host server vCenter atau ESX baru ke konsol pengelolaan:
Klik Kelola>Host.
Pilih + Tambahkan Penyelenggara.
Di kolom Name, masukkan fully qualified domain name host vCenter.
Pastikan nama di kolom Name host sama dengan yang ada di sertifikat vCenter.
Koneksi akan gagal jika ada ketidakcocokan.
Opsional: Di kolom Nama Sederhana, masukkan nama yang mudah digunakan untuk host.
Nama host harus diawali dengan huruf, dan dapat berisi huruf
dan angka (0-9). Jangan gunakan garis bawah (_) pada karakter dalam nama host.
Anda juga dapat menambahkan nama sebutan untuk host vCenter di kolom Friendly Name.
Masukkan alamat IP host di Alamat IP. Klik + untuk menambahkan beberapa alamat IP.
Di bagian Appliances, pilih satu atau beberapa appliance yang menayangkan host ini.
Jika daftarnya panjang, Anda dapat menggunakan kolom penelusuran untuk menemukan perangkat atau grup perangkat tertentu.
Di Host Type, pilih vCenter atau ESX Server.
Pilih mode transpor data, NFS atau SAN. NFS adalah
setelan yang direkomendasikan dan default. Masukkan nama pengguna dan sandi untuk
menghubungkan ke host, lalu gunakan tombol Uji untuk memvalidasinya.
Anda hanya perlu memasukkan port jika port non-standar sedang digunakan.
Setelan penyelenggara
Untuk melindungi
Memilih jenis host
Jenis koneksi
vCenter dengan VM ESXi
vCenter
Port pengelolaan vCenter default adalah 443. Jika Anda menggunakan port yang berbeda, masukkan port tersebut di sini. Masukkan Nama Pengguna vCenter dan Sandi vCenter, lalu pilih Uji.
ESXi mandiri
Server ESX
Port pengelolaan Server ESX default adalah 902.
Jika Anda menggunakan port yang berbeda, masukkan port tersebut di sini. Masukkan Nama Pengguna ESX dan Sandi ESX, lalu pilih Uji.
[[["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\u003eBackup and DR Service utilizes VMware vSphere storage APIs to create backups of VMware VMs, storing them in either the snapshot pool or OnVault pools.\u003c/p\u003e\n"],["\u003cp\u003eAdding a vCenter or ESX server host requires connecting to the host with a username and password that has the authority to perform necessary actions, ensuring the host's name matches its vCenter certificate name.\u003c/p\u003e\n"],["\u003cp\u003eA secure connection between the backup/recovery appliance and the vCenter is critical for the success of backup and restore jobs, with failures occurring if there's a name mismatch or untrusted certificates.\u003c/p\u003e\n"],["\u003cp\u003eThe process of adding a new vCenter or ESX server involves entering the fully qualified domain name, optional friendly name, IP address, selecting relevant appliances, specifying host type, and choosing a data transport mode, with NFS being recommended.\u003c/p\u003e\n"],["\u003cp\u003eESX servers are typically auto-discovered when their managing vCenter host is added, and to test connection you need to validate the credentials of the vCenter or ESX server host.\u003c/p\u003e\n"]]],[],null,["# Add vCenter and ESX server hosts to the management console\n\nBackup and DR Service uses [VMware vSphere storage APIs](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-3FD5AB1E-47B3-49B5-845E-5224BE062A59.html) data protection to\ncreate backups of VMware VMs, placing backups either in the snapshot pool\nof the backup/recovery appliance or in OnVault pools.\n\nTo make API calls, the backup/recovery appliance needs to connect to the\nvCenter or ESX server host with a username and password that has authority to\nperform the required actions. This page explains how to add a vCenter or ESX\nserver host in the management console.\n\nBefore you begin\n----------------\n\n- Be sure to review [Configure Google Cloud VMware Engine for Backup and DR protection](/backup-disaster-recovery/docs/configuration/prepare-vmware).\n\n- Make sure that the vCenter server is accessible from the appliance\n as described in [Third-party service certificate](/backup-disaster-recovery/docs/configuration/certificate).\n\n- Backup and DR Service establishes a secure connection with the vCenter. If a\n secure connection is not established, backup and restore jobs fail.\n The connection to vCenter fails in either of the following scenarios:\n\n - If there is a mismatch between the name of the vCenter and the name in the vCenter certificate.\n - If the vCenter certificate is not trusted by OS trust anchors or if vCenter has self-signed certificates.\n\nAdd a new vCenter or ESX Server host\n------------------------------------\n\nUse these instructions to add a new vCenter or ESX server host to the management console:\n\n1. Click **Manage** \\\u003e **Hosts**.\n\n2. Select **+ Add Host**.\n\n3. In the **Name** field, enter the *fully qualified domain name* of the vCenter host.\n Ensure that the name in the host's **Name** field is the same as in the vCenter certificate.\n The connection fails if there is a mismatch.\n\n4. Optional: In the **Friendly Name** field, enter a user-friendly name for the host.\n The name of a host must start with a letter, and can contain letters\n and digits (0-9). Do not underscore (*_* ) characters in hostnames.\n You can also add a friendly name for the vCenter host in the **Friendly Name**\n field.\n\n | **Note:** For existing vCenter hosts, if the hostname does not match the fully qualified domain name (FQDN) of the server, then the backup/recovery appliance automatically updates the hostname during the appliance upgrade. The existing hostname is moved to the **Name** column if the **Friendly Path** column is empty.\n5. Enter the IP address of the host in **IP Address** . Click **+** to add\n multiple IP addresses.\n\n6. In the **Appliances** section, select one or more appliances that serve this host.\n If the list is long, you can use the search field to find a specific appliance\n or group of appliances.\n\n7. In **Host Type** , select either **vCenter** or **ESX Server**.\n\n | **Note:** You normally do not need to add ESX servers as they are auto-discovered when you add the vCenter host that manages them.\n8. Select the data transport mode, either **NFS** or **SAN** . NFS is the\n recommended and default setting. Enter the username and password to\n connect to the host and then use the **Test** button to validate them.\n You only need to enter a port if a non-standard port is being used.\n\n \u003cbr /\u003e\n\n9. Click **Add**.\n\nWhat's next\n-----------\n\n- To discover and protect VM, see [Discover and protect VMware VMs](/backup-disaster-recovery/docs/configuration/discover-and-protect-vms)\n\nThe VMware administrator's guide\n--------------------------------\n\n- [Backup and DR for VMware VMs](/backup-disaster-recovery/docs/concepts/vmware-intro)\n- [Configure VMware Engine for Backup and DR protection](/backup-disaster-recovery/docs/configuration/prepare-vmware)\n\n- [Add vCenter and ESX server hosts to the management console](/backup-disaster-recovery/docs/configuration/add-vcenter-host)\n\n- [Discover and protect VMware VMs](/backup-disaster-recovery/docs/configuration/discover-and-protect-vms)\n\n- [Apply a backup template to protect a VM](/backup-disaster-recovery/docs/create-plan/apply-backup-template-to-manage-a-VM)\n\n- [Configure application settings for VMware VMs](/backup-disaster-recovery/docs/backup/configure-application-settings-for-vmware-vm)\n\n- [Restore a VMware VM](/backup-disaster-recovery/docs/restore-data/restore-vm)\n\n- [Mount a VMware image](/backup-disaster-recovery/docs/access-data/mount-vmware-image)\n\n- [Clone an image of a VMware VM](/backup-disaster-recovery/docs/access-data/clone-image-of-a-vm)\n\n- [Create LiveClone workflows](/backup-disaster-recovery/docs/access-data/create-liveclone-workflows)\n\n- [Move VM management between two backup/recovery appliances](/backup-disaster-recovery/docs/configuration/supported-vmware)"]]
