Feature Request - GFS Retention on Disk backups

[fijiboy]

Hello,

I would like to use GFS retention on my disk based storage for monthly Fulls. Veeam 9u1 does not allow me to do this.

Can we please have this feature?

This will help heaps with automation. We use Veeam primarily for archival.


Background:
1. We have SAN based snapshots on production SAN and replication to a DR site (over L2 10G service) for all workloads. We keep about a week of snapshots on prod and DR.
2. We use GFS retention on monthly copy to Tape jobs.
3. We have 2 X de duplication appliances as Scale out backup repositories.
a. One deduplication appliance has all the daily incrementals
b. The second deduplication appliance has my monthly Fulls. <-- This is where I would like to use GFS retention.
i. This device is used once a month for D2D, then it is free for the rest of the month for D2T (LTO6) which takes about a week.
4. We dont have a backup repository on Prod site, as we have a L2 10G service to DR - and a DR SAN on standby) - deviation from backup "best practice"


Thanks heaps for your consideration.

Love the features in v9, esp per VM backup chains.

Regards,
fijiboy

[nielsengelen]

Please take a look at Backup Copy Jobs. This supports GFS on disk copies.

[fijiboy]

Thanks heaps for your reply - but I don't want to use use D2D2D (disk copies).

It would be awesome to have GFS retention on the direct copies (as per my scenario).

Thanks heaps for your input.

[veremin]

As mentioned in the adjacent thread, we are a bit reluctant to implement functionality going against our best practices. Thus, the absence of GFS retention in primary backup jobs.

Anyway, thanks for the feedback; appreciated.

[SyNtAxx]

Yes, Agree. GFS on primary backup policy would be fantastic.

-Nick

[fijiboy]

As mentioned in the adjacent thread, we are a bit reluctant to implement functionality going against our best practices. Thus, the absence of GFS retention in primary backup jobs.

Anyway, thanks for the feedback; appreciated.

Thanks heaps for the reply. It is much appreciated.

IMHO -

1. Not all users of Veeam, use Veeam in the "one size/solution fits all" approach as defined by the Veeam Best practice. Some users may use a different primary backup solution or DR solution. Some users might have storage repositories that replicate (without the assistance of Veeam).. etc

2. I would suggest that if this goes against best practice for a the "one size fits all" type user - use a pop up warning or notification if GFS retention is used for the primary backup. If/when this feature is enabled.

3. Flexibility is key - let the user decide and let Veeam recommend. I don't think Veeam would loose customers or have informed customers loose data/but gain functionality for a different type of Veeam customer. One size definitely does not fit all..

Thanks for considering this.

Big fan of the work you guys do.

[Gostev]

It is starting to look like we will end up delivering this functionality, however in somewhat unexpected manner - with a cool twist, like everything we do - and most importantly, without violating our reference architecture and recommendations. I am currently planning this feature for v10 (our 2017 release) and still need to think the whole idea through, so I can't really discuss it yet, but stay tuned. Thanks!

[fijiboy]

It is starting to look like we will end up delivering this functionality, however in somewhat unexpected manner - with a cool twist, like everything we do - and most importantly, without violating our reference architecture and recommendations. I am currently planning this feature for v10 (our 2017 release) and still need to think the whole idea through, so I can't really discuss it yet, but stay tuned. Thanks!

Thanks Gostev, I am sure other customers will appreciate this as well. Good to know this functionality is in the pipeline. I will manually manage retentions for now.

Enjoy the weekend.