TM Renaming Sparsebundles

[DaveYHZ]

I'm seeing an interesting behaviour now:

After using the included tool, BMFU creates a sparse bundle named:

DaveYHZ-2_001ec21d2488.sparsebundle

I successfully connect TM to BMFU and begin a backup - which completes
successfully. A day or two later, I'm seeing a new sparsebundle in
the DroboCapsule folder named:

Dave’s MacBook Pro.sparsebundle

and the original file is no longer being updated (as noted in the Last
Modified Date).

I have tried taking TM offline, renaming the original sparsebundle to
the new name, deleting the .Apple* files and turning TM back on. It
immediately creates:

Dave’s MacBook Pro1.sparsebundle and begins backing up into there.

Weird huh?

[Mullet]

I'm getting the same exact thing. I've seen this with previous
versions of backmyfruitup and thought that version 3 might get rid of
the issue but it didn't. During version 2 I started with the
sparseimage that BMFU created. Then after a few weeks to a month later
I got a new image. I ignored it and let this image do its thing and
then after a few weeks an even a newer image was created. Since
version 3 I've had it create a new image once. Does anyone know why
this might be happening?

[Mullet]

I just want to report I'm still working with the newer sparse image
that was created as of my last post. I looked at my console log from
when everything changed and there was nothing that indicated an error.
Could it have been a corruption of those hidden .AppleXXX files? I'm
going to leave them be, so my backup doesn't decide to reback up
itself.

~Mullet