Mac Showing up twice on the server

Server
21

Thank you very much, this seems to work for now at least for new clients.

Any idea what we should do with existing clients? BTW: found a mac client this morning with two urbackup jobs running at the same time - but with different names…

On a test macbook, deinstalled urbackup client, set the hostnames using scutil, rebooted, reinstalled again.
Backup is not working and in log I get:

ERROR: Signature error: Verification failed

Even deleted the client from server, removed+installed client software - no way.

22

Falko,

What i did with my existing clients, i archived their backups and removed the clients on the server

Then i uninstalled the client from the Mac and in a sudo terminal window ran locate urbackup

Removed anything that still existed from urbackup on that mac and then reinstalled after running the scutil commands.

This has worked for me on all of my clients so far.

Let me know if this helps at all.

23

Thanx, mostly this works, but sometimes we have to fully delete the backups, then rename or at least set the names the same. Deleting all backups is not so sane for this moment, but luckily we’ve backups of the backup thanx btrbk :slight_smile:

In client beta 2.2.2 anyways there seems changes to our problems (just hit the symlink problem, too):

Do not follow symlinks if the symlink target is excluded
Use computer name and serial id to construct default macOS client name
Proper hash send error failure handling in file server UrBackup Server 2.2.3 beta/Client 2.2.2 beta

Is it possible to try beta client 2.2.0 with server 2.1.19, or should we wait for release?

24

So, after upgrading to UrBackup Server to 2.2.7 all Macs are named now mac-[name]-SERIAL, which seems ok.

But as the clients are not renamed, “old” client backup has it’s btrfs snapshots under urbackup/mac-[name], whereas now all clients get new dir/snapshot urbackup/mac-[name]-SERIAL not respecting the btrfs snapshot from mac-[name], which leads to duplication of needed backup space.

Tried something like

btrfs subvol snapshot urbackup/mac-name/180220-1600 urbackup/mac-name-C02SERIAL/180220-1600

But, as urbackup server doesn’t know of that, it doesn’t use that as snapshot parent and creates new full file backup.

Any advise on that?

25

In my situation, i would just archive the old backups to an external drive and start fresh with the clients. However what has worked for me in the past was simply stopping the urbackup server and moving the old backups into the newly created directory. I am not sure if there are any implications with this on the new version but it has worked for me previously.

26

Or give the clients the old name. It won’t append the serial if you manually name a client.

It links the files with the new client (global file level dedup), so it won’t use much new space.

27

Ok, thank you very much for your answers. Just tried to mv mac-name to mac-name-serial and to my surprise even the btrfs snapshots were renamed - so I’ll see if that works.

IMHO for renaming the client I have to activate “different settings for this client” - so e.g. the (lots of) excludes from the group settings cannot be updated for all clients at a time. Or is there some inheritance of the settings possible?

Another problem: most of the clients did rename itself to “mac-name-serial”, but some not - though the client version had been updated automagically to 2.2.4. Anything I can do about that?

28

8th checkbox of settings->general->server (actually just click settings) is “Autoupdate clients:”

29

Yes, auto update clients is activated. Or do you mean I should disable/enable the setting?

For me it seems that only these clients, which were online when upgrading UrBackup server from 2.1.19 to 2.2.4, could get the serial from the Macs, but none of the clients which came online any later.

30

If you don’t want the clients to update their version automatically, uncheck that.
As for the client names, i don t know.

31

ok, I thought you’ve wrote about the rename problem :smirk: