Determining the network topology is a crucial first step that can affect nearly every part of the Linux ROBO deployment in your environment.
Linux ROBO software leverages several technologies that are critically dependent on a fast and stable network connection. Due to that, there are guidelines on how the network should be configured to ensure that the appliance is stable and meets the performance expectations.
Important
Several pre-defined topologies have been validated and built into the software. These validated topologies are explained below.
If the network topology in your environment is not listed here, or if you are not sure of the topology that is required for your environment, contact your Commvault representative for assistance.
Answering the following questions will help to determine a recommended topology:
-
Do you require network redundancy?
-
Do you have a dedicated non-routable backup network?
-
Do you require the appliance to be connected to multiple vLANs?
Use the following selection guide to determine the topology required for your environment:
|
Require Network Redundancy |
Have dedicated non-routable backup network |
Require multiple VLANs connected to the appliance |
Recommended Topology |
|---|---|---|---|
|
No |
No |
No |
|
|
Yes |
No |
No |
|
|
No |
No |
Yes |
|
|
Yes |
No |
Yes |
Considerations
For proper operations, the Linux ROBO node require connectivity to the following networks:
-
Data protection network, which transfers data to and from the clients being protected and connect to the CommServe server. This will require a minimum of at least one dedicated 10 GbE network connection.
-
Optional Management network which is used only when the data protection interfaces are non-routable, and an alternative interface must be used for management.
-
When sizing inter-switch links, assume that Linux ROBO node will require a minimum of 20 GBPS bandwidth.