Data Backup and Backup Copy

In this article

    Backup

    To back up data of your Microsoft 365 and on-premises Microsoft organizations, you use backup jobs.

    A backup job is a configuration unit of the backup activity. A backup job defines a list of users, groups, sites, teams, and organizations to back up, a location where to store backups, a schedule according to which new backups must be created. The first backup job session always produces a full backup of all objects added to a backup job scope. Subsequent backup job sessions are incremental — Veeam Backup for Microsoft 365 processes only those objects that have changed since the last backup job session.

    Backup Copy

    To enhance protection of your data against disasters, you can extend your backup jobs with backup copy capabilities. Backup copy allows you to create an instance of your backed-up data in the following cloud-based object storage: Azure Blob Storage Archive access tier, Amazon S3 Glacier storage class, or Amazon S3 Glacier Deep Archive storage class.

    Data in backup copies has a different storage format as those created by backup jobs: blob files in backup copies are larger. Repacking of backed-up data is performed by either Veeam Backup for Microsoft 365 backup proxy or an auxiliary archiver appliance that Veeam Backup for Microsoft 365 can create in Microsoft Azure or Amazon EC2.

    As well as backup, backup copy is a job-driven process. You can create a backup copy job right after configuring a backup job or later whenever you want. For more information, see Creating Backup Copy Job.

    Getting Started with Backup Copy

    Before you start creating a backup copy job to protect your backups, you must perform the following actions in the Veeam Backup for Microsoft 365 backup infrastructure:

    1. Add an object storage where you want to keep your backups. For more information, see Adding Object Storage Repositories.
    2. Add an object storage that you want to use as a target for backup copy jobs.

    Azure Blob Storage Archive access tier, Amazon S3 Glacier and Amazon S3 Glacier Deep Archive storage classes are supported only to store backup copies. For more information, see Adding Amazon S3 Object Storage Repositories and Adding Microsoft Azure Blob Object Storage Repositories.

    1. Add a backup repository extended with an object storage where you want to keep your backups.

    You will use this backup repository as a target for your backup jobs. For more information, see Adding Backup Repositories.

    1. Add a backup repository extended with an archive object storage to which you want to copy your backed-up data.

    You will use this backup repository as a target for your backup copy jobs. For more information, see Adding Backup Repositories.

    Note

    An extended backup repository where you keep your backups and a backup repository where you store backup copies must be located on the same backup proxy server and have the same retention type.

    1. Create a backup job. When creating a backup job, map it to the extended backup repository where you want to keep your backups. For more information, see Specify Backup Proxy and Repository.
    2. Create a backup copy job for the source backup job. When creating a backup copy job, select a backup repository extended with an archive object storage as a target repository where Veeam Backup for Microsoft 365 will copy your backed-up data. For more information, see Creating Backup Copy Job.

    After Veeam Backup for Microsoft 365 has created backup copies, you can retrieve your data from a backup repository extended with an archive object storage when you need it. For more information, see Retrieving Backed-Up Data.

    Backups that you have retrieved become available for explore and restore. For more information, see Exploring Retrieved Data and Data Restore. Mind that you cannot explore and restore the retrieved data using Restore Portal.

    In This Section