Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
In some HPE SimpliVity clusters where StoreOnce backups are used, there may be an issue where SVTFS services will not start after upgrading Omnistack to version 5.0.0, but before committing the upgrade. The error message "Huge alloc mmap failed" can be observed in the svtfs.log.
SimpliVity Nodes upgrading to OmniStack version 5.0.0, but still uncommitted.
If this issue has already occurred, contact SimpliVity Support for assistance. The issue has been resolved in OmniStack 5.1.0U1 . Upgrading to OmniStack 5.0.0 is no longer advised. Before Upgrading to HPE SimpliVity 5.0.0 Proceed with the following steps using either the CLI or the vSphere Client graphical UI: Suspend policy-based backup activities destined to StoreOnce external store. GUI: Right-click on the cluster of interest > All HPE SimpliVity Actions > Suspend Policy-Based Backups > Click Suspend. Repeat the same with other clusters, if required. CLI: Use the " svt-policy-suspend " command with appropriate arguments based on the scope of the upgrade operation - " omnicube " or " cluster " or " all ". Repeat the same with other nodes or clusters, if required. Verify that no backups are currently in progress to StoreOnce, i.e., backups with status such as - "NEW", "QUEUED", "REBUILDING", "SAVING". Either wait for these to complete and their status to change to "PROTECTED", or cancel/delete the backups not in a "PROTECTED" state. GUI: Select cluster > Configure (tab) > HPE SimpliVity/External Storage > Click HPE StoreOnce Catalyst > Search Backups > Add Filter, Status = NEW", "QUEUED", "REBUILDING", "SAVING" > Click Search > All of which may selected for deletion, with "Delete Backups" under BACKUP ACTIONS CLI: Use the command " svt-backup-show --status new,queued,rebuilding,saving --backup-store-type storeonceonprem ", to list the StoreOnce backups of interest. Use the commands " svt-backup-cancel " or " svt-backup-delete ", with appropriate arguments to cancel or delete the backups, respectively. The StoreOnce appliance can be powered off if deemed acceptable, such as in the case of a federation-wide upgrade. Alternatively, it can be isolated from the identified select individual SimpliVity nodes by appropriately modifying the firewall rules. Start the operations associated with upgrading to the HPE SimpliVity 5.0.0 version. Once all nodes in the cluster have been successfully upgraded, proceed with committing the upgrade operation. Power on the StoreOnce appliance or alternatively, revert the firewall rules to their original state. Resume the policy-based backup activities, by following the same method as was used for suspending backups. NOTE: It is also worth considering that a thorough review and analysis of the configured StoreOnce backup policies, rules, frequencies, and schedules may help determine the ideal maintenance window for the 5.0.0 upgrade operation. By identifying a period during which no StoreOnce-related operations are scheduled, the upgrade will complete successfully within this timeframe and committed before any StoreOnce operations are generated. This proactive approach may eliminate the need for the prevention steps outlined above. NOTE: Another symptom of the same issue is that after successfully upgrading to version 5.0.0 and before committing the upgrade, StoreOnce operations may not complete and stay in a "QUEUED" state, despite SimpliVity remaining fully functional. This problem manifests with the same failure message as described earlier. Committing the upgrade operation is expected to resolve this issue. Revision History Document Version Release Date Details 2 September 27, 2024 Updated Resolution. 1 April 30, 2024 Original Document Release.