Unicenter Desktop & Server Management Scaling Options - SQL -Latest Revision June 29 2006 -Read the notes pages.

Slides:



Advertisements
Similar presentations
The CA MDB Revised May © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced.
Advertisements

SSRS 2008 Architecture Improvements Scale-out SSRS 2008 Report Engine Scalability Improvements.
© 2011 Autodesk Go Big or Go Home! Part 1 – Large Scale Autodesk Vault Deployments Irvin Hayes Jr. Technical Product Manager.
WSUS Presented by: Nada Abdullah Ahmed.
Jeff McCashland. Agenda Supported Deployment Scenarios System Requirements Installing DTM Controller Installing the DTM Logo Tests Installing DTM Studio.
Unicenter Service Desk (USD) -Preliminary Scalability Recommendations for r11 -Revised January
Unicenter Desktop and Server Management Architectural Options -Latest Revision 10/27/05.
Copyright 2009 FUJITSU TECHNOLOGY SOLUTIONS PRIMERGY Servers and Windows Server® 2008 R2 Benefit from an efficient, high performance and flexible platform.
Lesson 18 – INSTALLING AND SETTING UP WINDOWS 2000 SERVER.
Maintaining and Updating Windows Server 2008
Proper Care and Feeding of your SQL MDB -Recommendations for General MDB Maintenance -Read the notes on the foils! -Revised October
Unicenter NSM r11 Windows -SNMP Polling Analysis.
Microsoft ® Application Virtualization 4.5 Infrastructure Planning and Design Series.
MDB Install Overview for Federated and Shared MDBs Revised June 19, 2006.
VMware vCenter Server Module 4.
11 SYSTEMS ADMINISTRATION AND TERMINAL SERVICES Chapter 12.
16.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 16: Examining Software Update.
Unicenter Desktop & Server Management Network Challenges -Latest Revision 11/28/2005.
Highly Available Unicenter Solutions -A High Level Summary Draft – Last Revised June 9, 2006.
Best Practices for Implementing Unicenter Service Desk r11.x in an HA MSCS Environment - Part 3: HA Primary Server Revised January 02, 2009 Although this.
MCITP Administrator: Microsoft SQL Server 2005 Database Server Infrastructure Design Study Guide (70-443) Chapter 1: Designing the Hardware and Software.
Introduction to HP LoadRunner Getting Familiar with LoadRunner >>>>>>>>>>>>>>>>>>>>>>
Sales Kickoff - ARCserve
Migration to NSM r11. © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong.

Best Practices for Implementing Unicenter Asset Portfolio Management r11.2 in an HA MSCS Environment - Part 2 – Unicenter Asset Management Portfolio Draft.
IMPLEMENTING F-SECURE POLICY MANAGER. Page 2 Agenda Main topics Pre-deployment phase Is the implementation possible? Implementation scenarios and examples.
Module 13: Maintaining Software by Using Windows Server Update Services.
Implementing Update Management
Unicenter Desktop & Server Management Scaling Options -Latest Revision 12/09/2005.
Module 4: Planning, Optimizing, and Troubleshooting DHCP
Unicenter Desktop & Server Management Components & Communication -Latest Revision 12/09/2005.
Step By Step Windows Server 2003 Installation Guide Step By Step Windows Server 2003 Installation Guide.
Implementing Hyper-V®
Module 11: Implementing ISA Server 2004 Enterprise Edition.
Job Management Option (WLM) Scalability Tests r11 December
MDB Connectivity Scalability Tests r11 October 25 th
Hosting an Enterprise Financial Forecasting Application with Terminal Server Published: June 2003.
Systems Management Server 2.0: Backup and Recovery Overview SMS Recovery Web Site location: Updated.
Best Practices for Implementing Unicenter NSM r11.1 in an HA MSCS Environment Part II -Last Revision April 24, 2006.
DC-B312 BitLocker Improvements in Windows 8 MBAM 2.0 Investment Areas and Key New Features Deploying MBAM 2.0MBAM 2.0 End User Experience.
Section 11: Implementing Software Restriction Policies and AppLocker What Is a Software Restriction Policy? Creating a Software Restriction Policy Using.
Module 3 Planning and Deploying Mailbox Services.
R11 Management Command Center Scalability Tests Revised July
Crystal Reports Training
11 CLUSTERING AND AVAILABILITY Chapter 11. Chapter 11: CLUSTERING AND AVAILABILITY2 OVERVIEW  Describe the clustering capabilities of Microsoft Windows.
Unicenter Desktop & Server Management Scaling Options - Ingres -Latest Revision Jun Read the notes pages.
Best Practices for Implementing Unicenter Asset Portfolio Management r11.2 in an HA MSCS Environment -Part I: Installing UAPM Optional Components Draft.
Making r11 Agent Technology talk through a Firewall Last Updated 12/19/2005.
Unicenter NSM Repository Bridge 3.1 -> r11. © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos.
Upgrading from r4.1.4 to r7: Making a Smooth Transition Roger Suttmeier Support Distribution Manager June 14, 2006.
Installation of Storage Foundation for Windows High Availability 5.1 SP2 1 Daniel Schnack Principle Technical Support Engineer.
Best Practices for Implementing Unicenter NSM r11.1 in an HA MSCS Environment Part I -Last Revision April 24, 2006.
Unicenter NSM Debugging Tips & Tricks -Release r11.
Federated MDBs with Multiple SQL Instances Last Revision Date: September 6, 2006.
Best Practices for Implementing Unicenter NSM r11 in an HA MSCS Environment Part I -Last Revision April 24, 2006.
Windows SharePoint Services Installation and Configuration.
70-294: MCSE Guide to Microsoft Windows Server 2003 Active Directory, Enhanced Chapter 6: Active Directory Physical Design.
Best Practices for Implementing Unicenter Service Desk r11.1 in an HA MSCS Environment -Part II: Installing non-HA Primary Server Connecting to an HA MDB.
1 BCS 4 th Semester. Step 1: Download SQL Server 2005 Express Edition Version Feature SQL Server 2005 Express Edition SP1 SQL Server 2005 Express Edition.
1 © 2004 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective.
Planning Server Deployments Chapter 1. Server Deployment When planning a server deployment for a large enterprise network, the operating system edition.
ITMT 1371 – Window 7 Configuration 1 ITMT Windows 7 Configuration Chapter 8 – Managing and Monitoring Windows 7 Performance.
Configuring SQL Server for a successful SharePoint Server Deployment Haaron Gonzalez Solution Architect & Consultant Microsoft MVP SharePoint Server
9 Copyright © 2004, Oracle. All rights reserved. Getting Started with Oracle Migration Workbench.
Installation 1. Installation Sources
Installing Windows Server 2008
Introduction of Week 3 Assignment Discussion
2018 Real Dell EMC E Exam Questions Killtest
Microsoft Virtual Academy
Presentation transcript:

Unicenter Desktop & Server Management Scaling Options - SQL -Latest Revision June Read the notes pages

Domain Management: Scaling © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

3 Gather and understand…. …installation needs and expectations before beginning, then develop the architecture to satisfy those conditions. No hard and fast formulas…. …the intention is to illustrate the thought process and describe general principles used to make installation specific decisions.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 4 Things have changed…. …and will continue to change with regards to performance and best practices as testing continues. Always check for the latest facts and figures. Migration requires re-thinking…. …because limitations that applied to previous releases may not longer apply and consolidation of applications to a single system may be required.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 5 Ask…. Understand…. Why?

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 6 Simple, small environment…. Up to 2000 agents Single LAN or campus No DMZ or firewalls No constraining service level requirements Main motivation for implementing DSM: Simplify and unify desktop and server management functions.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 7 Simple, small environment…. All Domain Management components may be implemented on a single, adequately sized system. System Specification: CPU:Dual 2 GHz RAM:2 GB Disk:100 GB free

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 8 Simple, small environment…. …but this installation has service level requirements that must be met. Ability to deliver a common software packages be distributed to all targets within 3 hours. Requires asset inventory to be no more than 24 hours old Up to 2000 agents Single LAN or campus No DMZ or firewalls No constraining service level requirements

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 9 Simple, small environment…. One to two Scalability Servers are added…. Added System Specification: CPU:Single 2 GHz RAM:2 GB Disk:100 GB free Why?

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 10 Simple, small environment…. Expectations are more demanding then in the previous case. Common software package must be distributed to all 2,000 agents within 3 hours. Assumption: Common software package takes 5 minutes to distribute. Fact: Software deployment is limited by default to 25 concurrent activations from any Scalability Server.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 11 Simple, small environment…. Assumption: Common software package takes 5 minutes to distribute. Fact: Software deployment is limited by default to 25 concurrent activations from any Scalability Server. So, 2000 distributions at 5 minutes each at 25 at a time would take 6.67 hours. The service level requirement is not more than 3 hours so three source points, minimum, are needed.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 12 Medium Environment Recent performance enhancements and follow up testing make it necessary to reconsider best practice recommendations based on experiences with previous releases and even previous builds r11.1. Up to 50,000 agents Distributed LAN/WAN DMZs and/or firewalls Service level requirements Why?

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 13

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 14 Medium Environment Take note of the end population. The statistics were compiled while progressively adding computers, hardware and software inventory to DSM Domain with all components including the MDB (Microsoft SQL Server 2000 SP4) on a single high-end server until the number of computers reached 50,000 Up to 50,000 agents Distributed LAN/WAN DMZs and/or firewalls Service level requirements

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 15 Test Environment Architecture Architecture implemented for testing: Single server hosting MDB, DSM Domain Manager, Engine and Scalability Server Hardware/Software Specifications DSM Domain Manager, Engine, Scalability Server and MDB Server:  Microsoft Windows Server 2003 Enterprise Edition SP1  Microsoft SQL Server 2000 SP4  Dual Hyper-Threaded 3.19 GHz processor  8 gb RAM (no more than 4GB is required) Agent Simulator  Microsoft Windows Server 2003 SP1  Single Pentium III 993 MHz processor  512 mb RAM

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 16 Medium Environment Recommendations/Requirements to replicate performance - Apply database and binary updates (to be included in “Cut 6” of r Reserve 4gb of memory for Microsoft SQL Server on 8GB box -- Initialize the base MDB data file size at 5gb with “Unrestricted growth” enabled -- Initialize the base MDB log file size at 2 gb with “Unrestricted growth” enabled. Up to 50,000 agents Distributed LAN/WAN DMZs and/or firewalls Service level requirements

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 17 Medium Environment Fact versus Fiction: Although it was originally thought to be true based on results from testing with Ingres, deploying dedicated hardware for the MDB and DSM Manager (two servers) does not significantly impact performance. Single server model (MDB installed locally with DSM components) performed as well and in some cases better than the multiple server model. Up to 50,000 agents Distributed LAN/WAN DMZs and/or firewalls Service level requirements

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 18 Medium Environment With previous version, sites planning to manage more that 10,000 to 12,500 nodes were invariably forced to implement an Enterprise architecture. Our results indicate that clients can now choose the less complex, less costly option of implementing a single DSM Domain (provided of course there were no other business or administrative factors that would force separation). Based on test results 25,000 to 35,000 may be viable…. Up to 50,000 agents Distributed LAN/WAN DMZs and/or firewalls Service level requirements …but…

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 19 Medium Environment Limitations to what can be uncovered in simulation tests are well known. Although the test target population was set at 50,000 nodes, this does not imply that such a large single Domain would function adequately in “real world” production. Also note that most testing so far has been focused on database access and update performance as directly related to database population….

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 20 Medium Environment …various other scenarios have not been tested at high population levels and other break points could be unrelated to the number of managed computers alone. For example, policy groups for software deployment may cause delays at relatively low populations but very high linked procedures counts. Test yourself, and check CA sites frequently for latest data and recommendations…

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 21 Medium Environment More commonly, components will be distributed not only for performance and scalability reasons… System Specification: Domain Manager/MDB CPU:Quad 2 GHz RAM:8 GB Disk:200 GB Scalability Server: CPU:Single 2 GHz RAM:2 GB Disk:25-50 GB free

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 22 Network Challenges …but to address a variety of network topology challenges as well (more on this later).

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 23 Some basics still apply Domain Managers and Engines should be electronically close to the MDB. Scalability Servers should be electronically close to the agents

Enterprise Management: Scaling © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies.

25 Medium & Large Environments Given the enhanced performance of the Domain with Microsoft SQL Server, an Enterprise model should not be considered for small environments or most medium environments unless some specialized business or administrative requirements dictate. At this time the replication process is a potential performance obstacle and until that can be addressed properly (planned for r11.2) an Enterprise implementation requires careful consideration and a willingness to adjust architecture based upon measured results.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 26 One server or two… Although it was originally believed based on results from testing with Ingres that deploying dedicated hardware for the MDB and DSM Manager (two servers) would significantly improve performance the single server model (MDB installed locally with DSM components) performed as well and in some cases better than the multiple server model.. Microsoft Windows Server 2003 Enterprise Edition SP1 Microsoft SQL Server 2000 SP4 Dual Hyper-Threaded 3.2 GHz processor 8 gb RAM

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 27 The big (really big) picture… DGE, a project planned to build, populate and replicate five DSM Domains with 50,000 computers each in a single Enterprise of 250k was run in Many performance obstacles at the Domain level were found and have been addressed. The replication process itself currently takes a considerable amount of time but major enhancements have been architected and should be implemented in the GM of r11.2 As new test results are generated, they will be posted.

© 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos referenced herein belong to their respective companies. 28 Guidelines presented here were based on Stress Lab Testing. Please understand that because many test plan items could require installation of thousands of systems and agents, a simulation tool known as “Load Tester” was employed. “Load Tester” generates the CAM messages that agents would produce at a very high, configurable rate, “bursting” them onto the network in large batches. Such test results are estimates of actual performance as client network configuration and available capacity impact predicted thruput. DSM r11 From the Stress Lab