- Service Provider
- Posts: 443
- Liked: 30 times
- Joined: Dec 28, 2014 11:48 am
- Location: The Netherlands
We have experienced some issues with FLR that doesn't work as expected when restoring from a SOBR, resulting in an error message Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.
For now it has been resolved by pointing the mount server on all extents to the VBR server, where the FLR is working as expected without Exception messages.
Is it expected behaviour when that FLR are not working from a SOBR when using the extent server ( part of SOBR ) as a mount server ?
- Veeam Vanguard
- Posts: 499
- Liked: 117 times
- Joined: Aug 13, 2014 6:03 pm
- Full Name: Chris Childerhose
- Location: Toronto, ON
Mind the following:
For scale-out backup repositories, you must specify the mount server for every extent."
"By default, Veeam Backup & Replication suggests assigning the mount server role to the following infrastructure components depending on the OS of the backup repository:
For Microsoft Windows backup repositories, Veeam Backup & Replication suggests the backup repository server itself.
For Linux, shared folder backup repositories and deduplicating storage appliances, Veeam Backup & Replication suggests the backup server."
Are you using Linux for the extents in the SOBR?
Veeam Vanguard / Veeam Legend / Veeam Ceritified Architect / VMCE
vExpert / VCAP-DCA / VCP6 / MCITP
Personal blog: https://justvirtualization.blog
- Product Manager
- Posts: 7153
- Liked: 1889 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
I don't see why this should not work. Please open a support case and give our support team a chance to review the log files.
They will be able to tell from the logs why it is failing.
Please provide the case number in this topic for our reference.
Users browsing this forum: Bing [Bot] and 11 guests