Loading...

Edge Endpoint Solutions Architecture Planning Guide

This Architecture Planning guide illustrates how to plan and design an environment for endpoint laptop and desktop protection. Proper design and planning will result in optimal performance and the scalability required to protect your environment with minimal infrastructure.

Design Considerations

Use the following table to determine the number and size of the CommServe system and MediaAgent required to protect your environment.

If you have

CommServe

MediaAgent

Web Server*

Web Console*

Proxy*

Up to 500 clients or 25 TB

1 Medium

1 Small

1

1

1 per MediaAgent

Up to 3,000 clients or 50 TB

1 Medium

2 Medium

1

2

1 per MediaAgent

Up to 10,000 clients or 100 TB

1 Large

4 Large

1

2

1 per MediaAgent

More than 10,000 clients or 100 TB

1 Extra Large

2 Extra Large for standard mode or extended mode

1

2

1 per MediaAgent

More than 50,000 clients

2 Extra Large

2 Extra Large for standard mode or extended mode

2

2

1 per MediaAgent

* See additional considerations below for the Web Server, Web Console, and Proxy components.

For more information on hardware requirements for your environment, see CommCell Sizing.

Web Server and Web Console Considerations

These considerations are in addition to the information in the preceding sizing table.

Web Server:

  • If you have large number of files to be backed up, you might need additional disk space for the Web Server cache.
  • If the Web Server uses a 16 GB RAM, you might require an additional Web Server.

Web Console:

  • For environments with multiple domains, use one Web Console for each user domain.
  • For external access for use with mobile applications, use a dedicated Web Console.

For information about the operating systems supported for the Web Server and the Web Console, see Web Server: System Requirements and System Requirements - Web Console.

Firewall Considerations

For CommCell components to communicate across a firewall, the network TCP port numbers you select must be configured on your firewall. This specifically includes tunnel ports and additional ports. To review port requirements, see Network TCP Port Requirements - Firewall Ports.

Network Gateway Considerations

You can use a network gateway to enable communication across the LAN or WAN without a VPN connection.

For your environment, start with one network gateway host for each MediaAgent. Additional hosts might be needed for environments with large data size or low bandwidth.

We recommend that you designate a network gateway for a remote site even if the MediaAgent is not in the local environment.

For information on the hardware requirements for a network gateway, see Setting up the Commvault Network Gateway.

Last modified: 6/26/2019 6:39:21 PM