Exporting backups allows you to synthesize a complete and independent full backup file out of selected restore points that are located in your backup repositories. That is, you can transform any incremental or reverse-incremental backup chain (i.e all dependent .VBK, .VIB or .VRB files) into a standalone .VBK file.
Export applies to Full, Incremental and Reverse-incremental restore points located in:
- Backup repositories.
- Object storage repositories.
- Backup repositories of cloud service providers and their tenants.
Consider the following:
- The restore point that is being exported as a new full backup file is saved to the same repository, wherein the source selected restore points reside.
- Once export is complete, exported backup files will be displayed under the Backups > Disk (VeeamZIP) node.
- [For scale-out backup repositories] Backup files exported to the capacity tier will be displayed under the Backups > Object Storage (VeeamZIP) node, and backup files exported to the archive tier will be displayed under the Backups > Archive (VeeamZIP) node.
- If a restore point that is being exported resides on the tenant side, a new full backup file will also be exported to the same repository (on the tenant side) from which the source restore point is being taken.
- If a tenant initiates export of a restore point that resides in the subtenant directory, a new full backup file will be exported to the tenant directory.
- If you select a backup job consisting of multiple virtual machines, Veeam will synthesize a separate full backup file per each machine.
- When exporting VMs from VMware vCloud Director (vCD) backups, all the VMs will be exported without vApps, that is, a new full backup file will be exported as a simple VMWare backup, not vCD backup. For more information about vCD backups, see Backup of VMware vCloud Director VMs.
- Export session results are saved to the configuration database and available for viewing, as described in Viewing Session Statistics.
In This Section