Newsletter for New Features in Feature Release 11.21

• Enabling SSL Communication with the SAP HANA System

• Commvault VTL improves backup-restore throughput by going over a fibre channel.
• Commvault VTL simplifies disaster recovery of IBM i servers.

• Install Commvault VTL for the IBM i File System Agent on the Linux access node.
• Configure Fibre Channel (FC) network zoning to allow access to the Linux access node FC target from the IBM i server.

• Installing VTL on the Linux Access Node

• View the DB2 version upgrade history in the Command Center
• View the DB2 version upgrade history in the CommCell Console

• Disk and tape library settings
• Storage policy and storage policy copy settings
• Media management settings
• Data aging settings

• CommCell Configuration Audit Report

• Notes Database Agent: System Requirements
• Notes Document Agent: System Requirements
• Domino Mailbox Archiver Agent: System Requirements

• IntelliSnap Support for Virtualization

• Disk Caching for Frequent Log Backups
• Optimizing Informix Log Backups

• SharePoint Online
• Microsoft Office 365 with SharePoint Server

• Uses Commvault IntelliSnap technology to protect the cluster
• Protects both replica set topologies and sharded cluster topologies
• Protects the MongoDB databases from the secondary node, without using the primary node resources
• Allows recovery of the entire cluster
• Allows recovery to the original cluster or to a different cluster with the same number of shards, on-premises or within the cloud

• MongoDB

• MEDITECH with Nutanix AHV for the Command Center

• Configuring Copy-Only Backups on Availability Group Instances

• You can restore data from the copied snapshot even if the source snapshot or the source RDS or EC2 instance is deleted, thereby providing an additional layer of security or air gap.

• Amazon RDS
• VSA for Amazon

• Creating a Snapshot Copy of Amazon RDS or an Aurora Database in a Different Account
• Creating a Snapshot Copy of Amazon EC2 in a Different Account

• Backups for Azure (Command Center)
• Backups (CommCell Console)

• Backups and restores using vStorage APIs for Data Protection (VADP)
• Changed block tracking (CBT)
• Full, incremental, differential, and synthetic full backups
• Restores of full VMs, VMDKs (alone or attaching to a VM), and guest files and folders
• Agentless file recovery
• Application-aware backups
• VM conversion from VMware to Microsoft Azure
• VM conversion from Microsoft Azure to VMware
• Live Sync replication and Live Sync Direct for snapshot-based replication
• Replication from VMware to Microsoft Azure

• Support for Azure VMware Solution

• Backups for Google Cloud Platform

• Quickly configure file servers, storage, and subclients to back up
• Back up subclients immediately or on a schedule
• Restore CIFS shares and NFS exports to the source Nutanix Files file server or any other file location
• Monitor jobs, events, and alerts

• Windows File System Agent
• Linux File System Agent

• Nutanix Files

• Performing File System Restores to Cloud Storage Accounts

• Converting to Azure Stack Hub

• Replication of SAP HANA Databases

• Azure NetApp Files for SAP HANA

• Microsoft Azure Snap

• Creating Disk Filters for Google Cloud Platform

• Oracle
• SAP HANA
• UNIX File System
• Windows File System

• Google Cloud Platform

• The user must have Service Administrator role privileges.
• The access nodes must be in the Azure cloud.

• Configuring an Azure SQL Instance

• Use STS:AssumeRole to centralize backup operations, while assuming the role of each protected sub-account during backup activities.
• Remove the requirement to provision Amazon Access Nodes per account, by using a single pool of Access Nodes to protect many accounts.
• Remove the use of Access Key/Secret Key configurations which require manual key rotation to stay secure over time.

• Virtual Server Agent (VSA) for Amazon
• Virtual Server Agent for Elastic Kubernetes Service (EKS)
• Cloud Apps agent for Amazon S3

• At least two distinct Amazon accounts or IAM Roles must exist.
• The sub-account must explicitly trust the organizational service account to permit request of temporary credentials from the STS service.
• Both the service account and the sub-account must have the permissions to perform backup via either amazon_permission_backup_restore.json or amazon_restricted_role_permissions.json.
• The service account must be granted permission to call the STS:AssumeRole() API call.
• The Amazon Access Node must have layer 3 connectivity to https://sts.amazonaws.com either directly or via HTTP PROXY.

• Configuring STS Role Authentication
• Creating a Role with Restricted Access
• Creating a vmimport role
• Amazon Web Services Permission Usage
• Guided Setup for Amazon
• Adding an Amazon Hypervisor
• Creating an Amazon RDS Client
• Enabling Cross-Account Sharing of an Amazon RDS Snapshot Copy
• Using an IAM Role to Grant Permissions to Applications Running on Amazon EC2 Instances
• AWS Security Token Service
• AssumeRole

• Automatically creates up to 100 access nodes to back up VMs.
• Automatically decommissions access nodes after 1 hour of inactivity using the Power Management feature and the Lifecycle Management feature.

• Automatic Scaling for Azure Access Nodes

• Back up and recover AWS Outposts-hosted workloads.
• Cloud native snapshot orchestration and back up to Commvault cloud libraries.
• Ensure data residency needs are met for AWS Outposts backup data with plans.
• Migrate data between AWS region and AWS Outposts with Commvault automation.
• Extend your Disaster Recovery landscape with failover/failback between AWS region and AWS Outposts, and vice versa.

• Virtual Server Agent (VSA) for Amazon.
• Virtual Server Agent (VSA) for Amazon Web Services (EC2, RDS, EKS).
• MySQL Agent (if performing MySQL dump/export backup)
• PostgreSQL Agent (if performing PostgreSQL dump/export backup).

• At least one AWS access node is required to perform EC2, RDS, and EKS backups.
• The access node for EC2 and RDS backups must be located in the AWS region.
• The access node for EKS and RDS dump/export backups must be located within AWS Outposts.
• AWS Outposts workloads are identified by subnet only. Commvault recommends the use of AWS tagging to identify AWS Outposts applications for backup and restores.
• AWS Outposts does not currently provide Amazon S3 storage. All EBS snapshots are stored in the region.
  • If localized backup copies are required (within AWS Outposts), the EBS volumes can be provisioned as a Commvault disk library.
  • Commvault can be directed to write to local storage devices outside your AWS Outposts via an Amazon Local Gateway (LGW).

• AWS Outposts

• Creating a Laptop Plan

• After enabling a passkey, the Authorize for restore option appears. Enable the Authorize for restore option to allow an end-user that entered the correct passkey to browse and restore backup data for a period of thirty minutes.
• An MSP administrator and tenant administrator can enable and require the passkey feature, using the Command Center.
• A client owner can create and require the passkey feature using the Command Center, Web Console, and CommCell Console.
• All users (the MSP administrator, tenant administrators, and client owners) can use REST API requests to create and require a passkey for a client computer.
• If passkeys are defined at multiple levels, the lowest level passkey takes precedence. For example, a passkey that is configured for a client computer takes precedence over a passkey that is configured for a company, and a user who is performing a restore for the client computer must use the passkey that is configured by the client owner.

• Requiring a Passkey as an MSP Administrator
• Enabling CommCell environment Client Owners to Require a Passkey
• Configuring a Passkey in the Command Center as a Tenant Administrator
• Configuring a Passkey in the CommCell Console as a Tenant Administrator
• Enabling Company Client Owners to Require a Passkey
• Requiring a Passkey in the Command Center as a Laptop Device Owner
• Configuring a Passkey in the Commcell Console as a Client Owner
• Configuring a Passkey as a Client Owner in the Web Console
• Creating a Passkey for Virtual Machine Restores
• REST API - POST Passkey (Company Level)
• REST API - POST Authorize for Restore (Company Level)
• REST API - POST Passkey (Client Level)
• REST API - POST Authorize for Restore (Client level)

• Managing Service CommCells

• Ransomware Protection for Disk Libraries on a Linux MediaAgent

Virtual Server Agent

• To specify a standard location where VMs are mounted, or to enable non-admin users to configure backup validation, create a recovery target.
• Create a VM group for each set of guest VMs that run an application. For example, you can create one VM group for VMs that run SQL Server, and a separate VM group for VMs that run Exchange.
• Obtain credentials for guest VMs that run applications.
• Use a Windows access node (VSA proxy) for application validation.
• If necessary, create custom validation scripts for applications. A script for SQL Server is included with the Virtual Server Agent package.

• Application Validation for VMware VMs

• Viewing File Monitoring Information
• Adding File System Data Sources to a Project

• Adding a File Server Data Source for File Storage Optimization