• High Availability And Backup

    In the following article we all review our solution modules and the options for high availability and backup.

     

    ControlUp's Cloud Solution:

    The Entire Solution has High-Availability since most configurations and Insights Data are saved in the Cloud.

     

    ControlUp Real Time Console:
    Backup: For saving Personal’s user configuration such as Draft SBAs, Columns views, credentials set etc.
    You should backup the folder: C:\Users\<user>\AppData\Roaming\ControlUp.

    High Availability: The Console is by design has high availability feature by storing all configuration in the cloud or local directory services on the on-premise server.

    ControlUp Monitor:
    Backup: For saving the monitor's settings, backup folder -C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming

    High Availability: Install 2 Monitors, select the Primary Monitor, once the Primary fails, the 2nd monitor will automatically take over.

     

    ControlUp's On-Premises Solution:

    ControlUp On-Premises Server:
    Backup: Since the ControlUp server machine stores the LDS & IIS in addition to the CU server service, the only way to fully back it up is to create an image (using MS built in tool, Acronis or any other software).

    High Availability: We recommend using a Network Load Balancer with PVS, You can read more about it here.

    ControlUp's SQL DB:
    Backup: Use Microsoft’s recommendations on Backup SQL DB from Here.

    High Availability: Use Microsoft’s recommendations on how to make it HA from Here.

    ControlUp's On-Premsies Console + Monitor:
    Same as Online mode, backup the relevant folders is a must.

    IOP (Insights On-Premises):

    Backup: Backing up the Activity Files folder (It has to be a SMB share) will be enough for recreating the Historical Reporting, so if the Share is backed up regularly it is good, other solution could be using DFS or even Robocopy it to a location that is backed up on a regular basis.

    High Availability: Create an Image of the IOP machine or just install IOP on a fresh machine and check our KB afterwards - Adding Insights On-Premises IOP Module

  • Performance optimization for ControlUp's Real-time Console & Monitor

     

    In medium and large environments, the ControlUp Real Time Console administrator can optimize the performance of the console and the monitor.

    Here are few optimizations that can be applied, according to your needs (displayed in the table and detailed blow):

     

    Optimization Name Console Monitor
    Disable Process Flat Views  
    Increase Data Collection Cycle
    Dedicated Data Collectors
    Optimize Auto Connection Settings  
    Exclude Folders From Monitor  
    Disable Console Incidents Processing  

     

     

    1. Disable Flat Views:

    By default, the console offers 7 different views - Folders, Hosts, Computers, Sessions, Processes, Accounts and Executables.

    In large environments, the Processes view may cause high resource consumption during the operation of the console, mainly due to the high total number of processes the console monitors (summary of all processes running on all monitored resources).

    In such cases it is advised to disable the flat views and still monitor the processes, by drilling down Computer-> session-> processes or Computer-> Processes, as shown in the below screenshots.

     

     

    In order to disable the "Processes Flat Views", go to Settings -> Advanced Settings, as displayed in the following screenshot.

     

     

    Once you disable the processes flat view, those views will be grayed out, as displayed in the following screenshot.

     

     

     

    2. Increase the data collection cycle and regulate the information updates:

    By default all ControlUp agents push information updates to the console every 3 seconds. 

    The update interval can be configured by the ControlUp Admin, so the ControlUp Console will pull the information from the agents in set intervals. In addition you can set the number of computers the console connects to concurrently.

    To increase the data collection cycle and change the updates intervals, go to Settings -> Advanced Settings, as shown in the screenshot below.

    We recommend increasing the Console \ Monitor interval to 30 or 60 seconds.

     

     

    The ControlUp Monitor’s update intervals can also be configured by the ControlUp admin via the Monitor Settings.

     

     

      3. Setting up a dedicated Data Collector:

    By default every console and monitor connects to the hypervisor or to the XenDekstop broker.

    In large environments where multiple consoles and monitors are running, the best practice is to create a relay or a data collector so you have a single point of hypervisor\XD data collection.

    To define a data collector, right click on the hypervisor\XD and choose Connection Settings.

     

     

     

    Then go to Connection Options -

     

     

    Please remove the Console / Monitor and choose one of the agents to be the data collector -

     

     

    Now LVSITARGET03 will collect the data and all Consoles and Monitors will connect to that agent to retrieve hypervisor performance data - 

     

     Here is a screenshot of the XenDesktop connection properties and where to change the data collector -

     

    4. Optimize Auto Connection Settings:

     

    You can have the console automatically connect to disconnected computers. Once a computer gets disconnected for any reason, the console will try to contact that end point.

    To enable this feature: As seen in the below screenshot, under the organization tree, check the "Show Auto-Connect State" and check the computers you would like ControlUp to automatically connect to.

    This feature will also enable the console’s automatic connection immediately upon launching the console.

     

     

    The reconnect interval time can be configured by the ControlUp admin.

    To define the interval go to Settings -> Agent Settings as displayed in the following screenshot.

     

     

    In large environments, if all computers are set to auto connect, this may extend the console launch process, so please mark only important servers or folders to automatically connect.

     

    5. Excluding folders from the Monitor

     

    By default all folders, hypervisors and computers are monitored by the Monitor. You can reduce the monitored resources in order to optimize the Monitor performance.

    To exclude any resource, right click it and choose properties, and then "Exclude from Controlup Monitor" = Yes.

     

    6. Disable Console Incidents Processing:

     

    Once you add a monitor, the monitor is responsible for all your incidents collection and trigger alerts notifications. Having said that, the console still processes and collects all incidents in parallel to the Monitor.

    In order to disable the incidents collection and free up console resource consumption, open regedit.exe on the machine running the console and go to - HKCU\Software\Smart-X\ControlUp\Console and create a DWORD with Value name DisableIncidents, with value data = 1 

    That will disable the incidents collection and optimize the perfirmance.

     

     

     

  • Console performance issue / high RAM consumption

    The Issue:

    The Real Time Console performance is slow and the RAM consumption is high.

     

    The Reason:

    There are 2 distinct culprits for console performance issue / high RAM consumption 

    1. High rate of Windows events being reported to the Console
    2. A large amount of performance updates that are sent to the Console

     

    The Solution:

    Please try each of the following fixes separately:

    1. High rate of events – please go to Settings –> Events Settings –> Event Type and uncheck all 3 checkboxes. Click on OK to apply and restart the console process (this will disable Windows Events collection on the agent side)

     

    2. High rate of performance updates – please go to Settings – Advanced Settings and check the “Disable process flat views” checkbox (see attached screenshot). This will disable the Processes flat view

  • How to prevent vCenter excessive logging

    Issue Description - 

    When monitoring host environment, there is logging activity made by ControlUp. In some cases it might cause the ESX logs to grow.

     

     

    Cause Description - 

    ControlUp Console \ Monitor login to the vCenter and retrieve the hypervisor information and then logs out. The login \ log out process takes place about every 5 seconds.

     

    Solution Description - 

    You can change the connection to the hypervisor to be persistent.

    To define persistent connection to the hypervisor, first define a data collector:

    1. In the ControlUp Console please right click the hypervisor and choose Connections settings

    2. By default any ControlUp Console / Monitor will connect to your hypervisor. To save the bandwidth you can setup a relay or data collector.

    Please remove the Console / Monitor and choose one of the agents to be the data collector.

     

    Now LVSITARGET03 will collect the data and all Consoles and Monitors will connect to that agent, to retrieve hypervisor performance metrics data.

     

     

    3. Set a persistent connection between the agent and the hypervisor, by editing the registry of the agent's endpoint and creating the following key - 

    HKLM\SOFTWARE\Smart-X\ControlUp\Agent\vmDataCollector

    Then create a new DWORD value named vCenterPersistentConnection and set the value to 1 (0 = default mode / 1 = persistent mode)