What is this Time Machine?

Hi All,
I currently have a 24" iMac C2D and have a LaCie FW HD partitioned to backup my entire volume and my Home folder. I use Silverkeeper and the Backup volume is completely bootable. I thinking of upgrading to Leopard and wonder if Time Machine will take the place of this backup routine, or do I still need to do this. I have had my hard drive crap out and wonder if you'll be able to recover everything if your HD goes with Leopard.
Thanks
Nano

You will still need Silverkeeper to make bootable backups (once it is verified for Leopard.) Time Machine creates multiple backups of your system (changed files) every hour for 24 hours, every day, etc. Time Machine backups are restorable by time and can keep multiple copies of the same changed files.
Regards,

Similar Messages

What does this Time Machine error message mean?

Error: Flushing index to disk returned an error: -1
Here is the full log:
Thu Jul 14 14:47:42 Starting standard backup
Thu Jul 14 14:47:43 Backing up to: /Volumes/F3/Backups.backupdb
Thu Jul 14 14:48:04 No pre-backup thinning needed: 471.8 MB requested (including
padding), 1.25 TB available
Thu Jul 14 14:51:46 Error: Flushing index to disk returned an error: -1
Thu Jul 14 14:51:46 Copied 7900 files (346.9 MB) from volume Frie.
Thu Jul 14 14:51:56 No pre-backup thinning needed: 100.0 MB requested (including
padding), 1.24 TB available
Thu Jul 14 14:52:06 Waiting for index to be ready (-1 < 0)
Thu Jul 14 14:52:21 Waiting for index to be ready (-1 < 0)
Thu Jul 14 14:52:32 Bulk setting Spotlight attributes failed.
Thu Jul 14 14:52:32 Copied 211 files (1.7 MB) from volume Frie.
Thu Jul 14 14:52:33 Starting post-backup thinning
Thu Jul 14 14:52:33 No post-back up thinning needed: no expired backups exist
Thu Jul 14 14:52:33 Backup completed successfully.
I am running 10.5.8 and backing up from the startup disk to a separate internal disk.
Any help would be much appreciated.
Thanks,
Mike

mkb789 wrote:
Error: Flushing index to disk returned an error: -1
That's a problem writing to the Time Machine drive.
As BDAqua says, verify your internal HD and repair the external, per #A5 in Time Machine - Troubleshooting.
If that doesn't help, try the things in the green box of #D2 there.

What do I do when I get this Time Machine message? The backup disk image "/Volumes/Mark McConnell's Time Capsu/Mark's MacBook Pro.sparsebundle" is already in use.

What do I do when I get this Time Machine error message?
"The backup disk image “/Volumes/Mark McConnell's Time Capsu/Mark’s MacBook Pro.sparsebundle” is already in use."

Unplug your Time Capsule from power. Wait 10 seconds and then power it on again. When the light goes green try backing up again.

Can anyone tell me what this Time Machine error means? The network backup disk does not support the required AFP features?

Can anyone tell me what this Time Machine error means? The network backup disk does not support the required AFP features?

AFP - Apple Filing Protocol
The Network Attached Storage (NAS) that you are pointing Time Machine at does not have the features needed by Time Machine in order to do its Thing. Time Machine needs some specific features that are not typically available on generic networked storage devices.
There are manufactures that support the Mac OS X HFS+ file system formats and implement all the needed AFP protocol packets necessary so that they can be used with Time Machine, but apparently yours does not.
If you are not using a networked mounted volume for Time Machine, then more information will be needed about your Time Machine setup.

What exactly is Time Machine?

I am fairly new to Apple sytems and software having progressed from PC to iPad and now to Pro Mac Laptop.. A lot of times in passing Apple, whether at their store or in emails talk about things like Time Machine and Thunder something or other and lot of other lingo and I really do not know what they are talking about. The literature available on websites does not go into sufficient detail to tell me exactly what these things are so I can evaualte whether I need them or not. Can anyone direct me to where I can learn some of this stuff?

This Time Machine Tutorial should answer you questions. If you are serious about backing up Time Machine is good place to start. However in backup it's wise to have redundancy if you are serious about backing up. A popular method of redundant backup in addition to Time Machine is creating a Bootable Clone on another EHD. Both Carbon Copy Cloner & SuperDuper! will backup by creating Bootable Clones. Many people on these forums (including myself) use both TM and a Bootable Clone, I happen to use SD however many are very happy with CCC. Basic rules of thumb are
NEVER user the same EHD for TM and a Bootable Clone, the reason being is if that drive dies (and they all do eventually) you have lost ALL of your backup!
NEVER use the same EHD for storage that you use for backup. This is for the same reason as #1. In other words never store data (music, photos, important documents) on a EHD that you use for backup.

The window that opens when I click on the Time Machine icon is Finder (devices) and when I close this Time Machine also closes.

The window that opens when I click on the Time Machine icon is Finder (devices) and when I close this Time Machine also closes.

You will need to be much more specific about what you problem is. That is how TM works. That is how you find things to restore from TM, by using a Finder window so that you can browse through the Mac's hierarchy of folders and files.
Why are you double posting this?

The error that I am getting is this "Time Machine can't use the disk image because it can't be written to." Any ideas on the fix for this?

The error that I am getting is this "Time Machine can't use the disk image because it can't be written to." Any ideas on the fix for this? When I go to the Time Capsule my Macbook Pro shows that it is locked, I think I did something wrong, but can't figure how to unlock it to see if that fixes it.

As far as we know, Time Machine cannot write to a disk image. It needs to write directly to the Time Capsule disk.

What happens when Time Machine starts to fill up a drive?

Using Time Machine on a partitioned External HD has been an absolute snap! I love the app. My main disappointment with it is that it has no literature on HOW it works, and no real ways for me to set different controls for it other than on and off.
My question is that what happens when a drive starts to get full? I have about 30 gigs left on the partition, and I am wondering what Time Machine is going to do. Does it just delete the oldest material, or does it simply fill up and tell me to look at everything on there and decide to clear it all off. I hate that I don't know what will happen.
-Jon

From what I've read (I've not gotten a drive full so I can't speak from experience), when the TM drive gets full, it will notify you that it's going to start deleting the oldest backups to make space for the new ones. This general behavior is mentioned in the Mac Help for Time Machine, though it makes no mention about notifying you before it deletes the old backups, so I'm not sure about that part.

Hat is this "Time Machine couldn't complete the backup to "***Network Name***' The Backup disk image "/Volumes/Data/MacBook Pro.sparsebundle" is already in use"

"Time Machine couldn’t complete the backup to “***Network Name***’ The Backup disk image “/Volumes/Data/MacBook Pro.sparsebundle” is already in use"
What does this mean and how do you fix it?

I got that the file is in use, what is the trick to release the file. This has something to do with X.8, never had this problem befor I uploaded .8

What is my Time Machine Backing up

I've gotten quite interested in clicking on my Time Machine menu icon when it starts running recently. I've noticed what I think are large amounts of data being backed up, particularly considering I've just started using the machine a few minutes previously. For example, I've been on my computer for about 30 minutes now. I was writing a 1 page Word document for a class I'm taking, and then I started surfing. My Time Machine says it is backing up 51MB of data. Where did this come from? I've seen times when it has been several hundred MB of data, with very little actual files created on the system being backed up (i.e. I'm not working with my iPhoto library or editing a movie, etc).
I'm confused as to what is actually being backed up, and would love to hear some thoughts.
Thanks.
Nabby

Nabby wrote:
My Time Machine says it is backing up 51MB of data. Where did this come from?
Welcome to Apple's discussion groups.
Read item 7 of this post:
http://discussions.apple.com/thread.jspa?threadID=1964018

What drives are time machine compatible?

I'm trying to purchase a NAS or NAS Enclosure and I'm finding that some devices are compatible with time machine, while others are not. Only a couple of the manufacturers do a good job of highlighting if they are compatible or not and I'm driving myself nuts reading up on each drive via 3rd party sites to see if anyone has commented that this drive or that drive works with TM. So, does anyone have a tip for me on how to spot a time machine compatible NAS (or NAS enclosure)? Perhaps a specific tech spec that would indicate TM compatibility? [I'm looking for a 2TB drive or drive enclosure (single drive or dual 1TB with RAID/1) that is TM compatible and allows Web access to files.]

My experience with TimeMachine and a tethered USB or FireWire drive has been quite good - with TimeCapsule and other networked solutions not so good. When I first read about TimeMachine and TimeCapsule my immediate thoughts ran to network reliability and how that would affect the reliability and speed of both the backup and restore process. After more than 6 months of testing both TimeCapsule and other network attached drives with TimeMachine I gave up in disgust. After a few days, weeks, and in one case several months I received a backup failed error and nothing I tried would get TimeMachine backing up again. Oh, there were fixes that worked some times but never all the time and eventually my only recourse was to erase the backup and start over. Not what I had in mind for TimeMachine.
The other thought that crossed my mind early on was about how one could test the validity of the backup. Basically it is not possible you simply trust that it is. You check to see if there was an error during the backup and if there was not you hope the backup is actually good. On more than one occasion I've attempted to restore a file (or more) and experienced a failure. This has happened more often with a TC or network TM than one tethered. In fact, I've only had it happen once with a tethered drive. A backup that won't restore is as bad as no backup at all - worse since it provided a false sense of security.
The final problem is speed. TC is not fast at backing up or restoring. Of course the hourly backups aren't generally a big deal but that first one, or a backup after installing a new program or an OS update can be a biggie. Be ready for an overnight backup. In short, I strongly urge against TC or NAS drives with TimeMachine and so far Snow Leopard has not changed my mind.

Can someone interpret this Time Machine panic?

I've gotten it four times since Security Update 2010-001, never before that. I back up to a networked volume, if that makes any difference. It hasn't happened since I turned of automatic Time Machine backups; now I quit all apps and start it manually. Thanks!
Interval Since Last Panic Report: 2244443 sec
Panics Since Last Report: 1
Anonymous UUID: DD96E454-1668-4026-A1B1-BD80BC6AB5BC
Sat Jan 30 18:33:38 2010
panic(cpu 0 caller 0x226820): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/SourceCache/xnu/xnu-1486.2.11/osfmk/kern/sched_prim.c:1471
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x34eb2c98 : 0x21b2bd (0x5cf868 0x34eb2ccc 0x223719 0x0)
0x34eb2ce8 : 0x226820 (0x5876cc 0xffffffff 0x587664 0x226412)
0x34eb2d68 : 0x226f27 (0x88a301c 0x88a301c 0x34eb2dc8 0x232613)
0x34eb2dd8 : 0x226fb5 (0x0 0x0 0x0 0x2760)
0x34eb2df8 : 0x2217b0 (0x0 0x0 0x0 0x0)
0x34eb2e18 : 0x487be3 (0x5ae91f0 0x0 0x80f2540 0x0)
0x34eb2e88 : 0x4882d6 (0x0 0x0 0x0 0x5ae91f0)
0x34eb2ec8 : 0x4b22a7 (0x80f2540 0x5ae91f0 0x18 0x5c8bfd)
0x34eb2f18 : 0x4af634 (0x80f2540 0x1 0x3215ff00 0x0)
0x34eb2fd8 : 0x361e4ab3 (0x80f249c 0x0 0x560abc0 0x0)
0x34eb3058 : 0x361e9711 (0x4280bb0 0x0 0xab6022c 0x2)
0x34eb35f8 : 0x361ebd31 (0x0 0x32023e00 0x4fc5d20 0x490014)
0x34eb3618 : 0x4afc47 (0x651a4c8 0x0 0x32161900 0x0)
0x34eb36d8 : 0x4c3cd2 (0x651a4c8 0x0 0x0 0x32161900)
0x34eb3778 : 0x472101c3 (0x651a4c8 0x34eb3804 0x32161900 0x0)
0x34eb3848 : 0x47210816 (0x24055004 0x420443c 0x2409c674 0x14)
0x34eb3898 : 0x47211027 (0x24055004 0x420443c 0x2409c674 0x14)
0x34eb39a8 : 0x47209162 (0x24055004 0x420443c 0xb 0x44e000)
0x34eb3a38 : 0x4720b1bf (0x420443c 0x4c74a00 0x4fc5d20 0xab000)
0x34eb3ac8 : 0x2f4aef (0x34eb3ae8 0x0 0x2 0x2dc6b4)
Backtrace continues...
Kernel Extensions in backtrace (with dependencies):
com.apple.filesystems.afpfs(9.6)@0x471ff000->0x47255fff
com.apple.nke.asp_tcp(5.0)@0x361e3000->0x361f0fff
BSD process name corresponding to current thread: diskimages-helpe
Mac OS version:
10C540
Kernel version:
Darwin Kernel Version 10.2.0: Tue Nov 3 10:37:10 PST 2009; root:xnu-1486.2.11~1/RELEASE_I386
System model name: iMac7,1 (Mac-F4238CC8)
System uptime in nanoseconds: 385303584315937
unloaded kexts:
com.apple.driver.AppleFileSystemDriver 2.0 (addr 0x34b51000, size 0x12288) - last unloaded 200980298142
loaded kexts:
com.cisco.nke.ipsec 2.0.1
se.coolbook.driver2 2.0.3
at.obdev.nke.LittleSnitch 2.2.05
com.apple.filesystems.afpfs 9.6 - last loaded 109449881536
com.apple.nke.asp_tcp 5.0
com.apple.driver.AppleBluetoothMultitouch 30.9
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleHWSensor 1.9.2d0
com.apple.driver.AppleUpstreamUserClient 3.1.0
com.apple.DontSteal_Mac_OSX 7.0.0
com.apple.kext.ATIFramebuffer 6.0.6
com.apple.driver.AudioIPCDriver 1.1.2
com.apple.driver.AppleHDA 1.7.9a4
com.apple.ATIRadeonX2000 6.0.6
com.apple.iokit.AppleYukon2 3.1.14b1
com.apple.driver.AirPortBrcm43xx 421.91.26
com.apple.driver.AppleIntelMeromProfile 19
com.apple.driver.AppleLPC 1.4.9
com.apple.driver.ACPISMCPlatformPlugin 4.0.1d0
com.apple.driver.AppleBacklight 170.0.14
com.apple.driver.AppleIRController 251.1.4
com.apple.iokit.SCSITaskUserClient 2.6.0
com.apple.BootCache 31
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.driver.AppleUSBHub 3.8.4
com.apple.iokit.IOAHCIBlockStorage 1.6.0
com.apple.driver.AppleEFINVRAM 1.3.0
com.apple.driver.AppleAHCIPort 2.0.1
com.apple.driver.AppleIntelPIIXATA 2.5.0
com.apple.driver.AppleUSBEHCI 3.7.5
com.apple.driver.AppleUSBUHCI 3.7.5
com.apple.driver.AppleFWOHCI 4.4.0
com.apple.driver.AppleRTC 1.3
com.apple.driver.AppleHPET 1.4
com.apple.driver.AppleACPIButtons 1.3
com.apple.driver.AppleSMBIOS 1.4
com.apple.driver.AppleACPIEC 1.3
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 96.0.0
com.apple.security.sandbox 0
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.11
com.apple.driver.AppleIntelCPUPowerManagement 96.0.0
com.apple.driver.IOBluetoothHIDDriver 2.2.4f3
com.apple.driver.AppleMultitouchDriver 204.9
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 73.0
com.apple.iokit.IOBluetoothSerialManager 2.2.4f3
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.driver.DspFuncLib 1.7.9a4
com.apple.iokit.IOAudioFamily 1.7.2fc1
com.apple.kext.OSvKernDSPLib 1.3
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.IO80211Family 310.6
com.apple.iokit.IONetworkingFamily 1.9
com.apple.iokit.AppleProfileFamily 41
com.apple.driver.AppleHDAController 1.7.9a4
com.apple.iokit.IOHDAFamily 1.7.9a4
com.apple.driver.AppleSMC 3.0.1d2
com.apple.driver.IOPlatformPluginFamily 4.0.1d0
com.apple.iokit.IONDRVSupport 2.0
com.apple.kext.ATI2400Controller 6.0.6
com.apple.kext.ATISupport 6.0.6
com.apple.iokit.IOGraphicsFamily 2.0
com.apple.driver.CSRUSBBluetoothHCIController 2.2.4f3
com.apple.driver.AppleUSBBluetoothHCIController 2.2.4f3
com.apple.iokit.IOBluetoothFamily 2.2.4f3
com.apple.driver.AppleUSBHIDKeyboard 1.2.0a3
com.apple.driver.AppleHIDKeyboard 1.2.0a3
com.apple.iokit.IOUSBHIDDriver 3.8.4
com.apple.driver.AppleUSBMergeNub 3.8.5
com.apple.driver.AppleUSBComposite 3.7.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.0
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOATAPIProtocolTransport 2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.0
com.apple.iokit.IOUSBUserClient 3.8.5
com.apple.iokit.IOAHCIFamily 2.0.2
com.apple.iokit.IOATAFamily 2.5.0
com.apple.iokit.IOUSBFamily 3.8.5
com.apple.iokit.IOFireWireFamily 4.1.7
com.apple.driver.AppleEFIRuntime 1.3.0
com.apple.iokit.IOHIDFamily 1.6.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.TMSafetyNet 6
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 281
com.apple.iokit.IOStorageFamily 1.6
com.apple.driver.AppleACPIPlatform 1.3
com.apple.iokit.IOPCIFamily 2.6
com.apple.iokit.IOACPIFamily 1.3.0
System Profile:
Model: iMac7,1, BootROM IM71.007A.B03, 2 processors, Intel Core 2 Duo, 2 GHz, 2 GB, SMC 1.20f4
Graphics: ATI Radeon HD 2400 XT, ATI,RadeonHD2400, PCIe, 128 MB
Memory Module: global_name
AirPort: spairportwireless_card_type_airportextreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.91.26)
Bluetooth: Version 2.2.4f3, 2 service, 1 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: Hitachi HDT725025VLA380, 232.89 GB
Parallel ATA Device: MATSHITADVD-R UJ-85J
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8502, 0xfd400000
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfa200000
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0220, 0xfa220000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8206, 0x1a100000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0x5d100000

Ron Voss wrote:
panic(cpu 0 caller 0x226820): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/SourceCache/xnu/xnu-1486.2.11/osfmk/kern/sched_prim.c:1471
I can tell you at a very low level why it's complaining, but have no clue about why that situation is arising or how to prevent it. A "mutex" is a software "mutual exclusion" facility that's designed to control serial use of a system resource that can't be shared. A mutex is either locked or unlocked. A process that wants to use the resource locks its mutex (or waits until it's available, then locks it), uses the resource, then unlocks the mutex. In your case a process tried to unlock a mutex that wasn't locked.
BSD process name corresponding to current thread: diskimages-helpe
The message above may be a big clue about what process misbehaved (presumably "diskimages-helper").
I'd submit your panic log as a bug report to Apple. Try this URL to do that:
https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn
I'd guess that the same Apple ID you use to log into these discussion groups will allow you to log into that page.

What happens to Time Machine if my backup drive isn't connected?

I've got Time Machine set up to back up a MacOS Leopard Macbook to an external drive. Because of the way this computer is used, it's usually not plugged into the backup drive.
What does Time Machine do in this situation? Does it keep track of all the changes since it last saw the backup drive, or does it only keep one increment between the last backup and the current one? Does it still automatically back up, or do I have to prompt it?
I understand that Lion has a feature that keeps local backups until it sees the backup drive again, but it's not clear to me (because Apple updates the Time Machine support documents to reflect only the latest version of the OS...) whether something like this happens in Leopard.

Sockatume wrote:
***I've got Time Machine set up to back up a MacOS Leopard Macbook to an external drive. Because of the way this computer is used, it's usually not plugged into the backup drive.***
Time machine will recommence back ups from the last point backed up.
***What does Time Machine do in this situation? Does it keep track of all the changes since it last saw the backup drive.
Apple updates the Time Machine support documents to reflect only the latest version of the OS.***
It should scan and pick up alterations to previous back ups as a matter of course.
For all matters dealing with Time machine Google 'Pondini' and a variety of options about it will appear.
For trouble shooting ...Time machine. http://pondini.org/TM/Troubleshooting.html

Beside myself on this Time Machine

Ok, So I have tried resetting my Time Capsule several times. I finally downloaded the Time Machine Buddy. Here is what it says:
Starting standard backup
Mounted network destination using URL: afp://Time-Capsule.local/BigBlueSea%20network
Backup destination mounted at path: /Volumes/BigBlueSea network
Failed to mount disk image /Volumes/BigBlueSea network/ComputerName.sparsebundle (DIHLDiskImageAttach returned: 60)
Waiting 60 seconds and trying again.
Failed to eject volume /Volumes/BigBlueSea network (FSVolumeRefNum: -116; status: -47; dissenting pid: 0)
Backup destination alias resolved to path: /Volumes/BigBlueSea network
_CSBackupVolMgrCopyVolumeAtPath failed to find volume at path /Volumes/BigBlueSea network
Backup failed with error: 19
Failed to eject volume / (FSVolumeRefNum: -100; status: -47; dissenting pid: -1
I would really appreciate any help someone can give me. I am a newbie at this kind of thing and it is taxing my computer knowledge. Thanks in advance.

Does your computer have a name (in System Preferences > Sharing)?
If not, give it one. Keep it short, and use only numbers and letters (no punctuation or spaces).
While you're at it, rename your Time Capsule using the same rules.

What exactly does Time Machine back up?

May seem a basic question. I've always assumed my home folder which, at the moment, weighs 120 Gb, give or take a kb. So why does TM report that it cannot complete backup to a 180 Gb external drive as it now needs 220 Gb, despite having done so for a number of years without a hitch?

Time Machine backs up your entire system (except for some things like system work files, most caches, trash, etc.), unless you specifically exclude things.
It sounds like your TM drive is too small -- it usually needs 2-3 times the space of the data it's backing up, to keep a reasonable "depth" of old backups.
It may also be trying to do a new, full backup. Some possible reasons for that are listed in #D3 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
If in doubt, see #A1 there. Download the TM Buddy widget and copy and post the messages here. That may clarify the situation.

What is this Time Machine?

Similar Messages

Maybe you are looking for