Thats what I was looking for! I had never ever spotted the Backup copy button. I'm mortified I missed it
I was creating totally separate backup jobs and that was it - doubling the workload possibly?
Also is there a better explanation of the GFS? I've not quite grasped it - storage wise.
I'm looking to have a months worth of weekly fulls offsite, Then 3 month ends, 4 quarterlies and 10 years.
Since much of the data doesn't change - it's more adding to existing data, I dont want to store 100 full backups, but I'm concerned by offsite repository will run out quickly if I choose the wrong settings...
I'm also a little confused as to the scheduling
The backup copy jobs you can run every day. But I only want to run it as part of the backup job schedule. So I do my Backup locally on Monday night, Wednesday and friday. I want the backup copy to run then also? Not every day.
Mike Resseler wrote:moving VMs to a new vcentre the backup chain is broken and entirely useless now.
It's useless in that it's filled my cloud repository and cannot be added to.
Migrating to the new VCentre starts a new chain and I cant afford to fork out for additional storage for 2 full backups basically.
Moving forward and long term I want only to set this up one more time and do it right.
Forever incrementals as separate backup jobs was definitely wrong wrong wrong - in this situation at least.
Am I making sense?