ID: 13257

Print Friendly, PDF & Email

Managing Hubs in Zoom

The Hub Server handles archive/restore processes for Zoom version 7.3 onwards when configured as part of a Hierarchical Archive system on Zoom.

It needs to be configured on Zoom first and also installed on a server machine later. The Hub Server’s configuration can be managed through Zoom’s Web Management Console. This guide will cover:


Zoom stores Hub configuration to connect with a Hub Server. These configuration values should be added to Zoom before installing the Hub Server.

Log in to the Web Management Console and click the Hub Settings Panel under the System node in the Admin Menu sidebar.


On the Hub Settings Panel, click Add Hub and specify a name for the new Hub. Click Add.

You can also select an existing hub from the list and its settings are loaded in the Hub Settings Panel. When a Hub is selected in the Hub box, click Delete to delete that Hub. Select Yes to confirm the deletion.
For Zoom 7.3, while using multiple Hubs in a multi-location Zoom setup, when you want a Hub to only work for one location then you should name the Hub as that location.

Update the basic connectivity details for the hub, like Host and Port settings. For location-specific settings, also specify the location where the Hub should work.

Once the basic connectivity parameters are specified, enter values for the advanced configuration. It is categorized into two parts namely the Functional Configuration and the Archive/Restore Configuration. See the sections below to know about the values that should be entered for these:

If you are configuring Hub for AI, only Database Spec and Client Whitelisting Settings under Functional Configuration are needed to be set here.


Functional Configuration



Process Control

These are configuration parameters that control how responsive the hub will be and must be filled in based on your assessment of the expected load that the hub is expected to handle. If you are unsure about these then use the default values. 

  • Core Pool Size: Minimum number of threads that will be created by default for job execution.
  • Max Pool Size: Maximum number of threads that can be created for job execution.
  • Queue Blocking Limit: Number of jobs that can be queued in the Hub for processing. 
  • Keep Alive Time: Duration (in minutes) for which resources are kept when the Hub is not servicing any requests; after this duration, the resources are surrendered. 
  • Max Retry Count: Number of times the failed jobs are retried automatically. 
  • Enable Hub Analytics: Flag to turn on or off the Analytics module on the Hub. 


Database Spec

The Zoom Server uses SQL for some of its other modules too. If it is already configured and you would like to use the same SQL database for the Hub as well, then simply select the Copy from Zoom option. If you want to create a new or separate SQL database for the Hub, then follow here to download your OS-specific installer of MySQL. Run the installer and follow the instructions. Create a user and provide the host, username, password, driver (com.mysql.cj.jdbc.Driver) details here.


Client Whitelisting Setting

Here, you can add the list of IPs from which Hub will entertain requests.

Typically, the Zoom Server sends requests to the Hub. In addition, anyone viewing the Hub Dashboard will also be sending queries and so the IPs of all clients who would need access to the Hub Dashboard must also be added here.

If this is left blank, then the Hub will service requests from all client machines.

Archive/Restore Configuration

In this section, the details of all destination tiers are added.

All the paths should be with respect to the Hub Server.

FS Tier 1

  1. Default: Comma-separated list of TPM (Third Party Mount point) paths whose assets are expected to be archived using the current Hub.  
  2. Direct Asset Archive DB Mount Path: The default location where the Zoom Server archives the direct-ingest assets to. 
  3. Project-wise TPM Mapping: Project-specific archive destination locations as configured in the Zoom Server archive settings. 

FS Tier 2

  1. Default: Comma-separated list of TPM paths whose assets are expected to be archived using the current Hub.  
  2. Project-wise TPM Mapping: Project-specific archive destination locations for tier-2 archive

S3 Tier 2

Enter the details of the Amazon S3 bucket like the secret key, access key, and region. Here it is also possible to define unique S3 buckets for specific Zoom projects. For projects not assigned a unique bucket, the default one will be used. 

Click Save Hub after configuring the necessary details across various panels.


Any change in the Hub settings made via the Web Management Console requires the Hub to be restarted to take effect. Restart the Evolphin Job Hub service to see the changes.
Please be very careful when you try to edit the TPM paths or the Tier details. If you archive assets to a certain S3 bucket or a file-system location, and the configuration is changed after that then there is no way of accessing these assets from the previously-stored location. Thereafter, any attempt to restore assets from the lost configuration will fail with a data loss error. This will not be able to be corrected without a significant amount of manual intervention and copying of data. 



The Hub has a dashboard to track and monitor archive/restore jobs and it is accessed from Zoom’s Web Management Console.

After your Hub is set up and all archiving parameters defined, you can view the archive/restore jobs’ progress in the Hub Dashboard inside the Web Management Console. Log in to the Web Management Console and click the Hub Settings Panel under the System node in the Admin Menu sidebar.

On the Hub Settings Panel, select a hub from the Hub drop-down and click Dashboard.

The Hub Dashboard opens with a list of all recent jobs with details about each of those jobs. 


You can filter the jobs based on the type of job as shown here.


You could also filter based on submitted Data, Finish Time, Job Status and the user who invoked the request.

Job Details

To view the list of assets that are part of a job, double-click on the row for that job. This detailed view also shows the individual file-level status and relevant times like the status change times. 

Process Control

From the Dashboard you can Pause/Resume, Cancel/Resubmit, Resolve, Delete a job or some of its assets. 


A more detailed log is maintained and is available for viewing as well as downloading from the Logs tab in the dashboard.