CommVault Simpana allows the installation of multiple instances on a single server. Each instance can operate simultaneously and independent from each other. The instance itself belongs to only one CommCell!
Each instance has it’s own:
- Binaries installed (for example: “D:\Program Files\CommVault\Simpana\” and “D:\Program Files\CommVault\Simpana2“);
- Updates installed (the other instance is treated as another server, hence updates need to be installed separately);
- Set of services (with each own GXadmin);
- Registry settings (“HKLM\Software\CommVault Systems\Galaxy\Instance00x“).
The important question is.. why would you want to do this? Some use cases:
- CommServe DR: multiple instances are required when you want to backup the CommVault Simpana Disaster Recovery CommServ. By default, the CommServ DR instance is installed as instance001. If you want to deploy a filesystem iDataAgent, another instance (instance002) is required.
- Mixed-bit environments: the system being backed up is installed with 32 & 64-bit applications. To protect both types of application data, both the 32 & 64-bit can be required.
- Different CommCells: let’s say the customer wants two CommCells (one for protecting file system data and another one for protecting application data);
- Content indexing: by default a search engine belongs to only one storage policy. In case you want to content index data by using another storage policy, an additional physical server is required. Multi instancing allows one physical server to be shared over multiple storage policies by creating additional instances. (advise: create a CommVault incident to ensure the hardware is suitable to handle the extra load).
By default, the CommVault Simpana setup looks for existing installations and tries to add software components to the existing installation. If you want to use multiple instances on a Windows-based server, the following DWORD needs to be added to the registry: “HKLM\Software\GalaxyInstallerFlags\bAllowMultiInstances” with the value “1“. In case the key “GalaxyInstallerFlags” does not exist, you can create it manually.
Thanks for reading!