itelligence World 2019 – Let‘s transform! Design your future.
24. Oktober 2019
Andreas Hennig, Head of GMS Solution Design & Costing Managed Cloud WE,
itelligence AG
D2: SAP(not only) on Azure@itelli
Microsoft Azure | Availability worldwide
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
4
54 Regions 26 Regions mainly where instances for SAP
are available
Source: https://azure.microsoft.com/en-us/global-infrastructure/regions/
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
5
Analyst‘s(Crisp) view
User‘s(DSAG)
view
Sources:1 Study „SAP-Betrieb in der Public Cloud“, Crisp Research, July 2018, https://www.crisp-research.com/publication/sap-betrieb-der-public-cloud/2 Press release “ SAP-Anwender fordern einheitliche Datenmodelle und weitreichende Integrationsmöglichkeiten“, Deutschsprachige SAPAnwendergruppe
e.V., October 16, 2018; image: https://twitter.com/wolf_gregor/status/1052104590487969793
Microsoft Azure | The most relevant cloud platform after SCP
Microsoft Azure | Azure protection options for all scenarios
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
7
Availability Sets
High Availability protection from hardware failures in a datacenter.
Availability Zones
High Availability protection against loss of datacenters. Multiple datacenters per physically separated zone. Each zone features independent network, cooling, and power.
Region Pairs
Protection for your data and applications from the loss of an entire region with Geo-redundant storage (GRS) and Azure Site Recovery.
Zone 2 Zone 3
Zone 1
Availability
Availability
Availability
Region
Region 1 Region 2
Datacenter
Microsoft Azure | Enterprise-Grade VM Availability, SLAs & DR
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
8
Single VM
VM SLA
99.9%
Availability sets Availability zones Region pairs
VM SLA
99.95%
VM SLA
99.99%
Multi-region
Data Resiliency
Microsoft Azure |
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
9
Azure storage provides replication options based on availability needs
Zone 2 Zone 3
Zone 1
Availability
Availability
Availability
Storage
Microsoft Azure |
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
10
LRS
3 replicas, 1 region
Protect against disk, node, rack failures
Write is ack’d when all replicas are committed
Superior to dual-parity RAID
GRS
6 replicas, 2 regions (3/region)
Protects against major regional disasters
Asynchronous to secondary
RA-GRS
GRS + Read access to secondary
Separate secondary endpoint
RPO delay to secondary can be queried
ZRS V2
3 replicas across 3 Zones
Protect against disk, node, rack and zone failures
Synchronous writes to all 3 zones
Zone 1 Zone 2 Zone 3
Microsoft Azure | Azure provides best in class performance
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
11
960CPUs
Compute performance
Largest in public cloud
24TB RAM
Memory
Largest in public cloud
160KIOPs
Remote Storage(single disk)
Fastest in public cloud
3.7MIOPs
Localstorage
Fastest in public cloud
30Gbps Ethernet
100Gbps InfiniBand
VM-VM Networking
Fastest in public cloud
100Gbps Connectivity
Hybrid Networking
Fastest in public cloud
100KIOPs
File storage
Fastest in public cloud
Microsoft Azure | Azure covers 91 compliance offerings
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
12
https://aka.ms/AzureCompliance
Microsoft Azure | Microsoft Azure Supported Guest OS and DB
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
13
https://wiki.scn.sap.com/wiki/display/VIRTUALIZATION/SAP+on+Microsoft+Azure
Supported virtual Instances can be found here:
1928533 - SAP Applications on Azure: Supported Products and Azure VM types
Microsoft Azure | Certified SAP Solutions (AnyDB) on Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
14
See SAP OSS Note #1928533 (http://service.sap.com/sap/support/notes/1928533 ) for version details and further info IaaS only (no SQL Azure yet)
SAP NetWeaver based solutions e.g. Business Suite - ERP, SCM, CRM, BW, PO, SolMan etc.
SQL Server
OracleSAP ASE
Windows Server
Azure VMs: A5-A11, D11 - D15, D11v2 - D15v2, D2v3 - D64v3, E2v3 - E64v3, GS1-5, M8-2ms - M128ms
MaxDBIBM DB2
Linux (SLES, RHEL)
SAP ASE
IBM DB2
OracleLinux
OracleMaxDB
Additional supported SAP solutions on Windows• SAP BPC on NetWeaver• SAP BO BI Platform (see 2145537)• SAP BO Data Services 4.2• TREX 7.10• SAP Content Server• SAP Financial Consolidation• SAP liveCache• SAP Hybris Commerce
Additional supported SAP solutions on Linux• SAP BO BI Platform (see 2145537)• SAP BO Data Services 4.2• SAP Content Server• TREX 7.10• SAP liveCache• SAP Hybris Commerce
Microsoft Azure | Instance Types
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
15
Overview of Microsoft Azure Instance Types for SAP HANA
SAP Certified Microsoft Azure Instances:
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/iaas.html#categories=Microsoft%20Azure
Microsoft Azure | Regional based Cloud Services
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
16
Microsoft Azure | Itelligence Shared services
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
17
Internet
On-Premise itelli DC MY
Express Route or S2S VPN
GatewaySubnet
itelli Central Hub VNet
Customer VNet
Region 1
Customer VNet
Region 2
Customer
Central services provided within Azure offers maximum flexibility, highest quality and cost reduction, e.g. based on backup dedublication.
Microsoft Azure | Virusscanning and Monitoring
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
18
Microsoft Azure | Backup Design – for Customer
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
19
Internet
On Premise itelli DC MY
Express Route or S2S VPN
GatewaySubnet
itelli Central Hub1 VNet
Customer AzureVNet
Region 1
Region 2
Itelli ManagementVNet
MediaAgent
MediaAgent
Customer AzureVNet
Each Customer has
dedicated Cloud Library
so data segregation is
by default. Also, backup
performance is maximized as
the Cloud Library is
“local” to the data being backed up.
Microsoft Azure | SAP System Architecture – Network Details
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
20
Internet
On Premise itelli DC MY
Express Route orSite-to-Site VPN
GatewaySubnet
itelli Shared Management Hub VNET
DMZSubnet
On Premise Customer DC
VNET Peering
JumpboxSubnet
GatewaySubnet
Customer AzureVNET
DMZSubnet
Server Subnet
Shared Management Subnet
Express Route orSite-to-Site VPN
Fiori, Web Dispatcher and other Internet
accessible resources
HANA, BO and other internal
servers
Microsoft Azure | SAP System Architecture – SAP Details
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
21
Disaster Coverage DB with few changes
Microsoft Azure | SAP System Architecture – SAP Details
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
22
Disaster Coverage other DB
Microsoft Azure | SAP System Architecture – SAP Details
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
23
Disaster Coverage HANA
Microsoft Azure | Sizing Details
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
24
Storage performance Western Europe
Microsoft Azure | Regional Differences
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
25
Price difference between the regions up to 35%
Availability of products is not granted
Microsoft Azure | Deviation of Contract Term and Runtime of 3years reserved virtual Servers
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
26
NON-PRD on Pay as you Go
PRD RvS – 3 years
Pay as you Go
Project start
Term of contract
Project Management:Order of Reserved virtual Server
Service Management:Info customer for end ofReserved virtual Server
Microsoft Azure | Journey to SAP HANA and Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
27
ERP,Industry Add-ons
Non-SAP
Analytics
On-premisesMulti-Vendor
ALift and Shift to Cloud
BLift and Migrate to Cloud
CLift and Shift/Migrate to Cloud, Migrate part to HANA
DTransformation to S/4HANA and Cloud: Consolidation or (selective) Re-implementation or Greenfield
Migrate to HANA
Migration to HANA, Conversion to S/4HANA
Conversion to S/4HANA or BW/4HANA
SAP AnyDB on Azure
Non-SAP, Custom
Analytics
ERP,Industry Add-ons
Any DB
S/4HANA on Azure
Non-SAP, Custom
Industry solutions
Embedded analytics
S/4HANA
Any DBHANA
SAP HANA on Azure
Non-SAP, Custom
Analytics
ERP,Industry Add-ons
HANA
SAP SaaS HEC, SCP, SuccessFactors, Concur, C/4Hana (Hybris +)
Microsoft Azure | Microsoft SAP infrastructure 100% in Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
28
In 2014:
520 Servers
61% Physical Hardware
39% On-Prem VMs
3%
37%
60%
June 2017:
3% Physical Hardware
37% On-Prem VMs
60% Azure
Physical Servers On-Prem VMs Azure
Spring 2018:
100% Azure
Microsoft Azure | Snoozing of SAP Systems – December 2018
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
29
Microsoft Azure | Microsoft runs SAP on Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
30
110KInternal Users(Mostly Indirect
Access to SAP)6K
Named User
Accounts 96% Non-SAPGUI
users
SAP Surround
Strategy
High Quality Enterprise Service Offerings via SAP
16TBHighly
compressed
database 4M Dialog
Steps/Day 300KMonitored
Batch
Jobs/Month170M Transaction
steps/Month
99.998%RawSQL/Win
Uptime0.4 Seconds user
response time
Enable Modern
Experiences
Deliver Reliant & Agile
ERP Platform
Provide Real Time
Processes
2xSystem
growth in past
2 years≈600 Servers
(98% virtual) 250TBCompression
Storage
Savings
5-7%
yearlyIncident Ticket
Reduction2xTransaction
volume ever
18-24 months
Microsoft Azure |
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
32
Standard HDDManaged Disks
Standard SSD Managed Disks
Premium SSDManaged Disks
Azure Ultra SSD
Disk Latency
Double digit millisecond
Single digit millisecond
Uncached Read: ~4ms
Uncached Write: ~1ms
<1ms
Max Disk Size
4TB -> 32TB 4TB -> 32TB 4TB -> 32TB 4TB -> 64TB
Max Disk IOPS
500 IOPS -> 2,000 500 IOPS -> 2,0007,500 IOPS ->
20,000 160,000
Max Disk Bandwidth
60 MBps -> 500 MBps
60 MBps -> 500 MBps
250 MBps -> 750 MBps
2000 MBps
(H2 CY18)
768GB 1.5TB 1.7TB 2TB 2TB 4TB 4TB 6TB 8TB 12TB 16TB 24TB
OLTP
OLAP/ OLTP
SCALE-UP SCALE-OUT
OLAP
HANA Large InstanceHANA Virtual Machine
1TB512GB256GB
Microsoft Azure | SAP HANA on Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
33
192GB 20TB12TB6TB
ann
ou
nce
d
ann
ou
nce
d
SAP on Public Cloud | Market Lead
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
34
Gartner Magic Quadrant for Cloud Infrastructure as a ServiceWorldwide
https://www.sap.com/dmc/exp/2014-09-02-hana-hardware/enEN/iaas.html
SAP Certified Public Cloud Vendors
Public Cloud | Development in the Market
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
35
Microsoft Azure | Azure business continuity
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
36
From mission critical applications to backup
Microsoft Azure | Single-Instance SLA – 99.9%
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
37
o No Availability Set required
o Virtual machine connectivity of at least 99.9%
o Application servers that cannot be clustered or load-
balanced
o VM must use Premium (SSD-based) storage
Microsoft Azure | SAP S/4HANA on Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
38
aka.ms/saponazure-reference-architectures
Microsoft Azure | SAP NetWeaver (AnyDB, SAP HANA) on Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
39
aka.ms/saponazure-reference-architectures
Microsoft Azure | SAP Migration to Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
40
SAP Support Package
Setup (* optional)Database Server Setup
Database Backup or
SAP Export
SAP Application Setup
(ASCS)
SAP Application Setup (Global
Host Preparation)
File Copy to AzureFile Receive from
on-premises
Database Restore or
SAP Import
SAP Database Instance Setup
(with schema conversion)
SAP Application Setup
(Central Instance)
On-premises Azure
Rollout
OS/DB Upgrade/Migration possible
Microsoft Azure | Dual Redundancy with Active-Active gateways
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
42
Zero downtime during planned maintenance
From active-standby to active-active
Support both cross-premises and VNet-to-VNet connectivity
Spreading traffic over multiple tunnels simultaneously
On Premises
Site 5
ASN65050
10.51.0.0/16
10.52.0.0/16
On Premises VPN 1
On Premises VPN 2
AzureVPN vNet1
East US
ASN 65010
10.11.0.0/16
10.11.0.0/16
AzureVPN 2
Microsoft Azure | ExpressRoute
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
44
Customer’s Network
Azure Public Peering for Azure public IPs
Azure Private Peering for Virtual Networks
Microsoft Peering for Office 365 and Dynamics 365
ExpressRoute Circuit
Partner
Edge
Microsoft
Edge
Microsoft Azure | Azure’s load balancing portfolio
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
46
Application GatewayHTTP / HTTPS
Regional
Public &
Internal
Traffic ManagerDNS
GlobalPublic CNAMEs
Requests
Load BalancerAll TCP & UDP
Regional
Public &
Internal, + AZ’sFlows
Microsoft Azure | Traffic Manager
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
47
DNS request routing
• Easy Onboarding
• Multiple Routing Methods
• Endpoint monitoring
• High resiliency
• Real User Measurement & Traffic View
Routing based on profiles
• Priority
• Weighted Round Robin
• Geographic
• Performance
Diagnostics and Probes
• Traffic View visualization
Understand the volume of traffic generated by your users and the latency experienced by them, at a per region level
• TCP & HTTP health probes
Microsoft Azure | Application Gateway
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
48
Microsoft Azure | Load Balancer
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
49
Layer 4, per flow
• All TCP & UDP applications
• Inbound & outbound
• Flow-based Load Balancing with Health Probing
• Inbound NAT rules (port forwarding)
• Availability Zones support
• HA Ports load balancing
• 2 SKUs: Standard & Basic
High performance
• Part of the Azure SDN stack, not a VM
• Low latency
• High throughput
• Outbound bandwidth only limited by VM in pool
Diagnostics and Probes
• Multi-dimensional metrics and alerts in Azure Monitor
• TCP & HTTP health probes, Data path health
3 key scenarios
Attacker Azure Backbone VNet
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
51
Protecting your application
Automatic mitigation for 60+ network layer attacks
Adaptive tuning based on platform insights
and application traffic patterns
Advanced protection for your virtual networks
Any injected workload in the VNet is automatically
protected
DDOS Protection
From the
Internet
Within the
VNet
Within Azure
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
52
Protect your app against
prevalent X- Site Scripting
and SQL Injection attacks
Blocks threats based on
Top 10 OWASP signatures
Integrated with Azure
Security Center
Real-time logging with
Azure Monitor
Platform managed,
scalable and highly
available
Web Application Firewall
From the
Internet
Within the
VNet
Within Azure
Protecting your application
AppGateway
L7 LB
WAF
Microsoft Azure | Selection criteria of Azure VMs for SAP
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
58
oNot all Azure VM types are certified for SAP
oMinimum requirements for VMs:
oAt least 2 vCPUs
o Ratio between memory and vCPU at least 6GB:1vCPU
o Not all Azure VMs qualify
oOther rules for certification of VM SKUs:
o Some of the VM SKUs are exclusively certified with Premium Storage.
E.g. No SAP certification for G-series, but certification of GS-Series
o If the largest VM of a series does not provide sufficient results with Standard Storage, we do not
certify any of the VMs of the series and rather wait for VM series being available with Premium
Storage. E.g.: Dv2 series
o From the SAPS-based sizing standpoint, we are not making any difference between VMs for the
SAP application layer (no significant dependencies on storage interaction) and DBMS VMs
(sensitive to storage latency and throughput)
Microsoft Azure | Storage Planning Tips
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
59
oUse managed disks
o Premium Storage:
o Required for database and log files on production servers
o Recommended for database and log files on non-production servers
o Not required or beneficial for application servers
o No IOPS limit on per storage account level – the limit on the number of disks per storage account
o 280, 140, 35 disks for P10, P20, P30 disk sizes (respectively)
o Consider VM SKU throughput/IOPS limits
o Host cache settings:
o None for write-only and write-heavy disks
o ReadOnly for read-only and read-write disks
o Standard Storage:
o 20,000 IOPS limit on per storage account level
o Keep in mind implications of using GRS:
o Lower ingress/egress throughput per storage account
o No guaranteed cross-partition consistency
Wir machen mehr aus SAP-Lösungen!
Althardstrasse 80, CH-8105 Regensdorf / ZH Tel.: +41 44 735 85 55Fax: +41 44 735 85 50
Bogenschützenstrasse 9A, CH-3008 BernTel.: +41 31 340 32 32Fax: +41 31 340 32 30
E-Mail: [email protected] Internet: www.itelligence.ch
24.1
0.2
019
© 2
019 ite
llig
ence
-itellig
ence
World 2
019
61
Copyright itelligence AG - All rights reserved
24.1
0.2
019
© 2
019 ite
llig
ence -
itellig
ence W
orld 2
019
62
Die Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch itelligence AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der itelligence AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind. Die in diesem Dokument erwähnten Namen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von itelligence. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen Vereinbarung mit itelligence. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Produktfunktionen und ist für itelligence nicht bindend, einen bestimmten Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. itelligence übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. itelligence garantiert nicht die Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
itelligence übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks zugreifen, unterliegen nicht dem Einfluss von itelligence, und itelligence unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of itelligence AG. The information contained herein may be changed without prior notice.
Some software products marketed by itelligence AG and its distributors contain proprietary software components of other software vendors. All product and service names mentioned and associated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to itelligence. This document is a preliminary version and not subject to your license agreement or any other agreement with itelligence. This document contains only intended strategies, developments and product functionalities and is not intended to be binding upon itelligence to any particular course of business, product strategy, and/or development. itelligence assumes no responsibility for errors or omissions in this document. itelligence does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
itelligence shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. itelligence has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.