Commvault Questions
Commvault Questions
© Copyright by Interviewbit
Contents
Storage Area Networks (SAN): The VMware Backup Host must be installed on a
physical computer that has access to a Fibre Channel or iSCSI SAN that contains
the virtual discs to be accessed. Because no data must be sent through the
production ESX/ESXi host, this is an efficient data channel. In this mode, the
vStorage APIs get information about the structure of VMFS LUNs from the
vCenter server or the ESX/ESXi host and then read data directly from the SAN or
iSCSI LUN where the VMDK is stored.
Local Area Network (LAN): The ESX/ESXi host reads data from storage and
transmits it via a network to the VMware Backup Host in this mode. Unlike SAN
transfer, this kind of transport does require a LAN. The following are some of the
benefits of LAN transport:
Any storage device, whether local storage or NAS, can be used by the
ESX/ESXi host.
Because the VMware Backup server could be a virtual machine, you can use
VMware vSphere's resource pool and scheduling capabilities to reduce the
backup's performance impact. You can put the VMware Backup Host, for
example, in a different resource pool than the production ESX/ESXi hosts,
with a lower backup priority.
If the ESX/ESXi host and the VMware Backup Host are on the same private
network, you can use unencrypted data transfer instead of NBDSSL, which
is faster and uses fewer resources. You can transport virtual machine data in
an encrypted form using NBDSSL if you need to protect sensitive
information.
HotAdd: When running VMware Backup Host on a Virtual Machine, vStorage APIs
can use the ESX/ESXi server's SCSI Hot-add feature to attach the VMDKs of a
backed-up Virtual Machine to the VMware Backup Host. It's simple to move a
virtual machine around, and it can back up local storage without utilising the
LAN, however, this has a higher burden on the physical ESX/ESXi host than using
SAN transport mode.
Network Attached Storage (NAS): The VSA proxy computer can read data
directly from the network file server using NAS.
IRM CommCell: The IRM CommCell, which is based on the Microso Windows
platform and Microso 's SQL Server Express, consolidates all task management
functions, metadata, scheduling, and reporting into a single console. The
CommServe application and the MediaAgent are two standard components in
this IRM CommCell. These two components share a single operating area known
as a CommCell.
CommServe: CommServe is the master server in charge of CommCell's
configuration and operations. It runs on a Windows host server and includes an
embedded version of Microso SQL Express, which serves as IRM's top-level
database. Each CommCell has one CommServe, which must be available to run
operations. The CommServe handles only job control and metadata. The
MediaAgent specified in the CommCell is used to perform indexing and snapshot
management.
CommServe Database: The CommServe Database is built on Microso SQL
Express Edition and contains all of the CommServe's history and usage.
Information such as work history, client settings, media type, and so on are all
maintained in the database, and every item of data that is retrieved, saved, or
deleted is recorded in the CommServe database.
CommCell Console: It is the console that contains all of the CommCell
environment's administration features and capabilities in a single pane. The
console is java-based and may be launched as a local console instance or
accessible through a browser from anywhere. In this console, all policies,
operations, scheduling, alerting, and reporting are integrated and displayed to
users depending on their security permissions and roles.
MediaAgent: The MediaAgent is a data mover and indexing resource in a data
management environment's data movement workflow. This component plays a
variety of roles in the creation/mounting of snapshots and the cataloguing of
client-relevant material. The MediaAgent will also act as the disc library's media
library manager, storing index data. Those indexes are stored in the Archive file
format, so they can't be mounted or used directly; instead, you'll need to do a
restore to get a native recovery copy of the data.
IRM Clients: In IRM, clients are servers and systems that use snapshot
integration with production storage arrays. Each server will have a base File
System iDataAgent installed to facilitate essential connectivity with the
CommServe. You can then load more iDataAgents for application integration or
VMware integration, depending on the information or data you want to
safeguard. These agents provide the appropriate level of integration for File
Systems, Databases, Exchange, SQL, and VMware guests to guarantee that the
necessary data is secured at the appropriate level.
These agents will also ensure that VSS writers are properly called to ensure that
the data in the snapshot at the point-in-time is consistent, that "ESEUtil"
commands can be used to check Exchange Database consistency, and that
VMware calls the appropriate so ware quiescing mechanisms to create
consistent VMs.
The following points illustrate the differences between snapshot and backup:
Backups can be kept in multiple places, on the same disk, or even on the same
server. They don't necessitate both off- and on-site storage. Snapshots
necessitate both on-site and off-site storage, and they must always be kept in
the same locations as the original system data.
Backups for SQL servers are normally done through a subscription service. The
operations involved in creating snapshots are normally free and can be done at
any time.
When it comes to backups, there can be discrepancies between when they
started and when they finished. Snapshots are "pictures" of your server that
retain it in its current state.
Making backups can be a time-consuming and laborious task. Snapshots are
instantaneous and take a fraction of the time. Snapshots also save time when
copying data.
Only the file system is included in backup files. Different types of systems can be
captured in snapshots. Files, programs, settings, and other items fall into this
category.
Backups are saved in various locations and can be readily recovered. Backups
are frequently verifiable as well. Snapshots aren't the same thing as backups.
They can (and should) be utilised as a part of the backup process, but they are
primarily short-term solutions. When a backup is finished, snapshots are
removed.
12. How can you know if a job has been encrypted, and if so,
how?
For jobs that have been so ware or hardware encrypted, a superscript E or a HE will
appear next to the job ID in the Jobs in Storage Policy report.
So ware encryption is a CPU-intensive activity that can slow down your backup or
supplemental copy by 40 per cent to 50 percent. This projected performance hit does
not apply to deduplicated data because the deduplication process removes all
duplicate data and only encrypts data blocks that are unique throughout the whole
deduplication database. As a result, the performance impact of deduplicated data
will be minimal.
For a few seconds, all communication with the active DDB is halted. To ensure
that the DDB is in a dormant stage, the information in memory is committed to
memory.
The DDB process uses VSS (Windows) or LVM (Linux) snapshots to make a
snapshot of the volume.
The file systems Extended 3 File System (ext3) and VERITAS Volume Manager
(VxVM) are also supported on the Linux platform.
All communication with the DDB is resumed when the snapshot is created, and
the DDB is automatically backed up from that snapshot.
If a VSS (Windows) or LVM (Linux) snapshot fails, the DDB backup falls back on a
live volume backup.
The snapshot is erased a er a successful DDB backup. The Job Controller
displays the DDB Backup job in a running condition at this point.
If the DDB MediaAgent restarts during a DDB backup job, the job is marked as
Pending. The DDB backup job resumes from the beginning a er the restart.
The DDB backup jobs for the auxiliary copy operation are disabled by default,
and these jobs appear as unavailable when viewed from the primary copy.
Allowing DDB Backup Tasks from Being Copied to Secondary Copy describes
how to enable or prohibit DDB backup jobs from being copied to secondary copy
during the auxiliary copy procedure.
Storage Policy: The storage policy determines where the data is saved and how
long the snapshot will be kept. Copies can be found within a Storage Policy. In
the IRM environment, these copies define retention for the designated storage
devices. Within IRM, there are just two versions of interest. The Primary
Snapshot Copy and the Primary Copy are two different copies of the same thing.
The Primary Snapshot Copy merely specifies how long the snapshots will be kept
and which MediaAgent will be cataloguing them. The Primary Copy specifies the
location of the catalogued indexes.
Job Manager: Displays all information about a running job, including data
protection, recovery, and Auxiliary copy, as well as settings and media usage.
Snapshot jobs can be launched, suspended, restarted, and cancelled by the Job
Manager.
Backup Set: A backup set is a sub-container present within each of these agents.
The backup set is the client's overall container. The most straightforward
approach to comprehending a backup set is to relate it to the context of the
system being snapped in the environment. The backup set for the file system
iDataAgent is the fundamental physical system storage environment, whereas
the backup set for these two database agents is the Exchange Information Store
or SQL instance. An overall vCenter is the backup set in a Virtual Context since it
encompasses numerous ESX servers that house and manage virtual machines.
Subclient: The smallest subset of a client is called a subclient. From the
perspective of a Windows host, it may be a single folder, a single database, a
single Virtual machine, or a single LUN or drive letter (regardless of how many
LUNs are meta-LUN'ed to produce one huge LUN pool). Sub clients are backup
set definitions that are related to Storage Policies, which define the snapshot
data's retention and location.
Collect Files: During an IntelliSnap job, Collect Files are smaller text files that
will gather information on what is on each of the clone/snapshots. The original
information lying on the snapshots is indexed by the collect files saved under the
task result directory under each of the IRM clients when the snapshot is
mounted to be catalogued. Once the cataloguing is complete, the information
will be given immediately to the MediaAgent who will store it in indexes for a
longer period of time. These indexes will remain on the MediaAgent for the
duration of the snapshot's retention period, either in the local MediaAgent index
cache or in the disc library set up to protect the indexes and the CommCell
database backup.
CommVault Documentation
VMware Interview Questions
Technical Interview Questions
Coding Interview Questions
Online Coding Round 1: The coding round is typically a 1 hour long round and it
usually consists of 10 - 15 MCQs and 2 - 3 coding questions. The MCQs are based
on computer fundamentals like Operating Systems, Object-Oriented
Programming, Database Management Systems and Computer Networks.
Coding Round 2: The candidates who clear the online coding round have to go
through one more coding round. This round assesses a candidate’s data
structures and algorithms knowledge as well as system design skills. This round
is a long one, usually ranging from 5 to 7 hours. Candidates are connected with
mentors who can help them while they are designing.
Technical Interview Rounds: The candidates who clear the online coding round
are then required to appear for face-to-face technical interview rounds. Usually,
at Commvault the candidates are required to go through 1 technical round. Here
the interviewer assesses the technical skills of the candidate. You can expect
questions based on computer fundamentals like Object-Oriented Programming,
Database Management Systems, Operating Systems, Computer Networks and
coding questions based on data structures and algorithms.
HR Round: The candidates who clear the above rounds need to go through one
last HR round. Here the interviewer assesses whether or not the candidate is a
cultural fit for the company.
Css Interview Questions Laravel Interview Questions Asp Net Interview Questions