Symantec Mobile Security 7.2 Sizing and Scalability Information

Article:TECH203377  |  Created: 2013-02-28  |  Updated: 2013-05-01  |  Article URL http://www.symantec.com/docs/TECH203377
Article Type
Technical Solution


Issue



This document is intended to assist administrators who are designing the architecture of their planned Symantec Mobile Security 7.2 (SMS 7.2) implementation.  Additional information beyond these Frequently Asked Questions (FAQs) is available in the articles referenced below.

 

Additional information may be found in the Connect forum article Illustrated Guide to Installing Symantec Mobile Security 7.2.

  


Solution



Q.  How many Android and Windows Mobile clients can be supported through one Symantec Mobile Security 7.2 (SMS 7.2) management server?  

A.  A healthy Symantec Mobile Security 7.2 server can easily manage 20,000 clients, with a theoretical maximum on 50,000 clients if configuration is adjusted to minimize the burden placed on the server by each client.  Note that this assumes that no other products are managed through this Symantec Management Platform (SMP) and that the SMP server has ample resources.

Q. What are the best settings to configure to improve performance on very large implenetations?

A.  Alter the communciation settings that control the device check-in frequency for new policies, actions, and inventories. Increasing the time will allow the SMP to process communications with additional clients.

Q.  What versions of MS SQL are suitable for use as a database?  

A.  Installation documentation calls for Microsoft SQL Server 2005 (SP2/SP3/SP4) or Microsoft SQL Server 2008 (SP1/SP2/R2/R2,SP1).  SMS 7.2 can use the MS SQL Express version, but this is only suitable for trial purposes or Symantec Mobile Security installations of 500 devices or less.  The Express version of SQL 2005, for example, has a maximum size of 4 GB.  It is unsuitable for long-term enterprise use as running out of space can stop the management component from working.  If an express version must be used, Symantec recommends MS SQL Express 2008 R2 (size limit increased to 10 GB per database).

Q. How large will the SMS database grow?

A. A safe guideline is to expect that each device will use 100 KB of database space.  If the Symantec Management Platform (server) is managing 20,000 Android devices, their combined records should require less than 3 GB of space in the database. 

Q. The Android clients check in with the server every so often to communicate events, check for new policies, and so on.  How much network bandwidth does communicating with a managed Android client require?
 
A.  Using the default policy, each managed Android device can be expected to use from 0.2 MB to 0.5 MB of traffic per day.  If there is a policy with many app control rules, requiring very frequent check-ins, and debug communications settings, this will of course increase.
 
Q.  What is the size of the definitions downloaded by each SMS Android client?

A.  Android clients can download their anti-malware definitions either from internet-based LiveUpdate servers or from an internal LiveUpdate Administrator 2.x (LUA 2.x) server's Distribution Center.  At the present time, the size of a complete definitions download is less than 500 KB.  This will gradually increase as additional threats which target Android are discovered and protection added to the definitions.  Administrators can configure how often the clients run LiveUpdate.  In order to maximize protection, Symantec Technical Support recommends a daily check.

Q.  What network ports need to be opened for communication? 

A.  Please see Ports Used by Symantec Mobile Security 7.2.

Q. How long will the SMP retain logs and other data from devices?  Will this impact performance?

A. The length of time is configurable by the administrator.  Admins who are concerned that logs may consume too much space can set the server to purge data sooner.  For more information, please see About the Android Purge Schedule in Symantec Mobile Security 7.2.

 

 

 





Article URL http://www.symantec.com/docs/TECH203377


Terms of use for this information are found in Legal Notices