Skip to main content
Question

VBR13 backup server certificate fails to install

J

Veeam newbie and first-time poster here (go easy on me!) …

 

I am trying to attach an Ubuntu Linux 24.04 “minimal” server to a VBR13 test environment.  This server is only intended to provide backup storage for VBR.

 

While attempting to add the host as a managed server, I get the following error:

 

“Setting backup server certificate Error: Remote failed with message:  /opt/veeam/deployment/veeamdeploymentsvc: boost::filesystem::copy_file: Invalid cross-device link: "/tmp/VeeamUpload_20250328T170010Z/ServerCertificate", "/etc/veeam/certs/cert.p12"
--tr:Failed to install server certificate”

 

/tmp and / (where /opt and /etc reside) are separate logical volumes.

 

Any ideas on how to troubleshoot this?

 

VBR13 imported OVA (VMware), Console (Windows Server 2019), and Ubuntu server all on local LAN.  Managed credentials for Ubuntu added in VBR Console seem to work.

 

Thanks in advance!

6 comments

Chris.Childerhose
Forum|alt.badge.img+21

Your license for VBR v13 is not expired right?  I am pretty sure this is a much older appliance now.  Unsure where to check with this but you may need to wait on a newer build.

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
Tommy O'Shea
Dynamic
2 people like this
  • Tommy O'Shea
    Tommy O'Shea
  • Dynamic
    Dynamic
J
  • Jerod Parker
  • Author
  • New Here
  • 2 comments
  • March 28, 2025

License is valid (thanks to Rickatron).  I agree that the appliance is older (from late September), but I don’t have access to a newer one.

Chris.Childerhose
1 person likes this
  • Chris.Childerhose
    Chris.Childerhose
Chris.Childerhose
Forum|alt.badge.img+21

Unsure at this point how to help as I know support will not.  Might be something you need to tinker with to get working or not unfortunately.

Unless someone else knows maybe??

 
 
 
Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
J
  • Jerod Parker
  • Author
  • New Here
  • 2 comments
  • March 28, 2025

I totally get it.  I just wanted to ensure I’m not overlooking something obvious.  Thanks for the feedback.

Chris.Childerhose
1 person likes this
  • Chris.Childerhose
    Chris.Childerhose
Chris.Childerhose
Forum|alt.badge.img+21

Not a problem.  Maybe someone in the community will chime in that might have had and resolved this issue.

Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
D
Forum|alt.badge.img+3
  • ddomask
  • Comes here often
  • 115 comments
  • March 31, 2025

https://unix.stackexchange.com/questions/79132/invalid-cross-device-link-while-hardlinking-in-the-same-file-system

I think you’re hitting this. I doubt it’s about which preview version, it’s likely about the Ubuntu configuration with / and /tmp.

When Veeam is deploying the components, it will hardlink the components to a folder under /tmp with a uuid like you see. That hardlinking failed, and you can manually make the same folders and paths from the error and try hard-linking them yourself, likely it will fail.

https://www.veeam.com/kb2099

The registry value from here may help, create a special folder on the disks backing / and set the registry value to be that folder and see if it goes.

0x0D 0x0A
Chris.Childerhose
Tommy O'Shea
2 people like this
  • Chris.Childerhose
    Chris.Childerhose
  • Tommy O'Shea
    Tommy O'Shea

Comment


Terms & Conditions