Time Machine GUI broken on headless server

I have 10.5.1 server running on a headless mini C2D and outside of some other rough edges, is running quite well. My issue is that whenever I connect to the server with Screen Sharing and kick off the Time Machine UI (via the Dock) to browse my local backups, I don't see the fancy interstellar user interface at all. Almost nothing happens on the screen except my Finder window repositions itself. It behaves as if the UI is there (i.e. the Dock, while visible, doesn't respond, I can't do anything else) If I pretend that the Time Machine UI is there and click on where the "Cancel" button should be, my Finder window goes back to where it was and I get control of my server again.
It's behaving as if the Time Machine UI is running, but just not visible.
Any ideas? Anyone else seeing the same thing? (or *not seeing* as the case may be)
Config: Mac Mini C2D 1GM RAM, internal 80GB HD, external Seagate FreeAgentPro 750GB drive for TimeMachine. (here's a tip for future forum searchers: with the FreeAgentPro drives, you need to take it to a Windoze machine and disable the drive's sleep timer, otherwise OS X Server gets upset that the drive went to sleep on its own and makes navigating shares from a client give inconsistent results. The "Put drives to sleep" option in Energy Saver still works as expected, but the drive won't be in control of its sleeping schedule, the OS will be.)

What screen resolution has your headless machine defaulted to ? Since you can get in via screen sharing, see what it's defaulted to.
Consider that TM probably has a required resolution (like, Workgroup Manager requires 1024x768 minimum).
If you need to have the resolution default to a different setting on reboot, try this that I put together:
http://www.afp548.com/article.php?story=20070211165654615
It's not my work just easy-to-use packaging of existing software (read the article).
It's Universal and there's a link there for a double-clickable installer.
For those bemoaning their experience jumping ahead with 10.5 server in a production environment:
well, that's your doing. Did you do full pre-testing in a non-production setting and confirm for yourself that it's ready for your needs ?
If you think 10.4.0 was perfect you are living in a fantasy. 10.4 server was a very rocky road til around 10.4.3 and there were still many fixes needed that came with later revisions.
10.3 had plenty of problems (!!) and 10.2 was a beast til 10.2.8 and I don't miss it.

Similar Messages

So, is Time Machine just broken in 10.5.2?

I know I'm in the minority here (although Macfixit has a bunch of people complaining as well), but ever since the 10.5.2 update, Time Machine has gone from rock solid to the flakiest feature of OSX since the days of 10.1.5. I've encountered pretty much every error you can think of over the past few days including:
1. My startup disk was showing up as the Time Machine drive (both the icon and in the pref pane)
2. I'm sometimes getting very slow backups (measured in KB!)
3. Time Machine is quitting out on me after it chokes on certain files (and when I omit those files, it chokes on another one)
I've done everything I can think of: reinstalled the full 10.5.2 update and the graphics update (for good measure), repaired permissions, deleted caches, ran DiskWarrior on everything, took my USB drives off the hub they were on, reformatted my Time Machine drives (loosing all my old backups in the process), and removed my SuperDuper clone from the Time machine drive, putting it back on its own partition.
I'm really at a loss, and I've submitted feedback to Apple, but everything was working fine under 10.5.1 and now with .2 it's all busted. What do you think, it Time Machine simply broken? Should I just turn off Time Machine until it gets fixed? My concern is that there is nothing to fix. That it's working fine for most people, and I've just been cursed.
Thanks for listening.

Barney,
The issue isn't with Time Machine backing up wireless to a NAS connected to a running workstation or server with open shared directory but with it not working when connected to a wireless router such as the Airport Extreme Base Station. As per Apple's online Time Machine documentation it states "Time Machine in Mac OS X 10.5 Leopard can be used to back up to many kinds of Mac OS Extended-formatted drives, but it does not support AirPort Extreme's AirPort Disk feature. Time Machine can back up to another Mac running Leopard with Personal File Sharing, or to a Leopard Server volume, or an Xsan storage device." Keep in mind though people were able to get Time Machine to backup to the NAS connected to the AEBS after entering the terminal command for Time Machine to use unsupported hard drives back when we used 10.5.1 but not since updating to 10.5.2. The reason people are upset is because Apple clearly advertised prior to Leopard's release that Time Machine would work over WIFI to a NAS connected to the AEBS but pulled that information just after releasing Leopard (Reference: http://www.appleinsider.com/articles/07/10/26/appleyanks_wireless_backup_from_leopard_lastminute.html ). This was after several customers including myself had already purchased the AEBS with a NAS drive with the understanding from Apple that Leopard would support this set-up. Apple still has not fixed the issue and their only solution seems to be for customers to buy their Time Capsule which is just the AEBS with an internal NAS drive. I can't speak for everyone but I feel mislead by Apple which is frustrating because I didn't imagine they would pull something like this.

Time machine backup from 10.6 server to Lion

Hi
I am running a Mac mini Server with SL Server, but I do not use the server features, it's pretty much a regular workstation. Now I want to upgrade to Lion (workstation) by formatting the hard drive and do a clean install. My question is if it is possible to restore my user data from the Time Machine backup done in SL Server during the setup of Lion? Are those os'es backups compatible or do I have to manually backup my home directory and user data and add everything after finishing the Lion install?
Thanks in advance
/Niclas

Thanks for your reply.
I guess that on 10.6 as far as TM is concerned the server version is exactly the same as the client version, except that we don't have the benefit of Migration Assistant to do the inherit for us.
I am using a USB disc for TM.
I can see that under Backup.backupdb I have a folder named after the old server, which contains the backups.
I did try simply renaming that to the new server name, just in case the solution might be that simple. But I get "operation not permitted". It's not a permissions problem, and doing chflags nouchg doesn't help. I guess it could be the schg flag, but I'm reluctant to try too hard in case I lose the old backups.
Soooooo I think I am out of options and the only thing I can do is as you say and start again.

Import stand-alone time machine backups to OS X server?

Can I import stand-alone (direct connect) Time Machine backups into OS X server Time Machine services so I can see & use them?

Local backups are stored in a folder. Network backups are stored in a folder on a disk image. In theory, you could start a network backup and then replace the folder with a copy from another device, but in practice copying TM backups doesn't work very well, if at all. It makes more sense to set the old backup drive(s) aside until you're sure you'll no longer need the data, then erase them and start over. Meanwhile start new backups over the network, if that's what you want to do.

Mobile backups not show up in time machine GUI

Mobile snapshots are missed in time machine GUI. So there is no white ticks on time line, except Current. It may be some kind of missing permissions on folder after update from Snow Leopard?
Current permissions is: drwxr-xr-x+ 3 root wheel 102 11 сен 09:59 .MobileBackups
I've checked this by doing: ls -al /
There are few snaphots with files inside .MobileBackups directory, I can access to files inside of it with sudo, but can't see it neither in /Volumes/MobileBackups nor in GUI.
Please help,
Thanks.

Hi,
Twice, I solved this issue with a full reset = http://web.me.com/pondini/Time_Machine/A4.html
Admin is gone : Wheel is the Lion's good group.

Time Machine: Lion vs. Lion Server... Lion Server breaks existing function?

Hello, I hope someone can point me in the right direction,
I recently upgraded (clean install) all of my machines to Lion. I decided to "start over" with a new time machine setup where each computer would have its own partition on the external drive. I hooked this drive up to a mac mini I had and connected all the other machines to it via the LAN and everything went well for a few days... until I tried to be clever. I decided to try Lion Server on the mini. After I added Server (which just seems to be a bunch of admin utils) and rebooted, my time machine setup stopped working. I am now getting the dreaded "the network backup disk does not support the required AFP features" (specifically TM Lock Stealing). From the client log:
8/7/11 9:31:28.531 PM com.apple.backupd: Starting standard backup
8/7/11 9:31:28.548 PM com.apple.backupd: Network destination already mounted at: /Volumes/Yggdrasil TM
8/7/11 9:31:43.988 PM com.apple.backupd: Destination /Volumes/Yggdrasil TM does not support TM Lock Stealing
8/7/11 9:31:54.000 PM com.apple.backupd: Backup failed with error: 45
Also, that volume doesn't appear anymore in the "Select Disk" dialog of the client. The volume does appear in sharing and I can copy files to/from it via Finder on the client.
Now, I went in to Lion Server and enabled "Time Machine" and set the "backup destination" to the same volume. That works fine. I can select that location and backups from my client go with no problem. That makes me think this is an arcane configuration issue... how can I get Tiger Server (or maybe it's on the client end) to recognize that the exact same disk/partition, just a different Folder is ok to save TIme Machine backups?
In other words... One share: "Yggdrasil TM" is at the root of a partition, which used to work for Time Machine in Lion prior to Server. Another share, "Backups" is inside "Yggdrasil TM" (/Volumes/Yggdrasil TM/Shared Items/Backups on the mini server). Any ideas?
I did notice that /Volumes/Yggdrasil TM/Shared Items/Backups has a .com.apple.timemachine.supported file in it, but it still didn't work after I "sudo cp -p" that file into where my older sparsebundle was.
I even went so far as to double check permissions and ACLs for both directories as being the same:
$ ls -ldae /Volumes/Yggdrasil\ TM/ /Volumes/Yggdrasil\ TM/Shared\ Items/Backups/
drwxrwxrwx+ 10 root staff 408 Aug 8 00:37 /Volumes/Yggdrasil TM/
0: group:com.apple.access_backup allow list,add_file,search,add_subdirectory,delete_child
1: user:_spotlight allow list,search,file_inherit,directory_inherit,only_inherit
drwxrwxrwx+ 5 root staff 170 Aug 8 00:32 /Volumes/Yggdrasil TM/Shared Items/Backups/
0: group:com.apple.access_backup allow list,add_file,search,add_subdirectory,delete_child
1: user:_spotlight inherited allow list,search,file_inherit,directory_inherit
I also played around with the /usr/sbin/sharing command, but that doesn't seem to have any real settings to do with this.
I guess I'm stumped, any suggestions before I restore the mini from time machine and give up Lion Server as a lost cause?
Thanks

Hi, it's been a while, but what I think I did was when I enabled the "real" Lion Time Machine Backups location, it created a sharepoint called Backups.plist. I looked at what was set in there to see if there was anything likely with this command
sudo defaults read /private/var/db/dslocal/nodes/Default/sharepoints/Backups.plist
and I found this bit, which looked interesting
timeMachineBackup = (
1
so, I figured I'd try it in the other plist files where I really wanted the backups as I was basically stumped. Luckily for me, it worked.
As for how I figured out where the sharepoint plist files were... I have a long name and I got tired of seeing the mounts show up as "MyFirstName MyLastName's Public Folde" (note truncation) on all my macs, so I went looking for those files some time ago. :-)
Hope that helps.

Time Machine on OS X Advanced Server

Hi, can anyone confirm that using Time Machine on an Advanced OS X 10.5.6 server will cause any issues? It seems to run fine, but if it's going to cause any problems, I'd like to know. Perhaps this was a warning not to use it on Advanced server, in earlier OS releases? ~ Jeanette

Without reliability in either backup or restore (especially restore), what's the point of using it when other solutions are available.
My experience with Time Machine on Mac OS X Advanced Server has 100% reliability for what I use it for.
I don't use Time Machine on Mac OS X Server to backup and restore configuration data - no web server configs, open directory data, mysql databases, etc., etc. I have zero expectation of this data being backed up reliably (even though it may work - Apple provide hooks in the Mac OS X SDK to enable dynamic data-based applications to work with Time Machine - take Mail.app, for example, where Time Machine is able to restore individual mailboxes).
As such, for what I use it for - primarily personal backups of home directory data, it works fine.
Maybe I'm odd in that I use Mac OS X Server on my personal workstation, and I'll accept that
My point is that there is no automatic block that prevents Time Machine from running (i.e. it doesn't say "oh, you're running Mac OS X Server so I'm not going to start up"). You just have to be aware of - and have reasonable expectations of - what does and doesn't work.
FWIW I don't use Time Machine on any of my production servers. For that I rely on replication, load balancing, and version control systems and if a machine dies I'm more likely to re-install the OS from scratch and re-install the specific applications/data that I need rather than try to restore from a backup of that individual machine.

BUG: Degraded performance, unresponsive system, syslog flooded with IOUserClient.cpp kernel errors when Time Machine starts (10.8.5 Server)

Every couple of months, my 2009 Mac Mini becomes suddenly unresponsive to Screen Sharing, Remote Desktop, AFP/SMB connections, VPN connections, and even SSH logins. It was still pingable, and the router showed many active network connections from an application that I knew was still running on it.
It is a headless machine, so the only way I can gain control is to manually reboot.
The Time Machine volume is an iSCSI target on a Synology DS412+ connected from the Mac by GlobalSAN's iSCSI Initiator v5.2.0.429. I am using iSCSI because of poor performance using Time Machine directly over AFP.
I looked at the logs this time and found a direct link between the starting of the backupd service and the appearance of these log entries. It has happened once every hour for the last 7 days.
3/11/14 2:53:37.915 AM com.apple.backupd[49366]: Starting automatic backup
3/11/14 2:53:38.067 AM com.apple.backupd[49366]: Backing up to: /Volumes/timemachine/Backups.backupdb
3/11/14 2:53:39.600 AM sudo[49393]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:43.960 AM sudo[49415]:     root : TTY=unknown ; PWD=/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:45.154 AM serveradmin[49437]: servermgr_swupdate[WRN]: Missing or invalid language for product items request. Using default "en".
3/11/14 2:53:46.663 AM sudo[49460]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:48.476 AM sudo[49483]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:50.759 AM sudo[49559]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:54.993 AM sudo[49581]:     root : TTY=unknown ; PWD=/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:53:57.799 AM serveradmin[49618]: servermgr_swupdate[WRN]: Missing or invalid language for product items request. Using default "en".
3/11/14 2:53:59.487 AM sudo[49643]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:54:01.371 AM sudo[49666]:     root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/Applications/Server.app/Contents/ServerRoot/usr/bin/psql -h /Library/Server/PostgreSQL For Server Services/Socket -U webauth -d webauth -c SELECT max(version) FROM schema_migrations
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:02.000 AM kernel[0]: /SourceCache/xnu/xnu-2050.48.12/iokit/Kernel/IOUserClient.cpp: mach_msg_send_from_kernel_proper {1000000d}
3/11/14 2:54:03.150 AM com.apple.backupd[49366]: Using file event preflight for Tardis SSD
3/11/14 2:54:03.251 AM com.apple.backupd[49366]: Will copy (128.5 MB) from Tardis SSD
3/11/14 2:54:03.259 AM com.apple.backupd[49366]: Found 216 files (128.5 MB) needing backup
3/11/14 2:54:03.283 AM com.apple.backupd[49366]: 913.2 MB required (including padding), 275.36 GB available
3/11/14 2:54:11.008 AM com.apple.backupd[49366]: Copied 2215 files (129.6 MB) from volume Tardis SSD.
3/11/14 2:54:11.037 AM com.apple.backupd[49366]: Using file event preflight for Tardis SSD
3/11/14 2:54:11.044 AM com.apple.backupd[49366]: Will copy (119 KB) from Tardis SSD
3/11/14 2:54:11.045 AM com.apple.backupd[49366]: Found 23 files (119 KB) needing backup
3/11/14 2:54:11.046 AM com.apple.backupd[49366]: 759.2 MB required (including padding), 275.23 GB available
3/11/14 2:54:13.402 AM com.apple.backupd[49366]: Copied 567 files (119 KB) from volume Tardis SSD.
3/11/14 2:54:13.589 AM com.apple.backupd[49366]: Created new backup: 2014-03-11-025413
3/11/14 2:54:14.679 AM com.apple.backupd[49366]: Starting post-backup thinning
3/11/14 2:54:18.200 AM com.apple.backupd[49366]: Deleted /Volumes/timemachine/Backups.backupdb/tardis/2014-03-10-015424 (128.9 MB)
3/11/14 2:54:18.200 AM com.apple.backupd[49366]: Post-back up thinning complete: 1 expired backups removed
3/11/14 2:54:18.582 AM com.apple.backupd[49366]: Backup completed successfully.

JoBidun wrote:
Thanks a lot for this really quick reply.
When you say: "I would though go back to 7.5.2 firmware." Do you mean a reset to factory default ?
Greetz
NO, your time capsule is running 7.6.1 but it is built with AFP following increased security for LION.. that is not required or available in Leopard.. so there is no point.. it is also not as stable on the older hardware.. at least in my experience.. I have repaired about 200 of the suckers so I do see a few.
When you select firmware update in the airport utility.. hold the option key.. all valid firmware versions for your TC then show up.. not only upgrades.. select 7.5.2 and upgrade to that.
Do a factory reset when you do it is a good idea though.. start off again.
And do reset of TM.. A4 in pondini.
See if it helps.
Oh, the TC will continually complain about needing a firmware update.. turn off automatic checking of updates.. it will still annoy you for fun every few weeks but that is better than daily.

Time Machine backup on OSX Leopard Server, no user logged in

Hi
I'd like to use Time Machine to do backups of a Mini running OSX Leopard Server. It has a TimeCapsule connected, which it backs up to fine, at the moment.
However, I've been wondering, if it still backs up, if no user is logged in? I've been reading a few old tips about making removable drives not dismount, when no user is logged in by adding/modifying a key in /Library/Preferences/SystemConfiguration/autodiskmount.plist, setting AutomountDisksWithoutUserLogin to true.
Is this still nescessary?
Is TimeMachine actually running when no user is logged in?
Is it a good idea to set the key, if my users homedirs is on a removable drive too?
If TimeMachine is NOT the way to do it, which way is the best/smartest?
Best regards
Nicolai

When reading my report, I forgot to mention how the external hard drive is formatted :
Hard Drive FW/USB:
Manufacturer: LaCie
Model: 0x0
GUID: 0xD04B78070AD64B
Maximum Speed: Up to 400 Mb/sec
Connection Speed: Up to 400 Mb/sec
Sub-units:
Hard Drive FW/USB Unit:
Unit Software Version: 0x10483
Unit Spec ID: 0x609E
Firmware Revision: 0x110
Product Revision Level:
Sub-units:
Hard Drive FW/USB SBP-LUN:
Capacity: 298.09 GB
Removable Media: Yes
BSD Name: disk1
Mac OS 9 Drivers: No
Partition Map Type: APM (Apple Partition Map)
S.M.A.R.T. status: Not Supported
Volumes:
Aristotle:
Capacity: 297.97 GB
Available: 164.85 GB
Writable: Yes
File System: Journaled HFS+
BSD Name: disk1s3
Mount Point: /Volumes/Aristotle
Raf

Can I use time machine to backup on my server HD?

I've mac Leapard with Time Machine but never made use of it because:
- I don't have and don't want to have an external HD.
- Don't have Time Capsule, and cannot afford it.
Yet I was wondering if it was somehow possible to use Time Machine, to backup directly to my server (online) for example.

-(.)^(.)- wrote:
Time Machine backups are NOT supported for NAS devices except Time Capsule or a USB HDD connected to an AirPort Extreme Base Station. All other options are hacks.
I would add that even if a network drive were available, unless it was formatted HFS+ with either GUID or APM depending, it would not be acceptable anyway for TM.

Time Machine Backup Not Performed (OSX Server)

On a newly installed 10.6.4 OSX Server (MiniServer hardware), I am trying to do a Time Machine backup to a freshly formatted external FW drive (GUID Partition map). Whenever I attempt a first backup I get a dialog:
"The backup was not performed because an error occurred while copying files to the hard disk. The problem may be temporary, try again later."
Disk Utility can find no problem on the drive. Repaired permissions, and verified both disks (Boot and Data) to be backed up.
Yes, the server is running and AFP is on.
I excluded the boot volume from Time Machine, and the Data drive seems to be backing up fine- so it's only the boot volume that is having a problem.
Can the Boot drive of a server be backed up with Time Machine?
(Both drives get cloned every night, as well as Time Machine and offsite Retrospect backups.)
Thanks.

Gary Hobish wrote:
"The backup was not performed because an error occurred while copying files to the hard disk. The problem may be temporary, try again later."
See #C3 in Time Machine - Troubleshooting (or use the link in *User Tips* 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.
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.
Can the Boot drive of a server be backed up with Time Machine?
Yes.

Bug in Time Machine 10.6 OS X Server, Error: (-41) SrcErr:NO Copying

Hello
It seems there is a bug in Time Machine which never occured in 10.5.8
We had a Mac OS X Server 10.5, with 2 external RAIDs, one with the SharePoints of Data and one as Time Machine Volume. This solution runs soomthly for 1 1/2 year.
Now we updated the OS X server from 10.5.8 to 10.6.4 with a clean install.
Since then it wasn't possible to make a finished BackUp with time machine. It stucks always. In the Console it listed the errors.
example.
19.09.10 11:49:41 com.apple.backupd[14514] Error: (-41) SrcErr:NO Copying /Volumes/RAIDserver HaKa ZH/Server HK/Auftraege in Arbeit/BLESSING/F2010/Lewis_Das_komische_Manifest/Layout_Protokoll/LewisSmilie/alt/K01/alt to /Volumes/HaKa-TM (Drobo)/Backups.backupdb/raidserver/2010-09-18-022427.inProgress/8F2F98D2-2F5E- 4BE0-BD20-971BC9E4E39C/RAIDserver HaKa ZH/Server HK/Auftraege in Arbeit/BLESSING/F2010/Lewis_Das_komische_Manifest/Layout_Protokoll/LewisSmilie/alt/K01
I can manualy delete this file or folder. Then the backup runs till the next error. very often the file involved is the ".DS_Store"
First I deleted my Time Machine Volume and also delete die com.apple.timemachine.plist and make a complete new backup. This also stucks.
Then I exclude the Data Volume and the BackUp of the bootVolume (server) runs fine. On the Data Volume are 4 Sharepoints. Owner is the administror and all the ACL and access-right are the same for the subfolders.
Of these 4 SharePounts, I individually exclude them. 1 runs smoothly with 3 I have problems.
I repaired the drives with DiskUtiliy and DiskWarrior. All errors are repaired but still the backup can't finished
I also tried different issues mentioned in http://discussions.apple.com/thread.jspa?threadID=2057525
I suggest that Time Machine change the way it verify it file to backup. The Backup Volume hasn't change since the update to 10.6 (only some new files)
I am very ****** off that Time Machine does'nt finished the backup and give me a list with all the errors.
Is there a Program that is able to list file with error in the same way Time Machine verify it file.
The last option I have it that is change back from 10.6 to 10.5.
Is there a list with new features and bugs within 10.6.4?
Is their a solution?
Gérard

Gerard Dirks wrote:
Hello Pondini
I running on this machine an OS X Server 10.6. In a unofficial note is written that this server software has builtin ClamAV (http://www.apple.com/server/macosx/specs.html), but we are not using the mail services!
Ah, I'd not seen that. ClamXav is free, and about the only one recommended here to find PC viruses so you don't pass them between Windoze machines, as it's not intrusive or damaging to the OS as most other anti-virus products are.
What i hate is that i need to exclude everything which has error. On the Data Volume are hunderd tousands of File (1.8 Tb), it would take me months to sort it out which files/folders occured the errors. I repaired the drives whit different tools and now their are no errors on all drives.
Agreed, there's no point to that. It's doubtful there's really anything wrong with the files. There does appear to be something wrong with the drive or file system, though.
Are you sure the drive is compatible with Snow Leopard? A number of drives that worked fine with Leopard needed new firmware or drivers to work well with Snow Leopard. Check with the maker.
If Apple has no fix in the next 10 days I will switch back to 10.5.8 server (and leave all that buggy new features for other people wo want to be experimental users for the staff of Apple)
You're not talking to Apple here -- this is a user-to-user forum.
Post your feedback here: http://www.apple.com/feedback/server.html
Or, much better, call AppleCare, via the Contact link at the bottom of this page.

Time Machine GUI not working

I have an odd issue with time machine: it can backup my system to my second drive just fine, but the gui will not load. When I click the time machine icon in the dock it attempts to center the desktop window but then freezes. Thus, it does not load the background so I can view the various backups by time. I'm thinking the issue is due to my old graphics card, since time machine works perfect with my 2 G4 minis. Any help would be greatly appreciated.
My specs are:
Powermac G4 (AGP Graphics)
Sonnet 1.8 Ghz G4 Processor
512 MB of RAM
Sonnet PCI SATA controller card
ATI Rage 128 Pro Graphics 16 MB AGP
HD 1 Seagate 160 GB SATA
HD 2 Seagate 80 GB SATA
Mac OS X 10.5.1

Look at this extract from the definitive Time Machine website:
http://pondini.org/TM/5.html
Ciao.

Time Machine is broken

Since I upgraded to Mavericks, Time Machine won't work. It took a whole day to backup about 16 GB over a wired ethernet connection. At 29 GB, my Mac crashed; totally unresponsive; it wouldn't even respond to a ping from another computer. I've tried this several times, once using the Mac booted in "safe mode" and it's crashed every time and at different points in the backup.
Some details about my environment:
I'm using a Macbook Air.
I'm using the USB Ethernet adaptor.
The ethernet is a 10G switch.
I'm backing up to a QNAP, Network Attached Storage (NAS) server using the Time Machine service provided by the NAS.
I've used the QNAP to backup this Mac before upgrading to Mavericks and other Macs on the network are using it and it's working.
I've run a verify disk with Disk Utility and no problems are reported.
Has anybody else seen similar problems since upgrading to Mavericks?

After upgrading two macs to OSX 10.9.3 (from 10.9.2) not only are time machine backups no longer working for these macs (backing up to a Synology NAS drive) but it also appears that time machine has "fixed" the issue by deleting the previous backups. Not happy !
Its clearly a Mavericks 10.9.3 problem as I have one mac still running 10.8.5 and time machine backups for this mac are running flawlessly to the same NAS unit.
Prior to the upgrades all three Macs had regular time machine backups to the NAS with no problems.
Apple please fix this issue. Its not acceptable to have such flaky backup software,
Im so glad I have one stable Mac running mountain Lion.
Rob

TIME MACHINE - EMAIL NOTIFICATION in the server

Hi,
I need to remove all email notification from Time Machine in my Mac OS X Server 10.6.5, do you know how?
I try to find the default write option to make that, or another way
Txs

Finally I found the answer, uncheck a disk notification option in WorkManager of the server, so easy !
Txs

Time Machine GUI broken on headless server

Similar Messages

Maybe you are looking for