Instances hosted on Sugar’s cloud service are automatically upgraded with Sugar’s periodic releases (approximately one per month) to ensure they are benefitting from the latest feature enhancements and bug fixes. The entire upgrade process is handled by the Sugar Operations team, so there is no action required on your end to receive these improvements. This article provides answers to some common upgrade questions for SugarCloud instances.
All major version upgrades, defined by a change in the first two digits of the release number (e.g. 18.104.22.168 to 22.214.171.124) will be communicated a minimum 7 days in advance. An email is sent out seven days in advance of the upgrade to all configured email addresses as described in our SugarCloud Policy Guide.
Minor version upgrades, defined by a change in the 3rd or 4th digits of the release number (e.g. 126.96.36.199 to 188.8.131.52) will occur without prior notification. The purpose of these upgrades is to resolve critical bugs in the application, and our goal is to limit the exposure to those bugs as much as possible.
The Upgrade Wizard is disabled for instances on Sugar’s cloud service as upgrades are performed and managed by the Sugar Operations team. Instances hosted on Sugar’s cloud service are set to automatically upgrade which allows you to receive new features and fixes without any effort on your part. You can also file a case with the Sugar Support team to request and coordinate a schedule for the upgrade.
After receiving a request to upgrade via a case, the Sugar Support team will review your instance then coordinate the upgrade date and time with you. If there is a specific date or time that you would like the upgrade to occur, please include it when filing the case.
SugarCRM takes a backup of your instance before every upgrade. Should the upgrade fail to complete successfully, the upgrader will automatically restore your instance to the previously working version. Rolling back to the backup is not an option after the completion of a successful, scheduled upgrade. Should you encounter an issue with your instance after an upgrade, please file a case with the Sugar Support team to investigate the cause and potential solutions.
You can file a case to request an upgraded test instance in order to evaluate a new version in advance of your production instance’s upgrade. Sugar support will provide a temporary sandbox which will be deleted after the upgrade case is closed.
All users must be logged out from the system during the upgrade window provided to you by your upgrade notification or your communication with Sugar Support. Instances are put into maintenance mode for the duration of the upgrade. Any users accessing the instance when it enters maintenance mode will be logged out.
Please file a case with the Sugar Support team if you have any questions that we did not address in this article. A Support representative will respond to your questions promptly.