You guys are for all practical purposes right about what was causing Time machine to start a new backup. The backup is apparently tied to specific hard drives via a UUID. Changing to a new hard drive changes the UUID thus Time Machine thinks this is a new setup. More info and possible fix.
Time Machine: Inherit Backup Using `tmutil` - Simon Heimlicher
Thanks for this Sly óle mate
Ill remember that for next time, and the author is one smart cookie, and i also found this,
Time Machine: UUID of Disk Changed - Simon Heimlicher as well that might well come in handy, and would of for me a few times.
What i ended up doing was, to delete the sparse.bundle and it took about 3 hrs to completely delete OTA, but it went, and i had already done a SuperDuper backup to a 750gb Ext, and i cleaned the Macintosh HD up and got my iTunes in order with iDentify and looks beautiful, then i set up time machine again from the SSD.
What i find funny, is TM was seeing that the new SSD and the old Macintosh HD as 1 ?? Can anyone explain that too me please ?? So i went ahead and excluded my SSD Home Folder, Music, Movies, DropBox, Google Drive and Applications (From Mac HD) and set it on its way.
This is why i know TM saw the 2 HD's now as one, because as i was excluding Folders from my SSD, the size of the initial Backup was getting smaller, so i excluded the Home Folder from the Mac HD and the size went down again, and then i deleted it from exclusions and it went back up.
All very confusing but i have now got a TM backup going perfectly and only backing up a few MB's every hour as it should be as i am only surfing at the moment.
Thanks for the help Sly and liab