Physical Media agent Configuration

Hi @Garima 
 

Unless im mistaken, CIMC is just console access to the Server essentially giving you the same access as if you were physically standing infront of it with a keyboard, mouse and monitor?

If yes, than you can do everything from CIMC and won’t need any RDP or Putty access to the OS directly.

From network requirements, its fairly flexible and theres no hard or fast rule, however a few things to consider are;

• splitting up your Data and Production network
  • This is to prevent saturation of your Production Network
  • This also helps to limit performance impact to your Data Network (data network being the network between the storage and the Media Agent).

• You may also consider VLANing the networks your Media Agents are on to split traffic for inter-MediaAgent communication.
  • This will help to manage Aux Copy and Deduplication traffic on the network and prevent your ‘Admin’ tasks performed within Commvault from impacting any production network.

If i were deploying an MA I’d aim to have 4 VLANs (3 depending on how storage is being presented):

• VLAN1 for Production Network Comms
  • This is used for any regular activities the MA’s may be required for, GP Updates, wsus updates etc.
• VLAN2 for Backup Network
  • This is used for clients to communicate with MAs
• VLAN3 for Inter MA comms
  • Literally just for MAs to talk to each other. This becomes more important when the MA’s are all part of the same Deduplication Database as latency can severly impact DDB Performance.
• VLAN4 for storage network.
  • This is relevant if the storage is presented via IP, if its locally attached SAN storage or local disk, this is obviously not a requirement.

Cheers,
Jase

EDIT: I should note, there are people on here that do design and deployment for a living and likely performed hundreds of these in the past, so they may have more insight into how this is best planned out!