Support Lab Guide

An Always-On Lab for all of

Global Support
V4.0 US-SUPPORT Lab Guide July 2020

Contents
Lab Access - Quick Start ................................................................................................................................................................................................................... 2
Permanent Modification Requests ......................................................................................................................................................................................... 2
Introduction & History .......................................................................................................................................................................................................................... 3
CommCell Breakdown ..................................................................................................................................................................................................................... 3

Lab Access - Quick Start Guide

Always-On Lab Commcell Console and Command Center Access

1. If you want to access either the Commcell Console or Command Center - Just double click on either link.

2. When prompted for a User Account, you will want to utilize your Commvault-NJ Account and Password.

3. This will provide you access to either console, but with the Command Center, you may need to accept the risk from within your
Internet Browser.

Always-On Lab RDP Access

1. Download the mRemoteNG zip file

2. Extract the mRemoteNG file locally

3. Navigate into the extracted folder and open the mRemoteNG Application

4. You may be prompted to automatically check for application updates - You can select "Use the recommended settings"

5. You will now be able to automatically RDP into any of the Always-On VMs that were made available to you.

Note: We have restricted the RDP access for US11v-CSA, US11v-MA1, and all three US11v-DCs for quality control –
We will consider opening them up as the lab stabilizes over time.

Permanent Modification Requests

If you have a suggestion on an enhancement or change to the lab, we are interested in your feedback. We are not limited
to just new VMs but any change or addition you may find to be required. If you want to volunteer your time, it will accurate
the turnaround time of implementing the change request. If you want to volunteer your time, do additionally email the
Request Form as well and state so.

Please send us an email and we will coordinate from there - Request Form

Commvault® - Support Enablement Team Page 2 of 7

V4.0 US-SUPPORT Lab Guide July 2020

Introduction & History

To consolidate SETs and moderators' efforts and to improve our capabilities to support our customers, we have put forth
an effort to create a single unified Support Lab environment for our entire Global Support Team.

This started because SET/Tier2s have been teaming up to run each of the US - Focus Groups lab environments,
independently for each focus area. Each one of those labs took a massive amount of work to create, expand, and
maintain. This maintenance took a number of us away from our day-to-day activities (queues included); as a lab, in
general, it takes a great deal of continuous care – hardware, software, CV, etc. This led to different levels of consistency,
quality, and functionality across all focus groups.

What was our Plan:

As this effort was designed to reduce the duplicate administrative time spent on our labs, redundant setups, limited
setups, non-working setups – we have put a master plan together to provide all engineers access without being
handcuffed on usability, and give all lab admins peace of mind as to not fear destructive tendency of our engineers.

We had to first identify all hardware/subnet information across the focus groups of US-based MM, Client, Server, and
Messaging resources. In addition to the consolidation of hardware, we also optimized our efforts by enabling each skill
group to properly design and own their portion of the lab environment. Each focus group will have the chance to build up
their areas the way they desire, without having to duplicate efforts against external focus groups features/areas. We are
taking our specialists and leveraging their experience and knowledge to create a specialized lab for all.

There will always be two sets of the Always-On Commcell lab running within our virtualization environment. We have a
production side CommCell which is our “Alpha” image of the entire lab environment, and a second copy version of the
same CommCell but fully accessible on the network for all.

Each client will have a GEO descriptive ID as part of its name, so we all know the GEO location of the servers. With an
example of US11v-CSA.us-support.lab, where we quickly understand this resource is located in the US. We will see other
GEO descriptive IDs leveraged as this lab continues to grow in features and servers across the globe.

Production Lab (Current Code Name: Alpha)

This will be an entirely virtualized version of our US-Support Lab where only defined Lab Admins have access to grow as
they need to. It will be hidden and off the network, as it's going to be our Gold version of the lab.

It will be built out where we will continuously perform backup operations to nearly 100% SLA.

As this is the Gold version, any additions to this lab will be handled by a Request Form available to all engineers/admins –
This will be to gather information on you feel we need to be added to the lab, configure in the lab by default, and to control
the lab's growth in a unified fashion.

TestOps Lab (Current Code Name: Omega)

The lab will consist of a full set of replicated VMs from the Alpha lab and be considered a Silver version of the US-Support
Lab. This will be fully accessible to everyone, with the exception of US11v-CSA, US11v-MA1, and all three US11v-DCs
as we currently want to control the stability of this lab.

If you need to work with any of these types of clients and fear damaging the main CommCell, you will want to deploy your
own Virtual Lab.

As a form of cleanup, we will periodically look to replicate the entire Alpha Lab out over the Beta lab to provide our
engineers with a consistent, updated, expanded, and working lab configuration to leverage – This is being discussed but
may line up for every Service Pack.

CommCell Breakdown
This will be broken down by focus group areas to better understand our layout and the resource’s usage.

Commvault® - Support Enablement Team Page 3 of 7

V4.0 US-SUPPORT Lab Guide July 2020

Server Focus
Client Name Function
US11v-CSA This is the main CommServe running on Windows 2016

MM Focus
Client Name Function
US11v-MA1 This is the primary Media Agent with a 5 TB+ MagLib attached which is designed
to service the CommCell with historical datasets and newly created datasets.
US11v-LINUXMA This is a secondary Media Agent built on CentOS 7 to service Linux MA needs
within a CommCell. It doesn’t have a MagLIb by default but one can be added if
requested.
US11v-WebSvrMM1 This is a secondary Media Agent built on Windows to service Content Indexing
searches within a CommCell. It doesn’t have a MagLIb by default but one can be
added if requested.
US11v-Search1 This is a secondary Media Agent built on Windows to service Content Indexing
searches within a CommCell. It doesn’t have a MagLIb by default but one can be
added if requested.
US11v-REFARCH1, These are secondary Linux Media Agents designed off of our HyperScale
US11v-REFARCH2, & Appliance Reference Architecture.
US11v-REFARCH3
US11v-NETAPP This is a NetApp 9.7 Simulator for storage and IntelliSnap.

https://172.19.22.49/sysmgr/v4/
User: admin Pw: CommVault01

US11v-FreeNAS This is a FreeNAS storage VM for NFS or iSCSI presentations to lab VMs.

Portal: https://172.19.22.123/
User: root Pw: CommVault01

US11v-NUTANIX & This is designed with the node US11v-NUTANIX & svm US11v-NUTANIXSVM to
US11v-NUTANIXSVM be utilized for storage operations as MM sees fit.

Prism: https://172.19.22.37:9440/
User: admin Pw: C@mmVault01

Client Focus
Client Name Function
US11v-1TouchWin12 This is leveraged to support VirtualizeMe and 1-touch recoveries within the
CommCell from an actual source running system state backups.

US11v-Archiving This is designed for OnePass stubbing and ArchiveSet stubbing for Windows.
US11v-DC01, US11v- These VMs are the production domain controllers for all of the Support Lab.
DC02, & US11v-DC03

Commvault® - Support Enablement Team Page 4 of 7

V4.0 US-SUPPORT Lab Guide July 2020

US11v-HV1901 & US11v- These nodes are leveraged to support Hyper-V 2019 VSA backups and restores.
HV1902 (VSA-HYPERV) With VSA-HYPERV being the virtualization client.
VSA-VMWARE, US11v- This Virtualization Client is designed to protect US11v-bVcenter & US11v-bESX
bVcenter & US11v-bESX on VMware 6.7. We can add VMs to this host by default on request, and we can
add additional hosts if needed. With VSA-VMWARE being the virtualization
client. (This is not for personal VMs as it will be deleted upon the lab refresh)

vCenter: https://us11v-bvcenter.us-support.lab
User: administrator@vsphere.local Pw: CommV@ult01

ESXi Host: https;//us11v-besx.us-support.lab

User: root Pw: CommVault01

VSA-NUTANIX, US11v- This Virtualization Client is designed to protect US11v-NUTANIX & US11v-
NUTANIX & US11v- NUTANIXSVM. We can add VMs to this host by default on request, and we can
NUTANIXSVM add additional hosts if needed. With VSA-NUTANIX being the virtualization
client. (This is not for personal VMs as it will be deleted upon the lab refresh)

Prism: https://172.19.22.37:9440/
User: admin Pw: C@mmVault01

VSA-RHEV, US11v-RHVH, This Virtualization Client is designed to protect virtual machines on the US11v-
US11v-RHoVirt RHVH node and US11v-RHoVirt engine VM. We can add VMs to this host by
default on request, and we can add additional hosts if needed. With VSA-RHEV
being the virtualization client. (This is not for personal VMs as it will be deleted
upon the lab refresh). US11v-RHoVirt engine currently has an issue 6/14/2020

Portal: https://172.19.22.31:9090/
User: root Pw: C@mmVault01

US11v-OpenStack, These nodes are designed to support VSA backups from OpenStack. There is a
US11v-OpenStack-prx- controlling client which is VSA-OpenStack. (This is not for personal VMs as it
centos, & VSA-OpenStack will be deleted upon the lab refresh)

http://172.19.22.222/dashboard/auth/login/?next=/dashboard/
User: admin pw: Openstacks!

US11v-XenServer, US11v- These nodes are designed to support VSA backups from XenServer node
XENWIN US11v-XenServer. There is a controlling client which is VSA-XEN. (This is not
for personal VMs as it will be deleted upon the lab refresh)

Thick Client Download for XenCenter: http://172.19.22.33/

User: root Pw: C@mmVault01

US11v-XENWIN is the VSA proxy within the XenServer Hypervisor.

US11v-MC1, US11v-MC2, These nodes are designed to be leveraged by the MC/GEO for specific tests
US11v-MC3, US11v-MC4, where they don’t feel comfortable performing them on the production nodes
US11v-MC5, US11v- throughout the CommCell.

Commvault® - Support Enablement Team Page 5 of 7

V4.0 US-SUPPORT Lab Guide July 2020

APAC, US11v-EMEA, & (They can be expanded / redesigned per MC/GEO request)
US11v-INDIA
US11v-WIN10 This node is leveraged to support Windows 10 backups and restores
US11v-WIN12 This node is leveraged to support Windows 12 backups and restores
US11v-WIN16 This node is leveraged to support Windows 16 backups and restores

(This client is configured to be part of a CDR pair)

US11v-WIN19 This node is leveraged to support Windows 19 backups and restores

(This client is configured to be part of a CDR pair)

US11v-WIN7 This node is leveraged to support Windows 7 backups and restores
US11v-WIN8 This node is leveraged to support Windows 8 backups and restores
US11v-WIN81 This node is leveraged to support Windows 8.1 backups and restores
US11v-WIN2008 This node is leveraged to support Windows 2008 backups and restores
US11v-K8S This is leveraged to support Kubernetes/Docker built on Ubuntu 20.04

US11v-LINUXMA This is a secondary Media Agent built on CentOS 7 to service Linux MA needs
within a CommCell. It doesn’t have a MagLIb by default but one can be added if
requested. This can also be leveraged for VSA backup/restore

UNIX Focus
Client Name Function
US11v-CENTOS7 This is leveraged to support file system backups from CentOS7

US11v-FreeBSD This is leveraged to support file system backups from FreeBSD 12.0

US11v-K8S This is leveraged to support Kubernetes/Docker built on Ubuntu 20.04

US11v-RHEL This is leveraged to support file system backups from RedHat Enterprise Linux
Server 7.6
US11v-UBUNTU This is leveraged to support file system backups from Ubuntu 18.04
US11v-REFARCH1, These are secondary Linux Media Agents designed off of our HyperScale
US11v-REFARCH2, & Appliance Reference Architecture.
US11v-REFARCH3
US11v-LINUXMA This is a secondary Media Agent built on CentOS 7 to service Linux MA needs
within a CommCell. It doesn’t have a MagLIb by default but one can be added if
requested.
US11v-SQL-UX1 This is leveraged to support SQL Database backups built on Ubuntu 18.04
us11v-ora-lnx1 This is leveraged to support Oracle on Linux
us11v-ora-linx1 This is leveraged to support Oracle on Linux
us11v-saphana1 This is leveraged to support SAP HANA
us11v-ora-ms1 This is leveraged to support Oracle on Windows
us11v-ora-rac1 This is leveraged to support Oracle RAC
us11v-ora-rac2 This is leveraged to support Oracle RAC

Commvault® - Support Enablement Team Page 6 of 7

V4.0 US-SUPPORT Lab Guide July 2020

Messaging Focus
Client Name Function
US11v-MBX13-01 This is a standalone Exchange 2013 server.
US11v-MBX16-01 & These two nodes are part of an Exchange 2016 DAG.
US11v-MBX16-02
US11v-MBX19-01 & These two nodes are part of an Exchange 2019 DAG.
US11v-MBX19-02
US11-SP10-03 This is leveraged for SharePoint 2010
US11v-SP13-01 This is leveraged for SharePoint 2013
US11v-SP16-01 This is leveraged for SharePoint 2016
US11v-SP19 This is leveraged for SharePoint 2016
US11v-EX-CSMB Pseudo Client: Exchange Mailbox > Content Store > SMTP Journaling.
US11v-EX-Journal Pseudo Client: Exchange Mailbox > Journaling > Exchange Journaling
US11v-EX-Mailbox Pseudo Client: Exchange Mailbox > User Mailbox > Mailbox Archiving
US11v-EXDAG16 Pseudo Client: Exchange 2016 DAG client (US11v-MBX16-01 & US11v-MBX16-02)
US11v-EXDAG19 Pseudo Client: Exchange 2019 DAG client (US11v-MBX19-01 & US11v-MBX19-02)
US11v-IDX01 , US11v- These nodes are built on Windows 2019 and are designed to service the Index Server
IDXCN1 , & US11v- Cloud
IDXCN2
US11v-IDXHA1 , US11v- These nodes are built on Windows 2019 and are designed to service the Index Server
IDXHA2, & US11v-IDXHA3 Cloud as High Availability monitors.
US11v-PRX01, US11v- These nodes are built on Windows 2019 and are designed to service the Index Server
PRX02, & US11v-PRX03 Cloud
VSA-Splunk, US11V- These nodes are built on CentOS 7 and are designed to service the three-node Splunk
Splunk1, US11V-Splunk2, client. There is a controlling client which is VSA-Splunk
& US11V-Splunk3
US11v-SQL-03 This node is built on Windows 2016 and services SQL DBs versions of 2012, 2014, 2016,
2017, & 2019
US11v-SQL-06 This node is built on RedHat 7.7 and designed to protect SQL DBs.
US11v-SQLAG14 This node is built on Windows 2016 and services SQL DBs versions of 2012, 2014, 2016,
2017, & 2019
US11v-SQLAG16 This node is built on RedHat 7.7 and designed to protect SQL DBs.
US11v-SQLAG17 Pseudo client: SQL Server 2014 availability group. Replicas:US11V-SQLV-01/US11V-
SQL03
US11v-SQLN1-01 & Pseudo client: SQL Server 2016 availability group. Replicas:US11V-SQLV-02/US11V-
US11v-SQLN1-02 SQL03
US11v-SQLV-01, US11v- SQL 2014 Virtual cluster running on physical nodes US11v-SQLN1-01 & US11v-SQLN1-
SQLV-02, & US11v-SQLV- 02
03 SQL 2016 Virtual cluster running on physical nodes US11v-SQLN1-01 & US11v-SQLN1-
02
SQL 2017 Virtual cluster running on physical nodes US11v-SQLN1-01 & US11v-SQLN1-
02
PROD-OneDrive This pseudo client is leveraged to protect a OneDrive account. (Not publicly available for
usage at the moment)
PROD-O365 This pseudo client is leveraged to protect an O365 account. (Not publicly available for
usage at the moment)
PROD-ExchangeData This pseudo client is leveraged to protect Exchange data across the CommCell.

Commvault® - Support Enablement Team Page 7 of 7