Hi,
We are making some changes to our Veeam infrastructure. We have to make some chained jobs, as we copy the data to immutable repos and to secondary locations. The picure is like this:
BJ (Backup job) -> REPO1 -> BCI12 (Backup copy immediate job) -> REPO2 -> BCI23 (Backup copy immediate job) -> REPO3.
BCI12 will consist of multiple BCJ (around 20).
1. The question for BCI23 is any difference in performance or what is better to do? Make one BCJ BCI23 or make multiple - 20 BCJ BCI23 and pair them to 20 BCI12?
2. Currently we have multiple BCJ, that are targeted to REPO3. As we make changes, these jobs will be replaced with BCI23. We would like to have the continuitiy of the BCJ. The question is how to map or merge multiple current BCJ backup files to a single BCJ. Deatch and map works for one on one. If we delete the job, backups will end in Disk (Orphaned) and we can't make changes to retention anymore. We want to avoid that, as we have a GFS retention of 7D,4W,12M and 5Y backups. We are aware of bacground retention process, but this is not the real answer to handling and continuum of operation. Is there any direct way or a workaround to achieve this? We already have multiple orpaned BCJ files due to BCJ transformations…
Thanks for the answers
Janez
-
- Enthusiast
- Posts: 58
- Liked: 11 times
- Joined: Jul 25, 2016 10:42 am
- Full Name: Janez K
- Location: Slovenija
- Contact:
-
- Product Manager
- Posts: 9831
- Liked: 2601 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Backup copy jobs configurations
Hello Janez
May I ask how many VMs are protected by your backup server?
Under normal circumstances you will never require so many different backup copy jobs if the retention is the same between all jobs. Maximum allowed running copy sessions will be controlled by the task settings in your source and target repository.
Best,
Fabian
May I ask how many VMs are protected by your backup server?
Under normal circumstances you will never require so many different backup copy jobs if the retention is the same between all jobs. Maximum allowed running copy sessions will be controlled by the task settings in your source and target repository.
Use "Move Backup" to move backup chains from one backup copy job to another.The question is how to map or merge multiple current BCJ backup files to a single BCJ.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Enthusiast
- Posts: 58
- Liked: 11 times
- Joined: Jul 25, 2016 10:42 am
- Full Name: Janez K
- Location: Slovenija
- Contact:
Re: Backup copy jobs configurations
Hi Fabian,
We have more than 1500 VM's. The Reasoning behind different copy jobs is the virtual or logical separation between different "tenants". Currently we have more than 80 BCJ.
We would like to cut this down to 20 for site A and 20 for site B for BCI12.
BR
Janez
We have more than 1500 VM's. The Reasoning behind different copy jobs is the virtual or logical separation between different "tenants". Currently we have more than 80 BCJ.
We would like to cut this down to 20 for site A and 20 for site B for BCI12.
The move option to another job refers to exact VM's. Can you confirm, that this works specifically for Backup Copy Jobs as the section in the user guide talks about the backups.Use "Move Backup" to move backup chains from one backup copy job to another.
BR
Janez
Who is online
Users browsing this forum: alavik, Bing [Bot], Semrush [Bot] and 107 guests