| Info |
|---|
The directions in the subsequent sections assume you are installing up.time for the first time. If you are updating an existing up.time installation, there are other steps to consider. Refer to one of the following upgrade page pages on the up.time Support Portal (http://support.uptimesoftware.com/upgrade.php) to ensure , when upgrading, that that during an upgrade, your monitoring is uninterrupted and you have safeguarded your historical data: |
Understanding up.time's Components
...
The DataStore is where all historical performance and availability data are stored. up.time includes a MySQL database implementation, but it can also use either an Oracle or MS SQL Server database as its DataStore. If you plan to use either of these databases, refer to Running up.time with an Oracle database or Running up.time with an MS SQL Server database in our Knowledge Base for additional information.
...
When reviewing up.time resource requirements, it is important to note that sizing varies based on the number of monitors per element, the type of objects monitored, and the method used to gather performance data. up.time recommendations are based on an average of 2 or 3 monitors per element. For more information regarding resource requirements, see up.time Uptime Infrastructure Monitor Sizing Examples.
As a general rule of thumb when planning the allocated disk space, you should plan on allocating about 4 GB per monitored element. Note that per element usages are per year, unless you archive using old data.
...
The hardware configurations for a Monitoring Station can change depending on the number of up.time Agents you plan to monitor, the reports that you want to generate, and the amount of historical data that you wish to retain in the DataStore. For sizing examples, see up.time Uptime Infrastructure Monitor Sizing Examples.
DataStore
The amount of storage space for the up.time DataStore is dependent on the number of systems monitored. As a guide, use the up.time DataStore Sizing Calculator.
...