Reminder: Avaya Software Backup Policy
On September 26, 2016, Avaya announced an important change to its Software Support Policy. Under this change, Avaya will no longer distribute copies of software for specific versions of some legacy products. As a result, software downloads that were formerly available from the Avaya Support (aka SSO) website will no longer be available for download directly from Avaya. As a result, any failure that requires software re-install will require client-provided backups of the original media.
The first deadline is October 31, 2016. On this date, custom patches for the Communication Manager (CM) product family will cease to be available. But neither SPS nor any other partner has access to custom patches (client-specific updates, typically deployed to address a trouble ticket).
To mitigate this risk to the reliability of affected Avaya systems, clients whose systems depend upon affected products and versions must make their own backups for the affected files. For some files, SPS will support clients by hosting common update files on an SPS server. (Excludes client-specific patches affected by the Oct-31 deadline.)
Other deadlines stated in the Avaya communication include:
- January 31, 2017: Full copies of affected software will no longer be available for download from Avaya.
- November 30, 2017: Incremental service packs and common (non-custom) patches will no longer be available for download from Avaya.
Affected products include:
Currently, backups are generally considered a client responsibility. Subscribers to SPS Insight Services receive off-site backups of Avaya CM translations only. SPS is also developing a new service offer to provide broad backup and restore capabilities for a range of platforms. This service offer will be announced as it become available.
If you have any questions, please check your email files for the Avaya Sept-26 message, or refer to the following PDF posted to the Avaya Support website:
And please do not hesitate to engage your SPS team.