Hi All,
I have a query around how the Defragment and compact full backup file works with reverse incremental backups to a Cloud Connect repository?
My question is around performance, or more specifically where the processing takes place. Defraging a large file on a WAN target will be very slow, unless the process is handed off to the Cloud Connect repository so all the traffic isn't traversing the WAN link.
Can anyone shed some light on this? We have some large VBK files left over after some VM's have been decommissioned and removed from the jobs. Or how to other providers handle this?
Thanks in advance!
-
- Service Provider
- Posts: 21
- Liked: 5 times
- Joined: Sep 10, 2013 6:56 am
- Contact:
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: Compacting reverse incremental Cloud Connect
Hi Adrian and welcome to the community!
The processing should be performed on the cloud connect side without using the WAN link.
That was confirmed by the QA team. Thanks!
The processing should be performed on the cloud connect side without using the WAN link.
That was confirmed by the QA team. Thanks!
-
- Service Provider
- Posts: 21
- Liked: 5 times
- Joined: Sep 10, 2013 6:56 am
- Contact:
Re: Compacting reverse incremental Cloud Connect
Great news! Thank you for investigating for me.
Who is online
Users browsing this forum: Semrush [Bot] and 341 guests