VxRail: No se pudo actualizar VMware vCenter Server cuando se exportaban datos desde la VM de origen

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

{
    "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."
        }
    },

Este problema se produce porque el proceso de telemetría de inserción envía una cantidad excesiva de solicitudes con ID únicos, lo que da lugar a la creación de muchos archivos en el "/var/log/vmware/analytics/prod" directorio. A veces, esto ha llevado a la acumulación de 185.000 a 375.000 archivos.

Consulte el https://knowledge.broadcom.com/external/article/322053/vcenter-server-upgrade-from-70-to-80-fai.html de la base de conocimientos (enlace externo)

1. Conéctese al vCenter Server de origen mediante SSH
2. Ejecute el siguiente comando para comprobar la cantidad de archivos creados en vCenter Server debido al proceso de telemetría de inserción: ls /var/log/vmware/analytics/prod | wc -l
3. Descargue el archivo cleaning_vddk_script.sh de la sección Archivos adjuntos de este artículo.
4. Cargue el script en vCenter y asigne permisos de "ejecución" con este comando: chmod +x cleaning_vddk_script.sh
5. Ejecute el script: ./cleaning_vddk_script.sh
6. Reinicie la actualización desde el plug-in de VxRail.