Cloud Connect Repository Names

[Gsmith]

All,
I have recently installed Veeam B&R 10 on Windows server 2019, along with Cloud Connect. This is a 30-Day trial license.
Currently I have 2 VMs backing up to your cloud repository. The backup file is being restored using a GUID, unlike a traditional repository that names the backup file after the name of the VM. My question is how I can fix this to show the name of the Virtual machine FQDN instead of a GUID?

This example is my Veeam Cloud Connect repository as of now.

1606a8f4-2361-42c9-9189-a51a67067da6D2021-02-17T084350_18C1.vbk vbk 6.8 GB 2/17/2021 8:55:01 AM
ba440930-4739-4e96-8dfe-1f52a0773703D2021-02-17T082829_BE80.vbk vbk 972.7 MB 2/17/2021 8:31:35 AM


In a situation where a client is backing up 50 VM’s, all of whom’s back files are random GUID’s, and the client wants to restore a VM named “Carbon”, how do we know which is a backup of carbon?


This is example of another Veeam R&B server backup repository.
file-server.some_domain.com.d7c1b3dd-29ca-4ce1-9d93-cD2020-09-18T180212_16D2.vbk vbk 7.2 GB 2/17/2021 8:49:49 AM

[Mildur]

There is no way to change that.
Think of Cloud Connect as a dropbox. Only the client, the clients Veeam Backup Server knows whats inside the file.

Why do you want to know the file name on the cloud repo?
If your client want to restore that vm to his enviroment, then simply go to the clients backup server and do the restore. Right klick on vm and start the restore.

https://helpcenter.veeam.com/docs/backu ... ml?ver=100

[veremin]

Are you going to enable an MSP type of scenario for your clients, where you will be managing their backup infrastructure?

If so, wait for v11 GA and select “Allow this Veeam Backup & Replication installation to be managed by the service provider” checkbox in the Service Provider wizard in the tenant-side backup server.

This way backup metadata like machine names will not be obscured in the service provider-side backup server, which will allow you to deliver managed backup services more efficiently.

Thanks!

[Mildur]

Hi veremin
Thanks for this information. I'm looking forward for this.

[Gsmith]

@Mildur
Thank you for the reply.
I was just curious why it was like that, we are testing this software out and I noticed the name was no present on the file just GUID.

@veremin
Thank you for the reply and added info, I signed up for V11 event.

[bytewiseits]

This will be a welcome change to the MSP management side of things for us

For existing CC backup chains, once upgraded to V11 on the client side with management already enabled, will newly created incremental/synthetic full backup file names be non-obscured on the cloud connect side?

Or will we need to run something like an active full, or (worst case) completely disconnect the client VBR from CC and then re-add again to get rid of the obscurity moving forward?

[veremin]

For existing CC backup chains, once upgraded to V11 on the client side with management already enabled, will newly created incremental/synthetic full backup file names be non-obscured on the cloud connect side?

Should not require any additional action, but I will re-test this scenario to be completely safe. Will update the topic with the results of our findings. Thanks!