This 1.5 release of Quest Protect Dashboard accompanies the release of Foglight for Virtualization, Enterprise Edition 8.8.5. The following is a list of issues addressed and enhancements implemented in this release.
|
Defect ID |
Resolved Issue |
|
VRM-414 |
After upgrading the Protect Dashboard cartridge to version 1.4, the Data Protection panel disappears in the VMware Environment > Virtual Machines dashboard. |
This 1.5 release of Quest Protect includes the following known issues at the time of this release.
|
Defect ID |
Known Issue |
|
VRM-419 |
The VROOM Dashboard cartridge has been rebranded to Protect Dashboard cartridge since version 1.4. If you upgrade the VROOM cartridge (1.3 or earlier) to the Protect Dashboard cartridge (1.4 or later), both cartridges coexist after the upgrade. Meanwhile, the previous VROOM Dashboard cartridge still take effects while the new cartridge has been intalled. Workaround: On the Cartridge Inventory dashboard, disable the previous VROOM Dashboard cartridge, and then enable the new Protect Dashboard cartridge. |
|
n/a |
The Timeout for Virtual Machine Automation is controlled by the Protection Timeout property that is set to 5 minutes by default. If Rapid Recovery Server does not respond in the defined timeout period, a timeout error message will prompt. Note: Go to the Agent Properties dialog box, and then increase the value of Protection Timeout; otherwise decrease the number of monitored virtual machines. |
|
n/a |
Protect Virtual Machine Automation in Hyper-V environments only supports to export as an ESX file in this release. |
|
n/a |
If you encounter the error in debugging log: "Error occurs during collection. http_code=500 message=Specified port '27017' cannot be accessed at the specified host 'localhost'.", do any of the following: Workaround 1: Upgrade your Quest Protect Dashboard to this 1.3 release. Workaround 2: Increase the upper limit of ephemeral ports that have been dynamically allocated to client TCP/IP socket connections. a. Open the Registry Editor. b. Browse to select HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters. c. Select Edit > New > DWORD Value, and then specify the following values: • Name: MaxUserPort • Data: Any decimal value from 5000 to 65534 Workaround 3: Decrease the default timeout value of client TCP/IP socket connections. a. Open the Registry Editor. b. Browse to select HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters. c. Select Edit > New > DWORD Value, and then specify the following values: • Name: TcpTimedWaitDelay • Data: Any decimal value from 30 to 240 |
|
n/a |
The virtual machine ID cannot be obtained if this virtual machine is protected by installed agent, which results in the mapping failure between this virtual machine and the installed agent. Workaround: Change the protection mode to agentless mode for virtual machines protected in Rapid Recovery Core Server. |
The following Foglight product versions and platforms are compatible with this release.
|
Product Name |
Product Version |
Platform |
| Foglight Management Server | 5.9.4 | All platforms supported by this version of the Foglight Management Server |
| Foglight Agent Manager | 5.9.4 | All platforms supported by this version of the Foglight Agent Manager |
| Foglight For Virtualization, Enterprise Edition | 8.8 8.8.5 |
All platforms supported by these versions of Foglight For Virtualization, Enterprise Edition |
For information about system requirements for this release, see the corresponding Foglight System Requirements and Platform Support Guide.
Compatibility with Rapid Recovery and Veeam:
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.
| Minimum CPU | Minimum Memory | Minimum Host Memory | Total machines protected by Rapid Recovery | |
| Windows 64-bit |
1 |
2.5 GB |
3 GB |
100 |
| Linux 64-bit |
1 |
2.5 GB |
3 GB |
100 |
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.
| Minimum CPU | Minimum Memory | Minimum Host Memory | Total machines protected by Veeam | |
| Windows 64-bit |
1 |
2.5 GB |
3 GB |
400 |
| Linux 64-bit |
1 |
2.5 GB |
3 GB |
400 |
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 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.
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:
| Up to 100 machines |
1 CPU |
| 100+ machines |
add 1 CPU per 100 machines – round up when necessary |
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 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.
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:
| Up to 400 machines |
1 CPU |
| 400+ machines |
add 1 CPU per 400 machines – round up when necessary |
| # of protected machines | Memory* Foglight JVM settings |
# of CPUs |
| 100 |
Xms|Xmx=1G |
1 |
| 500 | Xms|Xmx=4G | 5 |
| 1000 | Xms|Xmx=8G | 10 |
* 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.
| # of protected machines | Memory* Foglight JVM settings |
# of CPUs |
| 400 |
Xms|Xmx=1G |
1 |
| 1000 | Xms|Xmx=2G | 3 |
| 2000 | Xms|Xmx=4G | 5 |
* 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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
