190 likes | 551 Views
High Availability and Persistence for SAP HANA with EMC and Cisco. EMC Corporation. SAPPHIRE 2012 Orlando. Agenda. HANA persistent storage. EMC VNX5300 – most suitable for HANA. HANA High Availability (HA). EMC/SAP joint collaboration for SAP HANA.
E N D
High Availability and Persistence for SAP HANA with EMC and Cisco EMC Corporation SAPPHIRE 2012 Orlando
Agenda HANA persistent storage EMC VNX5300 – mostsuitablefor HANA HANA High Availability (HA)
EMC/SAP joint collaboration for SAP HANA • EMC engagement at the HassoPlattnerInstitut (HPI) • Joint engineering and research collaboration • HPI FutureSoc Lab • EMC is a founding member • Member of the steering committee • HPI is using EMC storage technology • Nov 9th SAP announced • Preferred Three-Way Strategic Collaboration between SAP, VMware and EMC • Close collaboration around the SAP HANA™ platform for high-end system availability and scalability based on EMC's tiered storage & high availability technologies
EMC and Cisco teamed up for a joint SAP HANA solution • Cisco Unified Computing Servers for SAP Future-proof platform for SAP HANA Deployments Today • Best scale-out architecture to support future customer requirements • Single virtual chassis scales from one to over 300 blades • Single high performance networking fabric (client, storage, management) • Single open management interface across SAP infrastructure CISCO IS THE VENDOR WHO CAN DO THIS TODAY!!!
Do We Still Need Disks with SAP HANA? • What Happens to In-Memory Data in Case of Power Loss? • Do You Still do Database “Commit“ if all Your Data is In-Memory? • How Can You Move theIn-Memory Data to a StandbyNode? • Does your mission-criticalenvironment need: • Disaster Tolerance? • Infrastructure Repair/Upgrade?
HANA Persistence Layer HANA Node • Savepoints (Data Filesystem) • In-memorydatawrittentodisk in regularintervals (5 minsdefault) • Log Filesystem • Capturing all DB transactionssince last savepoint • Restore DB from last savepointonwards • High IOPS requirement • HANA Single Node • Usedserverinternaldisks (SSD, Fusion-io, SAS) • HANA scale-out (multinode) • Filesystemsreside on externalstorage In-memory DB DataFS LogFS Storage Array DataDevice LogDevice
EMC VNX Product FamilyMore Power, Less Management The most efficient and automated system ever • Next-generation architecture • Intel Xeon 5600 multi-core processors • Expanded UltraFlex I/O: Fibre Channel over Ethernet (FCoE), Fibre Channel (FC), iSCSI, CIFS, NFS, pNFS, MPFS • Five 9s (99.999%) availability for SAP applications • Data integrity, proactive global sparing, replication, EMC quality enterprise Flash • Redundant 6 Gb/s SAS back end • Optimized For Flash SSDs and high-capacity SAS drives • Designed for the enterprise • FAST Suite self-optimizing storage pools • Ideal for virtualized applications • Unified protocol support: file, block, and object
EMC #1 Storage Provider for Key Applications Source: “Storage User Demand Study, 2011 — Spring Edition: Unlocking the Minds of Storage Users,” IDC, Doc #230148, September 2011, n=998 IDC’s research confirms that EMC is #1 for… • SAP • Oracle • Exchange Server • SharePoint • BI/Analytics • VDI • Home Directory
HANA externalstorage Multi-Protocol – Multi-Purpose Cisco blade B440M2 SAP HANA System/Boot Device Non-shared, 30GB FC HANA Install FS shared, 100GB NFS Persistence Layer HANA DATA FS MPFS shared, 2TB HANA LOG FS MPFS shared, 600GB storagedevices per HANA node
Simple Network Configuration With Cisco Nexus Switches Compute blade B440M2 Network Switch Nexus Storage VNX5300 IP CEE/ FCoE FC vNIC vHBA
HANA High Availability All Worker Nodes Are Active HANA Node1Worker HANA Node2Worker HANA Node3Worker HANA Node4Standby In-memory DB In-memory DB In-memory DB Data1FS Log1FS Data2FS Log2FS Data3FS Log3FS Storage Array Data1Device Log1Device Data2Device Log2Device Data3Device Log3Device
HANA High Availability One Worker Fails – 1/3 of the Database is Temporary Unavailable HANA Node1Worker HANA Node2Worker HANA Node3Worker HANA Node4Standby In-memory DB In-memory DB In-memory DB Data1FS Log1FS Data2FS Log2FS Data3FS Log3FS Storage Array Data1Device Log1Device Data2Device Log2Device Data3Device Log3Device
HANA High Availability HANA Invokes Standby Node and Reassigns the Persistent Storage HANA Node1Worker HANA Node2Worker HANA Node3Worker HANA Node4Worker In-memory DB In-memory DB In-memory DB Data1FS Log1FS Data2FS Log2FS Data3FS Log3FS Storage Array Data1Device Log1Device Data2Device Log2Device Data3Device Log3Device
HANA High Availability Once Repaired, Failed Node Becomes a Standby Node HANA Node1Worker HANA Node2Worker HANA Node3Standby HANA Node4Worker In-memory DB In-memory DB In-memory DB Data1FS Log1FS Data2FS Log2FS Data3FS Log3FS Storage Array Data1Device Log1Device Data2Device Log2Device Data3Device Log3Device
HANA High Availability HANA Node1Worker HANA Node2Worker HANA Node3Standby HANA Node4Worker In-memory DB In-memory DB In-memory DB Data1FS Log1FS Data2FS Log2FS Data3FS Log3FS Storage Array Data1Device Log1Device Data2Device Log2Device Data3Device Log3Device
HANA High Availability HANA Node1Standby HANA Node2Worker HANA Node3Worker HANA Node4Worker In-memory DB In-memory DB In-memory DB Data2FS Log2FS Data1FS Log1FS Data3FS Log3FS Storage Array Data1Device Log1Device Data2Device Log2Device Data3Device Log3Device
Summary • EMC and Cisco deliver the optimal choice for SAP HANA • Flexibility through Multi-Protocols (unifies file and block) • Converged network technology to reduce Cabling & Complexity • Optimum Performance • Optimum TCO • Highest Reliability • SAP HANA Still Requires Disks for Persistence • External Storage Supports High Availability in what SAP calls a “Scale-Out” Installation • Allows each Node to Become a Worker or a Standby Node • Activation of a Standby Node is Triggered by the HANA Nameserver • EMC / Cicso provide a strong architectural foundation for upcoming SAP HANA features • i.e. Remote Replication for Disaster Tolerance & Backup