Hello
Never done this as I am currently building my new repos including offshoring to Veeam Vault.
I have one VM that needs:
- 30 daily restore points plus GFS of 12 monthlies for a year and yearlies for 10 years on the primary repo (on-prem S3 compatible).
-30 daily restore points plus GFS of 6 monthlies without any yearlies on Veeam Vault with immutability of 30 days.
Can this be achieved with an "immediate BCJ" that simply has a different GFS config than my BJ? Or will it automatically pull all long term GFS backups that the BJ creates by its GFS config and put them - with retention and immutability - on Veeam Vault?
-
KarmaKuma
- Enthusiast
- Posts: 56
- Liked: 7 times
- Joined: Feb 05, 2022 11:16 am
- Contact:
-
david.domask
- Veeam Software
- Posts: 3057
- Liked: 707 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: BJ with long GFS retention plus BCJ with shorter GFS retention
Hi KarmaKuma,
Sure this will work as you're expecting.
Backup Copy jobs take data from recent restore points and build a separate backup chain for the Backup Copy job from those points. Backup Copy jobs are _not_ a 1:1 copy of backup files, Backup Copy jobs create a "backup of a backup" with its own retention schedule.
Sure this will work as you're expecting.
Backup Copy jobs take data from recent restore points and build a separate backup chain for the Backup Copy job from those points. Backup Copy jobs are _not_ a 1:1 copy of backup files, Backup Copy jobs create a "backup of a backup" with its own retention schedule.
David Domask | Product Management: Principal Analyst
-
KarmaKuma
- Enthusiast
- Posts: 56
- Liked: 7 times
- Joined: Feb 05, 2022 11:16 am
- Contact:
Re: BJ with long GFS retention plus BCJ with shorter GFS retention
Thanks for the feedback, after reading the diverse Veeam Docs/KBs with your described behavior as mindset, it aligns, but otherwise - when not sure - some parts leave room to interpret wrongly or not 100% clear.... Altough I would not have a suggestion how to write it more clearly in the Docs. Maybe it's because one has a certain assumption (or traditional thinking) linked to the word "copy"...
Who is online
Users browsing this forum: No registered users and 11 guests