I would emphasize that it`s recommended to keep a short chain on the primary repository for faster restores and longer chain on the secondary repository for restores of historical data.
Damn - We're doing the opposite of that. We have a 30 restore point Forever Incremental strategy on Primary Fast Storage, and 7 restore points + 4x Weekly & 24x Monthly GFS on a Data Domain.
I hadn't read this thread before - but just noticed this ...
is it true that a copy-job also protects you against bitrot, because the copy job compares it's data to the data from the backup job?
Totally true, and it's the main advantage of backup copy job compared to storage replication
Does that mean, if I have Backup Copy's from the primary storage to the Data Domain - and the Data Domain organizes the Restore Points into GFS backups - I can switch off Health Checks on the Data Domain Backup Copys?