Scale-out repository : unable to add extent

[wiz2k10]

Hi all,

I try to create a Scale-Out Repository with 2 extents :
- 1st extent (Repository 1) is used actually as remotely target for backup copy job VMs & backup copy job for Windows Agent
- 2nd extent (Repository 2) is newer and never used, it will be a member of Scale-out repository with "Repository 1", to store backup copy jobs.

When I want to create Scale-out repository, I have an error :

Unable to add extent "Remote - Repository backups VM" because it serves as the target for one or more job types which are not supported by a scale-out backup repository


This job (Backup Copy Job - SVBRPRDFILE4007) is a Backup copy job of physical server, backup with Windows Agent for Windows (Free edition) in v2.0.0.700


I have read the user guide that explain the limitations of Scale-Out feature and i don't see what can be the problem.

More informations :
All backup environment is in Windows Server 2016
Deduplication Windows feature is installed on 2 extents.
Job is disable when I try to create Scale-out repository
I have disable WAN accelerator in the job, I use "Direct" Data Transfer
I have read this post : microsoft-hyper-v-f25/wan-accelerator-s ... 44551.html, not solve the issue.
I have read this other post : veeam-backup-replication-f2/cannot-add- ... 53053.html, not solve the issue too.

If you have any idea to solve my problem do not hesitate, otherwise I'll open a ticket.

Maxime.

[Alex Uryumtsev]

Hi Maxime,

I would recommend you to contact support team, because the root cause is not obvious in your case, since the backup copy job is supported by Scale-out Backup Repository.

Then after opening the case with our support team, please provide me your ticket number, so I can check your progress.

If you have any questions left, don't hesitate to ask.

BR,
Alex

[wishr]

Hi Maxime,

Welcome to Veeam Community Forums and thanks for posting.

A couple of questions for you:
1. Which B&R version do you use?
2. How the backup was done (using Standalone Free Agent or Free Agent Managed by B&R server)?

Thanks

[wiz2k10]

Thanks for your reply,

@Alex Uryumtsev :
I opened a case 03306075

@wishr :
1. I used VBR 9.5.0.1922
2. Free Agent managed by B&R Server

Maxime.

[Dima P.]

Hi Maxime.

It's a know issue that should be fixed in upcoming Update 4. As a workaround try to change the target for your backup copy job to another repository, then create Scale-Out backup repository and then re target the backup copy job to the newly created Scale-Out. Please let us know how it goes. Thanks!

[wiz2k10]

@Dima P.

Thank you for the clarification. What is the release date for U4?

I did what you asked me, it works, however, I can not point my backup copy job to the new target (scale-out repository), I have the following error:
Move all backup files to the new backup repository first


1. I have create a temporary repository and move all backup files, change the backup repository of my backup copy job, create Scale-out backup
2. I have move all backups files in the old repository that is a member of Scale-out now
3. I have rescan the Scale-out repository (but now, i cannot rescan the repository)


I think it's just a problem to populate the database of Scale-out backup to say it, now backups files are here, but how to do it ?

Maxime.

[wishr]

Hi Maxime,

Could you please take a look at this KB and let us know the result?

As about U4 release, unfortunately, we are not able to comment on the ETA, but I can probably mention that it will be available soon.

Regards,
Fedor

[wiz2k10]

@wishr

It doesn't work, I have the same error message that the original post :

Unable to add extent "Backup Repository 1" because it serves as the target for one or more job types which are not supported by a scale-out backup repository

[wishr]

Maxime,

Could you please try the following:
1. Move the backup files to a temporary location (3rd repository, separated from the first two). Make sure that all the related VIB, VBK, and VBM files are moved;
2. Point your Backup Copy job to the backup files in the new location;
3. Then create SOBR using the first two repositories;
4. Make a rescan - notice if it has completed or not (if not, please revert back and add one additional rescan between the steps 1 and 2);
5. Then move the files to SOBR (to a preferred extent);
6. Make a rescan;
7. Manually point your Backup Copy job to your backup files on SOBR.

And please keep us posted.

[wiz2k10]

Thank you @wishr for your time but it doesn't work ...

1. I moved backup file to newer location (all files VIB, VBK and VBM are moved)
2. I rescan the newer repository (backup files are added and i can map manually backup files in my job)





3. I make a rescan to my SOBR (1 skipped file, it's normal because another job - work fine - is in the SOBR)
4. I moved backup file from simple repository to SOBR
5. I make a rescan of my SOBR and 2 skipped rather than 1 add and 1 skipped.




6. So, I can not manually map backup files to my backyp copy job because it does not see its

I don't understand ! Even the bypass method would not work?

The engineer on your support team who processes the case I opened is currently analyzing the logs.

Maxime.

[wishr]

Maxime,

Thank you for your efforts.

That's strange. In this case, I would recommend you to keep working with our support team, maybe there is some unknown underlying aspect beyond our current vision.

We'll keep an eye on your support case and will be glad to assist when necessary.

BR,
Fedor

[foggy]

Try to remove corresponding backups from configuration prior to SOBR rescan.

[wiz2k10]

Hi @foggy,

I have try to remove the backup from configuration before rescan and it's the same way.

I have try another way to identify if the problem concern member of SOBR or concern the backup job :
I have copy the tree folder of my backup copy job with just the .vbm file inside (not .vbk , .vib), and when i rescan the SOBR, we can see 2 jobs are skipped on my 2 SOBR members. Previously, I put my backup files into the same SOBR member and it skipped 2 backups files also.


What can be concluded? The problem is related to the backup copy job from Veeeam Agent for Windows ?

I have to talk by phone this afternoon with support engineer Veeam.

I will keep you informed.

Maxime.

[wishr]

Hi Maxime,

Thank you for additional information. We are keeping an eye on the support case status. Let's see what we'll get during the session with our support representative and further analysis.

Regards,
Fedor

[wiz2k10]

Hi all,

A special thanks to @Claudiu at Veeam support team, to resolve my problem.

Claudiu realized these actions :
1. Remove from backup configuration
2. Move backup files to one member of SOBR
3. Remove member of SOBR (which we moved backup files step 2) without backup evacuation



4. Rescan this member
5. Add this member to SOBR
6. Map manually the new SOBR repository and backup files in the backup copy job

That's all...

He confirm me also that should be fixed in U4, coming soon...

Thanks all for your help !

Maxime.

[hcs_tech]

I am getting this same error and am on Veeam 9.5 update 4. Any help or fixes?

[wishr]

Hello Kyle,

Welcome to Veeam Community Forums!

Please review the posts above and reach out to our support team directly if you require additional help.

Thanks