We have been with Veeam now for 6 months or so, previously a Commvault shop. We are trying to achieve the simple extended protection policies that we had in place with Commvault and previous vendors. That was to create a secondary copy of Monthly and Yearly jobs in order to extend the retention period. In our Commvault environment, all longer retention was to tape. We did start out trying to do this with tape but abandoned that pretty quickly having witnessed Veeam's lack of capability in that sphere.
We have also now significantly minimised the workloads we are seeking to protect for longer than the 30 days that we hold on the primary disk repository. Limited now to Exchange, Sql and File. 3 Jobs.
At present we are running active fulls at end each week and incremental daily. Backup is across the FC fabric so all pretty quick.
What we want to do with longer retention is to create secondary copies of the weekly jobs (last Friday of the month or last Friday of year) to another disk target in separate data centre. We may eventually offload to a cloud disk service but at present will be deduped to disk. The combined total for the 3 jobs is ~10TB for an active full and will be able to get several years on disk deduped, given the current rate of change.
I have just got off my second Veeam support call regarding how I might do this, but it seems there is just no capability to wait for my end of month to complete and then copy to secondary location.
We obviously need to rethink this completely (rather than think in Commvault or other vendor terms) but not sure where to start. I am surprised that anyone can run a secondary copy in the way I describe, we are not attempting to do anything complex here, on the contrary the logic is very simple. ie. Wait until job finished, send it somewhere else, apply different protection policy.
I appreciate any advice from you experienced Veeam folk.
Any Veeam people reading, would appreciate advice as whether this simple capability is on the dev road-map.