Help
Post your comments for Moving a Time Machine backup here
Moving a Time Machine backup
#3
LDMartin1959 
- Newbie
-
- Group: New Members
- Posts: 7
- Joined: 13-July 11
Posted 07 November 2012 - 06:42 AM
Why do that? Time Machine now supports backing up to multiple drives. Just add the new drive and get the additional storage space.
#5
cdbm1967
- Newbie
-
- Group: New Members
- Posts: 1
- Joined: 07-November 12
Posted 07 November 2012 - 09:32 AM
Quote
Why do that? Time Machine now supports backing up to multiple drives. Just add the new drive and get the additional storage space.
How? I was looking for this feature for a VERY long time but I still do not see it. I am running on Mountain Lion with the latest patches applied.
#6
egnops
- Newbie
-
- Group: New Members
- Posts: 1
- Joined: 07-November 12
Posted 07 November 2012 - 10:30 AM
Quote
Why do that? Time Machine now supports backing up to multiple drives. Just add the new drive and get the additional storage space. How? I was looking for this feature for a VERY long time but I still do not see it. I am running on Mountain Lion with the latest patches applied.
IIRC, you can't just add more space with a new drive. What it now supports is multiple TM drives that can be switched out (so that you can keep one off-site, for example).
#7
collumend
- Newbie
-
- Group: New Members
- Posts: 1
- Joined: 07-November 12
Posted 07 November 2012 - 11:45 AM
I recently had to do exactly what is described in this article when I responded to the Apple recall of their Seagate 1TByte hard drives in my iMac. I was using that as an internal time machine drive (as part of a multifaceted back up strategy). I wanted to back up the time machine backup by moving to an external drive so that i could move it back again after the replacement. I didn't want to loose the version history. (my user data was on a SSD drive.) Problem was: the copy operation to an external drive kept dropping out. Try as i might i could not fix that. So in the end had to use SuperDuper to copy it all over to another drive (using options to avoid overwriting other files (a set of Retrospect backups) on the drive. After the Seagate drive replacement i couldn't copy the Timemachine folder (about 500Gbytes) back to the internal drive for the same reasons. SuperDuper doesn't support selective copy... so had to cheat and copy the whole lot over using SuperDuper and then delete the unwanted Retrospect files. This crashed out as the sum of time machine and Retrospect files was more that the 1TB Seagate files. LUCKILY: the TimeMAchine had copied over before it crashed out so i was able to kill it and just delete the extraneous files it had copied over.
Anyone understand have any ideas as to why my finder based copy would not work?
Anyone understand have any ideas as to why my finder based copy would not work?
#10
rbuis
- Newbie
-
- Group: New Members
- Posts: 4
- Joined: 07-November 12
Posted 07 November 2012 - 08:31 PM
Why would you go through all the confusing steps that you identified in your article. Just go to Help screen and lookup Time Machine. They tell you how to move to another hard drive and the steps are very simple and logical.
#11
Chris Breen
- Advanced Member
-
- Group: Moderators
- Posts: 5,926
- Joined: 11-December 00
Posted 07 November 2012 - 08:36 PM
rbuis, on 07 November 2012 - 08:31 PM, said:
Why would you go through all the confusing steps that you identified in your article. Just go to Help screen and lookup Time Machine. They tell you how to move to another hard drive and the steps are very simple and logical.
Which steps did you find confusing?
#12
Martian
- Veteran
-
- Group: Members
- Posts: 2,382
- Joined: 27-September 01
Posted 08 November 2012 - 08:53 AM
It's fair to mention that if the Time Machine file is on a network drive like a Time Capsule, the Backups.backupdb folder will be within the disk image called YourComputer'sName.sparsebundle (computer shown in the Sharing pref panel). You would then need to drag the entire sparsebundle to the new TM disk.
Also, if I am not mistaken, a sparsebundle dragged to a local drive (USB, firewire or thunderbolt drive) will continue to work even though the disk image container will no longer be mandatory. But the reverse, a Backups.backupdb folder dragged to a network drive will not work.
Also, if I am not mistaken, a sparsebundle dragged to a local drive (USB, firewire or thunderbolt drive) will continue to work even though the disk image container will no longer be mandatory. But the reverse, a Backups.backupdb folder dragged to a network drive will not work.
This post has been edited by Martian: 08 November 2012 - 08:55 AM
#13
rbuis
- Newbie
-
- Group: New Members
- Posts: 4
- Joined: 07-November 12
Posted 08 November 2012 - 11:51 AM
Quote
Why do that? Time Machine now supports backing up to multiple drives. Just add the new drive and get the additional storage space. How? I was looking for this feature for a VERY long time but I still do not see it. I am running on Mountain Lion with the latest patches applied.
At the finder level go to help and search for "Time Machine". The search returns a number of items - look for "if TM backup disk runs out of space" Here you will find simple instructions for starting a new backup and also moving your existing backups to the new larger disk.
