Super Duper BU vs Time Machine

Why would I want to replace my current fast and neat " Super Duper " backup software installed in 10.4 Tiger with SL's Time Machine ?

Bic Ford wrote:
Can and should the Time Capsule be partitioned ?
No, it can't. (Well, short of removing the disk, putting it in an enclosure and connecting it to your Mac, which voids the warranty).
Would partitioning be good or necessary if two Mac's are writing TM BU to same EHD ?
It's usually a good idea, for an external disk connected via FireWire or USB, or an internal disk. See item #4 in the Frequently Asked Questions *User Tip.*
In the end I hope to have SD backup going to the Lacie and TM going to the TC HD. Two BU's with two devices for each machine is recommended by BU seminar givers at Tekserve.
Lots of folks here, too, especially those of us who think Murphy was an optimist!

Similar Messages

Can i reconnect a "super duper" clone to "time machine" as original?

hi there.
i've recently upgraded the hard drive on my mbp 17, using super duper for cloning my stuff onto the new hd.
only later i've discovered that using the same hd name doesn't mean time machine recognizes it as the same, root hd.
i already slap myself endlessly for this naive mistake, as now i can only back my hd as another hd, multiplying the space and duration the backup requires.. still didn't let it go through.
i have no real experience using the terminal, and since i didn't find any result online relating exactly to my situation, i can't readily try to perform any suggestion i've already found, for the risk of damaging something permanently.
more info - leopard; time machine hd is accessible, as is the backed up info on it when reached through time machine.
i only need a solution for making the new hard drive be accepted by time machine as the old one.
thanx in advance,
yaneev

thx for the answer, i've actually read that article before.
no, i didn't start a new BU sequence, as i'm totally insecure even opening terminal.
by reformatting the HD i would lose months of mail backups etc.
i did take care of periodically manual BUs of important stuff,
so now i guess i just dont get the eventual purpose of TM..
sometimes it feels sad to be lost somewhere between being a very advanced mac user and being just a newbie without a clue of how to mess things up...
Message was edited by: yaneev

Time Machine Will Not Work - Onyx Broke it and I Can't Fix It!

Background
The external drive is a western digital my book 500 GB drive(black with round button on front) connected with fire wire, with three partitions, 200/200/what ever is left. One has super duper bootable clone/time machine/extra store space. I am using about 80GB of 320GB on my internal.
I used onxy utility on my old TiBook with good results so last week I though oh let me down load that and use it on my new MBP. I run the utility and the next day notice that TM is not working(Onyx has been uninstalled and should have a big warning this will F-U TM). Try to figure it out no luck, call support the guy points out he did a search and there are a bunch of people who say onyx broke their TM. The TM buddy message was along the lines of deep traversal needed and the UUID don't match. I run disk repair and do the regular stuff still no luck.
After reviewing the trouble shooting guide above and trying some of the fixes with out results, I decide to erase the partition as I only have a few weeks of data on there and I keep a super duper backup twice a week on another partition.
Now that I am trying to start it new the problem seems to be that the backup hangs after evaluating between 1.5 and 3.5 GB it makes not further progress after hours. Example, I tried a new backup this morning its hung at 1.64GB, I will check at lunch time and it will probably still be there.
Things I have tried and reviewed
All drives internal/external formated correctly
All external drives added to spotlight privacy
Trashed time machine preference file and restarted (twice!)
Checked to see if there is a firmware update for external drive and I don't think there is
I think this is from my try this morning, I need to double check...
Time Machine Buddy Message:
Starting standard backup Backing up to: /Volumes/BackUp TM/Backups.backupdb Ownership is disabled on the backup destination volume. Enabling. Event store UUIDs don't match for volume: Macintosh HD Backup content size: 81.0 GB excluded items size: 128 KB for volume Macintosh HD No pre-backup thinning needed: 97.17 GB requested (including padding), 199.33 GB available Waiting for index to be ready (909 > 0)
My frustration level has been rising since I noticed this on Saturday and have not been able to resolve it or make any progress, your help is appreciated.
Jerome

C. Jerome wrote:
Onyx has been uninstalled and should have a big warning this will F-U TM).
No. You're jumping to conclusions. Many folks (including me) have run OnyX for a long time with no ill effects on TM.
Try to figure it out no luck, call support the guy points out he did a search and there are a bunch of people who say onyx broke their TM.
What "support guy?" There are no such posts in this forum.
The TM buddy message was along the lines of deep traversal needed and the UUID don't match. I run disk repair and do the regular stuff still no luck.
Those are completely normal in some situations, such as your first backup, and the first backup after installing an OSX update. The "deep traversal" does mean there will be a long "preparing" phase.
After reviewing the trouble shooting guide above and trying some of the fixes with out results, I decide to erase the partition
That means you will continue to get the UUID and +deep traversal+ messages, and lengthy preparing phase, until TM can complete a backup.
All drives internal/external formated correctly
Double-check this, via the instructions in item #C1 of the Troubleshooting tip. Please post the results.
All external drives added to spotlight privacy
And excluded from any anti-virus scanning?
Checked to see if there is a firmware update for external drive and I don't think there is
They have released some fairly recently, and have fixed some similar problems. It's probably worth your time to double-check to be sure.
Time Machine Buddy Message:
Starting standard backup
Backing up to: /Volumes/BackUp TM/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Event store UUIDs don't match for volume: Macintosh HD
Backup content size: 81.0 GB excluded items size: 128 KB for volume Macintosh HD
No pre-backup thinning needed: 97.17 GB requested (including padding), 199.33 GB available
All normal.
Waiting for index to be ready (909 > 0)
As you see in item #D2 of the Troubleshooting tip, this can indicate a problem with the drive, or communicating with it. Have you tried all the other things in item #D2?
Also, there are some recent reports that seem to indicate a couple of other possibilities:
Reduced WIFI power when running on battery, since the 10.5.8 update. Are you running on utility power or battery power when this happens?
Some sort of conflict with Mozy version 1.4.0. So far, this appears to be related only to wireless backups, but if you're running Mozy, it might be worth investigating.
You might also want to use the Console app (in your Applications/Utilities folder) to see if there are other messages indicating a conflict with your backups.
When it starts, click +Show Log List+ in the toolbar, then navigate in the sidebar that opens up to your system.log and select it. Navigate to the +Starting standard backup+ message that you noted above, then see what follows that might indicate some sort of *error, failure, throttling respawn, termination, exit,* etc. (many of the messages there are info for developers, etc.). If in doubt post (a reasonable amount of) the log here.
Finally, how old is your disk drive? They do fail, sometimes sooner rather than later, and often exhibit just this sort of behavior.

Time Machine stalls on first backup of new iMac with 3TB Fusion Drive

I've got a brand new 27" iMac with latest patches up to OS X 10.9.1. I've loaded about 500GB of data onto this machine and wanted to make an intial Time Machine backup, so I connected a brand new 4TB Seagate Backup Plus USB 3.0 external hard drive, formatted the drive as Mac OS Extended (Journaled), pointed Time Machine at it, and let it go. It ran up to about 30GB before I walked away. When I came back maybe 8–10 hours later it was still stopped at about 30GB. I stopped it, and tried again. This time it just went a couple of GB before halting. I can hear the external drive stop spinning because it isn't being accessed.
I also have a new 2TB Western Digital My Passport USB 3.0 external drive, so I formatted that as Mac OS Extended (Journaled) and tried setting it as the Time Machine drive instead. Again Time Machine gets a little way into the backup before stalling and proceeding no further. I think this rules out the drive, since both drives behave the same way.
I also have Super Duper installed on this machine, so I tried doing a full disk copy to the WD drive and this worked flawlessly. This suggests that nothing is wrong with the drives themselves, as does the successful check of all three disks with Disk Utility.
I've checked "Prevent computer from sleeping automatically when the display is off" in Energy Saver. I've unchecked "Put hard disks to sleep when possible". I've checked "Enable Power Nap". I set Time Machine back to using the 4TB Seagate Drive and have been letting it run as long as it wants to. It got up to 13.32GB this morning before seeming to stall this morning. 10 hours later when I got from work it's still at 13.32 GB and it still says "About 7 hours remaining", just as it did at 8:30am.
I've read a bunch of discussions on here about issues like this, which is where I came up with some of the things I've tried. So far, nothing has worked. Can anyone suggest a working solution? It seems like the Time Machine software just isn't workin

Pondini's site is excellent, but didn't happen to cover this problem (or Mavericks in particular as of yet). But I did call AppleCare support as you suggested, rkaufman87, where I was quickly escalated since I'd already tried the things the first tier support people start with. After some investigation via screen sharing and inspection of my system log (which suggested the stall involved issues with the index) the main change we made was to clear out the Time Machine preference files and Spotlight's cache before rebooting and trying again. This time the backup completed without stalling, and has continued to work ever since. Thanks for encouraging me to call support!

Time Machine in addition to Super Duper

My previous backup external drive died and I just got a replacement. I have always used Super Duper (which is great) to back up my computers so that I have a bootable backup. The question is---does it make any sense to partition the drive so that there is one partition for Super Duper and a second for Time Machine? What benefit would Time Machine add?
Thanks

Keep in mind that TimeMachine backs up changes every hour, keeps daily backups for a month and weekly backups thereafter. At work my backup set is about 125GB and I began backing up to the current TM drive in August. The TM backup is now 244GB. Prior to upgrading to 10.6 my home computer's TM backup was nearly 3 times the size of the backup set. To me, the value of TM is the redundancy and its value is diminished when older backups have to be erased to make room for a new backup set. For this reason I recommend that a TM drive be no less than twice the size of the backup set and closer to three times the size. This is in addition to the SD! clone I keep.
If your external drive is large enough then yes, it is fine to partition it. If it isn't, use one method or the other and/or purchase a second backup drive. Also, keep in mind that SD! can be set to perform scheduled backups and it can also keep archives (copies of files that were changed since the last backup).

Time Machine or External Using Super Duper

Apple is going to change the HD on my computer. I know little about Time Machine but I have been backing up my HD using Super Duper and a LaCie external HD. I think it's working out so far. That's what I have done before replacing the HD. So, when the new HD is installed, I can start up using the external and transfer files, i.e., mail, iTunes, Safari, Firefox etc. from the Application file on the external to the Application file on the computer with the new HD without any change in content. Any advantage using Time Machine over the way I intend to do it which should work. Any preferences or none?
I have already posted in a different Topic but on this sight regarding another aspect of this operation.

I generally can get Time Machine to work for a while. It takes way more effort to get it working and to keep it working than you'd expect for a Mac.
The most recent event was when I mounted my new 500 GB Hitachi drive in a new Mercury Elite-AL Pro mini, connected with Firewire 800 to my Mac Mini Server. I formatted the drive, using the 7-pass erase in Disk Utility, with no errors. I used disk utility to verify the file system on the drive before I started using it with Time Machine.
I configure Time Machine to use that new drive, and it starts up, but pukes fairly quickly. I Googled the error messages, and found lots of other people running into the same error.
First off, the disk would not unmount. Had to force unmount it.
Used Disk Utility to Repair the file system. It encountered no errors. So, then I used Disk Warrior to rebuild the directory structure on the disk. It found some things that it corrected. Since then, Time Machine has been working on that disk without further errors (overnight).
How many Apple customers are going to want to deal with force unmounts, running disk utility and disk warrior to tickle Time Machine back into working?
These are my log entries from the most recent Time Machine errors:
Dec 30 09:42:13 MacMini com.apple.backupd[2388]: Starting standard backup
Dec 30 09:42:13 MacMini com.apple.backupd[2388]: Backing up to: /Volumes/Backups/Backups.backupdbDec 30 09:42:13 MacMini com.apple.backupd[2388]: Detected system migration from:
/Volumes/Christopher-J-Shakers-Mac.localDec 30 09:42:17 MacMini com.apple.backupd[2388]: Backup content size: 406.7 GB excluded items size: 34.0 GB for volume MacMini
Dec 30 09:42:17 MacMini com.apple.backupd[2388]: No pre-backup thinning needed: 447.22 GB requested (including padding), 465.02 GB availableDec 30 09:42:17 MacMini com.apple.backupd[2388]: Waiting for index to be ready (
101)Dec 30 09:42:17 MacMini mds[42]: (Normal) DiskStore: Creating index for /Volumes
/Backups/Backups.backupdbDec 30 09:42:30 MacMini ntpd[33]: time reset -0.559108 sDec 30 09:42:54 MacMini JollysFastVNC[898]: (00599870.0592)-[NetworkConnection disconnect] could not shut down writehandleDec 30 09:43:01 MacMini login[1339]: DEAD_PROCESS: 1339 ttys001
Dec 30 09:58:09 MacMini ntpd[33]: time reset -0.483469 s
Dec 30 10:00:34 MacMini kernel[0]: Dec 30 10:00:45: --- last message repeated 3 times ---Dec 30 10:00:45 MacMini com.apple.backupd[2388]: Error: (-36) SrcErr:NO Copying /Developer/Library/PrivateFrameworks/DTMessageQueueing.framework/Versions/A/DTM essageQueueing to /Volumes/Backups/Backups.backupdb/SNOWSERVER/2010-12-30-094033.
inProgress/02385079-1749-4E5A-BC4F-93367E30B581/MacMini/Developer/Library/Privat
eFrameworks/DTMessageQueueing.framework/Versions/ADec 30 10:00:45 MacMini com.apple.backupd[2388]: Stopping backup.Dec 30 10:00:45 MacMini com.apple.backupd[2388]: Error: (-8062) SrcErr:NO Copying /Developer/Library/PrivateFrameworks/DTMessageQueueing.framework/Versions/A/DTM essageQueueing to /Volumes/Backups/Backups.backupdb/SNOWSERVER/2010-12-30-09403
3.inProgress/02385079-1749-4E5A-BC4F-93367E30B581/MacMini/Developer/Library/Priv ateFrameworks/DTMessageQueueing.framework/Versions/A
Dec 30 10:00:45 MacMini com.apple.backupd[2388]: Copied 13388 files (10.5 GB) fr
om volume MacMini.Dec 30 10:00:45 MacMini com.apple.backupd[2388]: Copy stage failed with error:11Dec 30 10:00:46 MacMini com.apple.backupd[2388]: Error: (22) setxattr for key:co
m.apple.backupd.ModelID path:/Volumes/Backups/Backups.backupdb/SNOWSERVER size:1
0Dec 30 10:00:51 MacMini com.apple.backupd[2388]: Backup failed with error: 11Dec 30 10:06:19 MacMini mds[42]: (/Volumes/Backups/.Spotlight-V100/Store-V1/Stores/A3D115A8-4546-4A3B-B36E-59440 4EEA098)(Error) IndexCI in ci_ftruncate:ftruncat
e(34 /Volumes/Backups/.Spotlight-V100/Store-V1/Stores/A3D115A8-4546-4A3B-B36E-594404 EEA098/live.0.indexDirectory, 16448) error:22Dec 30 10:06:19 MacMini mds[42]: (/Volumes/Backups/.Spotlight-V100/Store-V1/Stor
es/A3D115A8-4546-4A3B-B36E-594404EEA098)(Error) IndexCI in expandMap:ftruncate err: 22
Here is another one:
Dec 30 10:06:20 MacMini mds[42]: (Normal) DiskStore: Creating index for /Volumes/Backups/Backups.backupdb
Dec 30 10:14:12 MacMini ntpd[33]: time reset -0.496024 s
Dec 30 10:29:48 MacMini ntpd[33]: time reset -0.481983 s
Dec 30 10:42:31 MacMini com.apple.backupd[2388]: Starting standard backup
Dec 30 10:42:31 MacMini com.apple.backupd[2388]: Backing up to: /Volumes/Backups/Backups.backupdb
Dec 30 10:42:35 MacMini com.apple.backupd[2388]: Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Backups/Backups.backupdb/SNOWSERVER size:10
Dec 30 10:42:35 MacMini com.apple.backupd[2388]: Detected system migration from: /Volumes/Christopher-J-Shakers-Mac.local
Dec 30 10:42:37 MacMini com.apple.backupd[2388]: Failed to create progress log file at path:/Volumes/Backups/Backups.backupdb/SNOWSERVER/2010-12-30-094033.inProgress/ .Backup.315427357.871281.log.
Dec 30 10:42:37 MacMini com.apple.backupd[2388]: Error: (-50) Creating directory 61478D74-6407-4DBA-A98D-8A20EC6F2140
Dec 30 10:42:37 MacMini com.apple.backupd[2388]: Failed to make snapshot.
Dec 30 10:42:37 MacMini com.apple.backupd[2388]: Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/Backups/Backups.backupdb/SNOWSERVER size:1
0Dec 30 10:42:42 MacMini com.apple.backupd[2388]: Backup failed with error: 2
So far, it has been running ok on that disk since I force unmounted it and used disk warrior to rebuild its directory structure.
While I was visiting my sister-in-law over Christmas, I had to resurrect Time Machine on my old PowerMac dual G5 I gave her. It's backing up to an internal SATA drive that I previously tested quite extensively. I had to use Disk Warrior to rebuild the directory structure on that disk as well to get Time Machine working again.
It seems to me that time machine, or the device drivers it relies on, needs some work.
Chris Shaker

Time Machine and Super Duper

I purchased Super Duper and did a full backup on my Mac Pro (I have 3 hard drives, the main one and 2 backup drives that are mounted on the desktop). Everything worked fine, I did the Super-Duper start-up/complete backup to one of the extra hard drives. The problem is when I run Time Machine it backs up everything including the extra copy of my computer that Super-Duper just created. This just filled up the extra hard drive that I use for Time Machine.
My question...
1) Is there a way to have the Super-Duper back-up copy of my computer but then not have it re-backed up by Time Machine? Do I need to remove the hard drive (the hard drive with the Super-Duper copy) from the desktop, and how do I do this... they are internal hard drives and not external hard drives.
2) What is the best way to undo what I have done and get the space back on my extra hard drive that I am using for time machine?
Thanks for the help
Chris

As Neville says, you can exclude the SD drive from future Time Machine backups via TM Preferences > Options.
And you can delete the prior backups of that drive, too. See #12 in the Frequently Asked Questions *User Tip,* also at the top of this forum.

Using Migration Assistant with Time Machine or Super Duper data

Can I use Migration Assistant with a Time Machine or Super Duper backup on an external drive instead of the original computer? I'm thinking of upgrading my Mini to a new one but only have one monitor. Not in the mood to hunt down an old monitor & buy adapters, etc. If I can, are there any tradeoffs using a backup instead of the original Mini? And is TM or SD preferable for this purpose? The current Mini runs 10.6 SL.

KevinD wrote:
Can I use Migration Assistant with a Time Machine or Super Duper backup on an external drive instead of the original computer?
yes to both.
I'm thinking of upgrading my Mini to a new one but only have one monitor. Not in the mood to hunt down an old monitor & buy adapters, etc. If I can, are there any tradeoffs using a backup instead of the original Mini?
none.
And is TM or SD preferable for this purpose?
makes no difference.
The current Mini runs 10.6 SL.

Time Machine or Super Duper??

I have been using Super Duper successfully under Tiger with an external Seagate USB Drive. Now that I have Snow Leopard... I was wondering about Time Machine. I only want to use it if it does something substantially better than Super Duper- outperforms in some way shape or form- why mess with a good thing?
Message was edited by: Micah Eavenson

Ditto what Mr. Boyd says, adding "every hour."
Time Machine gives you a *much, much* better chance of recovering something you changed or deleted in error (Save instead of Save As, for example), or somehow got corrupted.
Plus the ability to put your entire system back the way it was at the time of any prior backup.
It's no doubt more than you want, but here's a comparison:
There are three basic types of backup applications: Bootable Clone, Archive, and Time Machine.
This is a general explanation and comparison. Many variations exist, of course, and some combine features of others.
|
_*BOOTABLE "CLONE"*_
These make a complete, "bootable" copy of your entire system on an external disk/partition, a second internal disk/partition, or a partition of your internal disk.
Advantages
When your internal HD fails, you can boot and run from the clone immediately. Your Mac may run a bit slower, but it will run, and contain everything that was on your internal HD at the time the clone was made or last updated.
You can test whether it will run, just by booting-up from it (but of course you can't be positive that everything is ok without actually running everything).
If it's on an external drive, you can easily take it off-site.
Disadvantages
Making an entire clone takes quite a while. Most of the cloning apps have an update feature, but even that takes quite a while, as they must examine everything on your system to see what's changed and needs to be backed-up. Since this takes lots of time and CPU, it's usually not practical to do this more than once or twice a day.
Normally, it only contains a copy of what was on your internal HD when the clone was made or last updated.
Some do have a feature that allows it to retain the previous copy of items that have been changed or deleted, in the fashion of an archive, but of course that has the same disadvantages as an archive.
|
_*TRADITIONAL "ARCHIVE" BACKUPS*_
These copy specific files and folders, or your entire system. With many, the first backup is a full copy of everything; subsequently, they're "incremental," copying only what's changed.
Most of these will copy to an external disk or network locations; some to CDs/DVDs, or even tape.
Advantages
They're usually fairly simple and reliable. If the increments are on separate media, they can be taken off-site easily.
Disadvantages
Most have to examine everything to determine what's changed and needs to be backed-up. This takes considerable time and lots of CPU. If an entire system is being backed-up, it's usually not practical to do this more than once, or perhaps twice, a day.
Restoring an individual item means you have to find the media and/or file it's on. You may have to dig through many incremental backups to find what you're looking for.
Restoring an entire system (or large folder) usually means you have to restore the most recent Full backup, then each of the increments, in the proper order. This can get very tedious and error-prone.
You have to manage the backups yourself. If they're on an external disk, sooner or later it will get full, and you have to do something, like figure out what to delete. If they're on removable media, you have to store them somewhere appropriate and keep track of them.
|
_*TIME MACHINE*_
Advantages
Similar to an archive, TM keeps copies of everything currently on your system, plus changed/deleted items, on an external disk or Time Capsule.
Like many Archive apps, it first copies everything on your system, then does incremental backups of additions and changes. But TM's magic is, each backup appears to be a full one: a complete copy of everything on your system at the time of the backup.
It uses an internal OSX log of what's changed to quickly determine what to copy, so most users can let it do it's hourly incremental backups without much effect on system performance. This means you have a much better chance to recover an item that was changed or deleted in error, or corrupted.
Recovery of individual items is quite easy, via the TM interface. You don't have to find and mount media, or dig through many files to find what you're looking for.
You can also recover your entire system to the exact state it was in at the time of any backup, even it that's a previous version of OSX.
TM manages it's space for you, automatically. When your backup disk gets near full, TM will delete your oldest backup(s) to make room for new ones. But it will never delete it's copy of anything that's still on your internal HD, or was there at the time of any remaining backup. So all that's actually deleted are copies of items that were changed or deleted long ago.
Disadvantages
It's not bootable. If your internal HD fails, you can't boot directly from your TM backups. You must restore them, either to your repaired/replaced internal HD or an external disk. This is a fairly simple, but of course lengthy, procedure.
TM doesn't keep it's copies of changed/deleted items forever, and you're usually not notified when it deletes them.
It is fairly complex, and somewhat new, so may be a bit less reliable than some others.
|
RECOMMENDATION
For most non-professional users, TM is simple, workable, and maintenance-free. But it does have it's disadvantages.
That's why many folks use both Time Machine and a bootable clone, to have two, independent backups, with the advantages of both. If one fails, the other remains. If there's room, these can be in separate partitions of the same external drive, but it's a bit safer to have them on separate drives.
|
_*OFF-SITE BACKUPS*_
As great as external drives are, they may not protect you from fire, flood, theft, or direct lightning strike on your power lines. So it's an excellent idea to get something off-site, to your safe deposit box, workplace, relative's house, etc.
There are many ways to do that, depending on how much data you have, how often it changes, how valuable it is, and your level of paranoia.
One of the the best strategies is to follow the above recommendation, but with a pair of portable externals, each 4 or more times the size of your data. Each has one partition the same size as your internal HD for a "bootable clone" and another with the remainder for TM.
Use one drive for a week or so, then take it off-site and swap with the other. You do have to tell TM when you swap drives, via TM Preferences > Change Disk; and you shouldn't go more than about 10 days between swaps.
There are other options, instead of the dual drives, or in addition to them. Your off-site backups don't necessarily have to be full backups, but can be just copies of critical information.
If you have a MobileMe account, you can use Apple's Backup app to get relatively-small amounts of data (such as Address book, preferences, settings, etc.) off to iDisk daily. If not, you can use a 3rd-party service such as Mozy.
You can also copy data to CDs or DVDs and take them off-site. Re-copy them every year or two, as their longevity is questionable.
Backup strategies are not a "One Size Fits All" sort of thing. What's best varies by situation and preference.
Just as an example, I use TM plus a CarbonCopyCloner clone (updated daily, while I'm snoozing) locally, plus small daily Backups to iDisk, plus some other things to DVD/RWs in my safe deposit box. Probably overkill, but as many of us have learned over the years, backups are one area where +Paranoia is Prudent!+

Would Super Duper!/Time Machine function w/ Littlle disk - MacBook 2.0

RE: Would Super Duper!/Time Machine function w/ Littlle disk - MacBook 2.0
Thanks to all who read on...
The situation at hand is this...
I have 2 Lacie Little Disk Drives 120 & 250 GB, that I once used to make FW clones from iBook G4 to backup my information , applications etc.
1.0_How would I translate such operations with a substituted Macbook 2.0 Aluminum?
1.1_It seems the Macbook doesnt have any FW ports, nor is their any reliable source stating a T-100-to-Firewire adapter would work with OS 10.5.6...?
THAT being said, the USB ports do recognize the built in Lacie Hi-Speed 2.0 extractable USB Connector. (See Topic: Little disk on a hub with Macbook?)
I have given Super duper a try to make a Leopard (10.5.6) over this Hi-speed USB 2.0 and it seems to have made the backup, although I haven't as of yet actually used this clone -yet.
2.0_How can I take advantage of Leopards Time Machine instead of Super Duper!?
2.1_Whilst still possibly incorporating the usb/firewire Lacie Little disks? (As once sod on THIS very site)

I'll agree with the previous two posts. With TimeMachine, you always have your most current and previous versions of data backed up. With SuperDuper (or CarbonCopyCloner), your data is only as current as the last time you ran a backup. The major benefit of SuperDuper (or CCC) is that you can create a bootable backup. If you need to restore your system from a TimeMachine backup, you'll need to start your system from your install DVD which will allow you to restore your system from your TimeMachine backup. I think the biggest benefit to having an external clone is in case your internal drive fails. Since you can't boot from a TimeMachine backup, if you have a hard drive failure, you're out of luck until you get that drive replaced. If you have an external clone, you can simply boot up from that which will allow you to continue working until you can get your internal drive replaced. As has been mentioned, both have their benefits and using both to compliment each other is your best option. Since TimeMachine is part of OS X and both SuperDuper and CarbonCopyCloner are free for full clones (actually, CCC is completely free for all functionality now), there's really no reason not to use both.

Super Duper w/Intel & G5/Time Machine

I have an Intel MacBook, a G5 iMac and an external fire wire. I would like to format the fire wire in APM? or GUID?, partition it into four blocks and then use Super Duper to clone each into its partition, finally run Time Machine into the third and fourth partition. Question is will Time Machine and Super Duper each work properly on an Intel and Power PC Mac when saved onto a disk that is either APM or GUID?
Thanks
Ivan

You can format the external drive as APM with the 4 partions. An Intel mac will boot from a SuperDuper clone on APM. The G5 will boot from APM, and Time Machine can also use APM.
The confusion about an Intel mac and an APM partition is that you can not install an OS (or run updates I believe) to the partition, but SuperDuper doesn't care and will clone your GUID drive to the APM partition. I found out that this worked by accident when I first upgraded to Leopard. I cloned my drive to a new external drive and it worked fine. Later I tried to reuse the drive to install a second copy of Leopard and it refused with the non-GUID error.
You might as well try it first by using SuperDuper to create the bootable clone on the APM partition and then booting from it. That will prove that the rest of your plan should work.
I don't think you have any option to be able to use both APM and GUID on the same drive and the G5 can't boot at all from GUID.
SuperDuper 2.5 came out a couple of days ago. I've already used it to advantage:) It's nice having such a great program back online...

Backing up files to external HDD, time machine? Super Duper?

Well I finally did it. I gave myself an early Xmas gift... a 1TB WD drive. I currently have 4 internal drives in my G4 tower with OSX Tiger on one drive and OSX Leopard on another. I have my itunes, iphoto, imovie and idvd libraries running from the other two internal drives. Dont remember if I asked this before but here goes. What's the best way to back up files without interrupting the library directory system? In other words, itunes and iphoto will be asking me where are my **** files? I was also debating on creating a disk image of the OSX Tiger drive and erase it for other use? I can always mount it later if I need it, correct?
Your input is appreaciated. Thanks

how many drives do you have running?
Currently have 6 machines and a total of 21 drives running.
In two machines I use TM and SD! backup, in the other four I use SD! only.
I've never fallen back/used a TM backup, but constantly use SD! backups.
The performance benefit of running a SD! clone is one main reason.
When would it be appropriate to run SP or CCC?
I run the initial SD! clone upon setup of a drive.
After that, I base frequency on the usage.
With full time machines, Smart Update of SD! runs every night.
In other machines, I run Smart Update once a week.
Having so many drives, it can get hard to cover backups drive for drive, but 1:1 is a better backup scheme.
With the 1TB, 2 TB and 3 TB drives getting so reasonable, a single drive can be partitioned to serve as backup for two, three or even four volumes.
Of course, it is better to limit the number of volumes on a single drive in case of catastrophy....

HT1379 My computer I-mac is running super slow. If I zap the PRAM it goes back to running well , briefly... a few hours, then back to super slow. What is the resolution for this problem? I have a Time machine that does back up well.

My computer is running super slow. I can correct the problem briefly by zapping the PRAM but is resumes as a problem after a few hours. I have good time machine (capusle) backup daily. I have done a disk verify and there doesn't appear to be anything wrong there.
Help, this is wasting a lot of time to do simple functions.

Hard to say what's going wrong without more information. Try the troubleshooting steps in my Mac Performance Guide. Post back if you need help with any of that or questions about the results.

Mountain Lion Time Machine backup to USB drive super slow

I recently upgraded the MacBook Air to Mountain Lion. The time machine backup is SUPER SLOW even when doing it on a USB 3.0 Drive. It currently showing 2 days for 100GB backup. I was able to copy the same 100 GB of files on to the same hard disk in less than 1 hr. This is so slow that i might be better off managing back ups manually or just writing a small script to do it. But before I do so wanted to check if anybody else has the same issues.
Regards
Uddhav
Update:
Turning off the spotlight on the external hard disk helped improve the speed dramatically. Brought it down from 1 GB in 1 hr to almost 1 GB / minute.
System Preferences --> Spotlight
Add the Drive to the exceptions list. It will say this is a time machine disk so except the time machine folder everything else will be added to the exception list. Say Yes and thats it !!!
Now says 19hrs still a lot according to me but much better than 2 days.
Any body has any additional tips /tricks please share !!
Regards
Uddhav

uddhav wrote:
Turning off the spotlight on the external hard disk helped improve the speed dramatically.
That may indicate a damaged index. Keep an eye on subsequent backups -- if they take a long time, and/or show "indexing backup" on the Time Machine preferences panel for very long, you may need to delete it, so OSX can recreate it. See the pink box in #D2 of Time Machine - Troubleshooting for instructions.
It will say this is a time machine disk so except the time machine folder everything else will be added to the exception list.
Is there anything else on the drive (in the same partition)? If so, that's usually not a good idea. See Time Machine - Frequently Asked Question #3 for an explanation.
Now says 19hrs still a lot according to me but much better than 2 days.
Yes, that's quite slow, especially if your Mac supports USB 3.
If it doesn't, it should be running at USB 2 speeds, which for a full backup should be, very roughly, 40-50 GB/hour.
See the rest of #D2 in the Troubleshooting link for other causes of slow backups.

HELP: Time Machine super weirdness, ext drives just disappear...

Hi all and Merry Christmas!
I bought 2 brand new Maxtor One Touch 1TB Ext FW800 drives, intended one for Time Machine and the other possibly for backing up purposes or SuperDuper (http://www.maxtorsolutions.com/en/catalog/OTIII_Turbo/index.html)
*Both drives have the same result:*
I mounted the drive each for the first time, and use Disk Utility to erase (format) again, simple format, no raid no nothing.
Then I set up Time Machine to do the 1st initial back up, but after a while, into a few GB of data back up, the ext drive *just suddenly unmount and disappear from the Desktop*. Twice for both drives. Now when I *turn the drives back on, I can't get them to mount... HELP!!*
Did I miss something, did something wrong or I should have format it as a RAID drive as it should be?
*But right now I need to "rescue" the drives back, how do I do it?* OR that the drives are DOA and somehow faulty?
Thanks again and Happy Holidays, hope someone is reading this... cheers!

Hi. I did a Erase like any other internal or external Mac disk - Journaled, not FAT, etc. One simple partition, no GUID etc.
Anyway, I am very happy to report that the Time Machine drive is now working fine, here was what I did before that failed:
1. The 2 1TB Ext FW800 drives were connected to a Belkin FW800 Hub, the hub is then connected to the sole FW800 port behind the iMac
2. I gave the designated Time Machine drive a custom icon, using Get Info/Copy & Paste the icon graphic.
So I remove the hub, connected the 1st drive to the FW800 port, and the 2nd one daisy chain to the first drive. This actually remounted the 2 drives and I re-format and re-erase them again.
This time my designated Time Machine drive I left it alone as it is, no icon pasting whatsoever.
Did the initial backup, the FW disk icon immediately changed to the Green Time Machine icon drive, the process took quite a while but has completed and successful.
So I am not sure whether it's the combination of the above points 1 & 2, maybe the hub was faulty (it's new), or because I change the icon. Anyway, something learnt.
Cheers

Super Duper BU vs Time Machine

Similar Messages

Maybe you are looking for