Backup Infrastruktur - Versionsgeschichte

Zovi: /* ESX Config Backup */

2024-04-27T21:01:50Z

‎ESX Config Backup

Zovi: /* ESX Config Backup */

2024-04-27T21:01:30Z

‎ESX Config Backup

Zovi: /* Restoring ESXi host configuration data */

2024-04-27T21:00:32Z

‎Restoring ESXi host configuration data

Zovi: /* Restoring ESXi host configuration data */

2024-04-27T21:00:16Z

‎Restoring ESXi host configuration data

Zovi: /* Restoring ESXi host configuration data */

2024-04-27T20:59:02Z

‎Restoring ESXi host configuration data

Zovi: /* Restoring ESXi host configuration data */

2024-04-27T20:58:46Z

‎Restoring ESXi host configuration data

Zovi: /* ESX Config Backup */

2024-04-27T20:58:17Z

‎ESX Config Backup

Zovi: /* = Restoring ESXi host configuration data */

2024-04-27T20:55:16Z

‎= Restoring ESXi host configuration data

Zovi: /* ESX Config Backup */

2024-04-27T20:51:38Z

‎ESX Config Backup

Zovi am 27. April 2024 um 20:50 Uhr

2024-04-27T20:50:23Z

@@ Zeile 56: / Zeile 56: @@
 == ESX Config Backup ==
 on ESXi Command Line
-: Note: first you have to enable ssh on esx webgui
+: '''Note''': first you have to enable ssh on esx webgui
 === Backing up ESXi host configuration data ===
@@ Zeile 74: / Zeile 77: @@
 Note: To restore the configuration the destination ESXi host must be the same build as the ESXi host configuration data. The host build can be obtained using the command vmware -vl.
 === Restoring ESXi host configuration data ===

@@ Zeile 55: / Zeile 55: @@
 == ESX Config Backup ==
-ESXi Command Line
+on ESXi Command Line
 === Backing up ESXi host configuration data ===

@@ Zeile 89: / Zeile 89: @@
   vim-cmd hostsvc/firmware/restore_config 0
-: Note:  Add a 1 to force an override of the UUID mismatch.
+: '''Note''':  Add a 1 to force an override of the UUID mismatch.
 : For example:
   vim-cmd hostsvc/firmware/restore_config 1

@@ Zeile 89: / Zeile 89: @@
   vim-cmd hostsvc/firmware/restore_config 0
-Note:  Add a 1 to force an override of the UUID mismatch.<br>
+: Note:  Add a 1 to force an override of the UUID mismatch.
-For example: # vim-cmd hostsvc/firmware/restore_config 1
+: For example:
 * Executing this command will initiate an automatic reboot of the host after command completion.
 * However, starting from vSphere 7.0 U2, the configuration could be encrypted using TPMs and in which case, the -force option will not work if the host got changed. We need the same TPM that was used on the host during backup, to restore. In other words,from vSphere 7.0U2, the override will not work if the host has TPM enabled.

@@ Zeile 92: / Zeile 92: @@
 For example: # vim-cmd hostsvc/firmware/restore_config 1
 * Executing this command will initiate an automatic reboot of the host after command completion.
-* However, starting from vSphere 7.0 U2, the configuration could be encrypted using TPMs and in which case, the -force option will not work if the host got changed. We need the same TPM that was used on the host during backup, to restore. In other words,
+* However, starting from vSphere 7.0 U2, the configuration could be encrypted using TPMs and in which case, the -force option will not work if the host got changed. We need the same TPM that was used on the host during backup, to restore. In other words,from vSphere 7.0U2, the override will not work if the host has TPM enabled.
 = Prozesse =

@@ Zeile 86: / Zeile 86: @@
 . Once ESXi has rebooted, move the config bundle file to /tmp/configBundle.tgz.
-. Then run this command to restore the ESXi host configuration:
+: Then run this command to restore the ESXi host configuration:
   vim-cmd hostsvc/firmware/restore_config 0
 Note:  Add a 1 to force an override of the UUID mismatch.<br>
 For example: # vim-cmd hostsvc/firmware/restore_config 1
-. Executing this command will initiate an automatic reboot of the host after command completion.
+* Executing this command will initiate an automatic reboot of the host after command completion.
-. However, starting from vSphere 7.0 U2, the configuration could be encrypted using TPMs and in which case, the -force option will not work if the host got changed. We need the same TPM that was used on the host during backup, to restore. In other words,<br>
+* However, starting from vSphere 7.0 U2, the configuration could be encrypted using TPMs and in which case, the -force option will not work if the host got changed. We need the same TPM that was used on the host during backup, to restore. In other words,<br>
 from vSphere 7.0U2, the override will not work if the host has TPM enabled.

@@ Zeile 58: / Zeile 58: @@
 === Backing up ESXi host configuration data ===
-# To synchronize the configuration changed with persistent storage, run this command:
+. To synchronize the configuration changed with persistent storage, run this command:
   vim-cmd hostsvc/firmware/sync_config
-# To back-up the configuration data for the ESXi host, run this command:
+. To back-up the configuration data for the ESXi host, run this command:
   vim-cmd hostsvc/firmware/backup_config
@@ Zeile 67: / Zeile 67: @@
 Note: The command will output a URL (http://<host_fqdn_orIP>/downloads/123456/configBundle-xx.xx.xx.xx.tgz) from where you can download the backup file, either by opening it in a web brower or using other means like wget.
-From a web browser navigate to
+. From a web browser navigate to
   http://<host_fqdn_orIP>/downloads/123456/configBundle-xx.xx.xx.xx.tgz
 In this example the IP address of the host is 192.168.0.81
@@ Zeile 73: / Zeile 73: @@
 Note: To restore the configuration the destination ESXi host must be the same build as the ESXi host configuration data. The host build can be obtained using the command vmware -vl.
 === Restoring ESXi host configuration data ==

← Nächstältere Version		Version vom 27. April 2024, 20:50 Uhr
Zeile 54:		Zeile 54:
	= FAQ =		= FAQ =

		+	== ESX Config Backup ==
		+	ESXi Command Line

		+	=== Backing up ESXi host configuration data ===
		+	# To synchronize the configuration changed with persistent storage, run this command:
		+	vim-cmd hostsvc/firmware/sync_config
		+	# To back-up the configuration data for the ESXi host, run this command:
		+	vim-cmd hostsvc/firmware/backup_config

		+	[[Bild:rtaImage.jpeg\|300px\|right\|ESX]]

		+	Note: The command will output a URL (http://<host_fqdn_orIP>/downloads/123456/configBundle-xx.xx.xx.xx.tgz) from where you can download the backup file, either by opening it in a web brower or using other means like wget.
		+
		+	From a web browser navigate to
		+	http://<host_fqdn_orIP>/downloads/123456/configBundle-xx.xx.xx.xx.tgz
		+	In this example the IP address of the host is 192.168.0.81
		+
		+
		+	Note: To restore the configuration the destination ESXi host must be the same build as the ESXi host configuration data. The host build can be obtained using the command vmware -vl.
		+
		+
		+
		+	=== Restoring ESXi host configuration data ==
		+	The configBundle-HostFQDN.tgz should be renamed as configBundle.tgz before initiating the restore command.
		+	Put the host into maintenance mode by running the below command:
		+	# vim-cmd hostsvc/maintenance_mode_enter
		+
		+
		+	Copy the backup configuration file to the ESXi host or an available datastore.
		+	Reboot the host. This step is required, otherwise the restore workflow might not finish completely
		+	Once ESXi has rebooted, move the config bundle file to /tmp/configBundle.tgz.
		+	Then run this command to restore the ESXi host configuration:
		+	# vim-cmd hostsvc/firmware/restore_config 0
		+
		+	Note: Add a 1 to force an override of the UUID mismatch.
		+	For example: # vim-cmd hostsvc/firmware/restore_config 1
		+	Executing this command will initiate an automatic reboot of the host after command completion.
		+	However, starting from vSphere 7.0 U2, the configuration could be encrypted using TPMs and in which case, the -force option will not work if the host got changed. We need the same TPM that was used on the host during backup, to restore. In other words,
		+	from vSphere 7.0U2, the override will not work if the host has TPM enabled.

	= Prozesse =		= Prozesse =