Using Quest Protect Dashboard
Quest® Protect Dashboard accelerates the performance of your entire virtual infrastructure, transforms the application experience for users, and helps you control license and hardware costs. Go way beyond simple Hyper-V and VMware monitoring by maximizing resource utilization and improving virtual application performance across hybrid environments.
The Quest Protect Dashboard User and Administration Guide is intended for users who have access to Quest Protect Dashboard. To get access to the Quest Protect dashboard, the user should have at least one of the following User roles: System Administrator, Advanced Operator, Capacity Management Administrator, VMware Administrator, or VMware QuickView.
This section introduces you to the Quest Protect environment, and provides you with essential information.
For more information, see the following topics:
Installation requirements
Quest Protect Dashboard comes installed on Foglight® Evolve and can be installed on a Foglight Management Server.
Quest Protect Dashboard requires the following cartridges for data collection.
While Foglight Evolve comes with these cartridges pre-installed and enabled, a stand-alone Foglight release requires that these components be installed on the Foglight Management Server. The sequence of cartridge installation is important because of their dependencies. For more information about installing Quest Protect Dashboard, and for details about system requirements and version compatibility, see the Quest Protect Dashboard Release Notes.
Rapid Recovery Agent Configuration
The Rapid Recovery Agents collect data from your Rapid Recovery infrastructure and sends it to the Rapid Recovery Core Server. The agents keep track of resource utilization metrics and alerts you when certain predefined thresholds are reached.
On 64-bit hosts meeting the minimum system requirements, the embedded Agent Manager can be used to run Rapid Recovery Agents to monitor the Rapid Recovery Core Server that protects up to100 machines.
The Agent Manager JVM usually requires additional memory to monitor the Rapid Recovery Core Server that protects more than 100 virtual machines.
The following calculations are guidelines, not hard and fast rules. Memory requirements can vary greatly from installation to installation with similar machine counts. If insufficient memory is configured, the failure mode is easily recognizable: all agents on the Agent Manager host will go into a broken state after the agent(s) were activated for a short period of time, usually within 24 hours. In addition, the Agent Manager log will contain a line similar to the following: Caused by: java.lang.OutOfMemoryError: Java heap space
If this is the case, add memory greater than what is shown in the calculations below, in increments of 512 MB until the agents stabilize. As most of memory is consumed by events, the memory consumed by Rapid Recovery agents is calculated based on the amounts of events that have been generated in last 2 weeks. It is supposed that one protected machine generates 1500 events in last 2 weeks, and one event might consume 16.5 KB memory, then one protected machine would consume 16.5 x1500 = 20 MB. For example, if a Rapid Recovery Core Server protects 100 machines, this Rapid Recovery Core Server will consume 20 MB x100 =2000 MB (round up to 2 GB). Therefore it is strongly recommended to check the number of events that have been generated since last week. Use the following formula to calculate the required memory:
512 MB + 16.5 KB x events#
If you do not want to check the amounts of events, use the following formula to calculate the required memory based on the number of protected machines:
512 MB + 20 MB x protected machines#
The default setting for agents deployed on 64-bit systems is 2560 MB, which suffice this environment. Similarly, protecting 1000 machines requires 20512 MB of memory:
512 MB + 20 MB x 1000 = 20512 MB
Foglight Evolve Virtual Appliance comes pre-configured to support up to 100 protected machines. This requires the default Agent Manager settings to be changed.
|
2 |
On the agent machine, open the baseline.jvmargs.config file for editing. The file is located in the <Agent_Manager_home>/state/default/config directory. |
Note: If this file has been previously edited, increment the numeric parameters accordingly.
CPU usage on the Agent Manager host is relatively low most of the time. However, usage peaks dramatically during the performance metric collection. This is normal and expected. CPU utilization consistently over 50% is an indication that additional processing power is required. As with memory, usage can vary between different installations with similar numbers of protected machines. The following guidelines should be followed:
Veeam Agent Configuration
The Veeam Agents collect data from your Veeam infrastructure and sends it to the Veeam Backup Server. The agents keep track of resource utilization metrics and alerts you when certain pre-defined thresholds are reached.
On 64-bit hosts meeting the minimum system requirements, the embedded Agent Manager can be used to run Veeam Agents to monitor the Veeam Enterprise Manager Server that protects up to400 machines.
The Agent Manager JVM usually requires additional memory to monitor the Veeam Enterprise Manager Server that protects more than 400 virtual machines.
The following calculations are guidelines, not hard and fast rules. Memory requirements can vary greatly from installation to installation with similar machine counts. If insufficient memory is configured, the failure mode is easily recognizable: all agents on the Agent Manager host will go into a broken state after the agent(s) were activated for a short period of time, usually within 24 hours. In addition, the Agent Manager log will contain a line similar to the following: Caused by: java.lang.OutOfMemoryError: Java heap space
If this is the case, add memory greater than what is shown in the calculations below, in increments of 512 MB until the agents stabilize. Use the following formula to calculate the required memory:
512 MB + 5 MB x protected machines#
According to the above formula, monitoring 400 virtual machines requires 2512 MB of memory: 512 MB + 5 MB * 400 = 2512 MB.
The default setting for agents deployed on 64-bit systems is 2560 MB, which suffice this environment. Similarly, protecting 1000 machines requires 5512 MB of memory: 512 MB + 5 MB x 1000 = 5512 MB
Foglight Evolve Virtual Appliance comes pre-configured to support up to 400 protected machines. This requires the default Agent Manager settings to be changed.
|
2 |
On the agent machine, open the baseline.jvmargs.config file for editing. The file is located in the <Agent_Manager_home>/state/default/config directory. |
Note: If this file has been previously edited, increment the numeric parameters accordingly.
CPU usage on the Agent Manager host is relatively low most of the time. However, usage peaks dramatically during the performance metric collection. This is normal and expected. CPU utilization consistently over 50% is an indication that additional processing power is required. As with memory, usage can vary between different installations with similar numbers of protected machines. The following guidelines should be followed::
