Zoom Node Service Module Deployments

The following section provides deployment steps for the various Zoom Node Service Modules.

Service Module Deployment: Zoom Meetings Hybrid

Zoom Meetings Hybrid requires at least one Hybrid Meeting Zone to be created. The Hybrid Meeting Zone is anchored to a Zoom Hybrid Datacenter, which is typically selected to be the closest to the geographical area being served by the hybrid zone.

1. Create a Hybrid Zone and select a Data Center Region for the zone to be homed to.

2. From Zoom Node > Nodes (on the ribbon menu), select Meeting Zone from the menu bar:

1. Click + Add Meeting Zone to create a Hybrid Meeting Zone.

2. Enter a name for the Meeting Zone.

3. Click the Zoom Data Center drop-down list and select the appropriate data center region.

4. Click Confirm.

Hybrid Zone Controller Proxy (ZCP) Installation

1. Click the Services menu option in the Zoom Node ribbon to be sent to the service-level view.

1. Click Add Services to begin the installation process of Hybrid Meeting Services.

1. Select Hybrid Zone Controller Proxy to install this component.

1. Choose the Zoom Node server that you deployed in the previous section to install the Hybrid ZC Proxy service.

2. Select which certificate enrollment method you would like to use.

   1. Zoom Auto-PKI is recommended.

3. Define the primary IP address of the Zoom Node.

   1. This will auto-populate when you click the box.

4. Click Add.

Zoom Node will begin deployment of the Hybrid Zone Controller Proxy service.

Please wait at least 1 minute for the Zone Controller Proxy service to install and auto-enroll its certificates. You can disregard any error messages shown next to the Installed Status during the installation wait time.

After the service is deployed, the status will change from Installed to Stopped. After waiting for at least a minute, you will need to click refresh to see the status change.

Next, click the Start button to enable the new Hybrid Zone Controller Proxy and see the process status.

(Optional) Click the Hybrid Zone Controller Proxy name to see the attributes of the new Zone Controller Proxy. Then, click the Edit button on the right-hand side of the screen to change the Service Name. After making any changes, click Save to change the name.

For a production deployment, install a second Hybrid Zone Controller proxy on a separate Zoom Node VM by repeating these instructions.

Hybrid Multimedia Router (HMMR) Installation

Next, you can add a Hybrid Multimedia Router (HMMR) by performing the same process as the previous Hybrid ZC Proxy section, but you'll choose Hybrid Multimedia Router instead.

To install the HMMR service:

1. Choose the Zoom Node server where you just deployed the Hybrid ZC Proxy service.

2. Choose the Meeting Zone this HMMR serves.

3. Select which certificate enrollment method you would like to use.

   1. Zoom Auto-PKI is recommended.

4. Choose one of the secondary IP addresses assigned to the Zoom Node.

   1. This will auto-populate when you click the box.

5. Click Add.

Zoom Node will begin deployment of the HMMR service.

Please wait at least 1 minute for the HMMR service to install and auto-enroll its certificates. You can disregard any error messages shown next to the Installed Status during the installation wait time.

Once the service is installed, it status will be Stopped.

Click the Start button to activate the HMMR service.

To increase scale, follow this same process again and deploy a second Hybrid MMR on the second Zoom Node.

Enable Users to use Hybrid Meeting Services

Return to the Zoom Admin portal and navigate to Account Management > Account Settings > In Meeting (Advanced) and scroll down to the Use hybrid services for meeting hosts and participants option.

Enable the option slider and select which hybrid meeting zone you deployed your Zone Controller Proxies to.

Testing the Hybrid Meeting Service

From an account defined on the test Zoom instance, start a meeting and join from a few clients that have internal L3 connectivity and low latency to the Zoom Node.

Proxy Interactions and Security

Zoom Node OS supports proxy server communications for its non-media functions, including certificate enrollment and Zoom Node management traffic. However, all media traffic must transit directly to Zoom’s cloud, bypassing any applicable proxies.

Service Module Deployment: Meeting Survivability

Zoom Node Meeting Survivability introduces Survivable Zones, logical groupings of infrastructure components enabling uninterrupted communication during network emergencies.

A Region contains one or more Survivable Meeting Zones (SMZs), comprising Survivable Zone Controllers and Hybrid Multimedia Routers for resilient meeting hosting. Within an SMZ, Survivable Multimedia Routers route media traffic. Users join meetings in a Survivable Zone using the same Zoom Workplace app and a Survivable Meeting URL, allowing continued meetings even without internet. This organization helps ensure critical meetings continue despite network outages.

Survivable Zone Mapping:

• Region (contains SMZs)

• Survivable meeting zone (contains survivable zone controllers)

• Hybrid Multimedia Routers

• Survivable meeting URL

• Zoom Workplace app

At the initial launch of this feature, Zoom Meetings Local Survivability requires a unique Zoom Node for each of the five (5) components. As these services require minimal resources, the VM settings can be reduced from the default Zoom Node OVA/QCOW2 configurations. The vCPU count may be adjusted down to three (3) vCPUs, and RAM can be reduced to 8 GB.

Defining Survivability Zones

A minimum of one (1) Survivability Zone must direct the Zoom Workplace app to survivability resources. A Survivability Zone may service multiple Hybrid Meeting Zones.

To define these zones:

1. Browse to the Zoom Admin Portal.

2. Select Node Management > Modules.

3. Click Nodes at the top of the screen.

4. Click Survivability Zones.

1. Click Add Survivability Zone on the left-hand side of the screen.

2. Enter a name.

1. Click the Survivability Zone drop down and select the Survivability zone that was just created.

2. Using the drop-down lists, select one or more hybrid Meeting Zones to provide survivability for.

Deploying Survivability Components

Next, you’ll need to deploy five (5) Zoom Node VMs.

Each Node requires only one IP address, as each runs a single module. Refer to the Deploying a Zoom Node management server guide on Zoom Support for further details.

Installing Zoom Node Modules

After deploying the Meetings Hybrid modules (Zone Controller Proxy and Hybrid Multimedia Routers), there remain five (5) required components to deploy Meeting Survivability.

The following components provide the survivable infrastructure that will be used in the event of an outage:

1. Survivability Database: Provides persistent storage for survivability components.

2. Survivability Load Balancer: Distributes incoming traffic across multiple web servers to provide high availability and scalability.

3. Survivability Secret Agent: CSMS (Credential Store and Management Service): Securely stores and manages all sensitive credentials and secrets used within the Meeting Survivability zone.

4. Survivability Web Server: Manages Meeting Survivability settings and communicates with clients).

5. Survivability Zone Controller: Directs clients to existing HMMRs for meeting operation.

The Add Service menu in the Zoom Admin portal allows you to add these components. Note that each of these components is available under the Meeting Survivability header. The next steps of this guide will have you install all of the components shown in the following screenshot:

The Survivability Database component is first. The Add Database dialog window appears. After selecting the right Node, Survivability Zone, and naming the new database, you’ll add the load balancer.

Next, you’ll install the Survivability Load Balancer component.

Once added, you must wait for these components to install and start. Once you see the components as active and started, you can continue with the other component installations.

Next is the Survivability Secret Agent, which is also under the Add Service menu in the Zoom Admin portal.

Continuing on, you’ll next install the Survivability Zone Controller.

The next component to install is the Survivability Web Server.

The User Name and Password you’ll enter are for the administrator to manage and enable Survivability. Save and keep these credentials: you will use them later in this guide.

These components will typically start automatically. If one fails to do so, you will need to troubleshoot that specific service before continuing.

Manually starting the services requires a particular order. Start the services in the following order:

1. Survivability Database (3306)

2. Survivability Load Balancer (443)

3. Survivability Secret Agent (443)

4. Survivability Web Server (8080)

5. Survivability Zone Controller (443)

Once all services are active and running, the Hybrid Meetings section should look similar to following image:

DNS Configuration for Survivability

In order to ensure the Zoom Workplace app can connect to survivable resources in the event of a network outage, Zoom Meetings Local Survivability requires that each meeting service be reachable via a locally resolvable DNS hostname.

Zoom's Auto PKI service automatically enrolls Zoom Node, and all modules deployed on it, with valid publicly trusted Certificate Authority (DigiCert) certificates.

Zoom Node modules register with Zoom's zoomonprem.com domain for this process. Normally, Zoom handles all DNS records on behalf of our customers when using a Zoom-managed domain.

However, during a network outage, the public DNS may not be reachable to resolve these hostnames. Hostname resolution is mandatory to ensure TLS negotiation and secure communications between clients and survivability components.

It is essential that these hostnames are resolvable on your local DNS server to enable communication with each service during an outage. Meeting survivability will not work without proper DNS resolution.

To enable internal Zoom Workplace app instances to resolve hostnames during an outage, you must create a self-hosted <customervanitydomain>.zoomonprem.com domain in the local DNS server, along with the necessary A records.

The following services require a unique DNS entry:

• All HMMR modules

• Survivability Database

• Survivability Load Balancer

• Survivability Web Server

• Survivability Secret Agent

• Survivability Zone Controller

The following is an example of what these DNS entries might look like:

```private-fa4dfs828ds8f2321d8311.customer.zoomonprem.com```

Zoom Node uses these hostnames to connect with each service, even in the absence of a public internet connection. These hostnames are generated during the dynamic registration of certificates for each Zoom Node service and cannot be changed afterward.

You can find the DNS hostnames required in your organization's Zoom Node admin portal, which you can reach by connecting to https://zoom.us/node/home in your browser.

In the following example, there are two (2) HMMRs and the five (5) survivability components, which you installed during the last section.

An export function is available to export all necessary records.

To use it: Select all records by clicking the check box next to the Service column. A new button, Download DNS Record will appear.

Click the button to download the records in a text file.

The text file will look similar to the following example:

Now you must create a record for each entry in the DNS record list.

If each service's DNS entry does not match the assigned Zoom Node certificate, you may see the following error when joining a meeting or browsing to a scheduled meeting:

This tells you that DNS resolution is not operating properly. Ensure that all records are in the local DNS.

Enabling Services at Account/Group/User Levels

After deploying and starting the survivability components, configuration can be completed in the Zoom admin web portal. This enables survivability at three levels: the entire account, the group (beneficial for multiple Survivability Zones in different geographies), or the individual user (useful for testing).

To enable meeting survivability at the account level:

1. Browse to Account Management > Account Settings > Meeting > In Meeting (Advanced).

2. Using the drop down, select the Survivability Zone to use for the account.

3. Click the toggle button next to it to enable it.

1. (Optional) To enable meeting survivability at the group or user level, browse to the same setting within the Group or User level and repeat the previous steps.

Service Module Deployment: Zoom Recording Hybrid

Zoom Recording Hybrid (ZRH) is a key companion function to Zoom Meetings Hybrid (ZMH). It supports two recording modes:

• Zoom Meetings Hybrid - Private Mode Meeting Recording

• Zoom Meetings Hybrid - Hybrid Mode Meeting Recording

The Zoom Recording Hybrid module comprises five services with varying uses:

• Meeting Recorder: Records Private Mode meetings through joining the on-premises Hybrid MMR. Meeting media and recordings stay within your network.

• Hybrid Transfer Service: Transfer your meeting recordings from Zoom’s cloud to on-premises NFS storage.

• Content Streamer: Enables on-demand playback by streaming meeting recordings directly to the Zoom Workplace app. Users can access their local recordings through a browser.

• Streamer Load Balancer: Load balance traffic between one or more Content Streamers. This component is required when a Content Streamer is deployed.

• Meeting Archiver: Performs on-premises compliance archiving of meeting recordings for users assigned this functionality.

Zoom Meetings Hybrid - Private Mode Meeting Recording

Private Mode Meetings keep meeting media and signaling on-premises. All meeting participants are connected directly to meeting resources running within the customer premises, without the possibility of users joining the meeting through Zoom’s cloud resources.

The Zoom Recording Hybrid - Meeting Recorder service joins this meeting directly to record a meeting. The meeting media path and recording data stay within your organization’s network. Once the meeting concludes, the recording is queued to be transcoded and delivered to your provided NFS storage.

Zoom Meetings Hybrid - Hybrid Mode Meeting Recording

Zoom Meeting Hybrid processes meeting media locally for on-premises users and allows external users to join meetings through the Zoom cloud. The meeting media is cascaded between Zoom’s cloud MMRs and the on-premises hybrid MMRs. Zoom’s cloud-delivered services, such as AI Companion, captions, transcription, and cloud recording, are available for this type of meeting.

Meeting recording and transcoding functions are performed in the Zoom cloud for Hybrid Mode meetings. The Zoom Recording Hybrid - Hybrid Transfer Service is deployed on Zoom Node to facilitate relocating meeting recordings to your NFS storage.

Hybrid Meeting Archiver

Zoom’s meeting archival solution is typically deployed in compliance-driven scenarios where it is mandated that all meetings a particular user participates in are automatically recorded and archived. Unlike meeting recording, where a meeting host may stop or start the recording as they wish, meeting archival records and archives the entire meeting. A user assigned meeting archival functionality does not interact with meeting archival functionality at all.

The Meeting Archiver Service relocates meeting archives from the Zoom cloud to your NFS storage.

Deploying Recording Hybrid Services

The meeting types you want to record locally will determine which services need to be deployed.

• To record Private Mode meetings, deploy the Meeting Recorder.

• To record Hybrid Mode meetings, deploy the Hybrid Transfer Service.

• To allow your users to play their recordings back, deploy the Content Streamer and Streamer Load Balancer.

• To relocate meeting archives from Zoom’s cloud to your on-premises NFS storage, deploy the Meeting Archiver service.

If you were to deploy all five (5) services for a minimal deployment, you would need 1–2 Zoom Node VMs (one for the Meeting Recorder if doing Private meeting recording), and another for the other components. Additional Nodes may be required for additional system capacity.

Determine which services you need to deploy for your organization’s requirements. Typical customer deployments care about ensuring that Private mode meeting recordings stay inside the organization. In this scenario, the Meeting Recorder, Content Streamer and Streamer Load Balancer would be deployed.

Each Meeting Recorder must be installed on its own Zoom Node VM as that service uses all the capacity of the Node, and no other services may be deployed on it.

The Content Streamer and Streamer Load Balancer can be installed coresidently on a single Zoom Node VM.

Zoom Node VM Sizing - Private Mode

It is important to understand how many concurrent meetings you will be recording since recording media and transcoding it is a compute-intensive process and sufficient hardware resources must be allocated.

The default Zoom Node VM size (8 vCPU, 16GB RAM, 200GB HDD) provides enough resources to handle 10 simultaneous recordings and 2 transcodes.

For both standard and minimum VM hardware specifications, see the Virtual Machine Hardware Specifications section of the Zoom Node Infrastructure Prerequisites page.

Recording is the real-time process that receives meeting media and must have adequate CPU processing power to operate.

Transcoding is performed after the meeting to render an h.264 video. This process does not need to happen real-time and recordings will be queued for transcoding if there is no current capacity available.

Determine how many concurrent meetings you will be recording. If you are only recording Private mode meetings, ensure you are looking at the concurrent number of these types of meetings.

Please see the following chart to determine if you need 20 or 30 concurrent meeting recordings. You'll need to manually adjust CPU and RAM settings for the VM as shown:

Configuring a Recording Zone

A Recording Zone supports one or more hybrid Meeting Zones as the recording pool for those meeting zones.

1. Browse to the Zoom admin portal.

2. Select Node Management > Modules > Nodes > Recording Zones.

1. Click the Add Recording Zone button.\

   
2. Make the following selections:

   1. Choose the Zone Name.

   2. Click the Zoom Data Center drop down and select the relevant data center.

   3. Enter the NFS server in the NFS Server IP / FQDN text box.

   4. Add the NFS path in the NFS Path text box, which is where recordings will be stored.

Deploying the Meeting Recorder service for Private Mode meetings

To deploy the service:

1. Browse back to the Node Management dashboard.

2. Select Node Management > Modules > Services.

3. Click Add Services.

4. Click Meeting Recorder.\

   
5. Under Install on a node, select the server you want to deploy the service on.

6. Under Recording Zone, select the assigned zone for the Meeting Recorder.

1. Click Advanced Settings to configure additional settings for the Meeting Recorder service:

   1. Under Concurrent Recording Count, set the maximum number of meetings that can be recorded at one time.

   2. Under Concurrent Transcoding Count, set the maximum of recordings that can be transcoded at one time.

1. Click Add.

Deploying the Streamer Load Balancer service

To deploy the load balancer:

1. Browse back to the Node Management dashboard.

2. Select Node Management > Modules > Services.

3. Click Add Services.

4. Under Recording Hybrid, click Streamer Load Balancer.

5. Under Install on a node, select the server you want to deploy the service on.

6. Under Recording Zone, select the zone you want the service assigned to.

1. Under Internal IP, enter the internal IP configured for the service.

2. (Optional) Under Advanced Settings, you can optionally enable:

   1. Allow external access (NAT Mode): Enable to enable network address translation and allow external users to join meetings.

1. Click Add.\

   

Deploying the Content Streamer service

To deploy the streamer service:

1. Browse back to the Node Management dashboard.

2. Select Node Management > Modules > Services.

3. Click Add Services.

4. Under Recording Hybrid, click Content Streamer.

5. Under Install on a node, select the server you want to deploy the service on.

6. Under Recording Zone, select the zone you want the service assigned to.

1. Under Internal IP, enter the internal IP configured for the service.

2. (Optional) If desired, update the SSL port (default is 443).

3. Click Add.\

   

Once running, the Content Streamer is seamlessly invoked when playing back Meeting Recordings from Zoom's cloud recording web interface. The playback URL in the cloud will point to the Streamer Load Balancer which uses the Content Streamer to play back the recording from NFS storage.

Deploying the Hybrid Transfer service

To deploy the transfer service:

1. Browse back to the Node Management dashboard.

2. Select Node Management > Modules > Services.

3. Click Add Services.

4. Under Recording Hybrid, click Hybrid Transfer service.

5. Under Install on a node, select the server you want to deploy the service on.

6. Under Recording Zone, select the zone you want the Meeting Recorder assigned to.

1. Click Add.

The Hybrid Transfer service component will begin the installation. Once complete, the service Status will be Stopped. Next to the newly deployed service, click Start.

The service Status will update to Running.

Deploying the Meeting Archiver service

To deploy the archiver service:

1. Browse back to the Node Management dashboard.

2. Select Node Management > Modules > Services.

3. Click Add Services.

4. Under Recording Hybrid, click Meeting Archiver.

5. Under Install on a node, select the server you want to deploy the service on.

6. Under Recording Zone, select the zone you want the Meeting Recorder assigned to.

1. Click Advanced Settings to configure additional settings for the Meeting Archiver service:

   1. Under Concurrent Archiver Count, set the maximum number of meetings that can be recorded for archiving at one time.

   2. Under Concurrent Archiver Count, set the maximum of recordings that can be transcoded for archiving at one time.

1. Click Add.

The Meeting Archiver service component will begin the installation. Once complete, the service Status will be Stopped. Next to the newly deployed service, click Start.

The service Status will update to Running.