VxRail: VMware vCenter Server konnte beim Exportieren von Daten von der Quell-VM nicht aktualisiert werden
Summary: Während eines Upgrades von VxRail vCenter Center schlug dieses fehl, wenn Daten vom Quell-vCenter-Server auf den Ziel-vCenter-Server exportiert wurden. Aus dem Protokoll geht hervor, dass viel Zeit für das Exportieren von VMware Analytics Service-Daten aufgewendet wurde. ...
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Von VxRail
lcm-web.logaus:
2025-08-31T10:27:25.367Z <4304e36e4934ff08fc8120c70e58301b> lcm [WARN] <183> VirtualApplianceUpgradeService.java runUpgrade() (1158): LCM Exception occurred during upgrade for virtual appliance 0 - {}
com.vce.lcm.exception.LCMException: Failed to upgrade the VMware vCenter Server: Failed to export data from source VM VCENTER01.
at com.vce.lcm.api.LCMServiceImpl.handleUpgradeException(LCMServiceImpl.java:2129)
at com.vce.lcm.api.LCMServiceImpl.performUpgrade(LCMServiceImpl.java:509)
at com.emc.mystic.manager.upgrade.service.VirtualApplianceUpgradeService.runUpgrade(VirtualApplianceUpgradeService.java:1134)
at com.emc.mystic.manager.upgrade.service.PureUpgradeRestServiceImpl.lambda$retryVirtualApplianceUpgrade$0(PureUpgradeRestServiceImpl.java:129)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: com.vce.lcm.exception.LCMInternalException: Failed to upgrade the VMware vCenter Server: Failed to export data from source VM VCENTER01.
at com.vce.lcm.core.upgrade.ComponentUpgradeService.performComponentUpgrade(ComponentUpgradeService.java:339)
at com.vce.lcm.api.LCMServiceImpl.performComponentUpgrade(LCMServiceImpl.java:2439)
at com.vce.lcm.api.LCMServiceImpl.performCompositeUpgrade(LCMServiceImpl.java:1845)
at com.vce.lcm.api.LCMServiceImpl.performUpgrade(LCMServiceImpl.java:507)
... 7 common frames omitted Vom /var/log/vmware/upgrade/export.json Protokoll des neu entwickelten vCenter Servers schlug das Upgrade fehl, wenn "Exporting VMware Analytics Service data..." mit TIME_OUT Error:
{
"progress": 37,
"progress_message": {
"id": "ur.upgrade.script.export.progress.text",
"translatable": "Exporting %(0)s data...",
"args": [
"VMware Analytics Service"
],
"localized": "Exporting VMware Analytics Service data..."
},
"status": "error",
"info": [],
"warning": [],
"question": null,
"error": {
"detail": [
{
"id": "ur.upgrade.execution.timedout.text",
"translatable": "Upgrade phase timed out. The time planned for the upgrade phase was %(0)s minutes. The upgrade phase has already been running for %(1)s minutes.",
"args": [
60,
60
],
"localized": "Upgrade phase timed out. The time planned for the upgrade phase was 60 minutes. The upgrade phase has already been running for 60 minutes."
}
],
"componentKey": "upgrade_framework",
"problemId": null,
"resolution": {
"id": "ur.upgrade.execution.timedout.resolution",
"translatable": "To extend the default timeout, set environment variable %(0)s for export upgrade phase, %(1)s for import upgrade phase, and %(2)s for import historical data phase. The timeout is in minutes.",
"args": [
"UPGRADE_EXPORT_TIMEOUT",
"UPGRADE_IMPORT_TIMEOUT",
"UPGRADE_POST_IMPORT_TIMEOUT"
],
"localized": "To extend the default timeout, set environment variable UPGRADE_EXPORT_TIMEOUT for export upgrade phase, UPGRADE_IMPORT_TIMEOUT for import upgrade phase, and UPGRADE_POST_IMPORT_TIMEOUT for import historical data phase. The timeout is in minutes."
}
},Cause
Dieses Problem tritt auf, weil der Push-Telemetrieprozess eine übermäßige Anzahl von Anforderungen mit eindeutigen IDs sendet, was zur Erstellung vieler Dateien im "/var/log/vmware/analytics/prod"-Verzeichnis. Manchmal hat dies zu einer Anhäufung von 185.000 bis 375.000 Dateien geführt.
Resolution
Siehe KB https://knowledge.broadcom.com/external/article/322053/vcenter-server-upgrade-from-70-to-80-fai.html (externer Link)
- Stellen Sie über SSH eine Verbindung zum vCenter-Quellserver her
- Führen Sie den folgenden Befehl aus, um die Anzahl der Dateien zu überprüfen, die auf dem vCenter Server aufgrund des Telemetrie-Push-Prozesses erstellt wurden:
ls /var/log/vmware/analytics/prod | wc -l - Laden Sie die
cleaning_vddk_script.shSkript aus dem Abschnitt Anhänge dieses Artikels. - Laden Sie das Skript in vCenter hoch und weisen Sie mit diesem Befehl Ausführungsberechtigungen zu:
chmod +x cleaning_vddk_script.sh - Führen Sie das Skript aus:
./cleaning_vddk_script.sh - Starten Sie das Upgrade über das VxRail-Plug-in neu.
Affected Products
VxRail, VxRail Appliance SeriesArticle Properties
Article Number: 000372265
Article Type: Solution
Last Modified: 31 Oct 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.