Skip to main content
commvault.com commvault.com
Solved

O365 Resource Pool for MSP - Sizing and recommendations

  • November 10, 2022
  • 2 replies
  • 93 views
P
Commvault Certified Expert
Forum|alt.badge.img+8
  • PatrikCommvault Certified Expert
  • Commvault Certified Expert
  • 42 replies

Hi, 

We are thinking about implementing a Resource Pool for O365 in a MSP environment for ease of administration. There is not much details about this in the docs so I’m trying to reach out here to see if there is anyone with the correct knowledge. A few questions...

  • Are there any recommendations about how to distribute Applications? Use one O365 Resource Pool or use separate Resource Pools for each App - Exchange, OneDrive, SharePoint and Teams?
  • Are there any sizing considerations on how much data or how many users can be managed by one single Resource Pool? How many Access Nodes and how many Index Nodes can we expand the Pool with as we grow?
  • Is it possible to change current setup for our tenants from dedicated resources (i.e. their own AccessNodes and Index) to a Resource Pool? And if needed, is it possible to move a tenant from a Resource Pool to dedicated resources?  I would expect that a re-index will be needed in both cases?

Regards, Patrik

Best answer by Scott Reynolds

Hello @Patrik 

The resource pool it to assist with sharing of resources like access nodes/index servers. We have seen many ISPs setup onces for specific functions, like one just for Sharepoint.

There are no restrictions on distributing applications. it depends on needs. Also for number of users and first question it depends on how much total data/users, etc to plan on sizing. To my knowledge there is no limit on expanding.

You would still map the requirements based on the guidelines in BOL

https://documentation.commvault.com/2022e/expert/28818_hardware_recommendations_for_exchange_mailbox_agent.html

 

For you third question you are correct the issue with doing that is index server. It would have to playback all the action logs into the new index server this would limit browse and restore until its complete.

View original
Did this answer your question?

2 replies

S
Vaulter
Forum|alt.badge.img+14

Hello @Patrik 

The resource pool it to assist with sharing of resources like access nodes/index servers. We have seen many ISPs setup onces for specific functions, like one just for Sharepoint.

There are no restrictions on distributing applications. it depends on needs. Also for number of users and first question it depends on how much total data/users, etc to plan on sizing. To my knowledge there is no limit on expanding.

You would still map the requirements based on the guidelines in BOL

https://documentation.commvault.com/2022e/expert/28818_hardware_recommendations_for_exchange_mailbox_agent.html

 

For you third question you are correct the issue with doing that is index server. It would have to playback all the action logs into the new index server this would limit browse and restore until its complete.

Onno van den Berg
Commvault Certified Expert
Forum|alt.badge.img+19
  • Onno van den BergCommvault Certified Expert
  • Commvault Certified Expert
  • 1252 replies
  • November 11, 2022

I truly hope it is going to be expanded soon to add support for object storage! 

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings