sap hana on power-implementation 1.8 - ibm www page · pdf filenew features will be directly...

SAPHANAonIBMPowerServers

andIBMSystemStorage

SupplementalIBMInstallationGuidetothe

SAPHANAMaster,ServerInstallationand

AdministrationGuides

IBMDeutschlandResearch&Development,GmbHCreatedon3rdFebruary2015–Version0.5

LastmodifiedonMay4th,2017–Version18©CopyrightIBMCorporation,2016

2

IBMSystemsSolutionforSAPHANAonPowerandIBMSystemStorage©CopyrightIBMCorporation,2016

EditionNoticeandVersionInformation

©CopyrightIBMCorporation2015.AllRightsReserved.USGovernmentUsersRestrictedRights–Use,duplicationordisclosurerestrictedbyGSAADPScheduleContractwithIBMCorp.Alltrademarksorregisteredtrademarksmentionedhereinarethepropertyoftheirrespectiveholders.

IBMCorporationSystemsandTechnologyGroupRoute100Somers,NY10589ProducedintheUnitedStatesofAmericaEditionNotice:Thisisversion1.8ofthisdocument.Focus:SAPHANAscale-upandinitialscale-outsolutionsTarget:SAPHANAonPowerDeploymentsin2015/2016–Draft:Pleaselookforregularupdates!

Note:

Beforeusingthisinformationandtheproductitsupports,besuretoreadthegeneralinformationunder“DisclaimerandSpecialNotices”and“CopyrightsandTrademarks”.

3


PrefaceSAPHANAonPOWERisanewsolutionallowingcustomerstorunHANA-basedanalyticsandbusinessapplicationsonanagileIBMPowerbasedinfrastructure.ExistingITassets-servers,storage,aswellasskillsandoperations-caneasilybe(re-)used,insteadofenforcingadditionalinvestmentintodedicatedSAPHANAonlyappliances.

AboutThisDocumentThisdocumentisintendedforarchitectsandspecialistsperforminganSAPHANA®onPOWER®deployment.Itdescribestheimplementationspecificsforhardware,networking,andsoftwarecomponentsoftheSAPHANAonPOWERsolutionstacktocompletetheexistingSAPownedSAPHANAdocumentationforIBMPowerspecifics.

FurthermoreitprovidesadditionalchaptersreferencingtherelatedSAPHANAdocumentationasanentrypointasthehandlingofSAPHANAitselfisidenticaltoInteldeployments.

TheinstallationguidedoesnotreplaceexistingSAPHANAliterature.

ItprovidesguidanceonhowtomeetSAPHANAoperationalrequirementsusingIBMPowerSystems™,IBMSystemStorage®,IBMPowerVM®,andLinuxOperatingSystem.

Feelfreetoprovidefeedbackandchangerequestsforthisdocumentviaemailtoisicc@de.ibm.com.

4


TableofContentsPreface...................................................................................................................................................3

AboutThisDocument.............................................................................................................................3

Figures................................................................................................................................................7

Tables.................................................................................................................................................7

Introduction...........................................................................................................................................8

HowtousethisGuide........................................................................................................................9

UsedSampleConfigurations..............................................................................................................9

SampleConfiguration1:SAPHANASingle-HostSystem(scale-up).............................................10

SampleConfiguration2:SAPHANASingle-hostSystemwithSystemReplication(DisasterRecoveryorHotStandby)............................................................................................................10

SampleConfiguration3:SAPHANASingle-hostSystemwithAutoHostFailover(ColdStandby)......................................................................................................................................................11

Prerequisites........................................................................................................................................11

VerifyInstalledHardware.....................................................................................................................13

VIOS,SANandEthernetConnectivitySetup........................................................................................13

SetupConsiderations.......................................................................................................................13

RelatedPlanningSheetsfromthePlanningGuide.......................................................................14

ZonesforEthernetandFibreChannel.........................................................................................14

VIOSconfiguration.......................................................................................................................15

Nativeattachedconnectivity.......................................................................................................16

DedicatedEthernetAdapter........................................................................................................16

EthernetTuning............................................................................................................................16

Additionalrecommendeddocumentation...................................................................................17

Toolstoconsider..........................................................................................................................17

SampleImplementation...................................................................................................................17

ServerSetup.........................................................................................................................................17






HMCbasedpartitionsetup..........................................................................................................19

PowerVCbasedpartitionsetup....................................................................................................20

5


SANStoragePreparation......................................................................................................................21



SAPHANAFeaturesRequiringspecialstoragelayouts................................................................22



SampleimplementationinternalServerDisks.................................................................................22

SampleImplementationSAN...........................................................................................................23

Verifytheprerequisites................................................................................................................23

CreatestorageLuns......................................................................................................................23

Result............................................................................................................................................25

IBMSpectrumScaleInfrastructurePreparation(SANandElasticStorageServer)..............................25


OSPreparation.....................................................................................................................................25






Ensureandverifyuniformtopology.............................................................................................26

XFSFileSystemandMultipathSetup...................................................................................................29





Whenusing“fcClient”forSAPHANAautohostfailover..............................................................30

TuningforMultipathing...............................................................................................................30

SAPHANAConfigurationCheckTool(HWCCT)....................................................................................31

Prepare.............................................................................................................................................32

Execution..........................................................................................................................................32

Validation.........................................................................................................................................32

Tools,LinksandReferences.............................................................................................................32

SAPHANAinstallation..........................................................................................................................32


6






MigrationPath.....................................................................................................................................33

Introduction/Scenario....................................................................................................................33

MigrateSAPBusinessSuiteandSAPNetWeaverBWontraditionaldatabasestoSAPHANAdatabase.......................................................................................................................................33

TraditionaldatabasetoSAPHANAdatabase...............................................................................34

SAPHANAdatabasetoSAPHANAdatabase................................................................................35

Backup..................................................................................................................................................36

Additionalrecommendeddocumentation.......................................................................................36

OperatingSystemBackup................................................................................................................37

Linuxnativemethod.....................................................................................................................37

3rdpartysoftwaremethod..........................................................................................................37

HANAFileSystemBackup................................................................................................................38

HANAdatabaseBackupandRecovery.............................................................................................38

HANASnapshots...............................................................................................................................38

Recovery...........................................................................................................................................39

HANABackintIntegration................................................................................................................39

HighAvailabilityandDisasterRecovery...............................................................................................40

SAPHANASystemReplication.........................................................................................................40

SetupConsiderations...................................................................................................................40



Auto-Host-FailoveronshareddiskusingXFS...................................................................................41

ConfigurefcClientLVM.................................................................................................................42

VerifyfcClientLVMsetup..............................................................................................................42

Security.................................................................................................................................................42

SupportProcessandServices...............................................................................................................43

RelatedDocuments..............................................................................................................................43

DisclaimerandSpecialNotices.............................................................................................................44

CopyrightsandTrademarks.................................................................................................................45

7


FiguresFigure1Implementationpathoverview................................................................................................8Figure2Sampleconfiguration:SAPHANAsinglehostsetup...............................................................10Figure3Sampleconfiguration:SAPHANAscale-upwithSAPHANASystemReplication...................10Figure4SampleConfiguration:ColdfailoversetupbasedonlocaldiskwithfcClient.........................11Figure5SampleConfiguration:ColdfailoversetupbasedonSpectrumScale(GPFS)........................11Figure6SchematicoverviewofEthernetandSANconnectivity(withoutSAPHANASystemReplication)..........................................................................................................................................15Figure7DifferenceDualVIOSSetupvscsiandthedesiredNPIVsetup...............................................16Figure8SampleInstallation–Server....................................................................................................19Figure9SampleImplementation-PowerVCbasedLPARsetup..........................................................21Figure10CrateLun(part1).................................................................................................................23Figure11CreateLUN(part2)...............................................................................................................24Figure12Example:findmultipathsettingsforanIBMStorageSubsystem(hereIBMFlashSystems)31Figure13SAPHANAmigrationmethodsforBWandBusinessSuite(exampleshowsBS)..................34Figure14SchematicNetworkoverviewforSAPHANASystemReplicationdeployments..................41Figure15FromScale-uptoSAPHANAAutohostfailover...................................................................42

TablesTable1:SAPHANAdatabasemigrationoptions..................................................................................35

8


IntroductionSAPHANAcomprisesseveralfunctionalmodules.Thesearedeployedontopofahardwareandsoftwarestack,whichshouldbeplannedaccordingtotheIBMSAPHANAPlanningGuide.

SAPHANAonPOWERmeetsthecustomerrequirementsforahighdegreeofconfigurationsandadministrationflexibility.ThehardwareassemblyisatwofoldedprocessofaSAPsizingexerciseandanIBMmappingeffortoutlinedintheIBMSAPHANAPlanningGuide.

SAPHANAsystemscanbedeployedexploitingPowerVMcapabilities.ThiscanlowertheentrybarrierforSAPHANAsignificantly,sincetestsystemscanbeeasilyinstalledonapartitionusingavailableresourcesorCapacityUpgradeonDemand(CoD)capacity–thereisnoneedtopurchasededicatedhardwareforSAPHANAonPOWER.

Fromatechnologyperspective,IBMPowerSystemsareverywellsuitedtoprovideexcellentSAPHANAdatabaseperformanceandreliability.TheportoftheSAPHANAcodetoPOWERarchitecturebenefitsfromexcellentmemorybandwidth,SIMDparallelization,andSimultaneousMulti-Threading(SMT)onPOWER.

Figure1Implementationpathoverview

9


HowtousethisGuideThisguideisasupplementaltotheSAPHANADocumentation.ThecoreSAPdocumentswhichhavetobeusedtogetherwiththisguideare:

• SAPHANAMasterGuide• SAPHANAServerInstallationGuide• SAPHANAAdministrationGuide

Theflowandstructureisalignedtothe“SAPHANAonIBMPowerSystemsandIBMSystemStoragePlanningGuide”.Italsousestheplanningsheetsasareferencetoeasierinterlinktheplanninganddeploymentprocess.ThetablescanbedownloadedfromSAPHANAonIBMPowerSystemsandIBMSystemStorage-Guides.

NewfeatureswillbedirectlyreflectedinthefollowingSAPNotesforSAPHANAonPower:SAPNote2055470-HANAonPOWERplanningandinstallationspecifics-centralnoteSAPNote2133369-SAPHANAonIBMPowerSystems:CentralReleaseNoteforSPS09andSPS10Eachchapterwillcontainfollowinginformation:

• SetupConsiderationsThischapterreferencestherelatedplanningsheetsfromtheIBMPlanningGuideforSAPHANAandwillgivesomebackgroundinformation.

• Inthesubchapters“Additionalrecommendeddocumentation”and“Toolstoconsider”blanklineshavebeeninsertedtodocumentyourfindingstoreusethisdocumentashandoverbetweenteams.

• SampleImplementationThischapteroutlinesthestepstakentoachievethesetupofasampleinstallation.

•

UsedSampleConfigurationsTheSAPHANAonPOWERarchitectureprovidestheflexibilitytooperateSAPHANAonIBMPowerServersonallstoragesolutionswhichcanfulfilltheSAPHWCCTKPIs.SAPmaintainsalistofTDIcertifiedstoragesolutionswhichcanfulfillthoseKPIsifsetupcorrectly.ThisdoesnoterasetheneedtoverifytheStorageattachmentasdescribedinthechapter“SAPHANAConfigurationCheckTool(HWCCT)“.

DuetothebroadrangeofvalidoptionthisguideiswrittenbasedonthefollowingIBMPowerServersampleconfigurations.Evenforthechosenoptionsthereisavarietyofalternativespossibleinadditiontothedescribedones.IfnotexplicitlyexcludedinSAPNote2133369-SAPHANAonIBMPowerSystems:CentralReleaseNoteforSPS09andSPS10(attachment)allalternativesthatarepossiblewiththeAppliancesolutionsareallowedconfigurations.SomepretestedconfigurationscanbefoundinSAPHANAinDataCenters.TomakenewinnovativeideasreusablebyotherspleasesendanE-Mailto:[email protected].

TheAppserverinstallationstepsarenotcovered.

10


SampleConfiguration1:SAPHANASingle-HostSystem(scale-up)Figure2showsabasicSAPHANAdeploymentwithinasinglesite(greenborder).

Inred,theSAPHANAdatabaseprocessesareprotectedbytheSAPHANAAuto-Restartfeature.Itautomaticallyrestartssingleprocessesincaseoffailures.

Theserver(blue)isbasedonPowerVM,runningadedicateddonatingpartitionforSAPHANA.AdualVIOSsetupisusedforredundancyofEthernetandSANconnectivity.DualVIOSischosentoleveragePowerfeaturessuchasLifePartitionMobility(LPM),transparentmaintenanceofunderlyingstructuresandconsolidation(additionalpartitionswithadifferentworkloadarerunningonthesameservertogainoptimalredundancywithanoptimizednumberofconnectivity–networkandFibreChannelports).

TheusedfilesystemisXFS.

SampleConfiguration2:SAPHANASingle-hostSystemwithSystemReplication(DisasterRecoveryorHotStandby)SAPHANASystemReplicationprovidesbusinessresiliencybasedonasharednothingconceptusingmultiplesites/servers(greenboxes).ThissampleusesXFSfilesystems.

TheEthernetandFibreChannelcardsaredirectattachedtothepartition(withoutVIOS).

Toautomatethefailover,clustersolutionscanbedeployed.ThisismandatorywhenusingthissetupasaHotStandbysolution.

Figure3Sampleconfiguration:SAPHANAscale-upwithSAPHANASystemReplication

System Replication

V V

Figure2Sampleconfiguration:SAPHANAsinglehostsetup

11


SampleConfiguration3:SAPHANASingle-hostSystemwithAutoHostFailover(ColdStandby)ThisdeploymentisusingSAPHANAAutoHostFailoverforacoldstandbyhighavailabilitysolution.Forsingle-hostHANAnodesthefailovernodecanbestretchedtothesameextentthestoragecanbestretched.

Thetwomostcommonoptionsare:

1) UsingSAPHANAAutoHostfailoverinaSANwithlocalfilesystemsrequiresaSAPHANAcomponentcalledStorageConnectorcomingintwoversions:fcClientandfcClientLVM.TheStorageConnectorisresponsibletomounttheSAPHANAfilesystemonthestandbynodetoresumeoperationsbasedonthelatestdataandlogcontent(Figure4).Theclientreconnectisdonebasedonaddingbothnodes’IPaddressestotheconnectivitylist.ThealternativewouldhavebeentoexploittheSAPHANAfailoverhookstomovetheserviceIPaddressorreplacingtheSAPHANAAutoHostfailoverfeaturebyaclustersolutionsuchasSAMP.ThepreferredIBMstoragetechnologyforstretchingthissetupistheSVCstretchedcluster.

2) SpectrumScale(GPFS)canbeusedtomakethedataandlogoftheSAPHANAinstanceaccessiblefrombothhosts.ConcurrentwritesareavoidedbySAPHANAsoftware.DataProtectionhastobeputinplaceusingSpectrumScalefeaturesandSAPHANAbackups.

Figure5SampleConfiguration:ColdfailoversetupbasedonSpectrumScale(GPFS)

PrerequisitesBeforestartingwiththeImplementationGuideensuretohavewellplanned,ordered,andsetuptherequiredhardwareasdescribedinthePlanningGuide.

fcClient fcClient

Auto Host failover

Figure4SampleConfiguration:ColdfailoversetupbasedonlocaldiskwithfcClient

12


AssembletherightresourcestotheHANAinstallationproject.Thisrequires:

• Astoragespecialistfor:o I/Operformanceanddisklayoutwithknowledgeofthechosenfilesystemoptiono FlashCopy,VolumeMirroring(sync/async),andStorageVirtualizationo HostattachmentofLUNs

• ASAPHANAandSAPBasisspecialistforinstallingHANA,migration,applicationserverconnectivity,backup,HANASystemReplicationandSAPHANAAutoHostfailover

o RequiredSkillcanbedeterminedbasedontheSAPHANAClass:E_HANAINS131• APowerServerspecialistfor:

o SetupHMCandIBMPowerServerso PreparepartitionsandoptionalVIOSservers

• ALinuxspecialistforLinuxonPOWERfor:o OSsetupandinstallationaccordinglytotheOSvendorandSAPrequirementso Filesystemsetupandtuning

• Optionalskillsarerequiredfor:o IBMTivoliSystemAutomationforMultiPlatformsorotherclustersolutionsto

automateHAandDRcapabilitiesofHANAo Securityo Monitoringtoolso IBMSpectrumScale1SANorElasticStorageServer(ESS)planningandtuning.o …

Theguideassumesthehardwareissetupandconfiguredtotheextentthatpartitionscanbecreatedandstoragevolumescanbeattachedtotheserverhost.

Carefullycheckifallitemsofthesolutionaresupportedwithineachother.Forinstance,SAPHANATDIcompatibilitymatrixforstorage,andstoragevendorcompatibilitymatrixagainstLinuxversions.DecideonnetworkconfigurationforeachusedVLAN:

• Hostname• IP• Netmask• Gateway• Domainname• Atleast,twoDNSservers• NTPserver

ConfirmwhetherornotthePowerSystemisusingHMCandplanaccordingly.IfusingHMC,confirmitisrunningatleastHMCV8R8forPOWER8servers.SAPsetupparameters:

• SAPHANASID• SAPHANAInstancenumber

1IBMSpectrumScaleisthenewbrandingforGPFS.VerifySAPNote2055470-HANAonPOWERPlanningandInstallationSpecifics-CentralNoteforSpectrumScaleSupportofSAPHANA

13


• PasswordforSAPHANA

VerifyInstalledHardwareThetablesreferredtoarefromthePlanningsheetswhicharecompletedaspartofthePlanningprocess.Downloadofsources:SAPHANAonIBMPowerSystemsandIBMSystemStorage-Guides.

Server

UseTable3.SAPHANAServerPlanningSheettoverifytheserverinregardstotype,virtualizationandresources.VerifytheTable3reallyreflectstheneedsofthepartitiondesignasoutlinedinTable2.SAPHANAPartitionResourcePlanningSheet,Table7.VIOSServerResourcePlanningSheet,Table8.EthernetConnectivityPlanningSheet,Table9.FibreChannelPlanningSheet.PutsharedresourcesintothecontextofVIOSifinstalled.

Storage

TheStoragebackendissharedinsidethedatacenter.EnsurethechosenStoragesystemshavereservedresourcesfortheServer’sworkload.Table4summarizesthespacerequirementperStorage.Ensuredataprotectionmethodsareinplaceandappropriatebackupdevicesareinstalledandconnected.

CablingandZoning

Ensurepathredundancyisinplaceforallpaths.VerifywiththeSAPHANAguidesifthesetupmeetstherequirementsofthechosenSAPHANAinstallationtype,Table11.5(e.g.SAPHANASystemreplication,Scale-up/out,…).PuttheInstallationtypeintothecontextofadditionallyplannedSoftware,Table13.EcoSystemSoftwareforSAPHANA(e.g.SAMPclusterManager,TSMBackups,…).VerifyiftherequirementsofTable8.EthernetConnectivityPlanningSheetandTable9.FibreChannelPlanningSheetareinplace.

VIOS,SANandEthernetConnectivitySetupThedesignimplementedmustresultinSAPspecifiedfilesystemand–incaseofscale-out–Ethernetperformancecharacteristics.Toachievetherequirements,thefollowingchapterdescribesasetoftechnologiesandsettings.TherelatedSAPdocumentationandtooltoverifytheI/Ocharacteristicsisdescribedinchapter“SAPHANAConfigurationCheckTool(HWCCT)”.

FollowingtheIBMPlanningGuidewillresultinavalidhardwareconfigurationdesign.SAPHANAonPowerdoesnotfollowtheIntelappliancemodel.SAPhasestablishedaTDIprocessforPowerallowingforthedesiredflexibilityinhardwareconfigurations.

Note:SANbasedIBMSpectrumScale(formerlyGPFS)isnotdocumentedandnotpretestedasoftoday.Thesameistrueforinternaldiskdeployments.

SetupConsiderationsEnsurethedeploymentcanalsomeetrequirementsresultingfromadditionalpartitions(Table3.8).

14


RelatedPlanningSheetsfromthePlanningGuide• Table2.SAPHANAPartitionResourcePlanningSheet• Table3SAPHANAServerPlanningSheet• Table5.MinimumSingle-HostSAPHANAI/OAdapters • Table6.MinimumMulti-HostSAPHANAI/OAdaptersperServer• Table7.VIOSServerResourcePlanningSheet• Table8.EthernetConnectivityPlanningSheet• Table9.FibreChannelPlanningSheet

ZonesforEthernetandFibreChannelThearchitectureisbuiltonthe“invisibleinvincible”principle.ThisprincipleisbasedonutilizingIBM’svirtualizationtechnologiestobeabletosurvivesingleoutagesintheinfrastructurewithoutanyinterruptiontothebusinessapplicationandtoperformzerodowntimemaintenance.ToobtainthisfromtheOSlevel:redundancy,dualVIOSandStoragevirtualizationismandatory.Somedocumentationislistedbelowinthechapter"DedicatedEthernetAdapter”.

Thepartitionsaresetupusingthedm-multipathdriverforFibreChannelattachedstorage.Ensurethezoningwillresultintheappropriateamountofpaths(seePlanningSheets).

Typicaldeploymentswillbeinahighavailabilitysetup.Inordertohaveavitalheartbeatinginfrastructurepleaserefertoyourclustervendor’sguides.

AlsoSAPintroducesrequirements.ThefirstrequirementisbasedontheoverallSAPlandscapeaspects.ThisinvolvestheSAPsharedfilesystems(HANA-shared,SAPglobalandtransport)typicallyservedbasedoncentralhighavailableNFSserversoranIBMSpectrumScale/ElasticStorageServer(GPFS)oraV7000U.Thesecondrequirementcomesfromthesecurityneeds.AndthethirdisbasedontheSAPHANAinstallationoption.ASAPHANASystemreplicationrequiresEthernetconnectivitybetweenthetwopeers,SAPHANAscale-outwithAutoHostFailoverrequiresaspecialFibreChannelzoningforshareddisksandastrongHANA-sharedfilesystemacrossthenodes.ThoseconsiderationsarewelldescribedintheSAPHANAdocumentation.

ExamplesareshowninFigure6andFigure14.

15


Figure6SchematicoverviewofEthernetandSANconnectivity(withoutSAPHANASystemReplication)

VIOSconfigurationExploitingdualVIOShasthreekeyadvantages:

• ThephysicalresourcesforEthernetandFibreChannelcanbeloweredifmorethanasingleLPARisinstalled.

• Redundancyofadaptersatalowerpricetag.• LPM(LivePartitionMobility2)androllingmaintenance.

ThedualVirtualI/OServersetupmustbedesignedtoprovidecontinuousaccesstotheSANandnetwork.HenceeachoftheVIOSmusthavephysicaldedicatedFibreChannelandEthernetcards.Theyhavetobeconfiguredfor“SEA-failover”orafuturetechnologyprovidingatminimumthesameredundancy.NPIVcapableHBAcardshavetobeusedforthestandardizedsetup.Theclientsareconfiguredusingdm-multipathdriver.

2UsingLPMforaSAPHANAdatabaseunderloadwilllikelynotsuccessfulduetothelargememoryfootprintalongwithongoingfastchanges.ButthereareusecaseswhereLPMisbeneficial.

Frontend Single Node SAP HANA Server

SAN Storage

SAP, IBM, 3rd party management and monitoring

tools

SAP application server

Dedicated[-donating] Partition for HANA

Dedicated Partition

VIOS

Dedicated Partition

VIOS

10 GB

10 GB

HBA HBA1 GB

1 GB

Business Application

FC Switch FC Switch

Admin

Business Application

ETH0 ETH1 FC0 FC1 FC2 FC3

16


Figure7DifferenceDualVIOSSetupunpreferredvscsiandthedesiredNPIVsetup

NativeattachedconnectivityTherearereasonstosetupaServerinthefullpartitionmode.Ifsopleaseensurethefollowing:

• PhysicalredundancyhastobeensuredinsenseofHBAcardsandportsforEthernetandFibreChannel.

• UseJumboframesforEthernet(MTU9000)toutilizethe10GbEthernetports• ForEthernetbondingisrecommendedtoprotectthepartitionfromsingleadapterfailures.

DedicatedEthernetAdapterIfadedicatedEthernetAdapterisusedithastobeverified,thattheminimumkernelversion3.0.101-77-ppc64forSLES11SP4and3.12.51-60.25forSLES12SP1isinstalled.

Generallyitisstronglyrecommendedtoalwaysupdatetothelatestreleasedkernelversion.Theactualrecommendedkernelversion3.0.101-88-1-ppc64forSLES11SP4and3.12.67-60.64.18.1forSLES12SP1.

EthernetTuningOlderLinuxdistributionscannotsupportlarge_sendandlarge_receiverequiredtoutilizethefull10GbportsfromasingleLPARnortheVIOSprovidedvlanbandwidthwhensendinglargeamountsofsmallpackets.Thiscanbecomeinscale-outdeploymentsabottleneckbutisuncriticalforscale-updeployments.

Therearetuningopportunitieswhichcanbeevaluateddependingontheindividualworkloadtoday.

• TCPsegmentationoffload(TSO)enabledandJumboframes(MTU9000)setinOS,VIOSandInfrastructureimprovesI/O~3timesfromanOSperspective.ThissettinghelpsVIOSandnativeattachedEthernet.

• IfyourOSdoessupportlarge_send/large_receiveandjumboframes,itisrecommendedtoenablethisfeatureinallpartitionsonthisserverandallVIOS.

• EnsurewhentheOSdoesnotsupportlarge_sendandlarge_receivethattheVIOShasthisdisabledtoo.

• Pleaseverifyifthecomponentsused(adapters,OSandVIOS)dosupportnewtechnologyatthetimethedeploymentisdone(SR-IOV,…).

PhysicalFCAdapters

PhysicalFCAdapters

Device DriverMulti-pathing

hdisk

VSCSIserverAdapter

VSCSIclient

PhysicalFCAdapters

SCSILUN

Device DriverMulti-pathing

hdisk

VSCSIserverAdapter

VSCSIclient

PhysicalFCAdapters

VIOS1 LinuxPartition VIOS2

SAN

NOTRECOMMENDEDVSCSISETUP RECOMMENDEDNPIVSETUP

PhysicalFCAdapters

PhysicalFCAdapters

VirtualFCserverAdapter

VirtualFCclient

PhysicalFCAdapters

LUN

VirtualFCserverAdapter

VirtualFCclient

PhysicalFCAdapters

VIOS1 LinuxPartition VIOS2

SAN

dm-multipath

17


Note:BeforestartingtotuneforfastEthernetensureall–OS,VIOSandswitches–cansupportthisconfiguration.Ifonedoesnotsupportthetuningthiswilladdadditionaloverheadandareductionofthroughput.ForfurtherinformationandmethodstoverifyyoursettingsconsulttheIBMTechnote:ConfiguringplatformlargesendforSAPHANAonSLESwithVIOS.ThisdocumentationcomplementsSAPNote2382421-OptimizingtheNetworkConfigurationonHANA-andOS-LevelforSPS10andhigher.

Additionalrecommendeddocumentation• IBMSystemStorageArchitectureandConfigurationGuideforSAPHANATDI

IBMSystemStorageArchitectureandConfigurationGuideforSAPHANATDI(tailoreddatacenterintegration)V2.9

• •

Toolstoconsider• UseHWCCTNetworkTestfacilityforscale-outSAPHANAinstallations:Chapter“SAPHANA

ConfigurationCheckTool(HWCCT)”.• VirtualI/OServerPerformanceAdvisor:

InordertoensurethevitalityoftheVirtualI/OServerthePerformanceadvisorcanbeused.TheVirtualI/OServerPerformanceadvisorisanapplicationthatrunswithinthecustomer'sVirtualI/OServerforauserspecifiedamountoftime(hours),whichpollsandcollectskeyperformancemetricsbeforeanalyzingresultsandprovidingahealthcheckreportandproposeschangestotheenvironmentorareastoinvestigatefurther.ThegoaloftheVirtualI/OServerPerformanceadvisorisnottoprovideanothermonitoringtool,butinsteadhaveanexpertsystemviewperformancemetricsalreadyavailabletothecustomerandmakeassessmentsandrecommendationsbasedontheexpertiseandexperienceavailablewithintheIBMsystemsperformancegroup.FormoreinformationonVirtualI/OServerPerformanceAdvisor,seeIBM PowerVM Virtualization Managing and Monitoring,SG24-7590.

• •

SampleImplementationDownloadthelatestRedbookforthechosenadaptersandVIOS.ThisimplementationdoesnotdifferfromanormaldeploymentforLinuxpartitionsonPower.

InadditionyoucanfollowthefollowingIBMTechnoteinsteadofthissampleSetup:ConfiguringplatformlargesendforSAPHANAonSLESwithVIOS.Figure6providestheschematicviewofthesampleinstallation.Ifassistanceisdesiredpleaseseechapter“SupportProcessandServices”.

ServerSetupThischapterdescribesamanualdeploymentofadedicatedpartitionforSAPHANA.

18


SetupConsiderations

RelatedPlanningSheetsfromthePlanningGuide• Table2SAPHANAPartitionResourcePlanningSheet• Table3SAPHANAServerResourcePlanningSheet

1) Productionsystemsmustrun…• onPOWER8processorbasedserversorupcomingnewmodels.• indedicatedordedicateddonatingpartitions

2) NoneProductionsystemscanrun…• • inasharedpoolacceptingperformancedegradation.• Witharelaxedcoretomemoryratio(Cost-OptimizedSAPHANAInfrastructurefor

Non-ProductionUsage)3) TherearenospecialPowerSystemsfirmwarerequirementsintroducedbySAPHANA,

howeveritisrecommendedtoupdateifaHYPERdefectexistsonthecurrentinstalledversion.

4) MemoryvirtualizationfeaturessuchasAdvancedMemorySharing(AMS),AdvancedMemoryExpansion(AME),orMemoryDeduplicationarenotsupportedonSAPHANApartitions.

5) IntheSAPHANA,versionforIBMPowerServersArchitecture–InitialShipmentStackCoDplanningispossibleforasubsetofpossiblearchitectures.TheinitialGAcoderequiresacoldoperation(restart)toenableHANAtopickupchangesinCPUormemoryresourcesandadaptingthe*.inifiles.

Additionalrecommendeddocumentation• “SAPApplicationsonPowerVM”(www.redbooks.com)• •

Toolstoconsider• PowerVC• •

19


SampleImplementation

Figure8SampleInstallation–Server

FortheI/Oconfigurationseechapter“VerifyInstalledHardware”

HMCbasedpartitionsetupIntheIBMKnowledgeCenteryoucanfindagooddocumentationhowtosetupPartitionsusingtheIBMHardwareManagementConsole(HMC)(Creatinglogicalpartitions).

PleaseverifythatthefollowingconfigurationparametersaresetaccordinglytothevaluesfromtheplanningsheetsoutofthePlanningGuide.

• VerifyiftheIBMPowerServercanholdtheHANAPartitionandprovidessufficientspacefortheoverallworkloadplannedforthatserver.(SeeTable2andTable3fromthePlanningGuide)

• InthesampleinstallationtheHMCpartitionwizardwasusedtocreatetheHANApartition.ThisstephastoberepeatedasdocumentedinTable2.1

• Ensuretochooseadedicatedordedicateddonatingpartition

MEM MEM MEM MEM MEM

PowerVM

VIOS 2dedicated

Eth

Eth

FCFC

VIOS 1dedicated

Eth

Eth

FCFC

MEM MEM

HANADedicated/-

donating

Shared CPU Pool

LPAR1

LPAR2

V V

CPU CPU CPU CPU CPU CPU CPU

20


• UsetheSAPHANACPUcountfromTable2.3as“Minimumprocessors”value

• UsetheSAPHANAMemoryvaluefromTable2.2as“MinimumMemory”value.EnsuretoNOTactivateAME.

FortheI/OconfigurationverifythenumberofminimumpathsasoutlinedinTable2.4and2.5canbemet.

PowerVCbasedpartitionsetupInapreconfiguredPowerVCloginandpressthe”Images”buttononthelefthandside.

Selectanimagetodeployandpressthe“Deploy”button.

EnterthedesiredhostnameandIPandcreatethepartition.Thenpress“Deploy”onthebottom.

21


Figure9SampleImplementation-PowerVCbasedLPARsetup

SANStoragePreparationTheSANstoragepreparationtasksdiscussedinthischaptercomprisesof:

• UnderstandtheSAPHANAI/OperformancerequirementsreflectedintheSAPDocumentationandtheSAPHWCCT(HardwareConfigurationCheckTool)Tool.

• Creatingtherequiredsetofvolumesandhostattachmentsinasuitablemanner.

TheplanninganddeploymentofadditionalSLArequirementsfordataredundancy,backupaswellasHAandDRcapabilitiesspecialtoSAPHANAandtheSAPLandscapearenotcoveredasthisisaverycustomerspecificarchitecture.

SetupConsiderationsTheStorageandattachmentselectioncriteriaare:

a) DrivenbytheloadtimeaSAPHANArequirestostartortorestartafterafailure.b) TheI/OperformancerequirementsforSAPHANAdataandlogfilesc) Inthecontextofsharedresources

TheoverallStoragevolumeplanningisanadditiveprocessstartingfromtheSAPHANAQuicksizeroutputtoaSLAorientatedsolutionincludingBackup,HA,dataProtection,….

FinallythevolumesandattachmentshavetoalsorespecttheSAPHANAinstallationtypechosenasaSAPHANASystemReplicationconfigurationhasdifferentneedsthanaSAPHANAscale-outwithDRobjectivescoveredbyStoragereplicationorthirdpartytools.

RelatedPlanningSheetsfromthePlanningGuide• Table4.StoragePlanningSheet

22


• Table5.MinimumSingle-HostSAPHANAI/Oadaptersforproduction(floorconfiguration)• Table6.MinimumMulti-HostSAPHANAI/OAdaptersperServer(floorconfiguration)• Table9.FibreChannelPlanningSheet• Table10.SAPHANAFileSystem

SAPHANAFeaturesRequiringspecialstoragelayoutsSAPHANAbuilt-inHAandDRcapabilitiesrequiretoconnectdisksaccordinglytochosenHAfunctionality(findmoreinchapter“Backup”and“HighAvailabilityandDisasterRecovery”).

Additionalrecommendeddocumentation• SAPHANA–StorageRequirements • IBMSystemStorageArchitectureandConfigurationGuideforSAPHANATDI • •

Toolstoconsider• SAPmagic-StorageSizingToolforSAPlandscapes(IBMonly) • SAP Note 1943937 - Hardware Configuration Check Tool - Central Note • •

SampleimplementationinternalServerDisksOntheHMCdrivesattachedthroughVIOS:

23


ToviewthedriveslogintoLinux:

lsblk–f

liststhedisks.

SampleImplementationSANTheprerequisiteforthissampleisastoragesetupreadytocreatethelunsandhostattachments.

Verifytheprerequisites• UseTable9.FibreChannelPlanningSheettoidentifythezonesandensurethatthecabling

andzoningissufficienttoresultinsufficientpathsintheoperatingsystemasdocumentedinTable2.5.MatchtheresultwithTable4.8.

• IfTable10indicatestheuseofSpectrumScale(GPFS)ensuretousetheESSbaseddeplayment.

• UseTable4toverifytheSelectedStorageSubsystems.• EnsuretheconfigurationisnotbelowtheminimumrequirementsasoutlinedinTable5and

Table6)• ThelistofHostrequiredattachmentscanbefoundinTable2.6

CreatestorageLunsStep1:

VerifybasedonTable4.7ifthestoragesubsystemshavesufficientspacebeforestarting.AlsoincludeadditionalworkloadconsiderationsasdocumentedinTable3.8.ThiscanbedoneinSVCSystemsbylookingatthebottomofthescreen:

Youcandrilldowndeepertoverifyfortheovercommitmentlevelwhenusingthinprovisioning.

Step2:

1

2

3Figure10CrateLun(part1)

24


TheSAPHANAvolumefordatahastobeasplannedinTable10.2.AsSLAwewanttokeep3copieswithoutanyadditionaldataprotectionmechanisms.InthemultipathsetupintheOSwehave4activepaths(Table2.5).Tohaveaperformantsetup4LUNswith128GBeacharecreatedandattachedtothehost.

Openthe“Volume”view(1),press“CreateVolume”(2),“SelectaPresent”(weused“Generic”asasample)andfinally(3)selectthepoolanddoubleclick.

ThiswillbringyoutothenextscreenFigure11.SpecifytheLUNsasshownandpress“CreateandMaptoHost”.RepeatthisforallrequiredLUNs

Figure11CreateLUN(part2)

25


Result• ThesampleinstallationwillcombinetheSAPexecutablesandtherootfilesystemonasingle

disk.• SAPHANADataandLogfilesystemareseparatedstrictlyfromeachother• TheHANAsharedfilesystemwillbeservedfromacentral,highavailableNFSServerlater.• NoBackupstrategiesareimplementedinthissample.

IBMSpectrumScaleInfrastructurePreparation(SANandElasticStorageServer)Note:UnderInvestigation.

SetupConsiderations• Usingaclustersolution:alternativeheartbeatingcanbeperformedbasedonthegiven

connectivityanddisk.Ithastobeensuredthatdifferentprotocolsareused.TypicallythisisthreefoldusingFibreChannel(sfwcom),Ethernetanddisk.

• AsolutionfortheBootdiskhastobeputintoplace.• SpectrumScale(GPFS)isverysensitiveinregardstotuningfromthediskuptotheoperating

system.Ensuretherightsetupandregularmonitoringifthesystemstillmeetstheperformanceexpectation.

• EnsurethetheSpectrumScaleversionsupportsdualVIOSandLifePartitionMobility(LPM).

OSPreparationTheSAPNote1944799-SAPHANAGuidelinesforSLESOperatingSystemInstallationprovidestheofficialSUSEImplementationandtuningguideforSAPHANA.

SetupConsiderationsItisstronglyrecommendedtoenablethelandscapeforJumboframesandlarge_send/receiveforproductionsystems,iftheoperatingsystemsupportsthem.

NowisalsothebesttimetoensurethattheLPARhasavalidnumalayout(uniformtopology)togetoutbestperformancefromtheSAPHANAdatabase.

26


RelatedPlanningSheetsfromthePlanningGuide• Table11.SAPSoftwarePlanningSheet

Additionalrecommendeddocumentation• SAPNote1944799-SAPHANAGuidelinesforSLESOperatingSystemInstallation• ConfiguringtraditionallargesendforSAPHANAonSLESwithVIOS•

Toolstoconsider• PowerVC• •

SampleImplementationInoursampleimplementationPowerVCinstantlycreatedtheOSalongwiththecreationoftheLPARbasedonasnapshot.(Seechapter“PowerVCbasedpartitionsetup”)

Forthetunednetworkandkernelsetupsee:Technote-VIOSSetup_SLES11_2.docx

EnsureandverifyuniformtopologyLogintotheLPARandensurethecommandnumactl--hardwarehasasymmetricoutput.InspecialensureeveryNUMANodewithacoreholdmemoryaswell.

ThefollowingLPARhasabadnumalayout.NUMAnode0hascoresbutnomemorywhatcancausecrashesoftheSAPHANADatabase.NUMAnode6holdsallthememorybutnocoreswhatdegradestheperformanceofSAPHANA.

Analyzingandfixingmemoryplacementwiththedynamicplatformoptimizer(DPO): Inthenewerversionsofthefirmware,thehypervisorteamprovidedmethodstoanalyzeandfixmemoryplacementissuesonthesshshelloftheHMC.ThisworkstransparentfortheapplicationsandcanbeexecutedwhileeveryLPARisupandrunningaslongasthereissomememoryfreeonthemachineandifthisfeatureisenabled.Tolisttheservers:

lsh30021:~ # numactl --hardware

available: 2 nodes (0,6) node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 node 0 size: 0 MB node 0 free: 0 MB node 6 cpus: node 6 size: 32768 MB node 6 free: 31649 MB node distances: node 0 6 0: 10 40 6: 40 10

27


Toanalyzethecurrentsituationyoucanrunthecommandlsmemopt:

Thetooldoesnotshowtheexactplacementofmemoryandcores.Insteaditdoesarating,where100isthebestand0istheworst.AsyouseeitratedmyLPAR<nameofoptimalLPAR>witha100,whichmeanstheplacementcannotbeimprovedaccordingtotherulesofthehypervisor.TheexampleshowsthatLPAR<nameofimprovableLPAR>hasnottheperfectrating.Runningthecommandabovewiththeoption-ocalcscorewouldtelltowhatdegreeDPOcanoptimizetheLPARbasedonthecurrentsituation.TouseDPOtooptimizetheLPARSusethecommandoptmem:

AllotherLPAR'swerecandidatestobechangedaswell,inordertoachievebestplacementforthementionedLPAR's.IfaLPARshouldnotbetouched,itcanbespecifiedwithanotheroption(seemanpagesforoptmem).Sincethecommandisrunninginthebackgroundyoucanchecktheoptimizationstatuswith:

Analyzingandfixingmemoryplacementmanually:IncasetheDPOdoesnotoptimizethememoryplacementtotherequiredextend,orthefeatureisnotenabled,therearealsosomeoptionstofixtheissuesmanually.WhenthehypervisorcreatesanLPARitassignstheCores(orEntitlement)andMemoryDimmstotheLPARandthisassignmentisfixed,evenwhentheLPARislaterrestarted.Sotheideabehindthesolutionistoremovethefixedassignmentofresourcesandthenhope,thehypervisorischoosingabetterplacement,whentheLPARisactivatedlateragain.Thisobviouslywillworkonly,ifyouchangedtheprofileoftheLPARtofitbettertotheavailableresources,orifotherLPARsoccupyingneededresourcehavebeenchanged.TogetthememoryassignmentofLPAR'srunthecommandlshwres:

lssyscfg -r sys -F name

hscroot@<ip-hmc>:~> lsmemopt -m <Power Server Name> -r lpar -o currscore

lpar_name=<name of LPAR>,lpar_id=1,curr_lpar_score=100 lpar_name=<name of LPAR>,lpar_id=2,curr_lpar_score=100 lpar_name=<name of LPAR>,lpar_id=3,curr_lpar_score=none lpar_name<name of LPAR>,lpar_id=4,curr_lpar_score=100 lpar_name=<name of LPAR>,lpar_id=5,curr_lpar_score=none lpar_name=<name of optimal LPAR>,lpar_id=6,curr_lpar_score=100 lpar_name=<name of improvable LPAR>,lpar_id=8,curr_lpar_score=74 lpar_name=<name of LPAR>,lpar_id=12,curr_lpar_score=32 lpar_name=<name of LPAR>,lpar_id=31,curr_lpar_score=none

optmem -m <Power Server Name> -o start -t affinity -p <name(s) of improvable LPAR(s)>

lsmemopt -m <Power Server Name>

28


ToremovethefixedmemoryassignmentthecommandchhwrescanbeusedontheHMC:

SotheabovecommandwouldremovethememoryassignmentofLPAR<LPARnametobefixed>(ID=4).Theoption-qisthequantitytoremoveandthisisthecurr_memfromthepreviouslist.Thestrategytofixthememoryplacementisthenbasicallythefollowing:

1) ShutdowneveryLPARwhichneedstobechanged2) Getthecorrectmemorysettingswiththecommandlshwres(seeabove)3) Removethememoryassignmentwithchhwres4) StarttheLPAR'sinthecorrectpriorityorderandhopethehypervisorisdoingnowabetter

placement5) Checkthenewplacementagainwiththeresourcedump.

ReviewlocalityofLPARswhenusingmultipledrawersThefollowingcommandshowsinwhichdraweranLPARislocatedandinspecialifanLPARspansdrawerswithinoneserver.

1) CommandlineloginontheHMCconsole2) Issueastartdump:

startdump -m <machine name> -t resource -r 'hvlpconfigdata -affinity -domain'

3) Identify taken dump: ls –ltr /dump

4) View dump cat /dump/RSCDUMP.<my dump ID> | more

this displays a set of data. Verify if in the following table none of the LPAR IDs belonging to an HANA LPAR is spanning the drawers. If they span optmem command introduced above assists to optimize the layout.

hscroot@is37ssp:~> lshwres -m <Power Server Name> -r mem --level lpar -F lpar_name,lpar_id,curr_mem

<LPAR name>,12,131072 <LPAR name>,31,0 <LPAR name>,6,131072 <LPAR name>,5,0 <LPAR name to be fixed>,4,716800 <LPAR name>,3,0 <LPAR name>,2,4096 <LPAR name>,1,4096 <LPAR name>,8,1032704

chhwres -m <Power Server Name> -r mem -o r --id 4 -q 716800

29


XFSFileSystemandMultipathSetupTheSAPNote1944799-SAPHANAGuidelinesforSLESOperatingSystemInstallationprovidestheofficialSUSEImplementationandtuningguideforSAPHANA.

SetupConsiderationsThefollowingsubchaptersmightbringupadditionalrequirementstoreviewdependingonthechosenarchitecture3:

• UsingLinuxthepvidisnotguaranteedtobeunique.WhencreatingthevolumesalwaysusetheWWN/UUID.ThisismandatoryforAuto-Host-Failoverandclustersetups.

• Neverpartitionphysicalvolumes,inordertobeabletoimplementAuto-Host-Failoverandclustersetupsnoworlater.PartitioningwillalsoimpacttheperformanceofXFS.

• ForAuto-Hostfailoverdonotaddthefilesystemsinto/etc/fstabtoavoidconcurrentmounts.ThemountingisdonebyfcClientLVM(SAP)ortheclustermanager.

• ApplySAPNote2014225-Unforeseentoolusageleadstodatacorruptionundercertaincircumtancesifapplicable.

AshareddiskdeploymentismandatoryfForXFSbasedinstallations.ThisisthemostcommondeploymentoptionforSAPHANAscale-outimplementations.Thissetuprequiresadditional

3Theremightbeadditionalconsiderationsthanlistedhere.

Draw

erNo

LPAR

ID

30


preparationtaskscomparedtosharedfilesystems.Thefollowingisalistofimportanttopicsforplanningsuchasetup:

• AllworkernodesneeddedicatedXFSfilesystemsfordataandlog,whiletheunderlyingLUNsfordataandloghavetobesetupasshareddisksontheSAN,attachedtoallworkerandstandbynodes.

• fcClientLVMistheSAPHANAbuildintoolfordiskhandlingandauto-mountingthefilesystemsonthefailovernode.Aglobal.inifileasdocumentedbySAPmustbepreparedbeforetheinstallation.

• fcClientLVMonlyworkswithNPIV,vSCSIattachmentsarenotsupported.EnsuretosetuptheI/Ovirtualizationappropriately.

RelatedPlanningSheetsfromthePlanningGuide• Table10.SAPHANAFileSystem• •

Additionalrecommendeddocumentation• SUSELinuxEnterpriseServer11StorageAdministrationGuide• SUSELinuxEnterpriseServer12StorageAdministrationGuide• IBMKnowledgeCenter• •

Toolstoconsider• SAPHWCCTFilesystemTest• •

Whenusing“fcClient”forSAPHANAautohostfailoverThetoolfcClientLVMcomestogetherwithSAPHANAtohandletheunmountandmountoftheSAPHANAdataandlogfilesystemsifaHANAworkerchangesitsnodeduetoafailure.Thisscenarioisalsovalidforascale-upsolutionhavingonemasterandonestandby.

TomakethishandlingrobustcertainprerequisiteshavetobefulfilledforHANAdataandlogvolumes.CarefullyreadtheSAPHANAdocumentationforthesesetups.

TuningforMultipathingDependingonthechosenstoragesubsystemtheconfiguredpolicyandfeaturestheservicetimeand/orI/Oprotectioncanbepositivelyornegativelyaffected.

TooptimizeperformanceandprotecttheI/Osfromapathlosspleaseapplyfollowingsettingswhicharepartiallydifferentfromthosedocumentedinthe“IBMSystemStorageArchitectureandConfigurationGuideforSAPHANATDI”documentation:

31


Step1:

ReadintheIBMKnowledgeCentertherecommendedmultipathsettingsforthechosenstoragesubsystem:

IBM Knowledge Center

Step2:

CrosschecktheIBMRedbooksifthereisanewertunable-setforhostattachments.

Figure12Example:findmultipathsettingsforanIBMStorageSubsystem(hereIBMFlashSystems)

Step3:

FollowtheOSImplementationandtuningguideattachedtoSAPNote1944799-SAPHANAGuidelinesforSLESOperatingSystemInstallation.

TooptimizetheimplementationonLinuxthefollowingconsiderationsshouldbetakenintoaccountforthedataandlogfilesystems:

• DonotusethecfqasI/Oscheduler(somedistributionshavecfqsetasdefault.Pleasechangeaccordingly).

• Itisrecommendedtoincreasethedevicequeue_depthtoatleast64.

FollowingSUSEdocumentsprovideadditionaloptionstotuneafilesystem’sI/O:

Opensuse11SP4:I/OScheduler--/sys/block/<device>/queue/scheduler

SUSELinuxEnterpriseServer12:SwitchingI/OScheduling

(preferablydoNOTusecompletelyfairqueuing“cfq”).

SAPHANAConfigurationCheckTool(HWCCT)BeforestartinganinstallationofSAPHANA,theHWCCTtool,whichispartoftheSAPHANAinstallationimages,hastobeconfiguredandruntoverifythesetup.Forscale-updeploymentspleaserunthe“FileSystem”andthe“Landscape”test.Forscale-outruntheTDINetworkTestinadditionbetweentheHANAnodes.Onlythesocalled“LandscapeTest”inHWCCThasaPowerspecificoutput.Hence,thischapterwillfocusonlyonthelandscaperelatedfunctionalmodule.Allremainingfunctionalityisgenericand

32


describedinthefollowingSAPdocument:1943937-HardwareConfigurationCheckTool-CentralNote.

Prepare• FollowtheSAPNote1943937-HardwareConfigurationCheckTool-CentralNotetoinstall

thetool.Ensuretodownloadtheppc64build.• Forsinglenodesetupsthetoolcanbeplacedintoanydirectory.Forscale-outpleasefollow

theinstructionsgivenbySAP.

Execution

ValidationThefilesystemandtheNetworktestaretobevalidatedasdocumentedforIntel.AsPowerisadifferentarchitecturefromtheserverperspectiveaswellasfromtheHANAperspectiveasitgivesalargersetofchoicestheLandscapetestgivesamorecomprehensiveoutputtoreflectthedifferentoptions.Inotherwords,anoutputcontainingwarningswillbethetypicalcase.Pleasereadtoverifyandtaketherecommendedactions.

Tools,LinksandReferencesSAPNote1943937-HardwareConfigurationCheckTool-CentralNote

SAPHANAinstallation

SetupConsiderations• ForHANAinstallationsalwaysusehdblcmwhichispartoftheSWPM(SoftwareProvisioning

manager)assomefunctionalityisnotincludedinhdbinst.

RelatedPlanningSheetsfromthePlanningGuide• Table12.SAPHANAInstallationPlanningSheet

Additionalrecommendeddocumentation• E_HANAINS131: Hana certification• TutorialVideoInstallingSAPHANAserver-Concepts:SAPHANA2:thetransformer(Thislink

willprovideadditionaleducationmaterial)• SAPHANAServerInstallationandUpdateGuide• •

Toolstoconsider• SAPSWPM(SoftwareProvisioningmanager)• X•

# source envprofile.sh # ./hwval -Vf <my-landscape>.json

33


SampleImplementationSeeSAPDocumentation.

MigrationPathNote:thischapterisonlyasummaryandnoguidetoperformadatabasemigration.Itoutlinesimportantthoughtstotakebasedonquestionsaskedbyothercustomers.Additionalinformationcanbeaddedwritingane-mailtotheIBMSAPInternationalCompetenceCenter(ISICC)infoservice:[email protected].

Introduction/ScenarioMigratingdatatoaSAPHANAonPOWERsetuptheSAPbusinessapplication,thesourcedatabaseandthearchitecturehastobetakenintoaccount.ThefollowingthreesubchapterswilldescribetherequiredstepstobetakenintoaccountinadditiontotheSAPHANAofficialproductdocumentation.

SAPApplicationLayer:MigratinganexistingSAPsystemtotheSAPHANAdatabaseithastobeensuredtoupgradetheSAPreleasepriortomigration,ifthesourcesystemisnotonaversionofSAPwhichsupportsHANADB.Pleasereadthefollowingdocumentsasastartingpoint:

• SAPBusinessSuiteonHANA:BusinessSuiteandS/4HANARoadmapandReleaseInformation • SAPNetWeaverBWPoweredbyHANA:Upgrade/Migration-General

TheplanningGuidewilloutlineacompletesetofdocumentation.DatabaseLayer:Migratinganexistingstand-aloneandtraditionaldatabasetotheSAPHANAdatabase,additionalconsiderationshavetobetakenintoaccount.PleasecontactyourDatabasevendorandSAPforfurtherinformation.

Architectural Layer: MigratinganexistingSAPHANAdatabaseisendiansensitive.Thissubchapterwillprovideadecisiontable.

MigrateSAPBusinessSuiteandSAPNetWeaverBWontraditionaldatabasestoSAPHANAdatabaseTherearetwomethodstomigrateanexistingSAPsystemtorunonSAPHANAshowninFigure13.Theoneistheclassicalmethod(thatis,theheterogeneoussystemcopyusingtheclassicalmigrationtoolssoftwareprovisioningmanager1.0andR3load)andtheotheroneistheDatabaseMigrationOption(DMO)oftheSoftwareUpdateManager(SUM)method.

Botharevalidandprovedoptions.

34


Figure13SAPHANAmigrationmethodsforBWandBusinessSuite(exampleshowsBS)

ClassicalmigrationmethodTheclassicalmigrationofaSAPsystemisdocumentedforexampleat“BestPracticeGuide-ClassicalMigrationofSAPNetWeaverASABAPtoSAPHANA:BestPracticeGuide-ClassicalMigrationofSAPNetWeaverASABAPtoSAPHANA”.Mainlyitisathreestepapproachcomprisingof:

Step1: UpgradetothelevelofHANAsupport(ApplicationVersion,SupportPackageandKernellevel)accordinglytotheSAPHANAdocumentationorconsulting.

Step2:ExecuteUnicodeConversionifthesourcedatabaseisconfiguredasNon-Unicode.

Step3:ExecuteDB/OSMigrationwithSAP'sstandardtool(softwareprovisioningmanager1.0andR3load)bycertifiedOS/DBMigrationconsultant.

DatabaseMigrationOptions(DMO)methodintheSAPSoftwareUpgradeManager(SUM)PleasefollowtheSAPDocumentation.GoodSAPdocumentationresourcescanbefoundthrough:

• Up-to-dateinformation:DatabaseMigrationOption(DMO)ofSUM–Introduction • SAPNote1875197-UsingDMOofSUMforSAPBusinessSuitesystems(Suite-on-HANA,

includingERP,CRMetc.) • SAPNote1799545-UsingDMOofSUMforSAPBWsystems. • SAPFirstGuidance-migrateBWonHANAwiththedatabasemigrationoption(DMO)

TraditionaldatabasetoSAPHANAdatabaseThissectionwillrefertotheoverviewofthemigrationmethodfromthestand-aloneandtraditionaldatabaselikeOracle,MSSQLandDB2toaSAPHANAdatabase.DatabasespecificsrelatedtothecompatibilitybetweentheexistingdatabaseandSAPHANAhastobetakenintoaccount.Thesecompriseof:

35


• SupportedPlatform• SupportedLanguagesandCodePages• SupportedFunction

Also,pleaseseeindetailat:SAPHANASQLandSystemViewsReference

TraditionalMigrationmethod:Export/ImportFromahighleveltheprocessconsistsofthreesteps:

Step1:Exportthedatabasecontents.

Step2:PerformLanguageandCodePagesconversion(e.g.fromASCIItoUnicode)ifrequired

Step3:ImportdatabasecontentstoSAPHANA

PleaseseetheSAPDocument:SAPHANASQLandSystemViewsReference->SQLReference->SQLStatements->IMPORT,IMPORTFROMsection.

ETL(Extract,Transform,andLoad)toolmethodTherearesomeETLproductssupportingthemigrationfromatraditionaldatabasetoSAPHANA.Examplesare:SAPSLT(SAPLandscapeTransformationserver),SAPBODS(BusinessObjectDataServices),SDIandSybaseReplicationServer.

SAPHANAdatabasetoSAPHANAdatabaseCurrently,SAPHANAissupportedbytwodifferentplatformarchitectures.TheseareIntelarchitectureandPOWERarchitecture.

ThecurrentimplementationonIntelisusinglittleendianandonLinuxonPOWERlittle/bigendianmode.

TherearethreemajormethodstomigratethedatabasecontentfromoneSAPHANAdatabasetoanother:

• SAPHANAExport/ImportmethodusingSAPstandardtoollikeassapinst• SAPHANABackup/RestoremethodusingHANAStudio• SAPHANAsystemreplicationmethod(Thereareoptionstohaveazerodowntime

migration.)

AndthesemigrationtechniquescouldbeusedproperlyaccordingtothesituationlikeasfollowsaccordinglytotheexistingSAPHANAdocumentation:

Table1SAPHANAdatabasemigrationoptions

From/To Endian MethodInteltoPowerHANA2 LittletoLittle Asallbinarycompatible

solutions.PowerHANA1toPowerHANA2

BigtoLittle SAP Note 2380257

36


InteltoPowerHANA1 LittletoBig SAPheterogeneoussystemcopyorSUMwithDMO

PowerHANA1toPowerHANA1

BigtoBig Backup/RestoreSystemReplication

XFSonPowertoSpectrumScaleonPower

BigtoBig Backup/RestoreCopy

ScaleuponPowerHANA1toScaleoutonPowerHANA1

BigtoBig Backup/RestoreCopySAP’stool

ReadtheSAPServerInstallationandMasterGuidesforBWonInstallation,Implementation,MasterGuidesforinitialinformationandfurtherguidance.

BackupThissectiongivesashortoverviewaboutthebasicsofbackupandrecoveryforSAPHANAsystems.ThetoolstotakeabackuprangefrommanualtriggeredmechanismssuchasHANAstudiobackupwizardandSQLcommandstoscheduledoperationsfromDBSCockpit,con,HANAXS(xscron)or3rdpartytools.Note:thischapterisonlyasummaryandnoguidetosetupthebackupinfrastructure.Itoutlinesimportantthoughtstotakebasedonquestionsaskedbyothercustomers.Additionalinformationcanbeaddedwritingane-mailtotheIBMSAPInternationalCompetenceCenter(ISICC)infoservice:[email protected].

Additionalrecommendeddocumentation• BackupandRecovery–ConceptsTraining:SAPHANA2:thetransformer• •

DataBackup Filesystem Backint StorageSnapshotAdvantage Datacorruptionprotection

(checksum)IntegratedintoStudioBackupsimmediatelyavailableforrecoveryToolingincludedinSAPsoftware

ConsistencycheckonBlocklevelIntegratedintoStudioDatacenterintegrationFeatures:encryption,de-dupe,…BackupsimmediatelyavailableforrecoveryVendorsoftenprovideLandscapebackupoptionsincludingflatfiles

FastestBackuptoresumefromStoragelevelànonetworktrafficPartiallyintegrated

Disadvantage NoflatfilesincludedMonitoringoffilesystemfilllevelNodirectrecoveryNetworkload

Networkload NoflatfilesincludedNoOSlevelconsistencycheckNodirectrecovery

Volumerequirement

Payloadonly Payloadonly Fullvolumesize(compressionpossible)

Duration I/Oandnetworkbound I/Oandnetworkbound Instant(background)

37


Contrarytothemanuallytriggereddatabackupthelogbackupisdoneautomaticallyafterthedatabackup.TherelatedSAPtunablewiththedefaultvaluesare:

• log_mode=normal• enable_auto_log_backup=true• log_backup_timeout_s=900• log_mode=overwrite

OperatingSystemBackupTheLinuxOSmustbebackedupinadditiontotheSAPHANAdatabasebackup.ThisisalessfrequenttaskastheLinuxOSisnotchangedmuch.Forexample,updatingLinuxkernel,applyingsecuritypatches.

ThismethodcanbeusedtobackupallflatfilesrelatedtoSAPHANA(executables,HANAClient,etc.),thataren’tcoveredwithSAPHANAdatabasebackupfunction(fullsystembackup).Acurrentfullsystembackupwillensuretohaveabaselinetorecoveracrashed/destroyedfasterthanamanualinstall.Databasebackupsand/orSAPHANASystemReplicationwillcompletethebackupstrategy.Note:EnsurethechosenmethodcanhandlefilesonIBMSpectrumScale(GPFS)ifused.Inthefollowingtwooptionsareexplained.Othertoolsandmethodscanbeused.

LinuxnativemethodBootthesystemintotherescuemode.Executedump/restoreortarcommand(they'rethestandardLinuxnativecommands).Thebackupfilescanbewrittentointernaldisks,tape,orsharedfilesystems(NFS).Werecommendsavingfilestoanexternalsystemorenvironment.FormoredetailsseetheLinuxvendorspecificdocumentationandSAPnotesifapplicable.

Inaddition,migratingthefilesystemforSAPHANAdatabasefromXFStoclusteredfilesystem,orviceversa,youcanmigratefilesusingtarcommand.WhenusingtheLinuxnativemethod,SAPHANAdatabaseandrelatedprocesseshavetobestopped.

TheLinuxnativemethoddoesn’tcostextra,butisslightlymorecomplicatedthan3rdpartysoftware.

3rdpartysoftwaremethodYoucanbackupyourHANAOperatingSystemby3rdpartysoftware.Asoneexample,"StorixBackupAdministrator"supportsBare-metalbackupsolutionforPowerLinuxsystems."StorixBackupAdministrator"workswithTivoliStorageManagerforflexible,central-managedbackup/restore.MoredetailedinformationisdocumentedattheSolutionBrieffromIBM:StorixBackupAdministratoronIBMPowerLinuxservers

Therearemoretoolsavailablenotlistedhereprovidingsamefunctionalityandcomfort.Forexample,usingPowerVCcapturedsystemscanberedeployedinminutes.

38


HANAFileSystemBackupWithSAPHANAthreedifferentbackupoptionsareprovided:

• OnlineBackup:SAPHANAprovidesdatabasebackupandrestorefunctionnativelyintheSAPHANAAdministrationtoolbasedonfilesystemcopies.Thesecopieshavetobebackedupbythestandardbackuptoolstoaremotedestinationregularly.

OfflineBackup:Offlinebackupscanbeperformedalongafullsystembackupasdescribedinthesection“

Contrarytothemanuallytriggereddatabackupthelogbackupisdoneautomaticallyafterthedatabackup.TherelatedSAPtunablewiththedefaultvaluesare:

• log_mode=normal• enable_auto_log_backup=true• log_backup_timeout_s=900• log_mode=overwrite• OperatingSystemBackup”.• IfyouuseIBMSpectrumScale(GPFS)forSAPHANAdatafiles,logs,Kernel,etc.,youcando

filelevelbackupusingSpectrumScalefunction(mmbackupcommand)withTivoliStorageManager.Inaddition,mmbackupconfigcommandwillbeusefulforbackuptheSpectrumScaleconfiguration.Formoredetailedinformation,refertotheIBMSpectrumScaleAdministrationguide:GeneralParallelFileSystem

HANAdatabaseBackupandRecoveryYoucangettheSAPHANAdatabasebackupthroughtheSAPHANAStudioorSQLinterface.AndDBAcockpitwhichisSAPNetWeaverABAPstackfunctionisalsoavailableincaseofSuiteonHANAorBWonHANAscenario.Thebackupfilesaresavedtoadefinedstagingareathatmightbeontheinternaldisks,anexternalNFSshareddisk,oradirectlyattachedSANstorage.Inadditiontothedatabackupfiles,theSAPHANAconfigurationfiles(.inifiles)havetobesaved.Forpointintimerecovery,thelogareaalsohastobebackedup.MoredetailedinformationaboutthebackupandrecoveryprocessesfortheSAPHANAdatabaseisprovidedintheSAPHANABackupandRecoveryGuide,availableonlineatthefollowingsite:SAPHANAPlatform(Core)2.0

HANASnapshotsSAPHANAsupportsthecreationofstoragesnapshots.Storagesnapshotsarecreatedinthestoragesystemanddonotconsumedatabaseresources.Furthermoretheyruninthebackgroundwhichallowsthedatabasetoquicklyresumewritingitspersistency.Sosnapshotscanbecreatedwithminimalimpactonthesystem.Step1:PreparethedatabaseforthestoragesnapshotusingSAPHANAStudioorSQLcommand.Itpersistsallfinalizedcontenttothediskandfreezesthedisktocreateacopy.Step2:CreateasnapshotoftheSAPHANAdataarea.

39


• FlashCopyonIBMStorageSystemsTheadvantageisthetimethedatavolumehastobefreezed.TheFlashCopycanberuninbackground.Bythatthedataareacanbeinstantlyreleased(Step3)tocontinuewritingwhichwillreducetheexposurefromdataloss.ThedisadvantageisthatmaintainingandenumeratingthesnapsiswithinthecustomerresponsibilityunlessatoolservingtheSAP“Backint”APIisused(see“HANABackintIntegration”).MoredetailedinformationaboutFlashCopyisprovidedinthestorageuser'sguide.AdocumentedSolutioncanbefoundonIBMFlashCopybackupsolutionforSAPHANATDIV1.6(Intel&IBMPower)

• SpectrumScalesnapshotIfyouuseIBMSpectrumScale,youcangetstoragesnapshot.Formoredetailedinformation,refertotheIBMSpectrumScaleAdministrationguide.

• OthersnapshottechnologyStep3:Toresumethewriteoperationstothedataareachoose"confirm"or"abandon".IncaseofaSAPHANAfilesystembackupthestoragesnapshotsarelistedinthebackupcatalogofSAPHANA.YoucaneitherdisplaythebackupcataloginSAPHANAstudio,orSQLcommand(systemviewM_BACKUP_CATALOG).IBMprovidesfollowingsolutiontooptimizethisprocess:“IBMFlashCopybackupsolutionforSAPHANATDI“.

RecoveryASAPHANAdatabasecanberecoveredusinganativeHANAfilesystembackup,storagesnapshotsorfullsystembackups.SAPHANAdatabaseprovidethefollowingthreekindsofrecoveryscenarios(asofSPS9functionalscope).

• Recoveruptothelateststate• Point-in-Timerecovery• Recoverytoaspecificdatabackup• <moreoptionwillbeprovidedovertime>

MoredetailedinformationaboutthebackupandrecoveryprocessesfortheSAPHANAdatabaseisprovidedintheSAPHANABackupandRecoveryGuide,availableonlineatthefollowingsite:SAPHANAPlatform(Core)2.0

HANABackintIntegrationSAPHANAprovidesthe“Backint”APIforthird-partybackuptools.ThetoolcanbackupthedatathroughBACKINTandadditionalflatfilesontop.Thethird-partybackupagentrunsontheSAPHANAserverandSAPHANAcommunicateswiththethird-partybackupagentthroughtheBackintinterface.Currently,SAPHANAdoesnotprovidethebackupcompressionfunction.However,third-partybackupagentsandserverswillbeabletocompressthebackupdata.IBMprovidestheIBMTivoliStorageManager(TSM)supportingSAPHANABACKINT.

Thedocumentationcanbefoundon:IBM®TivoliStorageManagerforEnterpriseResourcePlanning

40


HighAvailabilityandDisasterRecoveryBesidesbackupandrestoreprotectingdatafromadisasterSAPHANAcanbemadehighlyavailablesuitingindividualRTOandRPOrequirements.BesidesSAPHANAinternalfunctionalityalsoavitalecosystemexistsforHAautomationandDRoptimization.

AllSAPHANAHAandDRfunctionalitycanbeuseddirectlyforPowerdeployments.ThisincludesAuto-Host-Failoverforscale-upandlaterforscale-outdeploymentsaswellasSAPHANASystemReplication.

TheRTOofaSAPHANASystemreplicationcanbeimprovedusingClusterManager.IBMhasenabledSAMPtomanagetheSAPLandscapeacrossoperatingsystems.SAMPprovidesthecapabilitiestomanageseamlesslyAppserversresidingonAIXornon-PowerHardware.LookingintoIBMfeatures,suchscenariosasDLPARoperations(whichcanlowertheTCOdramatically)canbebettermanagedusingIBMSoftwareandHardwarestacks.

ForpuredataprotectionSAPHANAsupportsStoragetechnologiessuchasvdiskmirroring,andLUNMirroringonstorageLevel.AlsothehybridsolutionHyperswapcanbeusedinconjunctionwithaclusterManagersuchasIBM’sSAMP.

Note:thischapterisonlyasummaryandnoguidetodeployHA.Itoutlinesimportantthoughtstotakebasedonquestionsaskedbyothercustomers.Additionalinformationcanbeaddedwritingane-mailtotheIBMSAPInternationalCompetenceCenter(ISICC)infoservice:[email protected].

SAPHANASystemReplicationSetupSAPHANASystemReplicationwithfailoverautomation.

SetupConsiderations

NetworkSAPdocumentstheirviewofbandwidthrequirementsintheSAPHANAguides.ThisincludesAppserverconnectivity,Replicationnetworkbetweensites,adminnetworkandforscale-outtheInternodecommunication.

41


Figure14SchematicNetworkoverviewforSAPHANASystemReplicationdeployments

Additionalrecommendeddocumentation• SAMPHANApolicies4.1.0.2Documentation:

http://www.ibm.com/support/knowledgecenter/SSRM2X_4.1.0.2/com.ibm.samp.doc_4.1.0.2/sampicpart4sapha_HANA.html

• SAPNote1834153-HANAhighavailabilitydisastertoleranceconfig•

Toolstoconsider• SAMPHANApolicies4.1.0.2:4.1.0-TIV-ITSAMP-FP0002,TivoliSystemAutomationfor

Multiplatforms•

Auto-Host-FailoveronshareddiskusingXFSBeforeplanningforAuto-Host-Failoverensuretofullyunderstandtheimpactofacoldrestartoftheentireorpartialdatabase.

HavingSAPHANASRimplementedasaHotstandbySolutionitmightbethebetterchoicetofailovertotheHAsitethanrestart.

Figure15FromScale-uptoSAPHANAAutohostfailoverdescribesthefollowingconsiderationsafterthedecisionhasbeenmadetouseAuto-Hostfailover(forscale-upHANAdeploymentsreducethepicturetoonemasterandonestandby):

Client network (Application Server)

Primary Site HANA swarm

communication network

SAP HANA System Replication Network

SAP HANA Application

SAP HANA clients find the master HANA node bya) a virtual IP which is located on the valid HANA

node, or b) a list of master candidates to go through, or c) a combination (one virtual IP per site).

Secondary Site HANA swarm

communication network

For scale-out HANA nodes require inter-node communication

The System Replication Network is used to shuffle the changed data from the primary to the secondary site.

For scale-out HANA nodes require inter-node communication

42


0:Beforescalingoutensurescale-upoptionshavebeenevaluatedfromaperformanceandlimitview.ScaleupprovidestheadvantageofminimizingtherequiredServerandStorageentitiesandbythatasimplerconfigurationandlesswork.

1:MigratingtoscaleoutisdescribedintheSAPDocumentationbysimplyaddingmorenodes.YoucanoperatethissetupwithoutAuto-Host-failoveranddotheHAprotectionusingSAPHANASRwithouttheshareddisk.Thismakesthedisksetupasharednothingarchitecture(orangelines)

2:decidingforcoldstandbyallSAPHANAdataandlogdisksfromeachnodehavetobemadeshared(connectedtoallnodes)toallowthefcClientLVMcomponentofSAPHANAtorestartthefailedpartofthedatabase(reddottedlines).Themorenodesinvolvedthemorecomplexthesetup,themaintenanceandeventualrootcauseanalysiswillbe.

Figure15FromScale-uptoSAPHANAAutohostfailover

ConfigurefcClientLVMExecuteoneachsitefollowingcommand

VerifyfcClientLVMsetupOneachnodeensurethefilesystemcanbemountedanddetachedusing/…/__installer.HDB/server/hdbmount.py

SecurityTheOSandSAPHANAsecurityguidelinescanbefoundhere:

• SAPHANASecurityGuide

Inter-node communication PowerVM

VIOSVIOS

HANA node

(master)

0.Scale-up

LUN LUN

1. Migrate from scale-up to scale-out

PowerVM

VIOSVIOS

HANA node

(worker)

HANA node

(worker)

LUN

2. Auto-Host-failover

PowerVM

VIOSVIOS

HANA node

(standby)

/…/__installer.HDB/server/hdbmount.py --sid=<SID> --configFiles=<HANA shared>/<confX> --datapath=<path to HANA data dir>--logpath=<path to HANA log dir>--partition=1

43


• SAPNote1944799-SAPHANAGuidelinesforSLESOperatingSystemInstallation:providestheofficialSUSEImplementationandtuningguideforSAPHANA.ItalsoincludesachapterforOShardening.

SupportProcessandServicesPleaseseetheSAPHANAonPowerPlanningGuideon:SAPHANAonIBMPowerSystemsandIBMSystemStorage-Guides

RelatedDocumentsPleaseseetheSAPHANAonPowerPlanningGuideon:SAPHANAonIBMPowerSystemsandIBMSystemStorage-Guides

44


DisclaimerandSpecialNoticesThisinformationcouldincludetechnicalinaccuraciesortypographicalerrors.Changesareperiodicallymadetotheinformationherein;thesechangeswillbeincorporatedinneweditionsofthepublication.IBMmaymakeimprovementsand/orchangesintheproduct(s)and/ortheprogram(s)describedinthispublicationatanytimewithoutnotice.

Anyreferencesinthisinformationtonon-IBMWebsitesareprovidedforconvenienceonlyanddonotinanymannerserveasanendorsementofthoseWebsites.ThematerialsatthoseWebsitesarenotpartofthematerialsforthisIBMproductanduseofthoseWebsitesisatyourownrisk.

Anyperformancedatacontainedhereinwasdeterminedinacontrolledenvironment.Therefore,theresultsobtainedinotheroperatingenvironmentsmayvarysignificantly.Somemeasurementsmayhavebeenmadeondevelopment-levelsystemsandthereisnoguaranteethatthesemeasurementswillbethesameongenerallyavailablesystems.

Furthermore,somemeasurementmayhavebeenestimatedthroughextrapolation.Actualresultsmayvary.Usersofthisdocumentshouldverifytheapplicabledatafortheirspecificenvironment.

Informationconcerningnon-IBMproductswasobtainedfromthesuppliersofthoseproducts,theirpublishedannouncementsorotherpubliclyavailablesources.IBMhasnottestedthoseproductsandcannotconfirmtheaccuracyofperformance,compatibilityoranyotherclaimsrelatedtonon-IBMproducts.Questionsonthecapabilitiesofnon-IBMproductsshouldbeaddressedtothesuppliersofthoseproducts.

Thisinformationcontainsexamplesofdataandreportsusedindailybusinessoperations.Toillustratethemascompletelyaspossible,theexamplesincludethenamesofindividuals,companies,brands,andproducts.

Allofthesenamesarefictitiousandanysimilaritytothenamesandaddressesusedbyanactualbusinessenterpriseisentirelycoincidental.

COPYRIGHTLICENSE:

Thisinformationcontainssampleapplicationprogramsinsourcelanguage,whichillustrateprogrammingtechniquesonvariousoperatingplatforms.Youmaycopy,modify,anddistributethesesampleprogramsinanyformwithoutpaymenttoIBM,forthepurposesofdeveloping,using,marketingordistributingapplicationprogramsconformingtotheapplicationprogramminginterfacefortheoperatingplatformforwhichthesampleprogramsarewritten.Theseexampleshavenotbeenthoroughlytestedunderallconditions.IBM,therefore,cannotguaranteeorimplyreliability,serviceability,orfunctionoftheseprograms

ANYINFORMATIONHEREINISPROVIDED“ASIS”WITHOUTWARRANTYORINDEMNIFICATIONOFANYKINDBYIBMANDDONOTANYEXPRESSORIMPLIED,WARRANTIESORCONDITIONSOFMERCHANTABILITY,FITNESSORUSAGEFORPARTICULARPURPOSEANDANYWARRANTYORCONDITIONOFNON-INFRINGEMENT.

45


CopyrightsandTrademarks©Copyright2015IBMCorporation.AllRightsReserved.IBMCorporationSystemsandTechnologyGroupRoute100Somers,NY10589ProducedintheUnitedStatesofAmericaNeitherthisdocumentationnoranypartofitmaybecopiedorreproducedinanyformorbyanymeansortranslatedintoanotherlanguage,withoutthepriorconsentoftheIBMCorporation.IBMmakesnowarrantiesorrepresentationswithrespecttothecontenthereofandspecificallydisclaimsanyimpliedwarrantiesofmerchantabilityorfitnessforanyparticularpurpose.IBMassumesnoresponsibilityforanyerrorsthatmayappearinthisdocument.Theinformationcontainedinthisdocumentissubjecttochangewithoutanynotice.IBMreservestherighttomakeanysuchchangeswithoutobligationtonotifyanypersonofsuchrevisionorchanges.IBMmakesnocommitmenttokeeptheinformationcontainedhereinuptodate.EditionNotice:2017Thisisversion1.8ofthisdocument.Theonlinecopyisthemaster.IBM,theIBMlogo,andibm.comaretrademarksofInternationalBusinessMachinesCorp.,registeredinmanyjurisdictionsworldwide.OtherproductandservicenamesmightbetrademarksofIBMorothercompanies.AcurrentlistofIBMtrademarksisavailableonthewebatat:Copyrightandtrademarkinformation.AdobeandPostScriptareeitherregisteredtrademarksortrademarksofAdobeSystemsIncorporatedintheUnitedStatesand/orothercountries.Fusion-ioisaregisteredtrademarkofFusion-io,intheUnitedStates.Intel,IntelXeon,Itanium,andPentiumaretrademarksorregisteredtrademarksofIntelCorporationoritssubsidiariesintheUnitedStatesandothercountries.JavaandallJava-basedtrademarksandlogosaretrademarksorregisteredtrademarksofOracleand/oritsaffiliates.UNIXisaregisteredtrademarkofTheOpenGroupintheUnitedStatesandothercountries.LinuxisatrademarkofLinusTorvaldsintheUnitedStates,othercountries,orboth.SAPHANAisatrademarkofSAPCorporationintheUnitedStates,othercountries,orboth.OracleisaregisteredtrademarkofOracleCorporationand/oritsaffiliates.Othercompany,productorservicenamesmaybetrademarksorservicemarksofothers.Informationisprovided"ASIS"withoutwarrantyofanykind.Informationconcerningnon-IBMproductswasobtainedfromasupplieroftheseproducts,publishedannouncementmaterial,orotherpubliclyavailablesourcesanddoesnotconstituteanendorsementofsuchproductsbyIBM.Sourcesfornon-IBMlistpricesandperformancenumbersaretakenfrompubliclyavailableinformation,includingvendorannouncementsandvendorworldwidehomepages.IBMhasnottestedtheseproductsandcannotconfirmtheaccuracyofperformance,capability,oranyotherclaimsrelatedtonon-IBMproducts.Questionsonthecapabilityofnon-IBMproductsshouldbeaddressedtothesupplierofthoseproducts.