Automatic Schedules for MySQL, PostgreSQL, and Sybase Log Backups
Create a schedule to automatically run a database log backup when specific threshold criteria are met. For example, run a backup when the archive log destination fills up to a specified capacity.
For more information, see Creating an Automatic Schedule for Database Log Backups.
Archiving Support for Hadoop (HDFS), IBM Spectrum Scale (GPFS), and Lustre
You can archive data in the file systems for Hadoop (HDFS), IBM Spectrum Scale (GPFS), and Lustre.
For more information, see Archiving Files.
Google Cloud Spanner
You can back up and restore Google Cloud Spanner databases.
For more information, see RDS for Oracle.
Cluster-Aware File Recall Operations on a Windows Cluster
File recall operations on Windows clusters are cluster aware. With cluster-aware recalls, you can easily recall a file after a failover. For more information about recalling files on a Windows Cluster, see Recall Operations On a Windows Cluster.
Perform Incremental or Differential Backups for Dell EMC Isilon/PowerScale
You can run incremental or differential backups on a user-defined backup set for Dell EMC Isilon/PowerScale NDMP clients.
For information about creating a user-defined backup set, see Creating a User-Defined Backup Set.
Reduce the RPO to Minutes with Streamlined Log Backups Using Disk Caching for Oracle RAC Databases
You can streamline database log backup operations to run on an automatic schedule that supports log backup frequencies of under 1 hour. Streamlined log backups using caching to a disk library reduce the RPO for database instances that have a high transaction rate.
The log backups are written directly to disk mount paths that are managed by the MediaAgent, removing the need for storing the backups on production servers. The database client and the MediaAgent automatically run the log backups, independent from the CommServe server, which increases the availability of the database client and MediaAgent pair, while also reducing the load on the CommServe application. A second operation commits and registers the logs periodically to support copy operations. Log backups will continue even if the CommServe server is unavailable because of maintenance, network disruptions, or other issues.
For more information, see the following topics:
Search Email Messages By Using Exact Keyword Matching
To search for email messages by exact keywords, enable exact keyword matching in Exchange archiving plans and Journal mailbox plans.
For more information, see the following topics:
Make Backups of a Standby Database in a Unified Data Guard Environment
In a Commvault Unified Data Guard environment, you can make backups of the standby database even if the primary database has read-only tablespaces and you want to make backups of the standby database using the "Skip Read Only" option. RMAN does not natively support skipping read-only tablespaces when running backups on standby databases. However, Commvault software intelligently omits any read-only tablespaces when making the backup, which allows the backup to complete successfully.
For more information, see Oracle RAC Client for Unified Data Guard.
The Number of Streams Used for Snapshot Restores of Some Databases Is Determined by the Number of Files to be Restored
Applies to: DB2, DB2 DPF, Oracle, SAP for Oracle, Sybase
The number of streams used for snapshot restores of some databases is now determined by the number of files to be restored rather than the number of mount points. This allows more streams to be used for the restore and therefore reduces the restore time. A restore of a log file snapshot is limited to one stream, since log files are relatively small.
For more information, see Number of Streams Used for a Snapshot, Backup Copy, or Auxiliary Copy Restore.
Optimized File System Backups Using Extent-Based Technology
Optimized backups (also called extent-based backups) integrate extent technology for faster backups.
Optimized backups are available for NAS file servers that are configured using the Changelist APIs. The following file servers support extent-based backups:
For more information, see Optimized Backups Using Extent-Based Technology.
Optimize SAP HANA IntelliSnap Backup Copies Using Extent-Based Technology
You can optimize SAP HANA IntelliSnap backup copy jobs using extent-based technology.
Extent-based backups integrate extent technology so that backup copy operations complete faster. Extent-based backups break a file into small independent extents, which causes backups to complete faster and with more resiliency to network disruptions.
Extent-based backups are automatically applied for files that are 1 GB or larger.
For more information, see Performing Extent-Based Backups for SAP HANA IntelliSnap.
Use Region-Based Storage Policy for SAP HANA System Replication
In an SAP HANA system replication setup, if the primary and secondary nodes are in different locations, you can configure the backups to automatically select the storage policy with libraries based on the region of the current primary node. Using a region-based storage policy avoids data transfer over a WAN and enables faster backups.
For more information, see Using Region-Based Backups for SAP HANA System Replication.
Virtualize Me Support for Azure Stack Hub
You can use Virtualize Me to convert a VMware, Hyper-V, or Azure virtual machine or a physical computer to an Azure Stack Hub virtual machine.
For more information see, Virtualize Me for Azure Stack Hub.