Hello Community,
we have two copies - primary copies stores on-premise lib and backup copies to s3
My goal is to create a backup copy that specifically pick the weekly full backup from the primary copy and transfers it to an S3 bucket.
Should I enable GFS on both the primary and backup copies?
How can the backup copy job be configured to exclusively select the weekly full backup from the primary copy and send it to the S3 bucket ?
thanks
-
- Enthusiast
- Posts: 31
- Liked: 1 time
- Joined: Nov 09, 2022 2:20 pm
- Full Name: Dan
- Contact:
-
- Product Manager
- Posts: 10273
- Liked: 2745 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: create a backup copy for weekly full only
Hi Dan
Our backup copy jobs do not create exact copies of backup files from a primary backup job. Therefore you cannot configure it to pick up exclusively only weekly full backup files.
But you can achieve something similar with the following setting:
Use S3 bucket as a direct object storage repository (available in v12).
For the backup copy job, use a periodic backup copy job which runs only once per week after the primary backup job has created its weekly restore point. Then the periodic backup copy job will copy only the latest restore point which is the weekly one to the S3 bucket. Backup Copy will be forever forward incremental. You can enable active full copies, but it will always copy the entire space of a full backup to object storage.
May I ask, why you don't want to copy daily restore points to object storage? Only changes or new data will be uploaded to S3.
Best,
Fabian
Our backup copy jobs do not create exact copies of backup files from a primary backup job. Therefore you cannot configure it to pick up exclusively only weekly full backup files.
But you can achieve something similar with the following setting:
Use S3 bucket as a direct object storage repository (available in v12).
For the backup copy job, use a periodic backup copy job which runs only once per week after the primary backup job has created its weekly restore point. Then the periodic backup copy job will copy only the latest restore point which is the weekly one to the S3 bucket. Backup Copy will be forever forward incremental. You can enable active full copies, but it will always copy the entire space of a full backup to object storage.
May I ask, why you don't want to copy daily restore points to object storage? Only changes or new data will be uploaded to S3.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Enthusiast
- Posts: 31
- Liked: 1 time
- Joined: Nov 09, 2022 2:20 pm
- Full Name: Dan
- Contact:
Re: create a backup copy for weekly full only
thanks Fabian
In a small environment where secondary copy not currently set up.
We aim to selectively copy data due to cost considerations when use S3 immutable bucket as the destination for 2nd copies.
In a small environment where secondary copy not currently set up.
We aim to selectively copy data due to cost considerations when use S3 immutable bucket as the destination for 2nd copies.
-
- Enthusiast
- Posts: 31
- Liked: 1 time
- Joined: Nov 09, 2022 2:20 pm
- Full Name: Dan
- Contact:
Re: create a backup copy for weekly full only
in v12, is it necessary to set up S3 immutability through scale-out backup repositories or can be on regular backup repositories ?Use S3 bucket as a direct object storage repository (available in v12).
-
- Veeam Software
- Posts: 425
- Liked: 251 times
- Joined: Apr 11, 2023 1:18 pm
- Full Name: Tyler Jurgens
- Contact:
Re: create a backup copy for weekly full only
If you add an S3-compatible bucket as a repository in v12, you set the immutability settings on the repository itself.
Tyler Jurgens
Blog: https://explosive.cloud
Twitter: @Tyler_Jurgens BlueSky: @explosive.cloud
Blog: https://explosive.cloud
Twitter: @Tyler_Jurgens BlueSky: @explosive.cloud
Who is online
Users browsing this forum: No registered users and 12 guests