All-in-one Configuration installation

You can find some info here about the load for a all-in-one:

 https://documentation.commvault.com/v11/essential/system_and_hardware_requirements_all_in_one_configuration.html

@Javier So, I assumed there was an option to select “All-in-one” somewhere in the setup.exe. I guess you’re just telling me to install the Commserve and MA binaries on 1 physical node and its now an “All-in-one” configuration, do I have that right?

I have a total of 5TB to protect (5 Windows servers total). Here is my hardware req. for Commcell:

1x Extra Small Media Agent per site

2 CPU cores, 16 GB RAM (or 2 vCPUs/16 GB)

OS disk - 200 GB (2 x 15K RPM min)

DDB disk – 200GB SSD or SATA

Index cache disk – 400GB SSD

HI @Jay Son ,

You are correct, you just need to installed both CS and MA packages within the same server to make it a All-in-on.

In regards to the hardware requirements, I am afraid yours won't meet the minimum requirements. Please refer to the details provided by @Ledoesp to confirm the minimum hardware you need to run an extra small setup with an All-in-one config

Thanks Javier.

It does not say “minimum requirements” or “extra small” in the article Leodoesp sent. Or are you saying that All-in-One Config will only work with the configuration below? I feel like its overkill. I compared this configuration with our other environment that have more that 100 VMs (no physical) and is NOT all-in-one config. Here is the Media Agent and Commserve

https://documentation.commvault.com/v11/essential/system_and_hardware_requirements_all_in_one_configuration.html

In this configuration, all Commvault components (CommServe server, Web Server, Web Console, Workflow Engine, MediaAgent, and access nodes) are installed on a single computer. This configuration supports a combination of up to 25 servers, 250 virtual machines, 1000 Microsoft Office 365 users, or 50 million total objects indexed.

• Windows Server operating systems

• 16 CPU cores

• 32 GB RAM

• 2 TB of working space for the CommServe database, the deduplication database (DDB), index, and job results (SSD disk is recommended)

Hi @Jay Son ,

Of course the environment may work with lesser hardware resources, but the requirements listed in documentations are those that have been tested and certified by engineering. Having less resources available may and will inevitably lead to performance issues under certain workloads.

In the even of having performance issues, and a support case needing to be opened, support will initially highlight the hardware requirements and will not be able to progress the case any further until they are met.

Thanks Javier. The configuration in the docs supports “up to”. I will start low and increase, if needed. We are backing 5 physical servers backing up flat files.