Kaseya Connect 2011 - Branding Your Company's DNA (LukeMysse)
Kaseya Connect 2013: Optimizing Your K Server - Best Practices in Kaseya Infrastructure & Operations
-
Upload
kaseya -
Category
Technology
-
view
1.633 -
download
3
description
Transcript of Kaseya Connect 2013: Optimizing Your K Server - Best Practices in Kaseya Infrastructure & Operations
Kaseya In The Cloud
Server Optimization And Infrastructure Considerations & Cloud
Presenters
Maxon Duncan● VP, Cloud Operations & IT
Jacques Eagle● Vice President, Cloud Architecture
Maxon Duncan● VP, Cloud Operations & IT
Jacques Eagle● Vice President, Cloud Architecture
Count the clouds ;-)
Obscene $$
Post name & count to #kaseyauc
Count the clouds ;-)
Obscene $$
Post name & count to #kaseyauc
Agenda
Planing, Scaling & Optimizing Kaseya
● Highly performant on-premises installs
Kaseya’s Cloud
● Benefits● Under the hood● How we do it
Recommend Configuration
Virtual Environments? YES!
Recommended Configuration
● Kaseya Can Scale to three servers:
● Resources for 1k agents ● .5 GHz App Server● 1 GHz on DB Server
● Typical IOPS● 15 Application Server● 40 Database Server
Recommended Configuration
● Reporting Services can run on another server● Typically, memory usage of reporting services is based on
50% of memory upon startup● You can manually change the ReportServer.conf if
necessary to reduce● C:\Program Files\Microsoft SQL Server\MSRS10_50.
SYSPREP\Reporting Services\ReportServer.conf● <MemoryThreshold>90</MemoryThreshold>● <WorkingSetMaximum>2000000</WorkingSetMaximum>● <WorkingSetMinimum>500000</WorkingSetMinimum>● <RecycleTime>720</RecycleTime>
Recommended Configuration
● Use Processor Affinity
Database Best Practices
It's all about SQL Performance!
Database Best Practices
● AV Exclusions● OS defrag & mdf/ldf locks● Do not enable auto shrink on the
Ksubscribers database● Above 8 cores, it's best to set parallel
query degree to 4
Database Best Practices
Setting Parallel Query
Database Best Practices
● Synchronous replication will cause performance issues
● Always-On in SQL Server 2012 and Replication can cause re-apply schema to fail
Database Optimization
● Cache Hit Ratio > 98%● DiskIO , keep it below 20ms● TempDB, Broker Services and 6.3● Seperate Networks ● Maintain it!!
● Rebuild/Reorganize Indexes● Update Statistics
Database Optimization
Database Optimization
Typical Memory Usage of SQL Server
● Agents measured by cache/hit ratio● Calculation is 2Gb/1000 Agents● Reserve 4Gb Min for the OS
● Log retention and audit details = database size
Database Optimization
● Optimal File Layout can help your database Performance
● Kaseya Databases are typically 75% Read and 25 % Writes
● Add multiple data files for Tempdb
Database Optimization
Hidden link - live demo
Database Optimization
Kaseya Application Server
● Kaseya recommended configuration is a Guideline
● Kaseya and SQL on the same server? How big can it get?
● workloads affect server performance
Kaseya Application Server
● Baseline Audits are “expensive”● Baseline Audits only need to be run once
(Automatically run once when you add the agents)
● Rescheduling when “out of sync” condition● Latest Audits are “cheap”● Can be run daily spread out over 12 hours
Kaseya Application Server
● Scripts do take resources, so be careful how many you run
● Global Policy changes can generate very large loads on the server
● Monitor counter scans can cause high CPU spikes (6.2)
Kaseya Application Server
● Handling more load with threads● Kserver Threads● Messagesys Threads (6.2)● PluginHost Service (6.3)
Hyper Scaling Kaseya
● Split server configuration● Leveraging multiple SQL Server
Instances● SQL Server Distributed Views● For high volume installs
● aggregation apps● for system of record
● Leveraging Solid State Technologies
Scaling Kaseya
FusionIO IODrive 2 SLC 1.2tb
5 SAS 15k drive array
FusionIO IODrive 2 SLC 1.2tb
Networking
Understand latency to endpoints
Leverage CDN's
OOB!!!!!!!!!!● Most firewalls strip
Firewall Session Management
● 5510x @250k
Virtualization
● Set reserves● Do not restrict, let it fly● Don't oversubscribe ● Don't allow ballooning● Backups / snapshots / revert● Independant mode● Use tiered storage● Reduncancy?
Leveraging Cloud Providers
● Use VMware monitor counters if possible to keep host honest
● Beware of adjacency issues● Kaseya can be spikes
● Test, monitor and understand iops● Port exhaustion● Vett network● Understand SLA's
The Kaseya Cloud.
Cloud Architecture
● Purpose built virtualized infrastructure● - 3 tier, 10gbit storage (SSD, SAS, SATA)● - vmdk placement according to
hotspots● - fully redundant architecture● - result: 15-20k endpoints on single
instance
Do you really want to deal with this?
Cloud Architecture
● Purpose built virtualized infrastructure● 3 tier, 10gbit storage (SSD, SAS, SATA)● vmdk placement hotspots● fully redundant architecture● result: 15-20k endpoints single instance
Benefits of Kaseya’s Cloud
● Secure, Robust, Flexible, Performant● On demand service offering● Global Delivery: Akamai / Presence● Datacenter Presence ● 24x7 Operations staff ● Transparent: http://status.kaseya.com● Managed Security● Licensing
Kaseya’s Cloud Architecture
We are Kaseya’s biggest customer!
We know how to do this.
Kaseya’s Cloud Operations
● Monitoring
● ITIL Configuration Management
● Level 4 Remediation
Security
● IDS● HIDS● Security Audits● Security Events & Incident Mgt (SEIM)● Change management● MFA● Strong internal controls
Metrics
- 700k licensed / 250k online
- 3 gbps presence sustained
- 1pb KDB data managed
- 40 physical servers
- 4 TB memory
- 2.1 THz Processor
- Many many TB of SAN Storage
Dedicated
● Dedicated instances available○ Outside the Cloud Box○ Large scale customers
● On premises management
We love Dogfood!
● KAV● BUDR● Service Desk (ticketing, ITIL)● 200 maintenance and remediation scripts● KNM monitoring● Patch management
Experience.
● 5 years delivery experience● Highly trained staff● Purpose infrastructure● We own the kit● We know what it takes.
Sign up today for a trial at Kaseya.com
Questions?
Cloud count =
42