Commvault SQL Server Training Session 18 - Summary Notes

Training Series Overview

Completed Sessions (1-17)

1. Session 1: Commvault product overview and course outcomes

2. Session 2: Package download for Linux and Windows

3. Session 3: Azure cloud VM creation and deployment

4. Session 4: VM creation in Azure environment

5. Session 5: Package installation in VMs (push install and local install methods)

6. Session 6: Home lab setup using VMware Workstation with Command Center focus

7. Session 7: Console package installation and first plan creation

8. Session 8: Day-to-day backup admin activities (L2 level responsibilities)

9. Session 9: Client machine creation and file system package installation

10. Session 10: Disk storage and server plan creation (dedupe and non-dedupe storage)

11. Session 11: Sub-client creation, plan assignment, backup and restore processes

12. Session 12: Command Center vs Console Console differences

13. Session 13: Backup types and data aging, disaster recovery jobs

14. Session 14: Cloud library setup with AWS S3 bucket

15. Session 15: Tape library configuration

16. Session 16: Hyper-V manager and architecture

17. Session 17: Hyper-V agent configuration and operations

Session 18 Focus

 SQL Server database setup and installation

 SQL Server agent configuration in Commvault

 Database backup and restore operations

SQL Server Background

Market Context

 Microsoft SQL Server is enterprise-level database platform

 90% of Fortune 500 companies use either Oracle or SQL Server

System Requirements for Lab

 Minimum 16GB RAM and 6-core processor for complete lab setup

 8GB RAM acceptable for basic testing (may experience performance lag)

 VMware Workstation for virtualization

SQL Server Installation Process

VM Preparation

1. Create new virtual machine in VMware Workstation

2. Install Windows Server 2019 operating system

3. Configure prerequisites:

o Disable all firewalls

o Configure static IP address

o Enable Remote Desktop Connection

SQL Server Software Installation

Required Components:

1. SQL Server Engine (database engine)

2. SQL Server Management Studio (SSMS) (management interface)

Installation Steps:

1. Download SQL Server Developer Edition (free version)

2. Select "Basic" installation type

3. Accept default configuration settings

4. Install SSMS separately from Microsoft website

5. Use Chrome browser if Internet Explorer shows compatibility issues

Database Setup

1. Download AdventureWorks sample database (.BAK file)

2. Restore database using SSMS:

o Right-click Databases → Restore Database

o Select "Device" option

o Configure file paths for data and log files

o Complete restore operation

SQL Database File Types

File Type Extension Description

Data Files .mdf Metadata database files (primary data)

Log Files .ldf Transaction log files (all database changes)

Commvault SQL Agent Configuration

Prerequisites Information from SQL DBA

 SQL Server hostname or IP address

 Server credentials (local administrator or service account)

 Database authentication details (if required)

Configuration Methods

Method 1 - Guided Setup:

1. Navigate to Command Center → Guided Setup → Databases

2. Select SQL Server option

3. Enter server details and credentials

4. Select appropriate backup plan

5. Complete installation

Method 2 - Add Server:

1. Navigate to Manage → Servers → Add Server

2. Enter hostname/IP address of SQL server

3. Configure credentials

4. Select SQL Server package

5. Assign backup plan

Credential Configuration

Server Credentials:

 Machine-level access credentials

 Use dot-slash format (\administrator) when no Active Directory

Database Credentials (Optional):

 SQL Server authentication if required

 Configured separately in SQL Server authentication section

Agent Installation Process

1. Installation job starts automatically after configuration

2. SQL Server agent and File System Core packages install together

3. File System Core is dependency package for SQL agent

4. Monitor installation through Jobs section

5. Verify successful installation in Manage → Servers

Database Discovery and Configuration

Automatic Discovery

 SQL agent automatically discovers database instances

 System databases appear by default after installation

 User databases require manual content selection

Content Configuration

1. Navigate to Products → Databases

2. Select SQL Server instance

3. Access subclient properties

4. Edit content to add specific databases

5. Select required databases (e.g., AdventureWorks)

Authentication Issues Resolution

Problem: "Does not have sysadmin role" error

Solution:

1. Verify sysadmin role in SSMS (Security → Logins → Properties → Server Roles)

2. Configure SQL Server authentication in Commvault

3. Create new credential with proper format

5. Apply hostname\administrator format for credentials

Backup Operations

Manual Backup Process

1. Navigate to configured database subclient

2. Trigger ad-hoc backup

3. Monitor job progress in Jobs section

4. Verify completion and backup time

Production Considerations

 Always obtain DBA consent before manual backups

 Respect production hours and maintenance windows

 Follow scheduled backup windows when possible

Restore Operations

Database Restore Process

1. Navigate to Products → Databases → SQL Server Instance

2. Select target database

3. Choose recovery point (latest backup)

4. Select restore type:

o In-place restore: Overwrites existing database

o Out-of-place restore: Restores to different location

5. Obtain customer consent for overwrite operations

6. Submit restore job

7. Verify completion with DBA team

Post-Restore Verification

 DBA team runs SQL queries for verification

 Confirm all tables and data integrity

 Database appears in SSMS after refresh

Console Console vs Command Center

1. Navigate to Client Computers → Add Client

2. Use Tools → Add or Remove Software for manual selection

3. Select MS SQL agent in Applications section

4. Configure same credentials and settings

5. Instance discovery occurs automatically

6. Manual content configuration required

Key Differences

 Terminology: "Client" in Console vs "Server" in Command Center

 Renaming only possible through Console Console

 Both interfaces provide same functionality

Resource Management Tips

Lab Environment Optimization

 Start only required VMs (CommServ, MediaAgent, SQL Server)

 Power off unused VMs to conserve resources

 Prevents laptop overheating and performance issues

Production Environment Notes

 All servers run 24x7 in production

 No stopping of services during business hours

 Resource management not applicable in enterprise environments

Network Requirements

Port Configuration

 Default CVD port: 8400 (between CommServ and clients)

 Additional ports: 8403 and others for Windows

 Port 443 for secure communications

 Firewall team coordination required for port opening

Troubleshooting Common Issues

Installation Problems
  VMware Tools installation enables copy-paste functionality

 Manual typing required without VMware Tools

 Credential format must match hostname\username pattern

Authentication Issues

 Verify sysadmin roles in SQL Server

 Use proper credential formats

 Configure SQL Server authentication when Windows authentication fails

Database Discovery Problems

 Instance discovery happens automatically

 Manual content configuration always required

 Refresh interfaces after configuration changes

Upcoming Sessions

 Session 19: Commvault upgrade and maintenance release procedures

 Future sessions: Oracle agent and VMware agent (pending lab setup)

 Doubt clearing session: Dedicated Q&A session for all accumulated questions

Important Notes for Backup Administrators

 L2 level training provides product awareness and implementation skills

 Interaction required with multiple teams (VMware, DBA, Cloud, Kubernetes)

 Cross-platform knowledge beneficial for career growth

 Documentation serves as primary reference guide

 Always follow documented procedures for configurations