Client:-: It Is Used To Reduce The Load On Commserver
Client:-: It Is Used To Reduce The Load On Commserver
Client:-: It Is Used To Reduce The Load On Commserver
Subclient :-
A Logical container which manages specific production data(drives, mailboxes, folders, databases) to be protected
Media Agent :-
The MediaAgent is the data transmission manager in the CommCell environment. It provides high performance
data movement and manages the data storage libraries. MediaAgent tasks are coordinated by the CommServe
Server.
Commvault Agent:-
Used to be installed on physical and on any physical servers and DB servers to communicate.
Storage Policy :-
A logical management entity with rules for the lifecycle management of protected data in a subclient
ComServe Server:-
DE-DUPLICATION
MediaAgent Indexing :-
An object(file, message, document and so on) is sent into multiple data blocks and these blocks are tracked by
media agent index. This index allows the data blocks to be reassembled so that the object can be restored or
copied to other locations.
General Architecture
Primary Commserver at HLB: HLBWCVCSP001.corp.standard.com
Six media agents at HLB: HLBWCVMAP101, HLBWCVMAP102, HLBWCVMAP103,
HLBWCVMAP104, HLBWCVMAP105, HLBWCVMAP106.
Six media agents at DFW: DFWWCVMAP101, DFWWCVMAP102, DFWWCVMAP103,
DFWWCVMAP104, DFWWCVMAP105, DFWWCVMAP106.
At DFW, Partitioned Deduplication with four partition each MA hosting two DDB.
Disk Library at HLB: HLB_DiskLibrary1, HLB_DiskLibrary2, HLB_DiskLibraray3
Disk Library at DFW: DFW_DiskLibrary1 & DFW_DiskLibrary2 (Shared with all DFW MA)
DASH enabled AUX copy for replication.
Primary Copy of clients located in HLB, is local at HLB and for Clients at DFW, local copy at
DFW disk library.
DASH copy for HLB primary backup to DFW and for DFW to HLB.
Aux copy enabled for both Production & Non-Production servers.
Two FRE (file recovery enabler) has been deployed. One for HLB and one for DFW. FRE
templates can be downloaded from commvault cloud store.
FILE RECOVERY:-
Unix work
PING
CVPING
Dash Copy :-
AUX Copy :-
It’s an operation for creating secondary copies. If the primary copy becomes inoperative due to a media failure or
library or network malfunction, one can promote secondary copy to primary without interrupting backup and
restore operations.
BACKUP WORKFLOW
DATA AGEING:-
the process of removing old data from the storage to allow the associated media to be reused for future backups.
You can change the retention criteria of your data based on your needs.
STORAGE POLICY
DATABASE
LUN
MOUNT PATH
SERVICES RUNNING
RETENTION
Commvault Backup
Schedule and Retentions.docx
TROUBLESHOOTING
ENVIRONMENT
LIBRARY
COMMVAULT SUPPORT
LOGS/TRANSACTION LOGS
INDEXING
DSR CALL
SLA CALL
CHANGE
Data Aging is the process of removing old data from the storage to allow the associated
media to be reused for future backups.
Both are the same which you got correct, both the processes are meant to remove the data from
commvault In data pruning the expired date data will be marked as pruned and will be picked for data
aging process, The data aging is a functionality through which the pruned jobs are picked and through
data aging job the pruned jobs gets deleted and the media occupied by the jobs will be released for
further use.
Both data pruning and data aging process are inter related, you cannot find a notification where it shows
data is pruned, The data pruning process is completely for commvaut softanwe understanding so that
when the data aging jobs run the aged jobs get deleted.
In the older versions we used to observe this processes running separately but later on both the processes
are merged into data aging job itself.
DATA DELETION
DECOMISSION
Difference between Commvault 10 and 11
Commcell id : fddd3
REQ0183189
REQ0183190
S006829
COMPONENTS _/
THEIR NAME
Definition
NETWORK BANDWIDTH
Physical Machines Daily Incremental - 06:00 Daily Incremental – 32
(Prod) PM Days
Weekly Full – 06:00 AM Weekly Full – 32 Days
Monthly Full – 06:00 AM Monthly Full - 365 Days
2x10Gig network connectivity between the two sites HLB and DFW
TYPES OF BACKUPS
SCHEDULE WINDOWS
TIMINGS
ADDRESS OF LOCATIONS
Datacentre City Address
1. No.
2. Commcell id : fddd3
3. Registered Mail ID : standard
4. Problem Description
5. Ask Mr. Vimal Shukla for a Document For the same
SLA
P1-15min- 1hour
P2-30min- 2hours
P3-1hours – 1day
P4-4hrs- 3-4days
Backup License
1. Per Machine
2. Capacity Based
DD data
Backup Cycle
JOBS
RESPONSIBILITIES
reporting, maintenance of our servers, health checks, backups performance and failures.
We handle all the criticalities, alerts and montoring phases, plus we also work on configurations,
vulnerabilities and upgradations of our environment supported services and Softwares.
Firstly Monitoring, this is very crucial ( Your basic responsibility would be to monitor mails, Incident queue
and ongoing jobs console for every 30mins as long as you're in the shift) this helps in achieving the timely
response to our tasks.
Secondly health checks, irrespective of shift make sure you check for the backup failures for past 24 hours
and the status of our backup servers through the console, include to check All the admin jobs histories as
well.
Finally the incident\Tasks management take ownership on your own and make sure all the incidents are
updated or closed same applies to tasks as well.
Physical/Virtual