McAfeeePolicyOrchestrator(3)

HerearecommonissuesMcAfeeePOadministratorsmayexperiencewhenrunningtheCertificateMigrationprocess:

-->

BasicSQLmaintenancecanprovideameasureofconfidenceinconsistentSQLperformance,acriticalcomponentofMcAfeeePOperformance.BecausetheSQLdatabaseforMcAfeeePOishighlytransactionalinnature,theexecutionspeedofthosetransactionsdirectlyrelatestohowfasttheproductisabletooperate.

TheRecommendedMaintenancePlan(loginrequired)fortheMcAfeeePOdatabasefocusesprimarilyonseveralconfigurationoptionsandaregularlyscheduledmaintenanceplanthatconsistsofthreetasks.

ConfigurationoptionsrecommendedfortheMcAfeeePOSQLdatabase:

ToconfigurearegularlyscheduledSQLmaintenanceplan:

NOTE:CreatingamaintenanceplanispossibleinfullversionsofMicrosoftSQL.MicrosoftSQLExpressisafreelyavailable,butlimited,versionofMicrosoftSQL.MicrosoftSQLExpressisonlyrecommendedforuseinenvironmentswithlessthan1,500managedsystems.

RebuildingandreorganizingindexesimprovesSQLperformance.Whenthedatabaseiswell-maintained,databasesizealonedoesnotnegativelyaffectqueryperformance.

NOTE:KB67184,theRecommendedMaintenancePlan,isaregisteredKBandrequiresaccesstotheMcAfeeServicePortal.Inadditiontowhatisoutlinedhere,theMaintenancePlandocumentincludesanSQLscriptoptimizedforrebuildingandreorganizingindexesinproductionenvironments.

WhendeterminingthehardwarespecificationsrequiredforacceptableSQLperformanceinaMcAfeeePOenvironment,considerthefollowing:

NOTE:TheSQLdatabasecanbehostedonthesamemachinethatisresponsibleforhostingMcAfeeePO,butthisconfigurationisonlyrecommendedinenvironmentswithlessthan10,000managednodes.Inenvironmentsgreaterthan25,000managednodes,theSQLservershouldnotonlybeseparate,butalsoonaphysical(asopposedtovirtual)machine.

SQLperformanceitselfismostcloselytiedtothreespecifichardwarefactors:

Hardwarerecommendationsaredifficulttoestimatebasedonthefactorsdescribedabove,butingeneral,theSQLservershouldhavesimilar,ifnotgreater,hardwaregrantedtoitthantheMcAfeeePOserveritself—especiallymemoryinlargeenvironments.Forexample,inanenvironmentwith75,000to150,000endpoints,thestandaloneSQLservershouldhavebetween32GBand128GBofmemoryinstalled,whiletheMcAfeeePOservershouldhavebetween32GBand64GB.

BlockingwithintheSQLdatabaseoccurswhentwotransactionsrequireaccesstothesameresource—essentially,thetransactionsformachain.Whentheheadblockeriscomplete,theresourceismadeavailableagainandthenexttransactioncanmoveahead.

Blocking,likeSQLdeadlocks,isanormaloccurrenceinabusydatabase.But,thereareextremescenariosthatcanarisewhenablockingtransactionrunsforalongtime.Inthatcase,especiallyifthelockedresourceiscommonlyused(forexample,thetablesresponsibleforstoringMcAfeeePOSystemTreedata),thenumberoftransactionswaitingontheheadblockercangrow.ThisconditioncancausetheMcAfeeePOconsoletobeunresponsive.

NOTE:BlockingissuesaremostfrequentlycausedbyinefficienciesinthedesignofobjectswithintheSQLdatabase—forexample,alargetablethathasnoindex.UpgradestoMcAfeeePOitself,orthepoint-productextensionresponsibleforthedatabaseobject,areoftenthefirststep.

Somemorecommonblockingscenariosinclude:

NOTE:Ingeneral,indexfragmentationcanmakeasignificantdifferenceintheamountoftimeittakesforatransactionandhowlongitlocksaspecificresource.Refertothesectionon“SQLMaintenance”orKB67184(loginrequired)forinstructionsonhowtoensurefragmentationisreduced.

AnSQLdeadlockisaconditionwheretwotransactionsarebothblocked,waitingfortheothertransactiontocompleteitsworkandreleasealock.Contentionforthesharedresourceleadstooneofthetransactionsbeingchosenasthe“deadlockvictim.”Thetransactioniskilledandthedeadlockvictimmaybeimmediatelyretrieddependingontheaction.

NOTE:Deadlocks,whilepreferablyavoidedentirely,areingeneralanaturaloccurrenceinabusySQLdatabase.DeadlocksmustbeaddressedwhentheyareconsistentorimpedeMcAfeeePOfunctionality.

DeadlocksarenotclearlydisplayedfromwithintheMcAfeeePOconsole.Instead,theconsolemightdisplayanunexpectederrororothersimilarproblem.DeadlocksareloggedintheApplicationServerservice’sprimarylog,theorion.log,locatedintheePO_install_dir\server\logsfolder.

Whendeadlockshavebeenconfirmedasaproblem,it’snecessarytocollectmoredatatoresolvetheproblem.KB90786(loginrequired)describesthethreemethodsofenablingandcapturingdeadlocktraceinformation,whichisnecessarytoprovidetoMcAfeeSupportwhentroubleshootingapersistentdeadlockproblem.

SQLdatabasesizeconsiderationsfallunderthreelargebranches:

NOTE:Databasefilesizedoesnotitselfleadtoperformanceproblems,eveninverylargeenvironments,iftheSQLdatabaseisproperlymaintainedanddefragmented.SQLExpressinstancesarecommonlyresponsibleforadministratorsexperiencingdisksizeproblems.WithSQLExpressitisnecessarytofirstidentifywhatisresponsiblefortakingupthemostspaceinthedatabaseandthenremovetheresponsibleeventsmanuallyor,preferably,viaMcAfeeePO-configuredServerTasks.

NOTE:McAfeeePO5.3.0,5.3.1,and5.3.2aremostcommonlyimpactedbytempdbgrowthproblemsbecausetheyuseanSQLconfigurationoptioncalledSnapshotIsolation.UpgradingtoMcAfeeePO5.3.3or5.9.1isrecommended.

DiskspaceisalsoaconcernduringaMcAfeeePOupgrade—thedatabasecandoubleinsizeduringtheinstallationprocessbecauseofschemachanges(especiallywhenupgradingfromMcAfeeePO5.3.xto5.9.xand5.10.x).KB79561coversimportantconsiderationsforpreparingthedatabasetoreducetheimpactofthedatabasegrowthbeforeanupgrade.

本文来自电脑杂谈，转载请注明本文网址：
http://www.pc-fly.com/a/jisuanjixue/article-120294-3.html