commvault.com commvault.com
Solved

Hardware refresh - Split CommCell and media agent?

  • 1 November 2021
  • 3 replies
  • 133 views
T
Rank
Badge +2

Hello, we’re currently due for a hardware refresh for our CommCell and media agents. 

Currently, we have an ‘all-in-one’ setup with CommCell and media agent both installed baremetal on a dell server. I understand that it is likely better to have the CommCell hosted on a separate server? If that is the case, which server hosts the index cache and DDB? 

This will be on a Windows install… would it be an issue running the media agent on a hyperv host with the commcell as a guest vm? 

Thanks

icon

Best answer by Mike Struening RETIRED 1 November 2021, 20:38

View original

3 replies

Mike Struening RETIRED
Rank
Userlevel 7
Badge +23

You can absolutely do that, all documented here:

https://documentation.commvault.com/11.24/expert/4792_separating_commserve_from_commserve_mediaagent_computer.html

Now, which machine hosts what is another matter, and dependent on scaling needs. Just be sure to follow the system reqs:

https://documentation.commvault.com/11.24/expert/2822_mediaagent_system_requirements.html

We have a very detailed Deduplication building guide here as well:

https://documentation.commvault.com/11.24/expert/12411_deduplication_building_block_guide.html#b12415_deduplication_system_requirements

With that said, the Index Cache and DDB would be better served on their own dedicated servers since if you ever need greater performance for one vs. the other, you can just modify the necessary vm hardware.

The requirements for a v2 Indexing Server can be pretty large as you expand your environment:

https://documentation.commvault.com/11.24/expert/92111_system_and_hardware_requirements_indexing_version_2.html

As you can see, an SSD is highly recommended for solid performance (no pun intended).

https://www.linkedin.com/in/michael-struening
T
Rank
Badge +2

You can absolutely do that, all documented here:

https://documentation.commvault.com/11.24/expert/4792_separating_commserve_from_commserve_mediaagent_computer.html

Now, which machine hosts what is another matter, and dependent on scaling needs. Just be sure to follow the system reqs:

https://documentation.commvault.com/11.24/expert/2822_mediaagent_system_requirements.html

We have a very detailed Deduplication building guide here as well:

https://documentation.commvault.com/11.24/expert/12411_deduplication_building_block_guide.html#b12415_deduplication_system_requirements

With that said, the Index Cache and DDB would be better served on their own dedicated servers since if you ever need greater performance for one vs. the other, you can just modify the necessary vm hardware.

The requirements for a v2 Indexing Server can be pretty large as you expand your environment:

https://documentation.commvault.com/11.24/expert/92111_system_and_hardware_requirements_indexing_version_2.html

As you can see, an SSD is highly recommended for solid performance (no pun intended).

 

Pretty small shop. Maybe 20 servers backed up for 2-3TB daily. Please correct me if I’m wrong but it looks like I can go with:

Raid 1 w/ 2 SSD: Hyper-V Host, CommCell VM, Media agent

Raid 1 w/ 2 SSD: DDB
Raid 1 w/ 2 SSD: Index Cache

Direct attached storage with Raid 10 with a stack of disks for mount points

Mike Struening RETIRED
Rank
Userlevel 7
Badge +23

You should be fine with that.  I would split the MA and CS just for scaling purposes (and you’re already at it, so why have to do it later?).

https://www.linkedin.com/in/michael-struening

Reply


Terms & ConditionsCookie settings