Dumb Question, but I don't want to have to have my systems team argle bargle. Media Agents have to be physical servers, correct? I am assuming there shouldn't be a reason why it cannot be a virtual machine, but before I put my foot in my mouth (tasty btw) I want to see what the community best practice is.
Best answer by Javier
View original
+3
Hi
Good day.
While configuring the Media Agent, the main components are DDB and Index, So I would like you to refer to the below documents and accordingly configure the Media Agent.
https://documentation.commvault.com/v11/expert/111985_hardware_specifications_for_deduplication_mode.html
https://documentation.commvault.com/v11/expert/1656_hardware_specifications_for_non_deduplication_mode.html
https://documentation.commvault.com/v11/expert/2822_mediaagent_system_requirements.html
Regards,
Wasim
Media Agents can be indeed hosted by a Virtual Machine, as long as they meet the hardware requirements.
Media Agents are pretty resource intensive, specially in regards to their DDBs and how sensitive they are to latency and delays (Q&I Times), that may be the reason why MAs are preferred to be hosted in Physical Machines.
I cannot see anything wrong with hosting a Media Agent as a VM and having pass-through disk for DDBs and Libraries (if they are local disk to the MA). Just keep in mind VM resources will be shared among all the VMs within the hypervisor, we need to ensure hardware requirements are meet at all times.
We have Hyperscale's and Virtual servers as MA’s. And planning to migrate off Hyperscale to Virtual as MA solution
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
