Note: If the issue persists, contact VMware support and file a support request with VMware Support and quote this Knowledge Base article ID ( 2057826) in the problem description. For more information, see Filing a Support Request in Customer Connect (2006985).
Note: ESXi host uses a non-persistent memory based file system. By default, configuration changes are written to the bootbank every hour by auto-backup.sh cronjob script or whenever there is a change invoked by internal/user invoked operation through backup.sh script. When the non-persistent memory based file system is unable to write to the bootbank and you must reboot the ESXi, any configuration change made since the last successful write will be lost.