Backup to Boost repository?

[Petrie]

Dear all,

can´t I choose a Boost repository as a destination for my endpoint backup?

We have a EMC Data Domain and used to access it via CIFS. - We recently switched to DD Boost. Being afraid of the ransomware threats we wanted to be able to switch off CIFS access.
I tried to reconfigure our endpoint backups jobs, but I can only choose the old CIFS repositories, the Boost repositories are not listed.

Am I doing something wrong?

Thank you and regards,
Helge

[Vitaliy S.]

Hi Helge,

Can you please clarify how this DD boost is exposed (what type of repository you're choosing) to your Veeam Endpoint backup job?

Thanks!

[nielsengelen]

Did you configure the correct Endpoint permissions on the new repository?

[Petrie]

Thanks a lot for the quick reply.

@Vitaliy: The repository is configured as "Dedup storage appliance / EMC Data Domain".
The repsository we used until last week was configured as "Shared Folder / CIFS". - This is the only repository that is visible in the VEB configuration.

@Niels: Which permissions do I have to set? I just realized that there is a "permission" setting dialog when I right-click on the repository.
- The setting is "Deny to everyone". I tried to add the appropriate server to this dialog, but when I choose the machine´s or the user´s AD account, an error message pops up: "Account does not exist".

Thanks again for your help!

[Petrie]

=> When I select "Allow to everyone", the repository is visible. Seems to be my fault, sorry... - Could this be a security issue? I only want one certain server to be able to write it´s endpoint backup to this repository.

[Vitaliy S.]

Yes, could be. If this repository is visible when you select "Allow to everyone", then you should look deeper into account settings you're using with Veeam Endpoint Backup. Try to grant access to any AD account and then login with this account to the VEB computer and try to configure the backup job.

[Petrie]

I just got it!

The error message is due to a little and annoying bug in VBR9, that I have alerady filed to the support team.

VBR9 assumes that the NetBIOS domain name is the same as the FQDN (except the .xxx). This leads to errors if both names are different, - like in our company. By typing in the account name manually, it works!

Thanks a lot for your help!

Regards,
Helge

[Mike Resseler]

Helge,

Thanks for coming back to us and with the solution

Much appreciated

Mike