Disaster recovery scenarios are a requirement for compliance with Sarbanes-Oxley, HIPAA, and other regulatory standards. Ultimately each firm will have to evaluate and decide on their tolerance for risk. This tolerance will enable business leaders to make the correct decision about recovery time objectives (RTO) and recovery point objectives (RPO). RTO is the time from failure to the time the business is back on line again. The RPO is the data loss that is to be tolerated when the business is brought back on line.
This blog will discuss a variation of the traditional OS/DB migration process of an application to the same migration for the purposes of DR. This involves moving from either an on premise location or a hosting center located in a hazardous area such as the earthquake zone of the San Francisco Bay Area. This zone in particular includes the infamous San Andreas Fault and lesser known Hayward, Rogers Creek and Calaveras Faults. An ideal solution is to migrate to the iStreet Northern California Cloud Center which houses a comprehensive concentration of carrier neutral Metro Ethernet providers. Metro Ethernet is the proven and cost effective technology to perform data intensive data moving including real time vMotion recovery scenarios. The Cloud Center is located in earthquake safe metropolitan Sacramento. (Click here to read our Earthquake Safe blog).
First, SAP migrations are not upgrades. For the sake of clarity SAP migration and SAP upgrade are briefly defined here:
1. Upgrade - This refers to installing a major version change of SAP, such as moving from SAP R/3 Enterprise to SAP ERP 6.0. In a technical upgrade, the upgrade project is about changing the SAP Basis layer's version and not about implementing the new functionality of that new version. In a functional upgrade, the goal is to move to the new functionality provided by the new SAP system. To summarize, adding functionality is a functional upgrade.
2. Migration - This most commonly refers to technology platform change. There are OS/DB migrations usually required when moving the SAP computing platform from one operating system or data base platform to a different operating system or database platform.
An SAP migration using colocation means utilizing an organization, preferably an SAP Certified Hosting Partner like iStreet' with data center colocation services, and migrating to the data center. This is could be for several purposes outlined below”
Hosting migration – usually an ideal time to move to iStreet’s hosting provider services is when an on premise or other hosting provider hardware upgrade is called for. This could be a homogenous upgrade, i.e. when the new hardware and OS is the same as the old but a current, more supportable version
DR – usually when a business continuity plan requires and alternate site for DR failover.
Moving to an earthquake safe environment from and on premise or hosting provider in the San Francisco Bay Area earthquake zone.
Whether the migration need is DR, hardware and/or OS/DB migration, or the need to move from an SAP Hosting provider located in the earthquake zone, SAP migration using colocation is an ideal solution. Migrations are not upgrades in SAP language and do not require a functional or technical skill set. The skill set is SAP Basis and system engineering. DR is a very common reason to do a migration as every company should have a business continuity plan.
Thank you for your time and consideration of SAP migrations using colocation. Contact us today for a free migration consultation.
President and CEO