following up the post on the apparent correlation between netatalk share names and avahi service advertisement i need to inform you that it wasn’t the whole truth.
as a matter of fact, netatalk registers (if compiled with zeroconf support) it’s services (thus including an eventually configured tm share) via dbus with avahi.
in case you manually advertise your time machine airdisk with a manually configured avahi service file, time machine may get confused.
i advice to decide for either technique to be used.
you can disable netatalk’s automatic service propagation via the