Systemic Migration in Several Stages

Started by RoyJones, Sep 07, 2022, 07:30 AM

Previous topic - Next topic

RoyJonesTopic starter

The migration of SAP systems is a difficult and meticulous process that requires coordination from all participants for success, especially when done in a short time frame. Some clients may be hesitant to undergo migration due to the lengthy and complex process, the risk of system downtime, or uncertainty about the benefits they will receive. However, some exceptions exist.



In this article, we will discuss the challenges faced by clients during the migration and maintenance of SAP systems, debunk stereotypes, and share a case study of how Runibex Technology migrated a client's systems to new infrastructure in just over three months.

SAP systems hosting is now more commonly implemented on cloud infrastructure due to outsourcing models and the cloud services market. The scalability of resources, reduced non-core competency development, improved risk management, and cost savings for high availability and DR scenarios are some of the reasons why customers choose cloud hosting for SAP.

However, changing SAP hosting providers can be daunting due to the complexity of the migration process and potential pitfalls, such as inconsistency with the level of service, limited resources, lack of flexibility, bureaucracy, technical limitations, and low competence of support specialists. Clients may only realize these issues after signing multi-page contracts and experiencing suboptimal service levels, which may lead them to consider alternative options.

The move to Zabbix unified hardware, OS, and SAP, while Grafana dashboards proved useful in collecting data. When alerts go off, Zabbix can start Jira for incident management and duplicate information in a Telegram channel. The team also set up a DNS server cluster, a separate file server, and Gitlab for storing configurations and HashiCorp Vault for sensitive information.

The migration process involves project documentation preparation, negotiations with the current provider, new equipment purchase and installation, test migration, and combat migration. For a project that fell over the new year, our engineers had to speed up the process and sacrifice their holidays to ensure the operability of vital enterprise systems. Non-critical systems first moved over to the new infrastructure before the productive ones, with a cutover plan detailing tasks, completion time, and responsible persons. By following this plan, the combat migration was smooth.

It's essential to note that the delivery time of certified SAP NAHA hardware can take 10-12 weeks and potentially longer due to seasonality. However, working closely with vendors and distributors for accelerated deliveries helped the team meet their deadlines.
  •  

Charlesth

When using HANA replication, the recovery time is typically just minutes as it processes the takeover command quickly. However, with a traditional backup and restore approach, recovering data backups and log backups can take much longer, especially for large databases. It's worth considering the SLA with the customer to ensure they are aware of this potential delay in case of a productive storage system failure.

It's important to note that HANA replication offers more efficient recovery times for productive landscapes compared to traditional backup and restore approaches. When a storage system fails, HANA replication processes the takeover command swiftly, allowing for a quick recovery within minutes. On the other hand, with traditional backup and restore methods, restoring data and log backups can take a considerable amount of time, especially for larger databases. This is something to consider when agreeing on an SLA with a customer to ensure they are aware of what to expect in case of such a scenario.
  •  

shane

The migration process you described seems typical without any unique difficulties worth discussing. However, it appears that you migrated through full backups without utilizing standby migration, which can significantly reduce migration time from hours to minutes. In contrast, a colleague who participated in migrating one of Europe's biggest ERP systems (with a size of 130 Tb) reported a timeout of only 15 minutes with all cases using a 10 gbit channel and a delay of 70-100 ms.

While the migration process may be commonplace, there are ways to optimize it for even greater efficiency. Utilizing standby migration could cut down the time it takes to migrate from hours to mere minutes, as demonstrated by a colleague who worked on one of Europe's largest ERP systems. Considering these kinds of optimizations could make a significant difference in the overall success of a migration project.
  •  

ashutoshkumar

While standby migration is undoubtedly an efficient and time-saving option, it may not always be possible to utilize it. In our case, unforeseen challenges with communication channels made it impossible to implement standby migration, so we had to rely on full backups for our migration process.

Despite the fact that the technical aspect of the migration process may seem straightforward, the timing of a migration project can present significant challenges. In such cases, it's worth exploring some of the nuances and difficulties that arise during the process and how they can be successfully overcome. By sharing experiences and solutions, we can help others navigate similar challenges during their own migration journeys.
  •  

dterbo

The challenges faced by clients during this migration process are multifaceted, including concerns about system downtime, complexity of the migration process, potential pitfalls with new service providers, and the time and effort required for negotiation, equipment purchase, installation, and testing.
One of the key trends in SAP hosting is the increasing adoption of cloud infrastructure, driven by the benefits of scalability, reduced development of non-core competencies, improved risk management, and cost savings. However, changing SAP hosting providers can be daunting due to potential inconsistencies, limited resources, lack of flexibility, and technical limitations. Clients may only realize these issues after committing to lengthy contracts, which can lead to dissatisfaction and the exploration of alternative options.

In a recent case study, Runibex Technology successfully migrated a client's SAP systems to new infrastructure in just over three months. They highlighted the use of Zabbix for unified hardware, OS, and SAP monitoring, along with Grafana dashboards for data collection. The implementation of alert notifications to Jira for incident management and duplication of information in a Telegram channel demonstrates a comprehensive approach to system monitoring and response.

The migration process involved meticulous project documentation preparation, negotiations with the current provider, purchase and installation of new equipment, test migrations, and the final combat migration. Notably, the team had to accelerate the process and sacrifice holidays to ensure the operability of vital enterprise systems, highlighting the dedication and commitment required for successful system migration.

It's also important to consider the challenges related to hardware procurement, as the delivery time of certified SAP NAHA hardware can take considerable time, potentially impacting project timelines. However, close collaboration with vendors and distributors for accelerated deliveries played a crucial role in meeting project deadlines.
The migration and maintenance of SAP systems require thorough planning, technical expertise, and a proactive approach to overcome the challenges and deliver successful outcomes for clients.
  •  

alexcray

Quote from: RoyJones on Sep 07, 2022, 07:30 AMThe migration of SAP systems is a difficult and meticulous process that requires coordination from all participants for success, especially when done in a short time frame. Some clients may be hesitant to undergo migration due to the lengthy and complex process, the risk of system downtime, or uncertainty about the benefits they will receive. However, some exceptions exist.



In this article, we will discuss the challenges faced by clients during the migration and maintenance of SAP systems, debunk stereotypes, and share a case study of how Runibex Technology migrated a client's systems to new infrastructure in just over three months.

SAP systems hosting is now more commonly implemented on cloud infrastructure due to outsourcing models and the cloud services market. The scalability of resources, reduced non-core competency development, improved risk management, and cost savings for high availability and DR scenarios are some of the reasons why customers choose cloud hosting for SAP.

However, changing SAP hosting providers can be daunting due to the complexity of the migration process and potential pitfalls, such as inconsistency with the level of service, limited resources, lack of flexibility, bureaucracy, technical limitations, and low competence of support specialists. Clients may only realize these issues after signing multi-page contracts and experiencing suboptimal service levels, which may lead them to consider alternative options.

The move to Zabbix unified hardware, OS, and SAP, while Grafana dashboards proved useful in collecting data. When alerts go off, Zabbix can start Jira for incident management and duplicate information in a Telegram channel. The team also set up a DNS server cluster, a separate file server, and Gitlab for storing configurations and HashiCorp Vault for sensitive information.

The migration process involves project documentation preparation, negotiations with the current provider, new equipment purchase and installation, test migration, and combat migration. For a project that fell over the new year, our engineers had to speed up the process and sacrifice their holidays to ensure the operability of vital enterprise systems. Non-critical systems first moved over to the new infrastructure before the productive ones, with a cutover plan detailing tasks, completion time, and responsible persons. By following this plan, the combat migration was smooth.

It's essential to note that the delivery time of certified SAP NAHA hardware can take 10-12 weeks and potentially longer due to seasonality. However, working closely with vendors and distributors for accelerated deliveries helped the team meet their deadlines.

This implies the migration isn't random or individual-based. There are underlying social, economic, or environmental factors pushing or pulling large groups of people to move.
  •