Hi,
I have a question regarding the use of FastClone on a BackUp-Copy-Repository. So far - from my own tests and documentation, I deducted, that FastCopy enables Synthetic Full Backups without having to pull all the data from the Source once again (in contrast to active Full Backups) - this is nice and it saves greatly on the transfered data and time needed to create those synthetic fulls.
My question now is, how does this affect offsite-repositories, that would have to take in a backup-copy. Our planned offsite-repo for BackUp-Copies is also a CentOS machine with XFS behind WAN/VPN with limited bandwidth. Am I correct to assume from the documentation, that FastClone would also work for this one? So it gets "informed" by the job to create a Synthetic full and does so on itself without having to transfer/copy the results of the created synthetic full on the primary backup-repo? Or does it not work that way?
Thanks for helping out.
-
- Enthusiast
- Posts: 25
- Liked: 1 time
- Joined: Jan 13, 2023 6:50 pm
- Contact:
-
- Product Manager
- Posts: 10100
- Liked: 2696 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Question regarding FastClone and BackUp-Copy
Hi
The difference with FastClone is that existing blocks on the repository are not copied, but only referenced for the new full backup file. This saves a lot of space and time.
You may check out our WAN Accelerator if the bandwidth is too low for the copy process.
Best,
Fabian
It doesn't matter if FastClone is used or not. Synthentic Full Backups always only transfer incremental blocks to the target repository and then build a new Full Backup from previously stored blocks and the incremental blocks. Active Full Backup will transfer all blocks to the target repository.FastCopy enables Synthetic Full Backups without having to pull all the data from the Source once again (in contrast to active Full Backups)
The difference with FastClone is that existing blocks on the repository are not copied, but only referenced for the new full backup file. This saves a lot of space and time.
Yes. Backup Jobs and Backup Copy Jobs works the same regarding FastClone. Only incremental blocks will be copied to the remote location. The repository server will then use references to existing blocks together with the incremental blocks to build the new synthetic full backup.My question now is, how does this affect offsite-repositories, that would have to take in a backup-copy. Our planned offsite-repo for BackUp-Copies is also a CentOS machine with XFS behind WAN/VPN with limited bandwidth. Am I correct to assume from the documentation, that FastClone would also work for this one? So it gets "informed" by the job to create a Synthetic full and does so on itself without having to transfer/copy the results of the created synthetic full on the primary backup-repo? Or does it not work that way?
You may check out our WAN Accelerator if the bandwidth is too low for the copy process.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Baidu [Spider] and 60 guests