Recently I upgraded our UrBackup server to 1.4, then began upgrading the clients as well. Many of the clients are connecting under an all uppercase version of their name (i.e. “ClientA” creates a new entry “CLIENTA”). This of course means they don’t get their client-specific settings and don’t map to their backups.
Can anyone tell me what is going on and how to I can convince it that the client is the same?
For reference, Windows client and server, both versions 1.4, no-tray client. Nothing useful in the debug log that I can see.
No, I only upgraded after the official release, though the linked issue seems to be what I’m experiencing.
I was able to get everything working by modifying the “Computer name” filed on the server side client-sepcific settings (client tab), and the client-side settings.cfg file to reflect the old (mixed case or lowercase) name. Oddly, this caused the imaging and file backup settings to be reset to “enabled” regardless of their previous state, while all other settings were unaffected. I just deleted the uppercase name entries in UrBackup after that.
I hadn’t previously considered this because, nearest I could figure, that filed only had to do with how the imaging portion of the client worked. I hadn’t considered that it could make a client override its discovered name.
Perhaps a better way to handle this would be to ignore case for client names such that “ClientA” and “CLIENTA” would be considered the same client? Though I suppose that point is moot going forward anyway.