Time Machine snapshots, but no hourly backups
System: MBP (late 2011), 2.8 GHz i7, 16 GB RAM, Mavericks 10.9.5, Samsung SSD and Samsung HDD in lieu of optical drive. Running Bootcamp too.
My technical acumen: ample and extensive...but I am stumped.
Problem: in September 2014, I noticed that my hourly TM backups were not happening regularly. Snapshots were occurring, but no "real" backup. I scoured the Console messages, and there is NO error...there is no NOTHING regarding backups unless I instigate a manual one. In that instance, the backup completes normally, and I am left with a normal and functional backup....as best as I can tell. Otherwise? Nothing. This was not concomitant with any major hardware upgrade(s); the second HDD was added since things stopped working and the RAM was added before. However, I did have 1 bad RAM module (when I went to 16 GB) that needed to be replaced, but as far as I can tell this is only coincidental.
Here's what I have tried:
1) Wiping and re-formatting the backup drive (WD My Book 2 TB, firewire, indended for Mac)
2) Replacing backup drive (WD My Book 3 TB, USB, intended for Mac)
3) Rest PRAM, SMC, repaired permissions
4) Ran Onyx cleaning and maintenance scripts, rebuild every cache I can think of, removed old and obsolete plists from Library (for deleted software)
5) Repaired disk from recovery partition (there were no issues)
6) EVERY suggestion I could find on pondini.org, including "full reset" of TM
7) EVERY suggestion I could find here on Apple Discussions
Nothing worked. At all. The problem is the total lack of console activity to indicate an issue...I can't fix what I can't see! Anyone know what I could be missing? just for verification, below are the console messages re: manual backups, backup drive and snapshots:
9/30/14 7:10:43.291 AM com.apple.backupd[289]: Starting manual backup
9/30/14 7:10:43.723 AM com.apple.backupd[289]: Backing up to /dev/disk2s2: /Volumes/Disaster/Backups.backupdb
9/30/14 7:10:51.261 AM com.apple.backupd[289]: Will copy (145.9 MB) from Macintosh HD
9/30/14 7:10:51.264 AM com.apple.backupd[289]: Will copy (22 KB) from Secondary HD
9/30/14 7:10:51.265 AM com.apple.backupd[289]: Found 601 files (145.9 MB) needing backup
9/30/14 7:10:51.268 AM com.apple.backupd[289]: 4.37 GB required (including padding), 1.69 TB available
9/30/14 7:11:33.675 AM com.apple.backupd[289]: Copied 731 items (145.9 MB) from volume Macintosh HD. Linked 5147.
9/30/14 7:11:36.918 AM com.apple.backupd[289]: Copied 15 items (801 KB) from volume Secondary HD. Linked 37.
9/30/14 7:11:37.584 AM com.apple.backupd[289]: Will copy (24.4 MB) from Macintosh HD
9/30/14 7:11:37.585 AM com.apple.backupd[289]: Not using file event preflight for Secondary HD
9/30/14 7:11:37.587 AM com.apple.backupd[289]: Found 30 files (24.4 MB) needing backup
9/30/14 7:11:37.588 AM com.apple.backupd[289]: 4.23 GB required (including padding), 1.69 TB available
9/30/14 7:11:39.927 AM com.apple.backupd[289]: Copied 33 items (24.4 MB) from volume Macintosh HD. Linked 700.
9/30/14 7:11:40.449 AM com.apple.backupd[289]: Copied 1 items (Zero KB) from volume Secondary HD. Linked 4.
9/30/14 7:11:41.192 AM com.apple.backupd[289]: Created new backup: 2014-09-30-071141
9/30/14 7:11:41.827 AM com.apple.backupd[289]: Starting post-backup thinning
9/30/14 7:11:41.829 AM com.apple.backupd[289]: No post-backup thinning needed: no expired backups exist
9/30/14 7:11:41.834 AM com.apple.backupd[289]: Backup completed successfully.
9/30/14 7:09:28.000 AM kernel[0]: nspace-handler-set-snapshot-time: 1412075370
9/30/14 7:09:28.546 AM com.apple.mtmd[62]: Set snapshot time: 2014-09-30 07:09:30 -0400 (current time: 2014-09-30 07:09:28 -0400)
9/30/14 7:09:31.860 AM mds[63]: (Normal) Volume: volume:0x7ff521108a00 ********** Created snapshot backup index
9/30/14 7:09:27.000 AM kernel[0]: hfs: mounted Disaster on device disk2s2
9/30/14 7:09:28.000 AM kernel[0]: hfs: unmount initiated on Disaster on device disk2s2
9/30/14 7:09:28.000 AM kernel[0]: nspace-handler-set-snapshot-time: 1412075370
SO: Am I missing something? I've tried everything short of wiping and restoring my primary SSD because...well, that's a pain and also because I'm afraid that the restoration process will simply restore whatever issue is causing this, leaving me with nothing gained. Thoughts?
When you replaced your MBP's original HD with the Samsung SSD, how did you originally populate its contents? In other words, did you begin with a new OS X installation, followed by using Setup Assistant and migrating your information from an existing TM backup, or...?
Edit: A persistent bug with this site prevented replies from appearing until I posted one. Since you resolved the problem by reinstalling OS X I'll only suggest you don't use OnyX or any other utility to "clean" anything or perform any other action for that matter. Although I understand you only used OnyX in an effort to address an existing problem, such utilities are only likely to add to or obscure the underlying cause.
Similar Messages
-
Time Machine no longer does hourly backups
Time machine has quit doing its hourly backups. I have two disks defined to Time Machine. One is Firewire and the other eSATA. So neither drive is on the network. This has been working for a very long time this way. The other day one of the drives encountered an error that made it unreadable. I verified that I still had a good set of backups on the other drive, and then removed the bad drive from Time Machine and reformatted it. I then added the now reformatted drive back to Time Machine.
My macbookpro is plugged into AC. There are no error messages in the console log for backupd. I have seen this happen off and on but it always seems to start up again after awhile. This time seems diffferent. I have done two restarts. I tried deleting com.apple.TimeMachine.plist from /Library/Preferences. I have removed both drives from Time Machine and added them back. I can manually do backups and the console log shows them to be successful. Time Machine properly flips between the two drives everytime I do a manual backup.You may find a solution at this website: Time Machine - Troubleshooting
OT -
Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." I've tried various suggestions I've seen on the forum but nothing has worked. TIme Machine worked fine for the last two years and just suddenly started having this problem every time. The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned. I have more than enough available backup storage space for it. Before failing, Time Machine has backed up no more than 12GB or so of the backup. It fails during different files each time.
I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem. It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine.
I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
I have system logs that I can share if helpful. The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
I always get this message near the beginning of the backup:
Event store UUIDs don't match for volume: Macintosh HD
I've gotten this messsage a number of times:
Bulk setting Spotlight attributes failed.
One Day
Stopping backupd to allow ejection of backup destination disk!
Another day
1/7/12 10:44:20 AM
mDNSResponder[18]
PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
1/7/12 10:46:37 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
1/7/12 10:46:37 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
Another Day
1/6/12 8:03:22 AM
Google Chrome[164]
Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
1/6/12 8:04:02 AM
com.apple.backupd[193]
Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
1/6/12 8:06:58 AM
/System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
No valid tickets, timing out
1/6/12 8:29:44 AM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
1/6/12 8:59:22 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
Another day
1/5/12 3:48:55 PM
mdworker[2128]
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
1/5/12 4:24:54 PM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
1/5/12 4:29:58 PM
com.apple.backupd[2074]
Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
1/5/12 4:39:00 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380bokon0n wrote:
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
Those indicate that your NAS is not fully compatible with Snow Leopard.
1/11/12 8:53:35 AM
kernel
jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
1/11/12 8:53:49 AM
kernel
jnl: disk2s2: journal replay done.
1/11/12 8:53:49 AM
fseventsd[41]
event logs in /Volumes/Time Machine/.fseventsd out of sync with volume. destroying old logs. (253512 14 253512)
1/11/12 8:53:50 AM
kernel
hfs: Removed 1 orphaned / unlinked files and 0 directories
That looks like a problem was found with the file system (data) on the TM disk. I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive. Likely a result of the incompatibility mentioned above.
1/11/12 9:47:40 AM
com.apple.backupd[1169]
Bulk setting Spotlight attributes failed.
That's a problem writing to the NAS drive.
But the backup continued after all this.
1/11/12 1:25:07 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
Something caused a disconnect. Can't tell from the log what it was.
I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
To be incompatible with Snow Leopard, this NAS must be at least a couple of years old. It may be beginning to fail.
Contact the maker. See if there's an update to make it compatible with Snow Leopard. If so, that might fix it.
If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light. -
I am trying to update my time machine backup on time capsule, but time machine keeps trying to create an entirely new backup (evidenced by the 200GB backup size). How can I get time machine to modify my old backup rather than create a new one?
It must have found the old backup corrupt.. so you will more than likely have little choice. You can archive off the old backup if it is still useful.
You can also verify it. See A5 http://pondini.org/TM/Troubleshooting.html
He also has some info on this problem. eg C13. -
i baught Seagate Backup plus 2T hard drive to use as my Backup time machine. But its not working. when i connect to time machine its not coping files, it keep saying preparing files. Can someone help me please...
Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test. -
Time Machine operates, but no changes are recorded in the backups.
Time Machine appears to make a backup each hour, and a new backup file is written. No error messages are produced. However, each new backup file appears to be exactly the same as the previous one. Using the "Get Info" function of the Finder, I can see that, indeed, each backup file on the "Time Machine" backup location records the exact same number of files and bytes as the previous backup file. This started ten days ago, during which time I have created, modified, or deleted several hundred files. When I enter the Time Machine application, I find that none of this activity is recorded in the backups. These results are the same, whether the backup is generated manually or under the automatic hourly schedule.
I am using OS 10.7.5 on an iMac 27" purchased in late 2011. Time Machine is set to back up the files from an internal 250 GB SSD and 2 TB HDD. The backup location (target drive) is an external iOmega 2TB HDD with its own power supply, connected by Firewire 800. This drive is about 14 months old.
The iOmega target drive has 624 GB used and 1.38 TB available space. According to the Time Machine Excluded Items dialogue, the extimated size of a full backup is 443 GB.
When I set Time Machine up about 14 months ago, I identified several folders to exclude from backups, and I have not changed that since. I have checked, and it is exactly the same as when I set it up.
Thanks for suggestions/solutions.When you replaced your MBP's original HD with the Samsung SSD, how did you originally populate its contents? In other words, did you begin with a new OS X installation, followed by using Setup Assistant and migrating your information from an existing TM backup, or...?
Edit: A persistent bug with this site prevented replies from appearing until I posted one. Since you resolved the problem by reinstalling OS X I'll only suggest you don't use OnyX or any other utility to "clean" anything or perform any other action for that matter. Although I understand you only used OnyX in an effort to address an existing problem, such utilities are only likely to add to or obscure the underlying cause. -
My Time Capsule/Time Machine has been showing Preparing Backup for past 48 hours continuously!
My Time Capsule reported Full the other day. I now have only 26.8MB of 497.96 GB available. Since then it seems to backing up continuously. The Time machine preferences window shows "Preparing Backup" andnothing else, and it has been doing so for at least past 48 hours. Any ideas as to the problem?
StuartyboyYes, the problem is the drive is full.
If you have other files or TM back from other computers, TM on your computer having issues will not be able to delete enough to get sufficient space to backup.
Read how to clean up and delete parts of backups.. http://pondini.org/TM/FAQ.html
Not a good idea though.
Solution.
1. Buy a new bigger TC.. cheaper (Than the original 500GB at least), faster and now the smallest is 2TB.
2. Plug in a USB drive.. archive the TC.. then erase it and start a fresh set of backups.. April 1st great day to do it.
3. Open up your old TC.. remove the 500GB drive and install a 2TB (if Gen1 a 3TB might even work). Google for how to do a hard disk upgrade.
Problem.. old power supply could die the day after and then the total cost would approach 1. Better to backup, wipe the 500GB and sell it on ebay and buy a new TC with 2 or even 3TB (2TB is better value IMHO).
4. Plug in a USB drive .. formatted to HFS+ and use that as the target.
Very slow. much slower than the same drive plugged into your computer. -
I have a problem with my Time Capsule. The message I get is: Time Machine could not complete the backup. This backup is too large for the backup disk. The backup requires 111.27 GB but only 42.1 GB are available. As a result, my backups are no longer running. My umderstanding was that the Time Capsule would automatically delete old backups to make space. Can anyone help me figure out how to get my backups to run again?
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting. -
Time Machine worked fine w. new HD for 16 backups, but started giving this mssg: [TIME MACHINE COULDN'T COMPLETE THE BACKUP TO "TOSHIBA EXT" ...An error occurred while creating the backup folder]
Make sure your hard drive is formatted properly for the operating system installed. Go to Apple menu -> About This Mac to determine what it is. You posted to the 10.5 forum, but your signature says you have 10.9. Here is the tip on what formatting supports what operating systems:
https://discussions.apple.com/docs/DOC-3003 -
Time machine starts but then freezes during backup
Time machine has been working well using a LaCie external hard drive. However when I start Time Machine, it freezes at 12kB backup. Any ideas?
Hello
I've the same probleme using time machine with my imac under mountain lion : it freezes the computer and i need to reboot it
here the log :
Nov 28 20:01:55 iMac.local com.apple.backupd[3136]: Starting automatic backup
Nov 28 20:01:55 iMac.local com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
Nov 28 20:01:55 iMac.local com.apple.backupd[3136]: Attempting to mount network destination URL: afp://;AUTH=No%20User%20Authent;[email protected]/Data
Nov 28 20:01:55 iMac.local com.apple.backupd[3136]: Mounted network destination at mount point: /Volumes/Data using URL: afp://;AUTH=No%20User%20Authent;[email protected]/Data
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: Mounted devices (
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: CleanMyMacHelperTool started as volume cleaner with cleanTrashes 1 cleanMacOSJunk 1 cleanWinJunk 1
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: Mounted devices (
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: Wont clean mounted devices.
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: CleanMyMacHelperTool exited...
Nov 28 20:01:55 iMac kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
Nov 28 20:01:55 iMac kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3138
Nov 28 20:01:55 iMac kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80706ff008 /Volumes/Data (error = 0, retval = 0)
Nov 28 20:01:55 iMac kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=3140[CleanMyMacHelper] clearing CS_VALID
Nov 28 20:02:05 iMac.local AddressBookSourceSync[3135]: *** -[IADomainCache init]: IA domains cache is out of date.
Nov 28 20:02:05 iMac.local mdworker[3145]: Unable to talk to lsboxd
Nov 28 20:02:05 iMac.local sandboxd[3146] ([3145]): mdworker(3145) deny mach-lookup com.apple.ls.boxd
Nov 28 20:02:06 iMac kernel[0]: Sandbox: sandboxd(3146) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:02:06 iMac.local AddressBookSourceSync[3135]: -[ABPerson valueForProperty:com.apple.Messages.FontSize] - unknown property. This warning will be displayed only once per unknown property, per session.
Nov 28 20:02:06 iMac.local AddressBookSourceSync[3135]: -[ABPerson valueForProperty:com.apple.Messages.FontColor] - unknown property. This warning will be displayed only once per unknown property, per session.
Nov 28 20:02:07 iMac.local AddressBookSourceSync[3135]: -[ABPerson valueForProperty:com.apple.Messages.BalloonColor] - unknown property. This warning will be displayed only once per unknown property, per session.
Nov 28 20:02:07 iMac.local AddressBookSourceSync[3135]: -[ABPerson valueForProperty:com.apple.Messages.FontFamily] - unknown property. This warning will be displayed only once per unknown property, per session.
Nov 28 20:02:11 iMac.local com.apple.SecurityServer[15]: Succeeded authorizing right 'system.hdd.smart' by client '/Library/Application Support/iStat local/iStatLocalDaemon' [62] for authorization created by '/Library/Application Support/iStat local/iStatLocalDaemon' [62] (B,0)
Nov 28 20:02:25 --- last message repeated 1 time ---
Nov 28 20:02:25 iMac kernel[0]: jnl: disk3s2: replay_journal: from: 9666560 to: 21950464 (joffset 0x3a2b000)
Nov 28 20:02:42 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 304 wr: 304 q_size: 1024 flags: 0x1
Nov 28 20:02:50 iMac kernel[0]: jnl: disk3s2: journal replay done.
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Mounted devices (
"/Volumes/Copies de sauvegarde Time machine"
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: DiskUtilities (
"com.apple.finder",
"com.twitter.twitter-mac",
"com.apple.iChat",
"org.mozilla.firefox",
"org.videolan.vlc",
"com.microsoft.Powerpoint",
"com.apple.Notes",
"com.apple.mail"
) diskUtilityIsRunning 0
Nov 28 20:02:50 iMac kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=3168[CleanMyMacHelper] clearing CS_VALID
Nov 28 20:02:50 iMac.local fseventsd[47]: event logs in /Volumes/Copies de sauvegarde Time machine/.fseventsd out of sync with volume. destroying old logs. (3435 26 7388)
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Wont clean /Volumes/Copies de sauvegarde Time machine because it's Time Machine Volume
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: CleanMyMacHelperTool started as volume cleaner with cleanTrashes 1 cleanMacOSJunk 1 cleanWinJunk 1
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Mounted devices (
"/Volumes/Copies de sauvegarde Time machine"
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: DiskUtilities (
"com.apple.finder",
"com.twitter.twitter-mac",
"com.apple.iChat",
"org.mozilla.firefox",
"org.videolan.vlc",
"com.microsoft.Powerpoint",
"com.apple.Notes",
"com.apple.mail"
) diskUtilityIsRunning 0
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Wont clean /Volumes/Copies de sauvegarde Time machine because it's Time Machine Volume
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Wont clean mounted devices.
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: CleanMyMacHelperTool exited...
Nov 28 20:02:51 iMac.local com.apple.backupd[3136]: Disk image /Volumes/Data/iMac.sparsebundle mounted at: /Volumes/Copies de sauvegarde Time machine
Nov 28 20:02:51 iMac.local com.apple.backupd[3136]: Backing up to: /Volumes/Copies de sauvegarde Time machine/Backups.backupdb
Nov 28 20:02:52 iMac.local fseventsd[47]: log dir: /Volumes/Copies de sauvegarde Time machine/.fseventsd getting new uuid: 6E582DCF-14FA-43D8-9F36-353E2E4FCD17
Nov 28 20:02:55 iMac.local WindowServer[91]: Created shield window 0x23c for display 0x04272340
Nov 28 20:02:55 iMac.local WindowServer[91]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
Nov 28 20:02:55 iMac.local WindowServer[91]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
Nov 28 20:03:05 iMac.local Notes[3055]: [IMAP] Expected untagged initial response from pop.laposte.net
Nov 28 20:03:22 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 49 wr: 49 q_size: 1024 flags: 0x1
Nov 28 20:03:22 iMac.local com.apple.PassXPCService[3099]: PAPassValidator: _signatureIsValid failed to load signature file
Nov 28 20:03:35 --- last message repeated 4 times ---
Nov 28 20:03:35 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 818 wr: 818 q_size: 1024 flags: 0x1
Nov 28 20:04:06 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 563 wr: 563 q_size: 1024 flags: 0x1
Nov 28 20:04:07 iMac.local mdworker[3180]: Unable to talk to lsboxd
Nov 28 20:04:07 iMac.local sandboxd[3181] ([3180]): mdworker(3180) deny mach-lookup com.apple.ls.boxd
Nov 28 20:04:07 iMac kernel[0]: Sandbox: sandboxd(3181) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:04:16 iMac.local com.apple.backupd[3136]: Event store UUIDs don't match for volume: Mac OS X Lion
Nov 28 20:04:18 iMac.local com.apple.backupd[3136]: Deep event scan at path:/ reason:must scan subdirs|new event db|
Nov 28 20:05:20 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 308 wr: 308 q_size: 1024 flags: 0x1
Nov 28 20:06:11 iMac.local mdworker[3185]: Unable to talk to lsboxd
Nov 28 20:06:11 iMac kernel[0]: Sandbox: sandboxd(3186) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:06:12 iMac.local sandboxd[3186] ([3185]): mdworker(3185) deny mach-lookup com.apple.ls.boxd
Nov 28 20:07:05 iMac.local Notes[3055]: [IMAP] Expected untagged initial response from pop.laposte.net
Nov 28 20:07:12 iMac.local com.apple.SecurityServer[15]: Succeeded authorizing right 'system.hdd.smart' by client '/Library/Application Support/iStat local/iStatLocalDaemon' [62] for authorization created by '/Library/Application Support/iStat local/iStatLocalDaemon' [62] (B,0)
Nov 28 20:07:42 --- last message repeated 1 time ---
Nov 28 20:08:26 iMac kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
Nov 28 20:08:26 iMac kernel[0]: macx_swapon SUCCESS
Nov 28 20:08:29 iMac.local mdworker[3190]: Unable to talk to lsboxd
Nov 28 20:08:29 iMac.local sandboxd[3193] ([3190]): mdworker(3190) deny mach-lookup com.apple.ls.boxd
Nov 28 20:08:29 iMac kernel[0]: Sandbox: sandboxd(3193) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:10:44 iMac.local com.apple.backupd[3136]: Finished scan
Nov 28 20:12:12 iMac.local com.apple.SecurityServer[15]: Succeeded authorizing right 'system.hdd.smart' by client '/Library/Application Support/iStat local/iStatLocalDaemon' [62] for authorization created by '/Library/Application Support/iStat local/iStatLocalDaemon' [62] (B,0)
Nov 28 20:12:19 --- last message repeated 1 time ---
Nov 28 20:12:19 iMac.local com.apple.backupd[3136]: Found 3052 files (597.4 MB) needing backup
Nov 28 20:12:21 iMac.local com.apple.backupd[3136]: 3.65 GB required (including padding), 1.41 TB available
Nov 28 20:12:32 iMac.local mdworker[3200]: Unable to talk to lsboxd
Nov 28 20:12:32 iMac.local mdworker[3201]: Unable to talk to lsboxd
Nov 28 20:12:33 iMac kernel[0]: Sandbox: sandboxd(3202) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:12:33 iMac.local sandboxd[3202] ([3200]): mdworker(3200) deny mach-lookup com.apple.ls.boxd
Nov 28 20:12:33 iMac.local sandboxd[3202] ([3201]): mdworker(3201) deny mach-lookup com.apple.ls.boxd
Nov 28 20:12:51 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 53 wr: 53 q_size: 1024 flags: 0x1
Nov 28 20:12:52 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 822 wr: 822 q_size: 1024 flags: 0x1
Nov 28 20:12:52 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 567 wr: 567 q_size: 1024 flags: 0x1
Nov 28 20:12:52 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 312 wr: 312 q_size: 1024 flags: 0x1
Nov 28 20:13:03 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 57 wr: 57 q_size: 1024 flags: 0x1
Nov 28 20:13:11 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 826 wr: 826 q_size: 1024 flags: 0x1
Nov 28 20:13:21 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 571 wr: 571 q_size: 1024 flags: 0x1
Nov 28 20:13:38 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 316 wr: 316 q_size: 1024 flags: 0x1
Nov 28 20:13:55 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 61 wr: 61 q_size: 1024 flags: 0x1
Nov 28 20:14:10 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 830 wr: 830 q_size: 1024 flags: 0x1
Nov 28 20:14:21 iMac.local mdworker[3214]: Unable to talk to lsboxd
Nov 28 20:14:22 iMac.local sandboxd[3215] ([3214]): mdworker(3214) deny mach-lookup com.apple.ls.boxd (pre-ls-info fstype:hfs fsflag:480D000 flags:48200000056 diag:0 uti:com.netscape.javascript-source plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 13586206)
Nov 28 20:14:22 iMac kernel[0]: Sandbox: sandboxd(3215) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:14:24 iMac.local mdworker[3211]: Unable to talk to lsboxd
Nov 28 20:14:24 iMac.local sandboxd[3215] ([3211]): mdworker(3211) deny mach-lookup com.apple.ls.boxd (pre-ls-info fstype:hfs fsflag:480D000 flags:48200000056 diag:0 uti:com.netscape.javascript-source plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 13593446)
Nov 28 20:14:27 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 575 wr: 575 q_size: 1024 flags: 0x1
Nov 28 20:14:52 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 320 wr: 320 q_size: 1024 flags: 0x1
Nov 28 20:14:56 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 65 wr: 65 q_size: 1024 flags: 0x1
Nov 28 20:15:04 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 834 wr: 834 q_size: 1024 flags: 0x1
Nov 28 20:15:04 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 579 wr: 579 q_size: 1024 flags: 0x1
Nov 28 20:15:04 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 324 wr: 324 q_size: 1024 flags: 0x1
Nov 28 20:15:04 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 69 wr: 69 q_size: 1024 flags: 0x1
Nov 28 20:15:05 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 838 wr: 838 q_size: 1024 flags: 0x1
Nov 28 20:15:06 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 583 wr: 583 q_size: 1024 flags: 0x1
Nov 28 20:15:06 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 328 wr: 328 q_size: 1024 flags: 0x1
Nov 28 20:15:12 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 73 wr: 73 q_size: 1024 flags: 0x1
Nov 28 20:15:17 iMac kernel[0]: Sandbox: sandboxd(3221) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:15:17 iMac.local sandboxd[3221] ([3220]): mdworker(3220) deny file-write-owner /Users/nicolas/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.st oredata-wal (import fstype:hfs fsflag:480D000 flags:48200000056 diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 13562288)
Nov 28 20:15:17 iMac.local sandboxd[3221] ([3220]): mdworker(3220) deny file-write-owner /Users/nicolas/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.st oredata-shm (import fstype:hfs fsflag:480D000 flags:48200000056 diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 13562288)
Nov 28 20:15:17 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 842 wr: 842 q_size: 1024 flags: 0x1
Nov 28 20:15:20 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 587 wr: 587 q_size: 1024 flags: 0x1
Nov 28 20:15:25 iMac.local mdworker[3222]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:15:28 --- last message repeated 3 times ---
Nov 28 20:15:28 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 332 wr: 332 q_size: 1024 flags: 0x1
Nov 28 20:15:33 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 77 wr: 77 q_size: 1024 flags: 0x1
Nov 28 20:15:33 iMac.local mdworker[3224]: Unable to talk to lsboxd
Nov 28 20:15:33 iMac.local sandboxd[3221] ([3224]): mdworker(3224) deny mach-lookup com.apple.ls.boxd
Nov 28 20:15:37 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 846 wr: 846 q_size: 1024 flags: 0x1
Nov 28 20:15:47 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 591 wr: 591 q_size: 1024 flags: 0x1
Nov 28 20:15:48 iMac com.apple.launchd[1] (com.apple.PassXPCService[3099]): Exited: Killed: 9
Nov 28 20:15:48 iMac kernel[0]: memorystatus_thread: idle exiting pid 3099 [com.apple.PassXP]
Nov 28 20:15:51 iMac kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
Nov 28 20:15:51 iMac kernel[0]: macx_swapon SUCCESS
Nov 28 20:15:57 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 336 wr: 336 q_size: 1024 flags: 0x1
Nov 28 20:16:00 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 81 wr: 81 q_size: 1024 flags: 0x1
Nov 28 20:16:01 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 850 wr: 850 q_size: 1024 flags: 0x1
Nov 28 20:16:05 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 595 wr: 595 q_size: 1024 flags: 0x1
Nov 28 20:16:08 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 340 wr: 340 q_size: 1024 flags: 0x1
Nov 28 20:16:10 iMac.local mdworker[3226]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:16:13 --- last message repeated 3 times ---
Nov 28 20:16:13 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 85 wr: 85 q_size: 1024 flags: 0x1
Nov 28 20:16:18 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 854 wr: 854 q_size: 1024 flags: 0x1
Nov 28 20:16:19 iMac.local mdworker[3226]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:16:24 --- last message repeated 3 times ---
Nov 28 20:16:24 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 599 wr: 599 q_size: 1024 flags: 0x1
Nov 28 20:16:32 iMac.local mdworker[3226]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:16:34 --- last message repeated 3 times ---
Nov 28 20:16:34 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 344 wr: 344 q_size: 1024 flags: 0x1
Nov 28 20:16:39 iMac.local mdworker[3226]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:16:40 --- last message repeated 3 times ---
Nov 28 20:16:40 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 89 wr: 89 q_size: 1024 flags: 0x1
Nov 28 20:16:48 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 858 wr: 858 q_size: 1024 flags: 0x1
Nov 28 20:17:01 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 603 wr: 603 q_size: 1024 flags: 0x1
Nov 28 20:39:07 localhost bootlog[0]: BOOT_TIME 1354131547 0
Nov 28 20:39:28 localhost kernel[0]: Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Nov 28 20:39:28 localhost kernel[0]: vm_page_bootstrap: 919981 free pages and 120403 wired pages
Nov 28 20:39:28 localhost kernel[0]: kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
Nov 28 20:39:28 localhost kernel[0]: zone leak detection enabled
Nov 28 20:39:28 localhost kernel[0]: standard timeslicing quantum is 10000 us
Nov 28 20:39:28 localhost kernel[0]: standard background quantum is 2500 us
Nov 28 20:39:28 localhost kernel[0]: mig_table_max_displ = 74
Nov 28 20:39:28 localhost kernel[0]: corecrypto kext started!
Nov 28 20:39:28 localhost kernel[0]: Running kernel space in FIPS MODE
Imac 8,1 4Go RAM early 2008
Time Capsule 2To
Thanks for your help -
Time Machine no longer finds the backup device
Have you looked through Pondini's extensive TM help site?
http://Pondini.org/TM/FAQ.html
http://pondini.org/TM/Troubleshooting.html
Can't imagine something not being covered there. -
Can someone explain what exactly is involved when it comes to Time Machine snapshots?
Can someone give me a brief and succint description and tutorial on how Time Machine snapshots work?
I use Time Machine (on Mac OS X obviously, ML 10.8.4) to backup my HD onto a separate external drive at least once a week.
However, like so many other users I'm online in a variety of places so most of the time (about 99%) my laptop isn't able to be connected to the external designated for HD backups and I've heard and read that the application Time Machine can use "snapshots" to create temporary backups to hold until you've connected your external the next time.
I wonder how that works?
How do I go about setting up this snapshot option so that my laptop can be regularly backing up my files without me having to be tethered to the external at the same time?
Won't that fill up my entire drive due to virtual memory or sleepimage or swapfiles or something along those lines?
And last but certainly not least, how can the user take use of this option but also prevent the TM snapshots from hogging every availabe byte of memory.Read > http://pondini.org/TM/30.html
CS7981 wrote:
However, like so many other users I'm online in a variety of places so most of the time (about 99%) my laptop isn't able to be connected to the external designated for HD backups and I've heard and read that the application Time Machine can use "snapshots" to create temporary backups to hold until you've connected your external the next time.
I wonder how that works?
That's how it works.
CS7981 wrote:
How do I go about setting up this snapshot option so that my laptop can be regularly backing up my files without me having to be tethered to the external at the same time?
Local snapshots are made automatically in portable Macs with OS X Lion or Mountain Lion. Simply disconnect the Time Machine drive from your Mac and your Mac will start making local snapshots.
CS7981 wrote:
Won't that fill up my entire drive due to virtual memory or sleepimage or swapfiles or something along those lines?
These snapshots are stored in the hard drive and they consume a lot of space, as they are backing up the whole hard drive. A lot of users complain about the space they take, but in general, you don't have to worry. See below.
CS7981 wrote:
And last but certainly not least, how can the user take use of this option but also prevent the TM snapshots from hogging every availabe byte of memory.
Local snpashots will be deleted automatically when the hard drive is full, so don't worry about it. If you want to remove them, simply open System Preferences > Time Machine, and turn it off. Leave it for some minutes or hours, and turn on Time Machine again, but there's no reason to do that -
Time Machine couldn't complete the backup due to a network problem
Firstly apologies for the long post, I've been bottling these problems up and could now use some expert advice.
I have a MacPro (10.6.3) with four internal drives (320GB system/apps. + 3x 750GB data, images etc) and a MacBook Pro (10.6.6) with a 320GB internal. With so much accumulated data (Mac user since SE FDHD) I wanted a reliable means to backup all my projects, books, papers, research, images etc. I had several bad experiences using Iomega drives (Ultramax and Storcentre) which were not very Mac compatible and shifted over to a 10TB LaCie 5Big Network 2 which is promoted as Time Machine compatible. Set up Time Machine (with a few hiccups) in Sept 2010 and it ran perfectly, backing up both main computers until March 2011. I have now experienced a string of problems backing up the MacPro, some of which have been resolved speaking to people, some by checking forums and some by using my own noddle to figure it out. The latest error message I am getting is "Time Machine couldn't complete the backup due to a network problem. Make sure your computer and the backup disc are on the same network, and that the backup disc is turned on. Then try again to back up."
The circumstances of this are as follows: TM seems to be trying to completely back up everything already backed up from previous months so I am using the "exclude" option to do this in manageable chunks (5.54TB of 7.99TB is available so there is a lot of stuff on there, hence my reticence to erase and start again). I started a backup last night which said it was 242GB and when I came back hours later (I estimate 30GB and hour or 500MB a minute) it has failed with the error message above. I asked it to back up again and it said it now had 191GB to backup, at the next failure it was 142GB, dropping by approx 50GB a time (if there a maximum it can manage in one go?), the next time it was starting again with 242GB.
I checked the disc it was backing up to, discovered it was now selecting Public-1, re-selected Public which houses the macpro.sparsebundle, dropped the backup size (Options) to 73GB and set it off again and it is backing up as I write. I am hoping it will complete and permit another chunk to be backup but the fact it looses network connection (seemingly) or has a maximum backup in one go, is annoying because it means you cannot leave it overnight and trust it to do the backups.
The other problem seems to be a shut down by LaCie 5Big because several times (and once this morning) I have had this message "The file server "LaCie 5Big" has closed down, followed by a complete Lacie shut down and auto-reboot with all lights and whistles. Lacie think this could be a power supply problem and say they are sending me another power brick. They also say they do not support Time Machine (they should check their own literature) and suggest I use LaCie 5Big for 'drag and drop' backup. If I wanted to do that I could pick up a cheap and nasty HD from PCWorld, not this high end 10TB drive which cost over £1,000 !
For a while y'day I could not even find the Lacie on the network but after changing the ethernet cable from Lacie to router (Linksys) it miraculously re-appeared so that problem may have been the original Lacie blue ethernet cable had developed a fault. Checking cables is an oft-overlooked option.
A catalogue of errors, some solved, others still all pervading, so any words from the wise would be gratefully accepted.I verified the macpro.sparsebundle and Time Machine backups in Disk Utility and it said both appeared to be Okay in green type. So that did not solve the issue. I did a Disk Utility repair a day or so again (despite Verify saying everything was fine) and said there was nothing to repair. I suspect two problems, the power brick may be faulty producing intermittent power and maybe causing the drive to close down (hopefully Lacie will send me a replacement to try) and second, I am thinking the network connection is getting dropped causing crashed backups without the Lacie shutdown/reboot sequence. The 73GB back up failed, I started it again at 54GB and it failed again, just started it again at 45GB - this is no way to progress!
Perhaps the relatively new (last year) Linksys router is the problem, I find my MBP says AirPort is active but it fails to appear in Go>Server unless I switch it off and on again and perhaps a similar problem drops the connnection to the Lacie. -
Using Time Machine to restore an *older* BackUp drive
Here's my situation - I have currently been backing up my 2 computers (A Macbook Pro and a Mac Pro tower) to two separate external bootable drives (not Time Machines). I then take the drives off site in case of theft or fire, and know that if I need to I can always restore from these bootable backups.
However, because of the time and effort of bringing them in from their offsite location, I only back up once every few weeks, sometimes a month or more. So I just purchased an internal drive (separate from my system drive) to use as a Time Machine drive, for both of my computers (only one partition). Since they will be backing up every day, I will retain much more recent material in case of drive failure.
My question is this - if I have a drive failure on my current internal system drive, and the internal Time Machine is intact, is it possible for me to take my external bootable backup (say 3 weeks older than Time Machine in how recently it was backed up), make a cone of that on a new internal system drive, and then use Time Machine to restore that drive to what is most current on Time Machine?
Does this question make sense? I'm essentially trying to use a combination of external bootable drives and Time Machine in order to have peace of mind, knowing that I will have a complete, bootable restore, but it will then be able to become as up to date as the last Time Machine backup.Daniel Greeney wrote:
So I just purchased an internal drive (separate from my system drive) to use as a Time Machine drive, for both of my computers (only one partition). Since they will be backing up every day, I will retain much more recent material in case of drive failure.
Let Time Machine back up every hour, as it's designed. That will protect you best.
My question is this - if I have a drive failure on my current internal system drive, and the internal Time Machine is intact, is it possible for me to take my external bootable backup (say 3 weeks older than Time Machine in how recently it was backed up), make a cone of that on a new internal system drive, and then use Time Machine to restore that drive to what is most current on Time Machine?
Does this question make sense?
The question makes sense until you realize that Time Machine backups contain everything you need (unless you do something silly, like exclude your system files).
Once the new drive is installed and formatted, you can restore your entire system from the TM backups faster than you can copy the clone to the new internal HD. See #14 in the Frequently Asked Questions *User Tip,* also at the top of this forum. Note that you use the Snow Leopard Install disc only for the Installer on it; you don't install OSX from it. -
I updated from Snow Leopard OS X 10.6.8 to Mountain Lion OS X 10.8.2 on my MacBook Pro
I used disk utility to restore my external hardrive because I read somewhere that that would fix the problem.
It did fix the problem but only temporarily. I was able to view my backups from Snow Leopard, but as soon as I tried to backup again, time machine was stuck
"preparing to backup" for 5 hours and when I quit the prepare I could no longer access my previous backups.So what happens if you go to System Preferences > Security & Privacy > General? Are you able to go there at all? If you are able to go there, can you unlock the preferences using the lock in the lower left and your login name and password?
If you are able to do this, can you change the "Allow applications downloaded from:" to Anywhere?
Best of luck.
Maybe you are looking for
-
Upgrading to FF, need to upgrade the glass too... 5D mkiii and 1 lens, or 6D and 2 lenses?
I've been shooting for several years now, and my trusty 40D has been in dire need of an upgrade. I have had some good paying jobs in the last few months and I have some cash to play with. I've just been beating my head against the wall trying to figu
-
My IMessage is sending from my email, and I am recieving Messages thru my email. I have tried to fix this by going to Settings > messaging > recieved at> and my phone number pops up along with my email. It will let me click on my email, but my phone
-
Anyone know of any killer countdown web widgets?
New to iweb, just now figuring out the use of web widgets and they sure seem cool but a bit hard to navigate as to what is what out there. I'd like to know if anyone an point me to their favorites, in particular I am looking for a countdown widget, w
-
Error draging data page component on strut flow diagram
i m using Jdeveloper10g(9.0.5.2) on windows 2000 creating web application using strut+ADF+JSP technology stack encounter following error, i tryed multiple restart to IDE but still have same situation. Message BME-99003: An error occurred, so processi
-
N80.. new firmware v 4.0632.0.38 ?????
v 4.0632.0.38 13-10-2006 RM-92 N-80(05) Code: 0546454 new firmware???????????????????????????????????????? Message Edited by dos_1 on 05-Jul-200705:59 AM Message Edited by dos_1 on 05-Jul-200706:03 AM