Any Ideas to create 3 mth retention backups without GFS

[bthorne]

Hello all

We would like to implement a backup environment without a landing zone or copy jobs. We want to achieve having 2 copies of backups with 3mth retention. We will not be using the tradition method of a landing zone and 2 copy jobs to orchestrate the GFS Policy. Does any currently use this type of method or has any interesting opinions on how to achieve this. We have stretched production storage between 2 sites
No copy jobs will be used due to speed. We will look to create multiple jobs to each unit.

Backup speeds are between 350mb and 1gb
Copy speeds were dreadful of 80mb to 160mb
Amount of
Link Speed: 10GB
Proxies/gateway: 2 Physical 16cpu 32 gig ram Separate Vlan for Backup traffic
Backup Units: 2 x 5100 Store Once - Total capacity 100TB
2 x 4500 Store Once - Total capacity 90TB
Licence: Enterprise Plus
Backup Type: Storage Snapshot/Hot Add

[DGrinev]

Hi Bernard and welcome to the community!

I'd suggest you to not refuse the copy job, as it was designed specifically for long term retention.
You can significantly reduce workload on the production environment by using BCJ.
Please share the bottleneck stats of the backup copy job, that should help to find out where is the weak spot in the infrastructure. Thanks!

[bthorne]

Hi DGrinev

We are looking outside the box on this as we do not want to allocate storage to land and create 2 copy jobs to create GFS. We understand the basis of a copy job it's just that we would have to allocate a lot of production storage which is currently not an option.

Based on that we can have 21 points and multiple jobs we think we can create another design.

Bottleneck to transferring Store once to Store once . Speed is approx. 80-150mb which is slow when some of the jobs would be 4tb. Hopefully with a little bit of thought we can come up with some fresh ideas. Look forward to letting you know our ideas soon.

[foggy]

Hi Bernard, could you please be more specific on what are you trying to achieve? Just two similar sets of backups with the same 3 months retention of daily backups but on two different StoreOnce devices?

Bottleneck to transferring Store once to Store once .

What bottleneck does the Veeam B&R report for the backup copy job? Knowing more about how you set up repositories on StoreOnce will also be helpful.