Based on the data at the provided links from Alnitak and John's earlier answers, here is what I did:
- Plugged in the (USB) Time Machine HD
- Turned Time Machine off
- Found the current ethernet MAC address
- Disabled the ACLs on the TM
- Moved the .[old mac address] file in the root of the TM to be .[new mac address]
- Updated the extended attribute for the Backups.Backupdb/[machine name] to match the new mac address
- Reenabled the ACLs
- Ejected and unplugged the TM HD
- Turned Time Machine back on
- Plugged the HD back in again
Steps 4 through to 7 were done as follows:
$ sudo fsaclctl -p /Volumes/Time\ thingy/ -d
$ mv .[old mac address] .[new mac address]
$ sudo xattr -w com.apple.backupd.BackupMachineAddress [new mac address (with colon separators)] Backups.backupdb/Thalia/
$ sudo fsaclctl -p /Volumes/Time\ thingy/ -e
It ran the backup OK (looking at the inodes it recreated the entire directory structure, but linked the files to the previously backed up versions where it could, so not flawless, but good enough), and I can now "Enter Time Machine" and see the expected history.
As a bit of a side note, before resetting the xattr I ran xattr -l
(list) on the Thalia directory (looking for any other attributes that might be around to cause problems), and noticed that the pre-existing mac address was displayed in hex editor style (the address column (0000 on one line, 0010 on the next), the hex data column (each byte separated by a space), and the data column) and the data was actually terminated by a zero byte. After resetting it, it is just displayed simply as the mac address string (so presumably not terminated by a zero byte) - I'm hoping this won't cause problems.