Download Commvault Definitions and Glosarry

CommVault Price Book Configuration Notes
Release 7.0 PB September 2007
Common Technology Engine Components
The CTE components provide the basic building blocks for a CommVault Simpana data management solution.
Ref
Comment
CS
CommServe: The CommServe component has an embedded MS SQL Server 20051 database. The
CommServe acts as the command & control module within a CommCell domain. Only one (1) CommServe is
used per CommCell domain.
The CommServe ties the elements of the CommCell together; it is the coordinator and administrator of the
CommCell. The CommServe communicates with all agents in the CommCell to initiate data protection,
management and recovery operations. Similarly, it communicates with MediaAgents when the media
subsystem requires management. The CommServe maintains a database containing all the top-level
information relating to the CommCell.
The CommServe also includes support for the following features:
MA
(MA-W =
MA on Win
Server)

Data Multiplexing

CommCell Readiness Check

Client Groups

Multiplexing

VaultTracker (not VaultTracker Enterprise edition)

Directory Services – Enables CV User Group security integration with external user directories (i.e.
Active Directory) for single sign-on authentication with Microsoft Active Directory only

Advanced Copy – Adds Storage Policy support for Deferred AuxCopy and Inline Copy

Advanced Media Mgmt – Enables Unbuffered I/O for disk, Libraries with Mixed Drive Types, SCSI-3
reserve/release resource reservation and support for Firewire, USB or IP libraries (such as ACSLS)

Data Verification – Allows periodic reports to be run against Storage Policies copies to verify the
state of the data stored on media. This can be used to identify media/storage issues before they
risk corrupting large segments data under management.
MediaAgent: The MediaAgent acts as the core data-mover used to transfer data from/to the client agents
(iDA) to the storage media. It can communicate locally or remotely to one or more storage devices that host
the storage media. The MediaAgent also controls the primary “object-level” indexing of all items moving
through the system.
A MediaAgent is valid for both LAN-based and SAN-based connections.
MediaAgents in LAN environment are designed for IP network-based data movement. This includes support
for configuring a single drive tape media management support (LMS & DMS). Additional tape drives, optical
or disk support, or sharing options must be ordered separately.
MediaAgents in SAN environment are installed directly on the production host machine along with the client
agents. SAN-Disk or SAN-Tape library/media mgmt support must be ordered separately.
The MediaAgent can also function as a copy manager to leverages other data transfer mechanisms, such as
NDMP and third-party copy. A copy manager role orchestrates data movement paths between two end
points which may not include the MediaAgent. In such cases, the MediaAgent interfaces with the Remote
Tape Server or the Quick Recovery Agent and Serverless Data Manager (SDM) to move data.
DISK
LIBRARY
Disk Library: A disk library connector enables the creation of disk (magnetic) library from an installed
MediaAgent. The disk library is created as one or many mount paths to locally attached (DAS or SAN) disk
or network CIFS/NFS shares. All disk libraries within the CommCell are now licensed under a consolidated
capacity model based on the expected usable disk space for the entire Cell.
LMS
Advanced Features:
SLMS
Single Instance Storage (SIS): The SIS connector allows the use of one or many Storage Policy SIS
copies to be created in order to more efficiently store backup and archive data on disk. SIS will determine
redundant copies of files and attachments written to the SAME Storage Policy. A link to a single instance of
that file stored on disk produces compression across the copies retained in the storage policy.
DSK
 SIS copies use standard disk within the disk capacity model based on the physical amount of space used
on the disk. This is not charged on the effective amount of logical data stored in the backup and archive
jobs.
Page 1 / 6
CommVault Price Book Configuration Notes
Ref
Release 7.0 PB September 2007
Comment
 Hardware-friendly SIS mode can also be configured on a disk library by using this feature. This controls
the format of backup or archive files written to the disk library. This will break out individual files and
attachments and write them as independent object files to the mount path rather than combining them
into consolidated container or chunk files. Individual object files are more suitable to deduplication
compression at a hardware/storage sub-file level. This mode is recommended with special deduplication
disk devices that present CIFS or NFS shares (i.e. Network Appliance ASIS volumes). In prior releases
this feature was controlled via the “CAS-Option”.
 Software SIS is generally complementary to all deduplication disk storage devices.
Dynamic Mount Path Sharing (DMPS) The Dynamic Mount Path Sharing option for disk libraries is
designed to support AuxCopy operations because it provides SEQUENTIAL access to the disk target. For that
reason, it is not designed to enable a group of MediaAgents to simultaneously share the same disk volume as
a backup/archive target.
VTL
LIBRARY
LMS
Virtual Tape Library: With the confusion in the marketplace, it is important to define a VTL. A VTL (for
CommVault software) is a disk storage system that presents a virtualized tape library (arm changer and tape
drives) interface to the CommVault software. A “VTL” that presents a disk interface: file system, drive, or
volume should be configured and priced as a Disk Library.
SLMS
 A Virtual Tape Library (VTL) connector enables the creation of a direct-attached virtual tape library for a
single MediaAgent. option per library.
TAPE
LIBRARY
Tape Library Management Software: Tape libraries can be configured either as direct attached or shared
access. Libraries can be converted from direct attached to shared access or the opposite.
Tape Library Management Software: (LMS)
LMS
SLMS
 Each direct attached library will require one (1) LMS Library Mgmt Software part #: MM-TAPE-LMS. This
provides library and robotic arm control from a single attached MediaAgent.
Tape Shared Library Management Software: (SLMS)
 Each shared-access, SAN-attached library uses one (1) SLMS Shared Library Mgmt Software part #:
MM-TAPE-SLMS
TAPE DRIVE
DMS
TAPE DRIVE
Tape Drive Management Software: Every drive within a direct attached tape library must be configured
for support.
This requires one (1) Library Mgmt Software item MM-TAPE-LMS, controlling the library and robotic arm
functions, along with the appropriate number of drive licenses MM-DMS. Please note any direct-attached
library can only be configured to a single MediaAgent.
Tape Shared Storage Option: This allows drive pools to be shared between MediaAgents.
Tape Drive Management Software options:
SSO
 In a shared-access, SAN-attached library each drive requires one (1) SSO/iDDS Shared Storage Drive
with intelligent Dynamic Drive Sharing. This item provides the basic DMS functions, so you do not need
to order both.
 An upgrade item, MM-UDDS-U, is available to convert an existing DMS drive to a shared DDS drive.
This upgrade is required on each drive.
Page 2 / 6
CommVault Price Book Configuration Notes
Release 7.0 PB September 2007
Archive Software Agents
The Archive Software client agents provide archive management policies within the Simpana data management
solution. This section is divided into three key sub-sections – File System clients, Application clients, and special
Bundles.
DA FS
DataArchiver File System Archiving: The collection of FS archiving agents enables file archiving policies on a
production host basis.
A FS archiving policy is directed against collections of drives or folders to selectively pick and copy items that
meet the archiving rules. Typically the original item is converted to a stub to reduce the primary storage
footprint and provide a direct access object for the end user. Alternatively the original item can be deleted
entirely from the production system (no-stub rule), shifting the user access method to browse/restore or
search/retrieve. The archived item is managed within the Storage Policy retention copy against a prescribe data
lifecycle.
FS archiving agents are installed on the server that hosts the primary file system and the agents are matched to
the operating system. For example if a Solaris file server hosts files which are in turn exported via NFS shares
to a group of Linux servers, then the DA-FS for Solaris agent would be used to support archiving services
against those files. The FS archiving agent must be installed at the root server which manages the read/write
file access to the primary disk storage system.
Clustered File Server Configurations: DataArchiver FS agents are cluster-aware and should be deployed
within the virtual server in a cluster environment to provide archiving policies on the shared disk and follow the
failover.
DANS
DataArchiver File Share Archiving: The File Share archive agent provides similar archiving capabilities as the
File System archiving agents. It is designed to archive data from Network Shares on NAS devices. Due to the
restriction imposed by NAS devices which that prevents loading local agents directly on the NAS device, this
agent uses a network-based CIFS file access protocol to archive files from the NAS shares and provide
transparent recall services. The File Share Archiver agent is installed on Windows server which is designated as
a Gateway server for this configuration.
Network Appliance FPolicy: A special configuration for Network Appliance ONTAP 7.X environments which use
the File Policy API to trigger stub recalls and extend support to NFS shares.
Page 3 / 6
CommVault Price Book Configuration Notes
DAE
Release 7.0 PB September 2007
DataArchiver Email Archiving: The Email archiving agents provide archiving policies that are targeted
against mailbox or public folder environments to apply either mailbox space management or compliance-capture
archiving policies.
A mailbox or folder space management policy is directed against groups of user mailboxes or folders to
selectively identify and copy items meeting the archiving rules. Typically the original item is converted to a stub
to reduce the primary storage footprint and provide direct access to the original object for the end user.
Alternatively, the original item can be deleted entirely from the production store (no-stub rule), shifting the user
access method to browse/restore or search/retrieve. The archived item is managed within the Storage Policy
copy for a prescribed retention period.
A compliance-capture archiving policies are unique to the email agents which target collection mailboxes where
archive copies of messages are deposited from either message journaling services, SMTP capture or Instant
Messaging systems. Unlike mailbox space management policies, these jobs collect, archive and delete all the
items found in the designated collection mailboxes on each run.
Client Access License(s): Email archiving has a CAL requirement for each active mailbox user and/or
custodian in compliance-capture. Outlook users can be enabled with offline archiving support, and end-user
search after the data has been Content Indexed. All journaled mailbox users are considered custodians.
Clustered Server Configurations: DataArchiver Exchange agents are cluster aware and should be deployed
within the virtual server in a cluster environment to provide archiving policies on the shared disk and follow the
failover.
DA-SP
DataArchiver SharePoint Archiving: The MS SharePoint archive agent provides similar archiving policies to
the File System archiving agents, while it is designed to archive documents from the SP2003 or SP2007
document libraries.
A SharePoint space management policy is directed against groups of folders or document libraries to selectively
identify and copy documents that meet the archiving rules. Typically the original item is converted to a stub to
reduce the primary storage footprint and provide direct access to the original object for the end user.
Alternatively the original item can be deleted entirely from the production store (no-stub rule), shifting the user
access method to browse/restore or search/retrieve. The archived item is managed within the Storage Policy
retention copy against a prescribe data lifecycle.
 MS SharePoint does not provide a journaling service. Compliance-capture archiving against SharePoint,
Public Folders or File data stores can be configured with the backup agents using continuous incremental
backup jobs. Please contact CommVault if this function is required.
Page 4 / 6
CommVault Price Book Configuration Notes
Release 7.0 PB September 2007
Backup Software Agents
Ref
Comment
Data Protection Agents: An intelligent Data Agent (iDA) is used to implement data policy management within a
particular FS, application or database production host server (client). A mixture of iDAs may be used to implement
different types of policies on the same host server.
iDA –
FS
Database Protection iDA: The Database Protection iDataAgent is used to backup and restore FS.
iDA DB
Database Protection iDA: The Database Protection iDataAgent is used to backup and restore databases. Each
agent – MS SQL, Oracle, Sybase, Notes offers a set of special features – please refer to BOLs for details.
iDAExchg
Database Protection iDA: The Database Protection iDataAgent is used to backup and restore databases. Each
agent – MS SQL, Oracle, Sybase, Notes offers a set of special features – please refer to BOLs for details.
Page 5 / 6
CommVault Price Book Configuration Notes
Release 7.0 PB September 2007
Release 8.0 uses Enterprise edition of SQL2005 database as the embedded CommServe database. This does not require
additional licensing for use.
1
Page 6 / 6