Product Life Cycle
The Storware Backup and Recovery product Support Life Cycle phases are described here:
- 1.Technical Support depends on the service level included in your Storware Backup and Recovery li-cense agreement.
- 2.Storware may choose, as an intermediate measure, to address serious issues that have an impact.
The Storware Backup and Recovery Product Support Life Cycle dates are described here:
During the Full Support phase, qualified Critical and Important Security issues will be addressed with released High Priority Bug Fix as they become available. Other Fix Advisories, may be delivered as appropriate.
For any minor release made available during this phase, the available and qualified Fix Advisories will be cumulatively included with the contents of previously released product updates. This means that if a customer is running an older version of the product and reports a bug, that bug will be fixed in the latest version of the software and a customer may need to upgrade to take advantage of that fix.
During the Maintenance Support phase, which starts with the second year after release, the defined Critical and Important Security Fix Advisories may be released as they become available. No other fixes to the software are available.
Upgrades and updates are still to be delivered within this period.
Storware will provide a supported upgrade path between major releases for Storware Backup and Recovery. Upgrades will be supported between the latest minor release of previous version to the most current version of the next higher major release. In these cases, the upgrade process will be limited to support upgrading from the latest minor release of the previous version to the new major version.
- Upgrading from vProtect 4.0 to Storware Backup and Recovery 5.0 is supported, assuming vProtect 4.3 being the most current release of the 4.x series and intermediary update to 4.3 is required in such case.
Upgrade from Beta / Pre-release releases to a fully supported release is not supported.
Customers are expected to update new minor releases as and when they become available. Accelerated fixes will not be provided for issues that have been previously fixed in a subsequent release; customers are expected and encouraged to keep their systems current and upgraded to the latest version of product to keep up to date on all patches and fixes.
In circumstances where the reported issue is not fixed in the current shipping release, the customer is still expected to upgrade their systems to the latest release (n) or in some exceptional cases, the immediate previous release (n-1). This is to ensure that any fixes are developed and verified against the latest or the immediate previous release.
Throughout the support lifecycle, qualified security issues of Critical or Important impact, as well as select mission-critical bugs, will be addressed by updated packages.
For the high-priority bugs and vulnerabilities Storware announces Fix Advisories with the recommendation to update to the specified version. Fixes are always included with the next version of packages (as the regular RPM updates).
Fix Advisories may contain security or bug fixes. All Fix Advisories are tested and qualified against the respective, active Storware Backup and Recovery major release.
All released Fix Advisories remain accessible to active subscribers for the entire Storware Backup and Recovery life cycle.
Storware actively develops only the last major version’s minor release (for example a bug found in vProtect 4.3 or vProtect 4.2 after the release of Storware Backup and Recovery 5.0 could only be fixed in the newest build of vProtect 4.3 release).
Fix Advisories or hotfixes for earlier releases are provided at the discretion of Storware to address critical impact security issues with a significant customer business impact.
During the life cycle of a major release Storware makes commercially reasonable efforts to maintain binary compatibility for the core runtime environment across all minor releases and Fix Advisories. If necessary, Storware may make exceptions to this compatibility goal for critical impact security issues or other significant issues.
Each minor version of product delivers a new Compatibility Level based on the minor version number. Each release supports at least the current and previous minor release Compatibility Level.