0. Running and Scheduling Backups

1. What are the parts to put together
Data to be backed up
SubClient
How to back it up and copies to make
Storage Policy
Schedule
When to run a Job for the SubClient
Job
Actual Dataset created

2. Key Commvault Terms
Job – Every backup activity. Has a unique ID and also represents the dataset.
Schedules– When and how frequent to run a Job. Set per-Job basis or via a Schedule Policy
SubClient – A logical object created under a client agent that defines what data to be backed up using which Storage Policy

3. CommVault clients and agents
Intelligent Data Agent (iDA)
FileSystem Agent
Exchange DB Agent
Exchange Mailbox Agent
SQL DB Agent
SharePoint Doc Agent
SharePoint DB Agent
Oracle DB Agent
Domino Notes Doc Agent
Domino Notes DB Agent
etc PC
Desktop
Win Server
UNIX Server
Linux Server
CommVault
Client

4. Client object structure
Job related settings:
“which storage policy to use”
Agent related settings : “Exchange login account”
CommVault Client
Filesystem iDataAgent
Exchange iDataAgent
Oracle iDataAgent
SubClient 1
C:\
SubClient 1
“Exchng Info Store”
SubClient 1
“orcl” instance
SubClient 2
D:\
SubClient 1
“Exchng DB2”
SubClient 2
“HR” instance

5. Subclient examples Subclient Type Subclient Content
Filesystem Subclient
D:\
Exchange DB Subclient
Exchange mail DB 3
Exchange Mailbox Subclient
Exchange User Mailbox “user1”
MS-SQL DB Subclient
SQL DB “datadb2”
MS-SharePoint DB Subclient
SharePoint Content DB 1-3
CommVault
iDAs

6. Subclient rules
DEFAULT subclient always exists and represents all the content for the client – for example all drives & system_state
User-created subclients cannot overlap in terms of data.
Filesystem iDataAgent
SubClient 1
C:\
SubClient 3
D:\data
Cannot be created as it overlaps with SubClient 2
SubClient 2
D:\

7. Filesystem iDataAgent
What is a backupset
BackupSet is only used if you need to define a SubClient which overlap existing SubClient content
Filesystem iDataAgent
DefaultBackupSet
NewBackupSet
SubClient 1
C:\
SubClient 3
D:\data
SubClient 2
D:\

8. Client and Subclient in the gui
BackupSet

9. Inside a subclient Content – the data on the client to be protected
Storage Device – the Storage Policy to use, compression & deduplication & stream settings
Pre & Post Scripts – customized scripts can be used to run pre-job and post-job

10. Jobs

11. Running backups Right-click a SubClient and choose option to “Backup”
Choose the type of backup
Full
Incremental
Differential
Synthetic Full
Choose when to run it
Create a permanent schedule
Create a one-time schedule
Run it immediately

12. Choosing the right type of backup
Synthetic FULL – Full backup/archive copy created internally by CommVault by assembling last full and incremental copies. Works for files, and documents.
Full, Incremental/Differential and Synthetic Full backups should have its own schedules
SubClient 1
Sched Name
Sched Type
Sched Timing
OneTimeFull
Full
1 Jan 00:00
DailyIncr
Incremental
Mon – Fri 00:00
WeeklySynFull
Synthetic Full
Sat 22:00

13. More on scheduling
You can view the SubClient schedules individually by SubClient or for the entire CommCell
Schedule Policies – Define a fixed schedule and apply it to multiple subclients. Useful in big customer environment where you have many SubClients and it is difficult to schedule each SubClient one-by-one.

14. Making copies
To trigger the 2nd or 3rd copies in the Storage Policy, you need to run a process called Auxiliary Copy
AUX Copy– A copy of a backup/archive dataset (Job).
DASH Copy – An AUX Copy that makes a replicated copy of a Job over to another Media Agent with Deduplication during the transport process

15. Scheduling aux copy Similar to scheduling or running Backups
Immediate
Scheduled
Automatic every 30 minutes
Run from Storage Policy, NOT SubClient
Schedule Policies can also be created to apply to AUX Copies
Backup
Run from SubClient level
Apply to that specific SubClient
AUX Copy
Run from Storage Policy
Apply to all SubClients using that Storage Policy

16. Viewing running Jobs Job Controller Job details
Shows Jobs (Backup or Aux Copy) running and status
Job will disappear after about 5 minutes afterJob completion
Job ID is unique identifier of the Job and the completed dataset
Job details
Double-click to get more detailed info about each Job

17. Summary of Creating backups
1. Create a SubClient
SubClient
2. Associate it to Storage Policy
Storage Policy
Backup Job
Aux Copy Job
3. Run or Schedule from SubClient
4. Run or Schedule from Storage Policy
View from JOB CONTROLLER

18. Lab