Hybrid Backup (legacy format)
Hybrid backup is supported for the current backup format only
Following the best practice in the backup industry unquestionably demands some sort of conflation of local and cloud backup. Having two different backups - one to local, another to cloud - is not particularly efficient as it puts extra workload on the utilized computer.
First, the files are uploaded from the computer to the local storage—let's say a local NAS—and then the same process repeats to upload the files from the computer to the cloud storage.
A hybrid backup allows combining these backups into one backup plan which naturally makes it easier to do the setup process. It first transfers the files to the local storage (NAS) and then uploads them from the local storage (NAS) to the cloud. This gives some relief to the main computer, requiring fewer disk operations as encryption and compression are only performed once during the initial backup to the local (NAS) storage.
Benefits of Hybrid Backup:
- Single backup plan
- Less workload on the source computer
- One-time encryption and compression
Note that using non-hybrid (local or cloud) and hybrid backup plans with the same or similar backup dataset may cause revision conflicts or other errors. Errors with the following codes may occur: 1524, 1525, 1526, 1527, 2600, 2601
To learn more, refer to the Hybrid/Non-Hybrid Errors article at kb.msp360.com
Supported for
- File backup
- Image-Based backup
- MS SQL Server backup
- MS Exchange backup
- VMware and Hyper-V backup
- Storage: any