A 5 part blog series by Zensar Architecture Centre of Excellence

Maintaining business continuity also means having latest version software and hardware such that the risk of failures is minimized. The software product companies end the support for older versions and expect customers to upgrade to newer versions. In such scenarios there is a risk of losing support if production systems do not run on latest versions. If you have your own data center it is more important however if you are choosing cloud service provider it is crucial to make sure about the versions.

Benefits of using newer versions are,

  • The software contains latest features helping optimize the non-functional and quality of service aspects such as improved capacity etc.
  • Defects and open issues in previous versions fixed so patching upgrades are not required frequently.
  • Resources utilized in optimized manner and maintenance, support overheads reduced.
  • More value for money spent on licensing and contracts.
  • Aligns more positively with organization’s roadmap.

It is quite often recommended to have latest or latest minus 1 version of software. Latest minus 1 ensures enough maturity of the product is there and required support will be available. The graphic below identifies possible areas where upgrades may be required.

img2

Zensar’s Architecture Centre of Excellence has successfully executed such upgrade assignments in the past for many customers and have also developed methodology to systematically implement the upgrades ensuring business continuity, time, cost and quality and also has added value maintaining customers long term technology roadmap. There are various phases undertaken such as:

  • Due diligence – Understand current version IT asset (hardware/software/platform) and record dependencies, risks and issues.
  • Plan and execute – Create a version upgrade plan with estimates and risk mitigations. Also create a migration and live transition plan along with rollback plans.
  • Address operational and support changes during the upgrade.
  • Test the upgrade at on test environments.
  • Transition the upgrade to live/production systems.

Part One

Business Continuity in IT Landscape

Part Two

High availability architectures

Part Three

Disaster recovery measures

Part Four

Data archiving and server backups

The Author

Vijaykumar Dixit – Vijay has over two decades’ industry experience and over 15 years in IT. Vijay is a TOGAF9.1 certified practitioner and Oracle master certified JavaEE architect. He holds bachelor’s degree in Engineering and a PG diploma in advanced computing. He is currently part of Zensar’s Architecture Centre of Excellence.

His areas of expertise are enterprise architecture, solution design-consulting, SaaS product development and cloud computing. He has helped clients define & setup technology road-map, establish architecture governance and best practices and achieve increased return on IT spend by promoting Service oriented architectures, cloud migration and applications portfolio review and rationalization. He has been a key contributor in Java based enterprise solutions development and also has a sound background of DotNet (Microsoft), Open source based bespoke development and COTS based integration. He has worked for blue chip clients such as Boots PLC, TNT Logistics, Carphone Warehouse, Verizon & Government organizations such as ONS and NHS in the UK and Liberty, Discovery etc. in South Africa.

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...


Avatar

Posted by Vijaykumar Dixit

Leave a reply

Your email address will not be published. Required fields are marked *