Quest Protect 6.3.0 - User Guide

Known issues

This 6.3.0 release of Quest Protect includes the following known issues at the time of this release.

Back to Top

Upgrade and compatibility 

The following Foglight product versions and platforms are compatible with this release.

Back to Top

System requirements 

For information about system requirements for this release, see the corresponding Foglight System Requirements and Platform Support Guide.

Compatibility with Rapid Recovery and Veeam:

• This version is directly compatible with Rapid Recovery 6.1.2 and later. Do not attempt to install it alongside any previous versions.
• This version is directly compatible with Veeam Backup & Replication 9.5 Update 1 (build 9.5.0.823) and later. Do not attempt to install it alongside any previous versions. VEEAM Backup Enterprise Manager must have Enterprise Plus or MSP VEEAM license.

Agent account privileges for Rapid Recovery and Veeam:

• For Rapid Recovery, the user credential must belong to the Administrators group of Rapid Recovery Core Server.
• For Veeam, the user credential must be assigned with one of the following roles: the Portal Administrator, the Restore Operator, or the Portal User role.

Agent and Agent Manager configuration

Standard environments: Rapid Recovery Agent and Agent Manager configuration

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.

Standard environments: Veeam Agent and Agent Manager configuration

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.

Large environments: Rapid Recovery Agent and Agent Manager configuration

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 and Foglight for Virtualization, Enterprise Edition Virtual Appliance comes pre-configured to support up to 100 protected machines. This requires the default Agent Manager settings to be changed.

To change the JVM memory settings:

1. Determine the amount of additional memory required. This will be the total from the last step above minus the default value of 2560 MB. In the example above, this is 20512 – 2560 = 17952 MB (round up to 17 GB).
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.
3. Add the following lines in the Memory Settings section:
   vmparameter.0 = "-Xms17g";
   vmparameter.1 = "-Xmx17g";
   Note: If this file has been previously edited, increment the numeric parameters accordingly.
4. Delete the existing deployed negotiation configuration settings directory: <Agent_Manager_home>/state/default/config/deployments
   Restart the Agent Manager for these settings to take effect.

CPU

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:

Large environments: Veeam Agent and Agent Manager configuration

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 and Foglight for Virtualization, Enterprise Edition Virtual Appliance comes pre-configured to support up to 400 protected machines. This requires the default Agent Manager settings to be changed.

To change the JVM memory settings:

1. Determine the amount of additional memory required. This will be the total from the last step above minus the default value of 2560 MB. In the example above, this is 5512 – 2560 = 2952 MB (round up to 3 GB).
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.
3. Add the following lines in the Memory Settings section:
   vmparameter.0 = "-Xms3g";
   vmparameter.1 = "-Xmx3g";
   Note: If this file has been previously edited, increment the numeric parameters accordingly.
4. Delete the existing deployed negotiation configuration settings directory: <Agent_Manager_home>/state/default/config/deployments
   Restart the Agent Manager for these settings to take effect.

CPU

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:

Foglight Management Server minimum memory and CPU requirements

Rapid Recovery: minimum memory and CPU requirements:

* Edit the Foglight Management Server JVM settings in the server.config file located under Quest\Foglight\config\. When running Foglight on a virtual machine, full memory needs be reserved at the hypervisor level.

Veeam: minimum memory and CPU requirements:

* Edit the Foglight Management Server JVM settings in the server.config file located under Quest\Foglight\config\. When running Foglight on a virtual machine, full memory needs be reserved at the hypervisor level.

Back to Top

Product licensing

Foglight includes a licensing capability that restricts access to those features that are defined in the license. Any Management Server installation requires a license that grants access to server-specific parts of the browser interface and the features associated with them. Foglight cartridges are also license-protected. While some cartridges are covered by the base Foglight license (such as Foglight Agent Manager cartridges and Foglight for Infrastructure), others may require an additional license. Quest Protect Dashboard is covered by the base Foglight Evolve license and Foglight for Virtualization, Enterprise Edition license.

To activate a trial or a purchased commercial license:

1. On the navigation panel, under Dashboards, click Administration > Setup > Manage Licenses.
2. Click Install.
3. In the Install License dialog box, click Browse.
4. In the file browser that appears, specify the location of the license file.
5. In the Install License dialog box, click Install License.

Back to Top