Time MAchine and Users

I just set-up Time Machine using a 1TB External Hard Drive. My question is: I have several Users set-up on my Mac. I have myself as the MAIN user but also my daughters have their own individual log-ons. Will TIme Machine back-up ALL users or just the one user that is logged on? Hope this makes sense?

bingalls wrote:
To follow up on this question....
So when a second user logs into their account and Time Machine starts up. It in fact could be turned off in their account because Account #1 has already backed up all of their files? (except newly created files of course).
No. TM backs-up your system, not individual accounts. Backups are either on or off, for the entire system. Anything that's been changed, anywhere, will be backed-up (except File Vault, and any exclusions).
External disk drive for Time Machine is near it's max so making sure I have only one backup of all is key for me.
Note that TM usually requires roughly 2-3 times the space of what it's backing-up to work well. If you have other data on your TM disk, it's best if you partition the drive so TM has it's own, exclusive space. See items #1 and 3 of the Frequently Asked Questions *User Tip* at the top of this forum.
You might want to review these:
Time Machine Tutorial
Time Machine 101
How to back up and restore your files
Time Machine Features
Apple - Support - Mac OSX v10.5 Leopard Time Machine
and perhaps browse the rest of the FAQ Tip.
If you have a problem setting-up or using Time Machine, start with the Time Machine - Troubleshooting *User Tip* at the top of this forum. It will show you how to locate the message(s) that describe the problem, then help you fix it.

Similar Messages

  • Can I use my external HD for Time Machine and still use it for storage?

    I have a 1TB external HD and my computer has yet to arrive. I was planning on backing it up via Time Machine and I'm wondering if my external HD will still be useable as a storage device once I pair it with Time Machine.
    There's no way the backup will take up the full 1TB of space, so I'm hoping it doesn't just go to waste >.<

    If you really only want backups of the current contents, don't use Time Machine.
    It's designed to keep copies of things you've changed or deleted for as long as possible. This allows you an excellent chance to recover a previous version of something you changed or deleted in error.
    It also allows you to revert your entire system to the exact state it was in at the time of any previous backup, even if that's a different version of OSX. It's rare, but if an OSX update, or installation of a kernel extension or 3rd-party app makes a huge mess, it's much easier and more reliable than rebuilding everything.
    You might want to review the [Time Machine Tutorial|http://www.apple.com/findouthow/mac/#timemachinebasics] and perhaps browse [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum). See #1 there for size considerations.
    For alternatives, see Kappy's post on [Basic Backup|http://discussions.apple.com/thread.jspa?messageID=12366915#12366915].

  • TIme Machine and Snow Leopard

    I'm getting a problem. I updated to SL last week, backed up before I updated just in case. The update went without a hitch.
    I went to do a weekly backup using Time Machine (I had turned off automatic backup under 10.5.x as it was taking over the machine and stopping me working), but could not get it to go past 40Mb before it stalled. This has happenned constantly. When I look at Timemachine none of the previous back-up records are there, and my Finder now seems to crash too.
    I am getting really fed up with Time Machine. It is nearly as bad as a Windows experience, and now with this new OS upgrade it will not work at all.
    I'd appreciate some word from Apple admitting to a problem.

    Philip Grifffiths wrote:
    I'm getting a problem. I updated to SL last week, backed up before I updated just in case. The update went without a hitch.
    I went to do a weekly backup using Time Machine (I had turned off automatic backup under 10.5.x as it was taking over the machine and stopping me working), but could not get it to go past 40Mb before it stalled. This has happenned constantly. When I look at Timemachine none of the previous back-up records are there, and my Finder now seems to crash too.
    Start with the Time Machine - Troubleshooting *User Tip.*
    It will show you how to locate the message(s) that describe the problem, then help you fix it.
    If that doesn't help, post back with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.
    It sounds like you were having problems on Leopard, too, so it's unclear just what started when.
    I am getting really fed up with Time Machine. It is nearly as bad as a Windows experience, and now with this new OS upgrade it will not work at all.
    I'd appreciate some word from Apple admitting to a problem.
    Then you need to talk to Apple, not us: this is a user-to-user forum. Call AppleCare, and be sure to tell them what you've done to diagnose and solve your problem, since it doesn't appear to be widespread.

  • Time Machine and Time Capsule don't seem to work well together?

    Reposted.
    I get the feeling there are some serious problems with the combination of Time Machine and Time Capsule.
    This is extremely disappointing, as the idea of a centralized backup device on the network (instead of disks attached to each and every computer we have running Leopard) seemed like such a good idea and a good way to supplement our tape-based backup that takes place with Retrospect.
    In reality, it's a disaster on both Intel and PowerPC systems. All systems and the Time Capsule are fully up to date with software updates from Apple. I have two 1TB Time Capsule units. It goes something like this:
    1. I have a few systems (mainly Intel) that work perfectly with the Time Capsule. There are no complaints and no issues at all. These systems just quietly run their backups as they should. They are the definite minority--maybe one or two have worked properly.
    2. I have some systems that complain from time to time (mainly PowerPC) but will back up with a little encouragement. These too are the minority.
    3. And finally, I have systems that are nothing but pain. These are both Intel and PowerPC systems. They are also the majority of the systems I have. The most common problem is sudden loss of the credentials needed to access the Time Capsule hardware--a user will be going along about their business when the Mac OS asks for the Time Capsule user name and password--after it's already been supplied and backups have been running. This should simply never ever happen.
    Another charming behavior I've seen is corruption of the sparse disk image file that each computer creates on the Time Capsule. Time Machine will complain that it can't perform the backup, and examining the disk image file with Disk Utility shows it to be severely damaged. Turning off Time Machine, deleting the corrupted sparse image file, and starting over fixes it. For a while.
    Finally, there are the machines (again, both Intel and PowerPC) that just can't seem to actually get through the first backup run. They either go so far and can't continue, or never actually manage to get started. I've checked the disks in these computers and found no problem with the hardware or file system. The installations are fresh and fully up to date.
    Meanwhile, I have computers running Leopard with directly attached disks configured for use with Time Machine. One is a QuickSilver that isn't even officially supported by Leopard, with a Firewire attached disk. It doesn't skip a beat. The other is an Intel Mac mini being used with Mac OS X Server 10.5.4 and a USB external hard drive. These machines just do their thing, and I never have to babysit them.
    These problems with the Time Capsule have been so severe that I've just given up on most of the computers and shut off Time Machine entirely. We have tape backups that run over the week, so it's not a huge loss. But that's not what really made me throw up my hands and say "enough"...no, that was the speed. Even with just one computer backing up to it, the Time Capsule seemed terribly slow. Watching the progress indicator was just painful.
    I put in a word about all of this to my independent Apple dealer, and they say I'm definitely not the first to complain about some or all of these problems. In fact, they told me they were going to set up a test lab in their shop to see if they could duplicate these findings. I have no doubt that they can.
    There are a total of seven computers backing up to one Time Capsule. They all store maybe ~40GB worth of data including the OS. There are about six computers on the other. Because of the way the network is laid out, the Time Capsule is connected to a Gigabit switch (and that is the only thing it's connected to). It cannot be used as the router, although I know Apple suggests this. The Airport section is disabled--I have no need or desire to use it. Some computers link up at 100 megabits, others at 1 gigabit. There are no network problems--we have no problems moving large amounts of data across the same network to our tape backup machine.
    Is anyone else seeing these kinds of problems? Am I doing something wrong or expecting too much from Time Capsule?

    I may be on to something. The Time Capsules I have live in a telephone equipment room that is indoors but not directly air conditioned or heated. It doesn't ever get too hot to be comfortable in there--the highest I've ever seen the temperature was 80 degrees (F). Most of the time the temperature is between 60-78 degrees.
    I happened to touch one of them the other day while it was in use, and I noticed that the casing was hot to the touch...not dangerously so I suppose, but much hotter than I would have expected.
    So I turned a small fan on both Time Capsules and have left it running. And I've noticed that not only do backups seem to complete more quickly, the reliability is also better. I am going to try some of my most troublesome computers once again just to see what happens.
    I know there is a fan pointed at the hard drive in the Time Capsule, but I can't see how it does much in the way of cooling things down. In my opinion, it's just surrounded by too many heat producing devices to do much good...after all, not only is there a 7200 RPM hard disk in there, but also a 500MHz Marvell processor and radio set.

  • Mail deleted a current inbox and restored an old deleted inbox. It won't restore from Time Machine, and I'm missing archived emails from the old account. I'm pretty sure there is other stuff missing, but it's hard to tell. Any ideas why it would do this?

    Our Mac was working fine last Monday, then Tuesday morning one of our current inboxes was gone, and an old, archived inbox was restored--twice. Other than some trouble-shooting on Tuesday, we've pretty much left things alone as we were busy doing other stuff.
    I tried restoring the files from Time Machine, but it didn't work. I followed plisk restore instructions--nothing. It's a mess. We have no idea what would have caused this. We're above average users--we weren't mucking about with anything. It was just so strange.
    I went back into Time Machine, and it just makes no sense that I can't restore anything. We're now missing important emails--nothing too tragic, but still a pain in the butt. Thankfully the current inbox that was somehow deleted had a back-up on our email server, but the archived/deleted inbox file that was magically restored had all the archived emails that we kept deleted.
    Any ideas would be wonderful.
    Thanks!

    Hello,
    Could be many things, we should start with this...
    "Try Disk Utility
    1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
    *Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
    3. Click the First Aid tab.
    4. Select your Mac OS X volume.
    5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
    (Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
    If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.
    If 10.7.0 or later...
    Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk.

  • Backup fail on Time Machine and My Passport for Mac on Yosemite

    Cannot seem to get Time Machine to do a full backup of my NEW My Passport for Mac.
    I've:
    - Updated firmware on WD external drive (and formatted correctly for Apple)
    - Updated to latest IOS 10.10.3 (Yosemite)
    - Verified and repaired Mac HD via iOS Disk Utility and the WD Drive Utility (no issues found on either)
    Error message continues to be "Time Machine couldn't complete the backup to My Passport for Mac. An error occurred while copying files. The problem may be temporary. If the problem persists, use Disk Utility to repair your backup disk."
    I'm backing up about 250 GB and have done this numerous times on my Passport for Mac. Everything SEEMS to be fine during backup, until after about 2-3 hours, into a 4-hour backup, the error message appears without any error codes.
    Does anyone have any input?  I don't think it is on the WD side.  Anyone know if there an issue with Time Machine and this external drive?  Help!
    Thanks,
    Dave

    Hi Linc,
    I hope this helps you.
    Thanks,
    Dave
    4/21/15 2:30:48.894 PM com.apple.backupd[696]: Starting manual backup
    4/21/15 2:30:48.924 PM com.apple.backupd[696]: Backing up to /dev/disk3: /Volumes/My Passport/Backups.backupdb
    4/21/15 2:30:50.165 PM com.apple.backupd[696]: Forcing deep traversal on source: "Macintosh HD" (device: /dev/disk1 mount: '/' fsUUID: FAA966F2-1745-37AB-9FF9-CF4C23D771E4 eventDBUUID: B2005948-1DDE-40E6-ABC9-46245CA94AD1)
    4/21/15 2:30:50.175 PM com.apple.backupd[696]: Didn't get valid migration dates.
    4/21/15 2:30:50.180 PM com.apple.backupd[696]: Found 1181547 files (63.52 GB) needing backup
    4/21/15 2:30:50.187 PM com.apple.backupd[696]: 77.33 GB required (including padding), 819.06 GB available
    4/21/15 2:30:55.943 PM mdworker[699]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
    4/21/15 2:30:56.050 PM mdworker[700]: code validation failed in the process of getting signing information: Error Domain=NSOSStatusErrorDomain Code=-67062 "The operation couldn’t be completed. (OSStatus error -67062.)"
    4/21/15 2:32:39.865 PM com.apple.mtmd[688]: low disk space thinning needed for volume Macintosh HD with 2.8 <= 10.0 pct free space , no snapshots can be thinned
    4/21/15 2:32:39.866 PM com.apple.mtmd[688]: volume Macintosh HD is now in an emergency freespace condition
    4/21/15 2:34:39.000 PM kernel[0]: nspace-handler-set-snapshot-time: 1429641281
    4/21/15 2:34:39.893 PM com.apple.mtmd[688]: Set snapshot time: 2015-04-21 14:34:41 -0400 (current time: 2015-04-21 14:34:39 -0400)
    4/21/15 2:34:44.894 PM com.apple.mtmd[688]: attempting to thin because of low free space on Macintosh HD by removing 2015-04-21 14:30:39 -0400, estimate 18498 bytes to recover, 1 snapshot can be thinned
    4/21/15 2:36:51.268 PM com.apple.backupd-helper[687]: Not starting scheduled Time Machine backup: Backup already running
    4/21/15 2:37:01.460 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/21/15 2:37:02.384 PM com.apple.iCloudHelper[838]: objc[838]: Class FALogging is implemented in both /System/Library/PrivateFrameworks/FamilyCircle.framework/Versions/A/FamilyCircl e and /System/Library/PrivateFrameworks/FamilyNotification.framework/Versions/A/Famil yNotification. One of the two will be used. Which one is undefined.
    4/21/15 2:37:02.402 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/21/15 2:37:02.662 PM com.apple.xpc.launchd[1]: (com.apple.auditd[840]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd
    4/21/15 2:37:02.673 PM david81968[844]: audit warning: soft /var/audit
    4/21/15 2:37:02.673 PM david81968[845]: audit warning: allsoft
    4/21/15 2:37:02.676 PM david81968[846]: audit warning: closefile /var/audit/20150421183034.20150421183702
    4/21/15 2:37:02.839 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
    4/21/15 2:38:59.000 PM kernel[0]: CoreStorageGroup::completeIORequest - error 0xe00002ca detected for LVG "Macintosh HD" (D6FA6085-F105-4739-8C98-5794D7B5F901), pv 0759D4F3-CB92-452D-98FD-C34240DB00A7, near LV byte offset = 60459065344.
    4/21/15 2:38:59.000 PM kernel[0]: disk1: I/O error.
    4/21/15 2:38:59.999 PM com.apple.backupd[696]: Error: (-36) SrcErr:YES Copying /Users/david81968/Pictures/iPhoto Library.migratedphotolibrary/Masters/2011/10/08/20111008-103336/SAM_0979.JPG to (null)
    4/21/15 2:40:50.969 PM imagent[281]: <IMMacNotificationCenterManager: 0x7fd518c317e0>: notification observer: com.apple.FaceTime   notification: __CFNotification 0x7fd518f10980 {name = _NSDoNotDisturbEnabledNotification}
    4/21/15 2:40:50.970 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a5487f0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7f801a41a7a0 {name = _NSDoNotDisturbEnabledNotification}
    4/21/15 2:40:51.010 PM imagent[281]: <IMMacNotificationCenterManager: 0x7fd518c317e0>:    NC Disabled: NO
    4/21/15 2:40:51.011 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a5487f0>:    NC Disabled: NO
    4/21/15 2:40:51.025 PM imagent[281]: <IMMacNotificationCenterManager: 0x7fd518c317e0>:   DND Enabled: YES
    4/21/15 2:40:51.025 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a5487f0>:   DND Enabled: YES
    4/21/15 2:40:51.025 PM imagent[281]: <IMMacNotificationCenterManager: 0x7fd518c317e0>: Updating enabled: NO   (Topics: (
    4/21/15 2:40:51.025 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a5487f0>: Updating enabled: NO   (Topics: (
    4/21/15 2:40:51.025 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a722240>: notification observer: com.apple.iChat   notification: __CFNotification 0x7f801a533500 {name = _NSDoNotDisturbEnabledNotification}
    4/21/15 2:40:51.033 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a722240>:    NC Disabled: NO
    4/21/15 2:40:51.041 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a722240>:   DND Enabled: YES
    4/21/15 2:40:51.041 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a722240>: Updating enabled: NO   (Topics: (
    4/21/15 2:40:51.120 PM WindowServer[155]: device_generate_desktop_screenshot: authw 0x7fd09e980ad0(2000), shield 0x7fd099f396d0(2001)
    4/21/15 2:40:51.156 PM WindowServer[155]: device_generate_lock_screen_screenshot: authw 0x7fd09e980ad0(2000)[0, 0, 1440, 900] shield 0x7fd099f396d0(2001), dev [1440,900]
    4/21/15 2:41:03.172 PM loginwindow[90]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.
    4/21/15 2:45:23.309 PM com.apple.backupd[696]: Stopping backup.
    4/21/15 2:45:23.310 PM com.apple.backupd[696]: Error: (-43) SrcErr:NO Copying /Users/david81968/Pictures/Photos Library.photoslibrary/Masters/2011/10/08/20111008-103336/SAM_0979.JPG to /Volumes/My Passport/Backups.backupdb/David’s MacBook Air/2015-04-21-143049.inProgress/442FA756-4F11-4553-B1AD-FD0D08D9DDF3/Macintosh HD/Users/david81968/Pictures/Photos Library.photoslibrary/Masters/2011/10/08/20111008-103336
    4/21/15 2:45:23.464 PM com.apple.backupd[696]: Copied 22884 items (437.4 MB) from volume Macintosh HD. Linked 90492.
    4/21/15 2:45:23.546 PM com.apple.backupd[696]: Copy stage failed with error:11
    4/21/15 2:45:23.605 PM com.apple.backupd[696]: Backup failed with error 11: 11
    4/21/15 2:45:23.644 PM com.apple.xpc.launchd[1]: (com.apple.auditd[1026]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd
    4/21/15 2:45:23.658 PM david81968[1030]: audit warning: allsoft
    4/21/15 2:45:23.658 PM david81968[1031]: audit warning: soft /var/audit
    4/21/15 2:45:23.660 PM david81968[1032]: audit warning: closefile /var/audit/20150421183702.20150421184523
    4/21/15 2:47:24.762 PM SystemUIServer[258]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
    4/21/15 2:47:24.764 PM com.apple.prefs.backup.remoteservice[683]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
    4/21/15 2:48:21.585 PM WindowServer[155]: CGXDisplayDidWakeNotification [1669794395052]: posting kCGSDisplayDidWake
    4/21/15 2:48:21.586 PM WindowServer[155]: handle_will_sleep_auth_and_shield_windows: Deferring.
    4/21/15 2:48:21.706 PM imagent[281]: <IMMacNotificationCenterManager: 0x7fd518c317e0>: notification observer: com.apple.FaceTime   notification: __CFNotification 0x7fd518c34ab0 {name = _NSDoNotDisturbDisabledNotification}
    4/21/15 2:48:21.706 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a5487f0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7f801a531dd0 {name = _NSDoNotDisturbDisabledNotification}
    4/21/15 2:48:21.750 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a5487f0>:    NC Disabled: NO
    4/21/15 2:48:21.750 PM imagent[281]: <IMMacNotificationCenterManager: 0x7fd518c317e0>:    NC Disabled: NO
    4/21/15 2:48:21.771 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a5487f0>:   DND Enabled: NO
    4/21/15 2:48:21.771 PM imagent[281]: <IMMacNotificationCenterManager: 0x7fd518c317e0>:   DND Enabled: NO
    4/21/15 2:48:21.771 PM imagent[281]: <IMMacNotificationCenterManager: 0x7fd518c317e0>: Updating enabled: YES   (Topics: (
        "com.apple.ess",
        "com.apple.private.ac"
    4/21/15 2:48:21.771 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a5487f0>: Updating enabled: YES   (Topics: (
        "com.apple.private.alloy.icloudpairing",
        "com.apple.private.alloy.continuity.encryption",
        "com.apple.private.alloy.continuity.activity",
        "com.apple.private.alloy.idstransfers",
        "com.apple.private.ids",
        "com.apple.private.alloy.phonecontinuity",
        "com.apple.ess",
        "com.apple.madrid",
        "com.apple.private.alloy.continuity.auth",
        "com.apple.private.ac",
        "com.apple.private.alloy.idsremoteurlconnection",
        "com.apple.private.alloy.sms",
        "com.apple.private.alloy.screensharing",
        "com.apple.private.alloy.maps",
        "com.apple.private.alloy.callhistorysync",
        "com.apple.private.alloy.continuity.tethering"
    4/21/15 2:48:21.772 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a722240>: notification observer: com.apple.iChat   notification: __CFNotification 0x7f801a41a7a0 {name = _NSDoNotDisturbDisabledNotification}
    4/21/15 2:48:21.782 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a722240>:    NC Disabled: NO
    4/21/15 2:48:21.788 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a722240>:   DND Enabled: NO
    4/21/15 2:48:21.789 PM identityservicesd[285]: <IMMacNotificationCenterManager: 0x7f801a722240>: Updating enabled: YES   (Topics: (
        "com.apple.madrid"
    4/21/15 2:48:26.347 PM com.apple.xpc.launchd[1]: (com.apple.auditd[1095]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.auditd
    4/21/15 2:48:26.357 PM david81968[1100]: audit warning: soft /var/audit
    4/21/15 2:48:26.357 PM david81968[1099]: audit warning: allsoft
    4/21/15 2:48:26.374 PM david81968[1102]: audit warning: closefile /var/audit/20150421184523.20150421184826

  • What to do if you simultaneously run Time Machine and File Vault

    Never do what is mentioned in the subject line; even if you decrypt your drive, it does not spread to Time Machine, and so if you ever need to do a system restore, File Vault will forget your password and lock you out of your own system.
    Thankfully, I ended up having recourse. The solution is to log in as root and create a disk image from the last Time Machine backup, "latest," and then duplicate that disk image. Having done that, paste the files into the user folder of your choice, recreating the account you have lost.

    Realistically, your only option is to upgrade to an Intel-based Mac.
    There is no way to use iCloud on a Mac running anything lower than OS X 10.7.2 - not even Snow Leopard.
    You can access iCloud.com through a web browser on your current computer, but you'd need a Mac running 10.7.2 to move to iCloud and it wouldn't sync anyway...

  • Time Machine and drive permissions question

    I'm using Time Machine on a MacBook with two admin accounts (let's call them admin1 and admin2). admin2 is the account used daily. admin1 is the account used very infrequently.
    Things were set up with admin1. I noticed today when I was logged in as admin2 that TimeMachine reported that the last backup was more than 2 week ago (when things were set up), and that the last backup failed because the user didn't have privileges.
    I did a Get Info on the drive, and it seemed to confirm that (admin 1 had read/write privileges, but admin 2 had only read access).
    To get around the problem I logged in as admin1 and turned Time Machine off. I then logged in admin 2 and selected the disk from there, and turned Time Machine on.
    My question is - is this normal behavior? Or if there's something wrong, how to fix it?
    Thanks...

    Scott Newman wrote:
    After a few minutes, an external drive that is mounted on the desktop will spin down--like it should. But...each time a "Save" or "Save As..." dialog box is opened in any application, things will grind to halt for a few seconds while the external drive spins up--even though I will not be saving files to that drive. I've always hated that, which is one reason I've always done manual backups.
    Does that happen with Time Machine (either with a drive physically or wirelessly connected via Export Extreme) and is there any way to avoid that?
    It happens with TM. I am not sure of any convenient work-arounds. You can of course eject the drive and reattach it when you want to make a backup, but that's a bit inconvenient, IMO.
    Is it possible to manually turn on and turn off Time Machine (and the external drive) so as to only do manual backups like I'm doing now? I don't really care about looking up a prior version of file that I've changed. I just want a reasonably current whole-disk backup.
    Yes, TM has an on/off switch. Just turn it off until you want a backup. It will simply continue where it left off. It will not create a completely new backup.

  • Time machine and MySQL

    I am a time machine and a MySQL user and want my MySQL databases backed up by time machine. Currently, the databases are not backed up because they are owned by root (there is a red x on the folder in TM). In addition, this is probably not what I want to backup. MySQL generates binary logs that are useful for backups and I can direct it to put them in a shared folder, but I do not know how to direct it to set their permissions so that they are world readable. A file does appear there in the TM when I look at the file that contains the binary logs, so I assume that I could restore from it, right?
    Is this all I need? Oh, I also have a snapshot of the files as they were right before I started the binary log.
    Are there better solutions?

    You could export all the mysql databases with mysqldump then let time machine back up the resulting file:
    <pre style="border: 1px solid #ddd; padding-left: .75ex; padding-top: .25em; padding-bottom: .25em; margin-top: .5em; margin-bottom: .5em; margin-left: 1ex; max-width: 60ex; overflow: auto; font-size: 10px; font-family: Monaco, 'Courier New', Courier, monospace; color: #444; background: #eee; line-height: normal">mysqldump -A -uYourUser -pYourPassword > mysql_all-databases.sql</pre>
    Cole

  • Time machine and 10.5.8

    Time Machine backup to my Time Capsule worked great until I installed 10.5.8. My TC is connected to Mac via ethernet cable, and I use tc as my router as well. Now I would consistently get the error message: the volume cannot be mounted. Here's what I've tried so far:
    - reboot the system and the time capsule
    - repair the sparsebundle via disk utility- it was unrepairable
    - repaired permissions
    - used airport utility to erase the time capsule
    - turned off time machine and reselected the time capsule as the backup volume
    - trashed the timemachine .plist and rebooted again
    Now when I start time machine a backup volume mounts but is stuck in "preparing mode." When time machine is active, my computer goes haywire- multiple processes and applications begin "not responding" and won't force quit, and I end up having to do a hard restart. I have been browsing threads regarding this issue and can't find any more suggestions other than what I've already tried. any ideas?

    Jonathan Clark wrote:
    I'm experiencing a similar issue as well
    No, you're not. This thread is about wireless Time Machine backups failing with "the volume cannot be mounted." message, due to a problem with the Mozy application.
    also since 10.5.8. TimeMachine ran almost non-stop since I updated, and would back up Gigs at a time, even though I had not been changing the drive contents to that level. Now, TM won't run at all because my 500GB drive only has 70GB of space even though there's only one 21GB backup. It appears to have completely deleted a years worth of backups, kept only the latest, and thinks there is no room on the drive. It seems as if it tried to delete all the previous backups but couldn't.
    I have never had an issue like this before, and definitely am not trying to back up 500GB at a time.
    Start with item #D4 in the Time Machine - Troubleshooting *User Tip* at the top of this forum.
    If that doesn't help, please start a *New Topic,* including the results from the Time Tracker app mentioned in that User Tip; what else, if anything, is on your TM drive besides backups, and the messages from the +Time Machine Buddy+ as mentioned in item #A1 of the same User Tip.

  • HT4889 Transferred files via time machine and not log in password will not allow me to log in

    I have a new MacBook pro, I transferred files via time machine and a removable hard drive. Now new MacBook does not recognize the log in password. What can I do to reset the password?

    Did you migrate when you first booted up in Setup Assistant or did you migrate later? When you migrate later it can create a second account, check in Mac HD/Users to see if this is the situation.

  • My document.numbers can not be opened how can i recover the version from yesterday i was not using time machine and it was not in icloud. is there an app i can buy that might help

    my document.numbers can not be opened how can i recover the version from yesterday? i was not using time machine and it was not in icloud. is there an app i can buy that might help

    Thanks Andy,
    I wish I could have told my sister about this as she could not open my homepage back before my new iWeb site. She now can open my site without the yet in case denial window does appear = I thank you.
    I think my iWeb site works as Noone has said otherwise from any platform etc...
    Alex L
    I do agree that should not have to be a consideration for any users so i agree that it would be great if Apple could allow simplicity to run seemlessly.
    I have had this problem since Homepage, and here is
    what has worked for me. I send out the link, and
    then for PC users I send the link with "<" after the address (without quotation
    marks. e.g., <http://site.com>).
    I also put a note that if that doesn't work, to just
    copy and paste the link into a browser. With that I
    have only had 1 person say they still can't open.
    Everyone else gets it to work.
    It's a lot to do and seems like a hassle, but you get
    used to it.
    Hope this helps!
    Andy Martini
    PS - APPLE! When are you going to fix this??! It
    seems like such a small thing yet you guys have been
    stumped for YEARS on this!

  • Win 7 client with machine and user auth stuck in 802.1x_REQD

    Hi everybody
    we have a WLC 5508 with 7.2.110.0 and an ACS 5.3 and do the following:
    - Win 7 client gets a GPO object with the wlan configuration for "Machine and User authentication" with PEAP
    - On ACS 5.3 I configured correctly the authentication and authorization for first machine authentication and then user authentication ("Was machine authenticated = true)
    - First when machine authentication happens, the client is configured into a quarantine VLAN, where it is only allowed to communicate with the domain controllers
    - When the user authenication happens, the client is moved into the productive client vlan with no restrictions.
    Everything works fine, except that after the user loggs in, it takes about 3 minutes until the client answers the EAP Identity Request and loggs in, see attached screenshot or the screenshot below:
    In the client status on WLC i can see that the client is stuck in the 802.1x_REQD state for these 3 minutes, until suddenly it authenticates (but then very often, about 5 times - see screenshot).
    We tried the following to find the problem spot. but we were not able to locate the problem:
    - Configure the machine and user authentication into the same vlan all the time
    - ONLY user authentication on the client
    - Played with the Win 7 settings (timers, and so on)
    - When we manually configured the WLAN profile on the Win 7 client and saved it, the Win 7 client connected to the SSID without any problems and without any delay (about 5 seconds after the save)
    Did someone ever had the same issue?
    Thanks a lot and best regards
    Dominic

    Hi Amjad
    very good point on this, thanks a lot. In this case, I did not even think about the client firmware side, thought that I should be the WLC or the client settings, but not the driver. We will give a shot on this next week, maybe this will help us to solve the problem.
    It is normal to have the clietn in 802.1x_REQD if it is not yet authenticated and that is the expected state to be at in your situation untlil the client fully authenticates.
    Absolutely correct that the client is associated and in the 802.1x_REQD state as long as the authenticator did not get the EAP identity Response, but that the client takes such a long time to answer is not normal ;-)
    - What is the supplicant that is used on the windows machines? default WLAN supplicant? or you use some commercial supplicants?
    WZC.
    - what is the result when testing with user auth only?
    The same, it takes such a long time.
    - what ist he result when testing with machine auth only?
    Machine authentication works as expected, fast and as soon as the client is booted, the client gets authenticated.
    Regards and have a nice weekend
    Dominic

  • 802.1x Machine and User Auth Vlan assignments

    I have machine and user auth working between Win2K PC and ACS 3.3 but not sure how to best use the Vlan assignment feature. I use Vlans for different departments and if I assign a vlan in ACS to a machine when it authenticates but the user is assigned to a different Vlan, I don't get a renewed IP.
    Here is how it's working now:
    1. Machine authenticates to ACS and assigned to a Vlan
    2. User logs in and if they are assigned to the same Vlan as the machine, works fine. If assigned to another vlan, the switchport does get changed but the PC still has an IP from the initial Vlan it was assigned to. Releasing and renewing doesn't work but I really don't expect it to.
    So, I figure the solution to this is just not set a per user vlan and only set it per machine. But, the group mapping in ACS looked like a great way to assign Vlans based on a user's Active Directory group but it doesn't appear to recognize the different computer OU's we have. So I can assign vlan's based on user groups but not computer groups. As machines are added to ACS, I could change them to an ACS group with the Vlan set but this would be a lot more work than an automated method like unknown user policy.
    So, how are others assigning machines to vlans in large multi-vlan networks using ACS and 802.1x?

    By default users and computers belong to different global groups. "Domain Users" vs. "Domain Cmpouters" for example.
    As for your example, it seems like you have a misbehaving supplicant, and authentication is attempting and then timing out and starting over .. that never actually gets to fail, so the auth-fail stuff won't help.
    Note: A good way to troubleshoot this is to notice it in action via show command:
    Here's an example of what you should see on a switch port.
    AuthSM State = State of the 802.1X Authenticator PAE state machine
    VALUES:
    AUTHENTICATED -- Auth Succeeded
    AUTHENTICATING -- Auth is attempting
    CONNECTING -- Dot1x is up and configured and trying to locate a supplicant.
    HELD -- Auth probably failed.
    BendSM State = State of the 802.1X back-end authentication state machine
    VALUES:
    IDLE -- Nothing is happening.
    REQUEST -- Switch sent some EAP data to AAA, and is waiting to get something back.
    RESPONSE -- AAA sent the switch back some data, and the switch in turn asked the supplicant for more data.
    NOTE: You should rarely see the RESPONSE state above. If you see it for more than a second or so i nthe middle of an auth attempt, that's a smoking gun that you might have a mis-behaving supplicant, b/c it shouldn't take that long to send an EAPOL frame. The switch will eventually time out, and start auth over.
    Hope this helps,

  • Time Machine - Deleting user

    We are re-situating the kids on their own computer. What I need to know so that I don't have to face the wrath of a 16 year old in case I mess up: I use time machine and have continual back-ups. I want to delete my son's user. Will his user data remain on my external drive (and be accesible) until the drive deletes it due to current back-ups?
    Thanks in advance...Karen

    Karen Woods wrote:
    We are re-situating the kids on their own computer. What I need to know so that I don't have to face the wrath of a 16 year old in case I mess up: I use time machine and have continual back-ups. I want to delete my son's user. Will his user data remain on my external drive (and be accesible) until the drive deletes it due to current back-ups?
    Yes. You can delete all backups of it, if you want, but otherwise it will remain until the last old backup it's on is deleted (likely more than a month).
    As Kappy says, if you back the new Mac up via TIme Machine, it will start fresh with a full backup. If you back it up to the same external HD, your best bet will be to partition it, if you can, so each Mac's backups are kept separate. See #4 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).

Maybe you are looking for