Quest® Protect Dashboard 6.1.0
Developed for Foglight Management Server 6.1.0 / Foglight Evolve 6.1.0
Release Notes
April 2022
Welcome to Foglight Quest Protect
Resolved issues and enhancements
Getting started with Quest Protect Dashboard
Quest® Protect 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. Quest Protect reduces hardware and licensing costs by proactively predicting and budgeting for capital expenditures, protects growing virtual environments automatically, and recovers from data loss or corruption in minutes with zero impact on your users, as if the outage never happened.
These Release Notes cover the resolved issues, known issues, workarounds, and other important information about the 6.1.0 release of Quest Protect Dashboard. Review all sections before starting installation.
This 6.1.0 release of Quest Protect Dashboard accompanies the release of Foglight Evolve 6.1.0. This release does not include any resolved issues or enhancements.
This 6.1.0 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. |
|
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. |
|
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: |
|
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. |
The following Foglight product versions and platforms are compatible with this release.
|
Product Name |
Product Version |
Platform |
|
Foglight Management Server |
6.1.0 |
All platforms supported by this version of the Foglight Management Server |
|
Foglight Agent Manager |
6.1.0 |
All platforms supported by this version of the Foglight Agent Manager |
|
Foglight Evolve |
6.1.0 |
All platforms supported by this version of the Foglight Evolve |
For information about system requirements for this release, see the corresponding Foglight System Requirements and Platform Support Guide.
Compatibility with Rapid Recovery and Veeam:
Agent account privileges for 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 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.
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 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.
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.
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:
Quest Protect Dashboard 6.1.0 is a software release, and consists of the .car file required for installation on the Management Server and the necessary documentation.
The Quest Protect Dashboard release package contains the following products:
1. Quest Protect Dashboard version 6.1.0
2. Product Documentation, including:
Quest Protect Dashboard 6.1.0 comes pre-installed on Foglight Evolve 6.1.0. Quest Protect Dashboard can be installed on the Foglight Management Server versions listed in the Upgrade and Compatibility section.
To install Quest Protect Dashboard:
Additional information is available from the following:
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
This release has the following known capabilities or limitations: This release is only localized for English but does support the Unicode character set.
Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit https://www.quest.com/.
Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.
The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:
Quest, the Quest logo, Foglight, and Where next meets now are trademarks and registered trademarks of Quest Software Inc. in the U.S.A. and other countries. For a complete list of Quest Software trademarks, please visit our website at www.quest.com/legal. Red Hat, JBoss, the JBoss logo, and Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the U.S. and other countries. CentOS is a trademark of Red Hat, Inc. in the U.S. and other countries. Fedora and the Infinity design logo are trademarks of Red Hat, Inc. Microsoft, .NET, Active Directory, Internet Explorer, Hyper-V, Office 365, SharePoint, Silverlight,SQL Server, Visual Basic, Windows, Windows Vista and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. AIX, IBM, PowerPC, PowerVM, and WebSphere are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Java, Oracle, Oracle Solaris, PeopleSoft, Siebel, Sun, WebLogic, and ZFS are trademarks or registered trademarks of Oracle and/or its affiliates in the United States and other countries. SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries. Products bearing the SPARC trademarks are based on an architecture developed by Oracle Corporation. OpenLDAP is a registered trademark of the OpenLDAP Foundation. HP is a registered trademark that belongs to HewlettPackard Development Company, L.P. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Novell and eDirectory are registered trademarks of Novell, Inc., in the United States and other countries. VMware, ESX, ESXi, vSphere, vCenter, vMotion, and vCloud Director are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Sybase is a registered trademark of Sybase, Inc. The X Window System and UNIX are registered trademarks of The Open Group. Mozilla and Firefox are registered trademarks of the Mozilla Foundation. IOS is a registered trademark or trademark of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries. Apple, iPad, iPhone, Mac OS, Safari, Swift, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries. Ubuntu is a registered trademark of Canonical Ltd. Symantec and Veritas are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. OpenSUSE, SUSE, and YAST are registered trademarks of SUSE LCC in the United States and other countries. Citrix, AppFlow, NetScaler, XenApp, and XenDesktop are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. PostgreSQL is a registered trademark of the PostgreSQL Global Development Group. MariaDB is a trademark or registered trademark of MariaDB Corporation Ab in the European Union and United States of America and/or other countries. Intel, Itanium, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and/or other countries. Debian is a registered trademark of Software in the Public Interest, Inc. OpenStack is a trademark of the OpenStack Foundation. Amazon Web Services, the "Powered by Amazon Web Services" logo, and "Amazon RDS" are trademarks of Amazon.com, Inc. or its affiliates in the United States and/or other countries. Infobright, Infobright Community Edition and Infobright Enterprise Edition are trademarks of Infobright Inc. POLYCOM®, RealPresence® Collaboration Server, and RMX® are registered trademarks of Polycom, Inc. All other marks and names mentioned herein may be trademarks of their respective companies.