So I finally got around to getting a 1tb drive to hook up to my airport extreme to do TM backups. I have ~420gb to backup on my mbp's hard drive. To avoid an absurdly long backup, I did the initial backup via usb (took the better part of the day).
Just now I was excited because it finished - I hooked the drive up to the extreme, mounted the drive so that it would show up as an option in the TM pref pane for a backup disk, and thought I was good to go. However, when I tried to get TM to do a backup so I could see it work (by selecting Back Up Now from the menubar), it took a ridiculously long time "preparing" and I saw that it was trying to create a whole new TM backup on the drive based on my computer's network name. It even had the audacity to think that the previous backup file was ~2gb, which freaked me out because I thought it had deleted it. But sure enough when I canceled the new backup and hooked it up to my mbp again, the backup was the correct size.
Any idea what might be going on here? I didn't run across this issue in any other posts.
TIA
Just now I was excited because it finished - I hooked the drive up to the extreme, mounted the drive so that it would show up as an option in the TM pref pane for a backup disk, and thought I was good to go. However, when I tried to get TM to do a backup so I could see it work (by selecting Back Up Now from the menubar), it took a ridiculously long time "preparing" and I saw that it was trying to create a whole new TM backup on the drive based on my computer's network name. It even had the audacity to think that the previous backup file was ~2gb, which freaked me out because I thought it had deleted it. But sure enough when I canceled the new backup and hooked it up to my mbp again, the backup was the correct size.
Any idea what might be going on here? I didn't run across this issue in any other posts.
TIA