VxRail: Nie udało się uaktualnić serwera VMware vCenter Server podczas eksportowania danych ze źródłowej maszyny wirtualnej

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

Ten problem występuje, ponieważ proces telemetrii wypychania wysyła nadmierną liczbę żądań z unikatowymi identyfikatorami, co powoduje utworzenie wielu plików w "/var/log/vmware/analytics/prod" katalogu. Czasami prowadziło to do nagromadzenia od 185 000 do 375 000 plików.

Zapoznaj się z artykułem https://knowledge.broadcom.com/external/article/322053/vcenter-server-upgrade-from-70-to-80-fai.html bazy wiedzy (łącze zewnętrzne)

1. Nawiązywanie połączenia ze źródłowym serwerem vCenter Server przy użyciu protokołu SSH
2. Uruchom następujące polecenie, aby sprawdzić liczbę plików utworzonych na serwerze vCenter ze względu na proces telemetrii wypychania: ls /var/log/vmware/analytics/prod | wc -l
3. Pobierz plik cleaning_vddk_script.sh Skrypt z sekcji Załączniki tego artykułu.
4. Prześlij skrypt do vCenter i przypisz uprawnienia "uruchomienie" za pomocą tego polecenia: chmod +x cleaning_vddk_script.sh
5. Uruchom skrypt: ./cleaning_vddk_script.sh
6. Uruchom ponownie aktualizację z wtyczki VxRail.