PlateSpin Recon Server hosts must meet the following system requirements:
NOTE:Disk space Requirements depend on the number of monitored workloads and the amount of historical summary and raw utilization data kept in the database. When using a remote SQL Server database, ensure that the database host has 2 GB of allocated space. Disk space requirements are based on 30 days of monitoring. At least one CPU core for every 750 monitored servers is recommended.
Table 1-1 System Requirements for PlateSpin Recon Server Hosts
|
Basic |
Large-Scale |
---|---|---|
|
|
|
Processor |
|
|
Virtual Machine |
1 Virtual CPU |
2 Virtual CPUs |
Memory |
1 GB (2 GB recommended) |
2 GB (4 GB recommended) |
Disk Space |
20 GB free |
100 GB free |
OS |
Any of the following:
PlateSpin Recon server is not supported on WOW64 (Windows-on-Windows 64-bit) or any other 64-bit operating system. IMPORTANT:User Access Control (UAC) should be turned off on Windows Server 2008. See Turning off UAC on Windows Server 2008 for more information. |
|
Database Engine |
Any of the following:
|
|
Software |
|
Click
> .In the Control Panel, click
.In the User Accounts window, click
.In the User Accounts tasks window, click
.(Conditional) If UAC is currently configured in Admin Approval Mode, the User Account Control message is displayed. Click .
Clear the
check box, and click .Click
to apply the change right away, or click and close the User Accounts tasks window to apply the change the next time you restart your system.PlateSpin Recon Client hosts must meet the following system requirements:
Table 1-2 System Requirements for PlateSpin Recon Client Hosts
You can install PlateSpin Recon Server and PlateSpin Recon Client software in a virtual machine (VMware* platform only). You should use a dual-vCPU virtual machine.
Installing PlateSpin Recon Server in a VM restricts the monitoring and inventorying capabilities of the software to:
5000 inventoried workloads
1000 monitored workloads
Table 1-3 Database Growth Projections
NOTE:Application database figures are based on average reporting usage. The DB size figures should be doubled when using PostgreSQL.