Non-Cisco Storage Server Node Configuration

Prior to Commvault HyperScale software installation each server must meet basic minimum configuration requirements. These steps must be completed in full prior to imaging or configuration servers with Commvault HyperScale and are not included in Commvault Professional Servers. Failure to complete all steps below will result in delays to configure Commvault software and storage.

The steps outlined below apply only to non-Cisco Reference Design server nodes. Refer to server vendor's documentation for specific steps required to complete this configuration. Begin with either 1a or 1b below depending on purchased hardware configuration.

1a.	Boot drive - Combined OS/metadata drives option Create a RAID5 volume for all four SSD drives to be used for combined OS/metadata volume. Set BIOS to boot from RAID5 volume. Continue to Step 3.
1b.	Boot drive - Individual boot drive option Create a RAID1 volume for the two SSD drives to be used for OS volume. Set BIOS to boot from RAID1 volume. Continue to Step 2.
2.	metadata drive - Individual metadata drive option on SSD or NVMe (used only with individual boot drive option) Dedicated metadata SSD or NVMe drive require no further configuration. Commvault HyperScale ISO will detect and format drive during initial imaging process.
3.	Storage Pool drives Storage Pool Large Form Factor (LFF) should have no RAID and no special configuration. Commvault HyperScale ISO will detect and format drives during initial imaging process. Hardware vendors each have unique label naming convention for storage pool drives. Ensure all LFF drives are labeled as one of the following depending on vendor: JBOD Pass through Non-RAID Any other vendor specific label for unformatted drives without RAID
4.	Networking and switch configuration Create a minimum of two VLAN: VLAN 1 = data protection network for public interface(s) VLAN 2 = Storage Pool network for private interface(s) Ensure all server network ports are connected to 10Gb (or faster) ports on network switches. If multiple VLAN are required for data protection, offsite copies, etc., ensure all VLANs are configured on switches. If multiple network cards are being used, ensure sufficient number of ports are available on switches. Total number of ports required will depend on total network cards and VLANs. If network bonding is being used, allow for 2x ports per VLAN.