1 Wednesday, 08 April 2015 [email protected]
SAP migration from on
premise to Microsoft
Azure Cloud
&
Managed Services
On Azure
Ver: 1.0
Created by: Mr. Saikat Banerjee Created for: MPS Limited
Reviewed, Verified, Cross-checked: Mr.Vishal Parpia
Legal Cross-checked: Mr.Rohit Pandey
2 Wednesday, 08 April 2015 [email protected]
Confidential Document Please do not distribute, email, forward, copy, print, fax and advertise without
prior written authorization of both parties involved in this document.
Document Created by: Mr. Saikat Banerjee
Document Created for: MPS Limited
Document Creation date: 07 April, 2015 (Tuesday)
Document Reviewed by: Mr. Vishal Parpia
Document Checked with Legal: YES
Document Checked and approved from management: YES
3 Wednesday, 08 April 2015 [email protected]
Contents
1. Requirements of MPS Limited
2. Service Level Agreements (SLA) for the environment on Azure
2.1. Combined SLA of CloudCover & Azure
3. SAP Migration from On Prem to Azure
3.1 Scope of Work
a. Deployment and Consultancy for Azure
b. Migration of on prem SAP on Azure
3.2 Pre requites - required before Migration and Iaas Deployment
(architecture diagrams for HA and without HA)
3.3 Exclusion
3.4 Assumptions
3.5 Project Duration
4. Managed Services from CloudCover
4.1. Type
4.2. Scope
4.3. Severity Levels & SLAs
4.4. Escalation Matrix
5. Reports
6. CloudCover charges for the 24*7*365 managed services with change and release
management
7. Deployment and consulting
8. Consolidated commercials
8.1 Azure pricing
8.2 Cloudcover charges
8.3 CloudCover charges
8.4 Managed service charges
8.5 Total Charges(Approx.)
4 Wednesday, 08 April 2015 [email protected]
1. Requirements of MPS Limited
Key requirement from MPS Limited is to
a. Migrate their existing on premise SAP to Microsoft Azure public cloud.
b. Managed Services for Infrastructure on Microsoft Azure On 24*7*365
Basis.
MPS Limited is seeking to collaborate with a Managed Services Partner of
Azure Cloud Platform who can assist them with the SAP migration to cloud, and
also manage the infrastructure on behalf of them i.e. Managed Services with
corresponding Service Level Agreements (SLAs).
Key deliverables of this Managed Services Partner will be
Migrate on prem SAP and LOB applications integrated with SAP to Azure
Perform a detailed analysis of the current environment variables
Devise a strategic roadmap for Managed Services
Provide SLA-driven 24*7*365 Managed Services with detailed description
of the severity levels, SLAs and resolution times for Azure environments
5 Wednesday, 08 April 2015 [email protected]
2. Service Level Agreements (SLAs) for
the environment on Azure
This section s 24*7*365 support offerings as well as
define the SLAs under which we operate. CloudCover provides architecture,
management, 24*7*365 managed services support and maintenance on cloud
infrastructure running on Azure. Microsoft Azure provides different SLAs for
each element of infrastructure they offer. These SLAs (current at the time of
creation of this documen support
By leveraging Azure is
able to augment and provide higher levels of service than the underlying
components, effectively the whole is greater than the sum of the parts.
Keep in mind this document presumes that your architecture has been designed
by CloudCover, has been implemented to leverage every high availability
solution Azure 24*7*365 managed
services for fault detection and mitigation.
This document does not take into account Information Technology Service
Continuity, Business Continuity or Disaster Recovery. Any such implementation
will include a custom SLA with specific recovery point objectives and recovery
time objectives, mutually agreed upon by MPS Limited and CloudCover.
http://azure.microsoft.com/en-us/support/legal/sla/6 Wednesday, 08 April 2015 [email protected]
3. SAP migration: on premise to Azure
SAP migration involves two different consulting and deployment activities:
a. Deployment and Consultancy for Azure
b. Migration of on prem SAP and LOB Applications on Azure
As requested, architecture for both SAP with and without high availability
is shown below:
Fig.: SAP in Azure without high availability
7 Wednesday, 08 April 2015 [email protected]
Fig.: SAP in Azure with high availability
3.1 Scope of work:
a. Deployment and Consultancy for Azure:
Analyzing on prem infrastructure
Sizing the infrastructure for Azure
Creation of VMs
Implement High Availability
Deploy and Configure the Web Server
Deploy and Configure Traffic Manager
Automate HA in case of Failover
Automate Health Probe for the VMs
8 Wednesday, 08 April 2015 [email protected]
Establish VPN between on prem Azure Public Cloud
Co-ordinate in Deployment of SAP on Azure
Preparation of the architecture of the Infrastructure
Include best practices for better uptime
Co-ordinate in case of any infrastructure related bottlenecks during
SAP migration
b. Migration of on prem SAP to Azure
SAP Landscape - Migration of ECC 6.0
Phase
Deliverables Responsib ilities
Project Preparation
Final Project Plan Cloud Cover & MPS
Installation of Solution Manager 7.1 SP13
Setting up the Hardware for SAP Solution
Manager Server Cloud Cover
Installation of Operating System and post
installat ion activities Cloud Cover
Check OS Prerequisites, dump SAP Solution
Manager DVD's Cloud Cover
Install & Patch SAP Solution Manager 7.1 SP13
Production system Cloud Cover
Post Installation Activities Cloud Cover
Perform initial, basic configur ation of the
Solution Manager system Cloud Cover
SAP Router installation & Testing Cloud Cover & MPS
Sign-off MPS
Proposed
Install Diagnostics agent and SAP Host Agent
on satellite systems
Enable Maintenance Optimizer
Enable Early -watch alerting
Configure SAP Download Manager and
patch repository Cloud Cover
Development System
9 Wednesday, 08 April 2015 [email protected]
Setting up the Hardware for SAP Development
Server Cloud Cover
Installation of Operat ing System and post
installation activities Cloud Cover
Migration of SAP ECC 6.0 & Upgrading MS SQL 2005 to SQL 2012 Cloud Cover
Post Processing Activities, Apply - SAP License etc. Cloud Cover
Technical Testing - BASIS Cloud Cover & MPS
Functional Testing MPS
Sign-off MPS
Quality System
Setting up the Hardware for SAP Quality
Server Cloud Cover
Installation of Operating System and post
installation activities Cloud Cover
Migration of SAP ECC 6.0 & Upgrading MS SQL 2005 to SQL 2012 Cloud Cover
Post Processing Activities, Apply - SAP License, STMS etc. Cloud Cover
Technical Testing - BASIS Cloud Cover & MPS
Functional Testing MPS
Sign-off MPS
Final Preparation
Cutover Planning & Preparation Cloud Cover & MPS
Go-Live & Post Go -
Live Support
Setting up the Hardware for SAP Production
Server Cloud Cover
Installation of Operating System and post
installation activities Cloud Cover
Migration of SAP ECC 6.0 & Upgrading MS SQL 2005 to SQL 2012 Cloud Cover
Post Processing Activities, Apply - SAP License, STMS etc. Cloud Cover
Technical Testing - BASIS Cloud Cover & MPS
Functional Testing MPS
Sign-off MPS
10 Wednesday, 08 April 2015 [email protected]
3.2 Pre requites - required before Migration and Iaas Deployment
Credentials for OS, Data Base & SAP for SAP Landscape ( SAP All Clients
SAP* & DDIC )
SAP Marketplace (OSS) User id & Password with full access
Data Center Access at MPS
Internet access
3.3 Exclusion
SAP Version Upgrades / EHP's
Disaster Recovery
Any Functional & ABAP Testing / Changes
Data Base Optimization, Fine Tuning
Or any other activity which is not mentioned in the Scope of Work (3.1)
11 Wednesday, 08 April 2015 [email protected]
3.4 Assumptions
MPS Limited will be responsible for taking backups during entire project
and will provide latest backup to CloudCover team as and when required.
MPS Limited will appoint or identify a Project Manager to work with for
CloudCover SAP Team dedicatedly.
MPS Limited Functional & ABAP team will carry out testing and will resolve
any issues related to same within time frame
MPS Limited
installation & migration of SAP System to CloudCover SAP Team.
MPS Limited will provide SAP Market place full access for downloading SAP
software, patches, kernels, SAP Licenses to CloudCover SAP Team.
MPS Limited will provide VPN / Router connectivity to CloudCover.
MPS Limited will register for the Azure subscription and share the
credentials for the same with CloudCover team.
3.5 Project Duration
6 man days ( for Azure infrastructure deployment)
6 Weeks = 6*7 = 42 days (for SAP migration)
Total no of days: 50 days (approx.. )
12 Wednesday, 08 April 2015 [email protected]
4. Managed Services from CloudCover
CloudCover is one of the handful of AZURE Advanced Consulting Partners in
India with a Managed Service Provider (MSP) competency. We offer a
completely managed infrastructure solution.
We effectively become your IT administration and operations arm and take care
servers, services, networking, security, upgrades and maintenance
transparently.
CloudCover will build additional tools (and provide you with a perpetual license
for the same) to manage and maintain your unique infrastructure. Our team of
software engineers and cloud specialists will tweak your network, optimize your
servers and recommend new architectural improvements to better leverage the
cloud. Complete management is only offered as a fully 24*7*365 managed
service.
4.1. Type
24*7*365 SLA-driven Managed Services
- All 24 hours round the clock is deemed key to your business operations
- Services Level Agreement (SLA)-driven Managed Services will be provided by
CloudCover NOC .
- For Managed Services scope, see Section 4.2.
- For SLAs, see Section 4.4.
- Contract period = 1 year
- Renewed every year
- Joint reviews performed every Quarter with management
13 Wednesday, 08 April 2015 [email protected]
4.2. Scope CloudCover will provide all these services mentioned below as part of the SLA-
driven Cloud Managed Services to MPS Limited.
Deployment
Provisioning
Basic Cloud Services Integration
Creation of secure environment
Image Replication to HA & DR
Cloud User Management
Auto scale management
Monitoring
Site Availability
CPU
Disk
Memory
Traffic
Application Specific Monitoring
Custom Metrics
Dashboard Access
Threat Monitoring
Database Management
Replication to HA & DR
Security Management
Firewall Configuration
File Permissions
Windows OS Patching
Server Hardening
Virtual Networking
VPN Integration
Encrypted File System
Single-Sign On and Federated Identity
14 Wednesday, 08 April 2015 [email protected]
User Management
ACLs and IAM setup
User policy setup
MFA setup and management
Backup / Restore
Image creation
File / Directory
Block Storage
Scheduling / Automation
Data Retention compliance
Snapshot Management or HA & DR Management
Fire drills
Storage Appliance Configuration
Disaster Recovery (optional)
DB Master / Slave
DNS Failover
Recovery Drills
Audit Management
Quarterly Backup
Quarterly Security
Quarterly Configuration
Quarterly Security Audit Reports
Monthly Backup
Monthly Security
Monthly Configuration
Resource Utilization Reports
Customer On-boarding
Configuration of Cloud infrastructure (VPN tunnel, Security groups
white listing)
Assisting Clients in VPN configuration
15 Wednesday, 08 April 2015 [email protected]
Log Management
Log File Shipping / Rotation
Log Backup
Integration with 3rd Party Logging Services
ADVISORY REVIEW (Quarterly Once)
Advisory meeting with a Solutions Architect
Key points for optimization of Infra (if any)
Key recommendations (if any)
Key concerns (if any)
Key new features on AZURE (if any)
Key best practices (if any newly released)
ADVISORY REVIEW (Quarterly Once)
Advisory meeting with a Solutions Architect
Key points for optimization of Infra (if any)
Key recommendations (if any)
Key concerns (if any)
Key new features on AZURE (if any)
Key best practices (if any newly released
4.3 Severity Levels and SLAs
hat an incident can have on MPS
Limiteds business. The following Severity Levels are applicable for Network,
Server, and Database Infrastructure Management Services:
Severity Level
Description
L3 Service outage resulting from failure of application, database, web servers, network devices.
Patch upgrade*
IMAC changes
User ID Creation and Deletion
16 Wednesday, 08 April 2015 [email protected]
Disc quota changes
Data backup or restore requests
*This activity may have a dependency on successful test of patches in UAT/test environment and/or availability of downtime for the activity. The ticket for such activities shall be raised in discussion with the Customer.
L2 Any failure of one of the multiple application, database, web servers or network devices that are configured under high availability using physical redundancy at the same location, that does not result in service outage.
Any other standalone server or network element in scope.
Any incident of backup activity or Job failure on servers running business applications, web servers, email, DNS, and databases.
Disruption due to virus attack.
L1 Any event that causes business disruption and escalated through L2 Support or directly by client
4.3.1. Service Levels
4.3.1.1 Incident Service Levels
Severity Level Response Time % SLA
L3 60 minutes 99.0%
L2 30 minutes 99.5%
L1 15 minutes 99.95%
17 Wednesday, 08 April 2015 [email protected]
4.4 Escalation Matrix Severity Level Handled By Service Level Item
L3 Operations Team 24*7*365 rotating service of technical personnel for all S3 jobs. This team comprises of Azure Certified SysOps.
L2 Solution Architects Team
This is 24*7*365 rotating service of Subject matter experts, platform experts and Azure experts with 3-5 years of experience. This team comprises of Azure Certified Solutions Architect Associate Level.
L1 Senior Solutions Architects Team
This is 24*7*365 rotating service of Subject matter experts, platform experts and Azure experts with over 8-10 years of troubleshooting and Azure experience. This team comprises of Azure Certified Solutions Architect Professional Level.
18 Wednesday, 08 April 2015 [email protected]
5. Reports
Following reports can be provided to MPS Limited:
1. Pingdom uptime reports
2. Monthly Incident Report (Report on Incidents, Response time,
Resolution time, SLA meet versus miss) Monthly infrastructure
performance reports
3. RCA Reports for S1 Incident within 2 days and for all other event, within
6 days
4. Initial report for a L3 Incident will cover Time of Occurrence, Duration of
Incident, Summary of Incident, Impact, and workaround. Analysis will be
shared within 24 hours of an incident
5. L1 Support is baked in our Managed Services Packedge.
19 Wednesday, 08 April 2015 [email protected]
6. CloudCover Charges for the 24*7*365
Managed Services with Change and
Release Management
This is a monthly recurring fee.
20% of clients AZURE Monthly bill or INR 20,000 per month whichever is
`higher will be charged for the Managed Services provided by
CloudCover in order to manage the said Cloud Infrastructre on Azure
Cloud Platform.
negement will be effective for 12
months in the start and client can extend it further after the said period
of 12 months.
* Usual taxes apply at the time of raising invoice.
Please note:
Consulting cost does NOT include License costs
Managed Services cost does NOT include License costs which will be purchased as on-
demand and invoiced to MPS Limited when it is needed
Managed Services cost will be revised and renewed post 1-year
20 Wednesday, 08 April 2015 [email protected]
7. Deployment and Consulting
Deployment and Consulting services is an one time service offered by
CloudCover to automate :
Instance Creation
Configruation and Reconfigruation
Enhancement in overall Deployment processes
All the DevOps activities are charged on daily fashion depending on the
resource level engaged in building the scripts for automation for your
stack on Cloud.
Daily Rate Card is provided below :
For the current proposal we are anticipating it to be approximately 6
man days.
Resource Level Hourly Charges
Senior DevOps Engineer INR 20,000/day
Mid-Level DevOps Engineer INR 15,000/day
21 Wednesday, 08 April 2015 [email protected]
8. Consolidated Commercials:
As stated earlier, there are 4 main pricing components :
1. Azure IaaS charges
2. Azure IaaS Consulting and Deployment charges
3. SAP migration charges
4. Managed Services
8.1 Azure IaaS charges: (all these charges are exsimated approximate charges)
8.1.1 Without HA:
8.1.2 With HA: