Loading...
Loading...
When using the new feature to auto upgrade the ESX cluster (splitters and JAM), it may timeout on ESX maintenance mode if the ESX evacuation takes longer than 60 minutes. This affects only RecoverPoint for Virtual Machines (RP4VM) versions 5.2 SP1 and later.
Slow evacuation process from the ESX
Workaround: Log in as root user to the RP CLI of the RPA that is used to run splitter upgrade . Once logged in, go to /home/kos/kbox/src/apis/splitter_upgrade_tool Do vi splitter_upgrade_tool.properties to edit the file. Change the value of HOST_MAINTENANCE_MODE_VM_TIMEOUT_SECONDS to 3600 and save and exit the file. Reboot the RPA. When upgrading the splitters, make sure to connect to this RPA and run the splitters upgrade from it, since this tweak is RPA specific. When upgrading the splitters, if the ESX does not go into Maintenance Mode, you have up to 60 minutes to troubleshoot it before the upgrade fails. If you are not comfortable doing these steps, open a SR and engage RecoverPoint support for assistance with this procedure.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.