Explore topic-wise InterviewSolutions in .

Pass-phrases are not saved. For each recovery, the USER must MANUALLY enter the pass-phrase. The system, on the other hand, can RECOVER the client's data to that (and only that) machine by producing and exporting a file that CONTAINS the scrambled pass-phrase of the client's computer to a designated directory on ANOTHER computer.

The encryption keys are not accessible to anyone. These keys are encrypted with the client's RSA public key and kept in the CommServe DATABASE. Depending on the settings, the client's RSA private key is encrypted with either a built-in PASSPHRASE or a passphrase provided by the USER. The Pass PHRASE entered by the user is not saved. These passphrases can only be set and changed by authorised users (as determined by user management). Passphrases are NEVER written down in plain text.

Disaster RECOVERY PROTECTION is PROVIDED through a regularly SCHEDULED EXPORT and Backup of the CommServe Database (DR Backup activity).

Software 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 jobs that have been software or hardware encrypted, a superscript E or a HE will appear next to the JOB ID in the Jobs in Storage POLICY report.

• Backup: A backup is a copy of a file or other piece of data. When you start a backup, it copies your files. These duplicates are stored in a different location. Depending on the amount of data you're backing up, backups can take a long time to complete.
• SNAPSHOT: Snapshots are a kind of "picture" of your server's file system that you can take at any time. This picture accurately depicts the server at the time it was taken. SERVERS can be restored using snapshots by restoring them to the state they were in when the snapshot was taken.

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.

A snapshot is a "picture" of your server's file system taken at a certain point in time. In the event of data loss or corruption, this picture of your file system is frequently UTILISED to recover complete servers. When there isn't enough space, fresh snapshots will typically overwrite EXISTING snapshots. Snapshots can come in handy in a variety of situations.

The following are the ADVANTAGES of having a snapshot:

• Snapshots are tiny and can be taken quickly and simply without causing too MUCH server load.
• They improve app availability, speed recovery, simplify backup administration for large data volumes, and reduce data loss risk.
• Snapshots can be scheduled and used for system backup as needed.
• They can almost completely eliminate the requirement for backup windows while ALSO lowering the total cost of ownership.
• Snapshots can be used to recover data that has been corrupted or destroyed. (In the event of file corruption, you can also roll back to an older version of a snapshot.)
• Rather than restoring the entire system, replicated snapshot copies can be used because they are already in their natural format.
• You can immediately begin restoring a server from a snapshot.

For deduplicated STORAGE POLICIES, the DEFAULT BLOCK SIZE is 128kb.

• IRM CommCell: The IRM CommCell, which is based on the Microsoft Windows platform and Microsoft'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 Microsoft 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 Microsoft 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 software quiescing mechanisms to create consistent VMS.

The following are some of the more COMMON or more frequent backup ISSUES:

• Network communication issues.
• Destination disk library full.
• Client services might be SHUT down for maintenance.
• Media AGENT offline.
• VSS snapshot backup failure.
• Data PATH offline.

First and FOREMOST, the backup administrator must ensure that all planned jobs are operating as expected. If they don't, they'll have to go over the WORK again to figure out what's WRONG and how to fix it.

They must ALSO participate in some of the following checkups:

• Check for Media agents to make sure they aren't in offline mode.
• To monitor the free space or remaining space in the disc libraries on a frequent BASIS.
• Extract a failed backup report and examine it so that the rectification process can continue.
• Check the reporting tool on a frequent basis for the deployment, decommissioning, and restoration requests.

• 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.

In Commvault, WHENEVER a storage policy with deduplication is implemented, signatures are generated for data blocks during BACKUPS, COMPARED, and then stored in the deduplication DATABASE (DDB). The DDB backup subclient automatically protects DDBs. All active DDBs controlled by the MediaAgent that hosts the DDB are backed up by this subclient. You can set up a reconstruction task for an automatic or on-demand RESTORE of the DDB from the DDB backup in the event of DDB failure. The storage metadata can then be used to rebuild missing records.

The key features of Commvault are as follows:

• Provides Backup: Virtual machines, applications (including cloud), databases, endpoints, and files are all protected by backups. This has the following benefits:
  • Customized schedules to satisfy any SLA with policy-driven automation, monitoring, and reporting; no TEDIOUS SCRIPTS are required.
  • Data that has been deduplicated for faster data transmission.
  • Auto-discovery protects newly uploaded data sets in a proactive manner.
  • Customized retention for compliance and recovery.
  • Encryption at rest and in transport can be configured.
• Provides recovery: Recovery of virtual machines, apps (including cloud), databases, endpoints, and files is ensured. This has the following benefits: 
  • Recovery of the full system, instance, or application.
  • Granular single file recovery.
  • In-place or out-of-place to a different location.
• Enables migration: Workload migration from on-premises to cloud, or between clouds is enabled. This has the following benefits:
  • Minimal need for customised scripts. 
  • No downtime for production systems.
  • Data portability between clouds. 
  • Avoids vendor lock-in.
• Integration of hardware snapshots: Commvault LEVERAGES hardware snapshots for near-instant recovery of full data volumes. This has the following benefits:
  • Support for all major snapshot hardware vendors.
  • Automated snapshot backup and recovery. 
  • Customized snapshot retention.
• Integration with the cloud: We can use the cloud for scalability, mobility, availability, and cost SAVINGS for production workloads. Commvault has the following benefits with regards to this:
  • Support for all major cloud vendors.
  • Backup, recovery, and migration to, in, and from the cloud on a single platform.
  • Maintain compliance control on both on-premises and cloud data management.
• Flexible storage options: We can have multiple copies of data in multiple locations. Commvault has the following benefits with regards to this:
  • Disk library – individual hard drives or RAID ARRAY. 
  • Tape library.
  • Cloud storage – all major suppliers supported. 
  • Network-attached storage (NAS).
  • Deduplication for more efficient – and cost-effective – data storage.

The following are the advantages of using Commvault:

• Storage: Data can be securely STORED on tape, disk, and DATABASE servers. We can employ data autonomous multiple copy management to meet all compliance and DISASTER RECOVERY requirements.
• Access to data and information: We can access and save emails and data files, as well as assist in retrieving and recovering them on a constant basis from mobile and online browser sites.
• Changing, analysing, and reporting: To give a full review to the CommCell, Commvault modifies the events that require attention, reports with in-depth information on the operations, and detailed data analytics.
• Data SECURITY: All of the major applications and operating systems provide data protection methods such as archiving, replication, backup, and snapshots.
• Administration: A single administration interface is used to manage all administrative tasks. Web pages and mobile devices can be used to perform the tasks.

Commvault is a data protection SOLUTION for medium and large businesses and is in EXTREME demand today. To handle an application’s disaster recovery and data protection activities, it offers an exceptionally flexible web user interface. It minimises the time it takes to perform routine data recovery and protection operations by USING default simplified methods and configuration parameters. We can identify the stuff we want to secure and start and control restores and backups using Commvault's command centre.

Leading multinational CORPORATIONS such as Adobe, Apollo Tyres, Microsoft, NTT DATA, and NASA rely on Commvault to manage their RAPIDLY changing business environments. The latest Commvault features streamline the data backup and recovery processes.