More financial transparency and control. Atos provided the ability to alter capacity requirements and spin up new environments, including increasing ECC system memory from six up to nine terabytes at a fraction of the time and risk associated with an on-premises upgrade. Working with Atos and AWS, RS Components completed a fast, smooth migration, despite the challenges of COVID-19. The second phase could be executed side-by-side in AWS on very large machines to minimize the time taken. Use newly-built systems in AWS as the target to avoid migrating technical debtĭowntime was minimized by ensuring that the initial phase of the migration could be completed with the systems online (and therefore still able to take orders). Hold dress rehearsals to resolve issues and refine the timing. Migrate development and testing systems in advance to build confidence in the process and conduct full regression testing, given the scale of change happening during the outage. Where required, replicate systems in AWS to bridge any downtime while migrating data from on-premises to AWS. #Rs components upgrade
Execute as much of the upgrade as possible without downtime on the on-premises systems.The team’s final migration approach used the following principles:
To determine the best migration strategy, Atos devised a proof of concept to test all aspects of implementation. The team’s approach made it possible to achieve a significant amount of change with minimal downtime - and at low risk.Ī traditional migration and upgrade approach directly from on-premises to AWS wasn’t possible due to the large volume of data, the number of systems to upgrade, and the limited bandwidth available via AWS Direct Connect.
0 kommentar(er)
