NextGen (V11)

CommServe
Installation
Bryan Clarke
World Wide Technical Enablement
Main objectives for the CommServe Installation:

• Requirements

• Planning the Commserve Deployment

• Installation Process

• Post Installation Best Practices

2
Requirements
 CommServe Category Express Work Group
(up to 25 servers or 50 (up to 1000 servers or
laptops) 5000 laptops)
Operating Windows 2008 SP2 or Higher Windows 2008 SP2 or Higher
System (64Bit) (64Bit)
CPU 8GHz Minimum Total Speed 12GHz Minimum Total Speed
CPU
Examples: Examples:
1x 4-core CPU @ 2.0GHz 2x 4-core CPU @ 1.5GHz
1x 8-core CPU @ 1.5GHz

Memory Memory 16GB 32GB

Drive 256MB Cache, Battery 256MB Cache, Battery backup.
Controller backup. Write cache enabled. Write cache enabled. Raid
Raid Strip 128K Strip 128K

Disk Boot Drive Boot Drive

2x 146GB 15K SAS – RAID1 2x 146GB 15K SAS – RAID1
HDD (Examples) Data Drive Data Drive
4x 146GB 15K SAS – RAID10 4x 300GB 15K SAS – RAID10

Pre-Install IIS IIS

4
 CommServe Category Data Center Enterprise
(up to 2500 servers or (up to 10,000 servers or
10,000 laptops) 25,000 laptops)
Operating Windows 2008 SP2 or Higher Windows 2008 SP2 or Higher
System (64Bit) (64Bit)
CPU 20GHz Minimum Speed (Total 30GHz Minimum Speed (Total
of all CPU cores) of all CPU cores)
CPU Examples: Examples:
2x 6-core CPU @ 1.6GHz 2x 6-core CPU @ 2.5GHz
1x 12-core CPU @ 1.6GHz 1x 16-core CPU @ 2.0GHz

Memory Memory 32GB 64GB

Drive 512MB Cache, Battery 512MB Cache, Battery backup.
Controller backup. Write cache enabled. Write cache enabled. Raid
Raid Strip 128K Strip 128K

Disk Boot Drive

2x 146GB 15K SAS – RAID1
Boot Drive
2x 200GB eMLC SSD – RAID1
(Examples) Data Drive Data Drive
HDD 8x 146GB 15K SAS – RAID 10 2x 400GB eMLC SSD – RAID1
OR
2x 400GB eMLC SSD - RAID 1

Pre-Install IIS IIS

5
Planning the CommServe Deployment
Planning the CommServe Deployment:

• Verify System Requirements

• Verify the Licenses

• Verify the Environment:

o Virtual or Physical
o Clustered?
 If so, pre-install SQL

 If so, the Web server and Web

console are not supported on a
cluster

 DR Considerations

7
Planning the CommServe Deployment:
Placement Considerations:

• In the main Data Center

• Close to Production servers

• In case of site failure, need to failover to
DR
• At the DR site

• Further from production servers,

dependency of connection speed and
resiliency between sites
• However, in event of DC failure, no need
for failover
• In the cloud

• Further from production servers,

dependency of connection speed and
resiliency between DC
• Less likely for need of failover 8
Planning the CommServe Deployment:
Single CommServe
Stand Alone, or Clustered?

• Most deployments are stand alone, however

clusters are fully supported

Physical or Virtual?
• Smaller environments Virtual is most common
• Larger (5000+), physical highly
recommended
Clustered CommServe

9
Planning the CommServe Deployment:
Disaster Recovery Options

Manual DR via DR backup/Restore

DR

\\DRCommServe\CommServeDR$

10
Planning the CommServe Deployment:
Disaster Recovery Options

CommServe DB replication via SQL iDA

DR

11
Planning the CommServe Deployment:
Disaster Recovery Options

Automatic CommServe Failover

DR

12
Planning the CommServe Deployment:
Method How does it work? Pro’s Con’s
• DB Sync: Manual
• Simple setup • DR Process: Manual
Manual DR via • Scheduled DR Backups • No need for additional • CS DB state as of last
DR Backup and • Manually set up standby CS, agents on CS DR backup, highest
restore DR backup via DRTool • Standby CS does not potential for
Restore need to be online configuration/data
loss

CS DB • SQL DB on Primary and Standby • DB Sync: Automatic • DR Process: Manual

• SQL DB on Primary and • Need SQL IDA installed
Replication via CS kept in sync via SQL log backup Standby CS not too far on Primary and
and restore
SQL iDA apart Standby CS

• Third party software monitors • Initial configuration

primary CS can be little involved
Automatic CS • SQL DB Sync via SQL iDA
• Automatic DB Sync • Need for extra servers
Failover • Sends alert when CS services or for service monitoring
CS fails. • Still requires 1 manual
• Admin needs to initiate failover process
13
 Planning the CommServe Deployment:
Attribute Value (Examples)
IP Address 10.200.200.100

Additional Packages FS, MA, Work Flow, Web Server

SQL Install Directory Drive:\Program Files\Microsoft SQL Server\

SQL Database Directory Drive:\Commvault\Database\

Commvault Software Drive:\Program Files\Commvault\ContentStore

Directory
DR Share \\DRCommserve\CSDR

Software Cache Drive:\Program Files\Commvault\ContentStore\Software

Download Cache Drive:\Program Files\Commvault\ContentStore\Updates

Additional Settings nSkipPlatformCheck

14
Planning the CommServe Deployment:

C:\

E:\

F:\
15
Installing the CommServe
The New Software Installer – The CommServe

• Much more simplified and streamlined

installer

17
The New Software Installer – The CommServe

• Select which options to install

18
The New Software Installer – The CommServe

• The server packages

• Notice Operations Manager is gone…it

is rolled into the Commserve.

• And 1-Touch is gone

19
The New Software Installer – The CommServe

• The Windows Packages

20
The New Software Installer – The CommServe

• The VSA agent

21
The New Software Installer – The CommServe

• Databases

22
The New Software Installer – The CommServe

• Applications

23
The New Software Installer – The CommServe

• Applications

24
The New Software Installer – The CommServe

• Tools

25
The New Software Installer – The CommServe

• Back to the CS installation, select the

components to install

• Reminder…don’t forget to backup the

DM2 database whenever installing the
Web Server

26
The New Software Installer – The CommServe

• Select Default install path

27
The New Software Installer – The CommServe

• Select SQL 2012 installation path

28
The New Software Installer – The CommServe

• Select CS Database install path

29
The New Software Installer – The CommServe

• Select DR install location…should be on

a network share, preferably on the DR
CommServe.

30
The New Software Installer – The CommServe

• Select to configure the Proxy Service.

31
The New Software Installer – The CommServe

• Summary Page

• Click the + sign beside more

information to view the third party
software also installed

32
The New Software Installer – The CommServe

• Summary Page

33
The New Software Installer – The CommServe

• Installation Progress

34
The New Software Installer – The CommServe

• You may see this screen which say

“Install Failed”. It did not actually fail,
just reboot and continue on. It should
look like thhe next screen, this should
be fixed later.

35
The New Software Installer – The CommServe

• A reboot will probably be required

36
The New Software Installer – The CommServe

• Resume the setup

37
The New Software Installer – The CommServe

38
The New Software Installer – The CommServe

• Commserve client Name and FQDN or

IP Address

39
The New Software Installer – The CommServe

• Disable the Windows Firewall

40
The New Software Installer – The CommServe

• CS DB Otpions

41
The New Software Installer – The CommServe

42
The New Software Installer – The CommServe

• Installation Summary

43
Post Installation Best Practices

44
 **NEW: Obtaining the License Key

One big change from Version 10, is prior to V11 we could obtain the license
key prior to arriving onsite, now there is a new process.

• CommServe must be installed in customer site

• Must collect CCID, IP Address, Serial No and the Registration Code.

• Then send e-mail to [email protected] to obtain key and apply it to

the Commserve

45
 Post Installation Best Practices
Open the CommVault Control panel and open the hightlighted areas

46
Post Installation Best Practices

Copy the license to

the Commserve and
browse and select
the XML file. Then
click apply.

47
Post Installation Best Practices

The CommCell ID, IP

Address and License
mode can be
determined from
here.

48
Post Installation Best Practices

Enable these options,

they are not enabled
by default

49
Post Installation Best Practices

Note the differences

between the Cloud
and Private
reporting. Be sure to
click “Upload Now”

50
Post Installation Best Practices

Ensure the DR backup

is pointing to a
network share,
preferably on the DR
Commserve

51
Post Installation Best Practices

Set the mailserver so

reports and alerts can
be sent out

52
Thank you.