Backing up to Veeam B&R Repository

[kleptos18]

Hey guys.

I setup a couple of physical servers to backup to a B&R Repository this morning. It's a local repository on the Veeam server, which then has a copy job to send the backups to the cloud.

Before I set this up this morning, Endpoint was already backing up to this external hard drive with no issues, so Endpoint has access.

After setting it up, I get the following immediate failure: "Error: Failed to create PathCommander, protocol 'Cloud' is not supported."

It's not a cloud based drive, it's local. I know it's seeing the right repository because there are only 2, or Service Provider and the local repository. It's seeing the right amount of space.

I've glanced through all the settings but not sure what I'm missing. I've opened a case and am waiting word back but figured maybe someone else had run into this.

[Dima P.]

Hello and welcome to the community Jason,

To tell the truth, I see this error first time. Can you share the case ID, please?

[kleptos18]

I opened it under my backup and replication login, and they moved it to endpoint support. I can no longer see the case.

Here's a little update.

If I remove the service provider (with the cloud connection) I can then run backups again.

There is somewhere that when I have the service provider repository in Veeam, Endpoint Backup thinks it's backing up to the cloud.

[Dima P.]

I think I get it now. Was that repository set as cloud connect repo by any chance?

[kleptos18]

No. I have both a local repository and a cloud repository.

If I remove the cloud repository, I can run backup jobs. They are running atm, so I'll add the cloud connection back in once they are done. But I assume, once I add it back in, backups will fail again.

[kleptos18]

Actually.

So I had 2 servers. One of those servers finished with the backup, so I re-added the cloud connection and got it setup for the one server and it started uploading the last backups. Good to go there.

So I went back to that server and kicked off an endpoint backup just to test, and it's now good to go.

Looks like I just had to trick veeam/endpoint with a backup to the repository, and THEN hook up the cloud connect. Odd behavior.

[Dima P.]

What VBR verion are we talking about?

[kleptos18]

It's version 9.

[Dima P.]

Thanks Jason. This is a confirmed bug now and we are going to fix it as soon as possible.

[davidrnexon]

Hi,

I have VE installed on a Windows 2012 R2 server with Exchange 2013 installed, I'm doing some tests in my lab and have attempted to backup first to a local disk, this was successful, exchange logs were cleared, etc

I then attempted to change the backup destination to a VBR repository and I get the following error:

Error: Failed to create PathCommander, protocol 'Cloud' is not supported

I have another server which is a plain Windows 2012 R2 server without Exchange and this backs up to the VBR repository successfully

Is there a limitation with VE and Exchange backing up to VBR repository ?

[JaxIsland7575]

This looks to be a confirmed bug.
The workaround was to disable the cloud jobs and then the endpoint jobs ran.

[davidrnexon]

Thanks Jax

I did have some cloud repository in VBR that I was testing with for this exchange server. I removed the existing cloud backup server reference in VBR but still had the same issue.

Looking at that article I need to completely remove the cloud repository from VBR ? I can try that tonight

FYI, this is with v9

[Dima P.]

Ryan is right – this is a known bug. Can you please open a case thru the VEB Control Panel - we might already have a fix at the support side. Don’t forget to post the case ID to this thread. Thanks.

[davidrnexon]

Dima - created a support request - ticket number 01688368

[Dima P.]

Thanks. To clarify: fix is on is way – QA team is testing it now. It should become available at the support side soon.

[davidrnexon]

Thanks Dima, much appreciated

[davidrnexon]

I applied the dll hotfix and re-ran the enpoint backup. I can confirm that this has resolved the issue. Will this be integrated into the next v9 patch ?

[Dima P.]

Hello David,

Thanks for confirmation! Yes, the plan is to include this fix in the upcoming Update 1.

[frankive]

After upgrading to B6R v9 we have an error on endpoint using b&r as a target repository.
"Failed to create PathCommander: protocol "Cloud" is not supported".

Any ideas?

Caseis from VEB: #01704905

[Shestakov]

Hello Frank,
As stated above in the thread, you should be able to obtain a hotfix via support team for the issue.
Thanks

[frankive]

Hot fix received from support, applied and everything is working again.
#veeamsupportrocks

[Shestakov]

Thanks for updating, Frank.
Great to know!

[skitch210]

Is the hotfix for the Endpoint or the Veeam B&R server?

[Dima P.]

Marty,

Hotfix should be applied at the VEB's end – in order to get it please open a support case via Endpoint’s Control Panel. Thanks

[Axeteg]

Same problem for me, case 01719008

[Vitaliy S.]

Mattias, in order to speed up the resolution, you can reference this thread in the support ticket. Thanks!

[praychiro]

same issue here. Can I get the hotfix? 01732855

[Vitaliy S.]

Our support team should be able to share this fix with you. BTW, we have just released a new version of Veeam Endpoint Backup, so it is worth upgrading.