FEATURE REQUEST: Seed AND local Backup

[Matthias_Hiller]

Hi,

we have some Tenants in Germany with lousy Bandwith so we seed the First Backup and the connect them to Cloud Connect either if they have Backup and Replication or the Agent.

It would be Nice to have a local Backup, too so if the need of a restore ist there to be done quickly we don´t need to transmit this via WAN.

So the Cache Option would be the easiest way to allow it by having the option to NOT delete it after e resync and by enabling it to ALWAYS first backup it to the cache Target!

This would be an awesome Feature!

[Dima P.]

Hello Matthias,

It is possible to map backup created locally to a VAW job pointed to Cloud Connect reposition. Kindly, take a look at this KB article for more details. Thank you!

[Matthias_Hiller]

I meant to have BOTH running sequentially! so i always have a local backup (NAS or USB) and the cloud connect repository!

that would be perfect / otherwise the possibility to have multiple jobs in the Windows agent (like in the linux agent) so then you can solve it by using one job to local and one to cloud

[Dima P.]

Aha. So it’s more a multiple job feature request, right?

[Matthias_Hiller]

it would solve multiple issues yes!

[Dima P.]

Matthias,

Added your vote to this feature request. Thanks!

[Matthias_Hiller]

Thank you very much i hope it will be in a future release soon