Backup Agents

Updated

Back Up and Restore Azure Repositories

You can back up and restore Azure repositories. You can back up repositories, metadata, and pull request items such as title, description, state, comments, reviewers, and tags. For restores, you can restore to the same location (in place), or to a different repository hosting service (out of place) such as GitHub, or to a disk.

For more information, see Azure DevOps.

Back Up and Restore GitHub Repositories

You can back up and restore GitHub repositories. You can back up repositories, metadata, and pull request items such as title, description, state, pull request issue comments, and pull request review comments. For restores, you can restore to the same location (in place), or to a different repository hosting service (out of place) such as Azure DevOps, or to a disk.

For more information, see GitHub.

Back Up and Restore Microsoft Teams

You can back up and restore Microsoft Teams. You can back up public and private teams, standard and private channels, and teams items such as posts, files, and Wikis. For restores, you can restore to the same location (in place) or to a different location (out of place). You can search for the team or the item that you want to restore, including previous versions and deleted items.

For more information, see Office 365 Teams.

Back Up OneNote Files and OneDrive Files Together

You can run OneDrive backups to back up both the OneNote files and the OneDrive files. You can back up and restore OneNote files, such as, notebooks, sections, and section groups to cloud, local storage, and secondary storage.

For more information, see OneDrive for Business.

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:

Run Oracle and Oracle RAC Block-Level Synthetic Full Backups Using Multiple Streams

You can run Oracle and Oracle RAC block-level synthetic full backups using multiple streams. You can also now run incremental IntelliSnap backups in parallel with synthetic full backups.

For more information, see the following topics: