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.

Similar Messages

Funny bugs with Time Machine connecting to MacBook when reboot

Found a bug for Time Machine.
Reboot with TM disk connect to the MacBook. Most of the time, there will be no show of TM Disk on the desktop and connect thumb drives will not detect too. And do a normal shutdown, I can still feel the warm air venting out from the MacBook.
Have to remove the battery for a few seconds, replace it back and power up. Then everything will back to normal. If reboot with thumb drive connect, such symptoms will not appear.

dilagan wrote:
i attempted to backup the imac with time machine to an external hard drive, it began backing up, stopped and I got the same error message: "time machine error unable to complete backup an error occurred while copying files." Little help!
Yes, that message is not some of Apple's best work.
Most likely, there's a damaged/corrupted file that Time Machine is choking on. See #C3 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum).
If you're getting a different message from the Pro, see #C2.

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.

Time machine issues after installing lion server

I have a macbook pro and an imac in my home network, both running lion 10.7.3.
For some time, I used time machine to back up the macbook over ethernet to an external usb drive attached to the imac, which worked fine.
A couple of days ago, I installed the server.app on the imac, but disabled all services after a couple of days.
But now, all of a sudden, I can't complete my time machine backups anymore, I get this error message:
"Time Machine could not complete the backup. The network backup disk does not support the required AFP features."
I am not sure what to do here,
thanks for your comments,
geb

I am having a similar issue, but in my situation, my users cannot log in. All of my users are network users on Mini's. I am running 10.6.8 on my server. I have created users before with no issues, but have not done so in months. When I try to log the new user in, I get the following error:
xpchelper: Could not get path of user account (uid:1029) home directory:/Network/Servers/server.xxx.net/Volumes/Data/Users/username; error; The operation couldn't be completed. No such file or directory. Using home directory.
CFPreferences: user home directory at file://localhost/Network/Servers/server.xxx.net/Volumes/Data/Users/username/ is currently unavailable. User domains will be volatile.
Authorizationhost: error |-[homedirmounter mount NetworkHomeWithURL: attributes: dirPath: username:]|PremountHomeDirectoryWithAuthentication (url=AFP://server.xxx.net/Users/homedir= /Network/Servers/server.xxx.net/Volumes/Data/Users/username, name=username) returned 5.
I have no idea of what to do. I have verified that the user looks the same as my other users in WGM. The user's folder was created on the server. The user has access to the folder. I'm not sure what else could be wrong here.

HT201250 Time machine in my MacBook is showing error 43

Time Machine in my MacBook is showing error 43

-43 fnfErr File not found; Folder not found; Edition container not found; Target not found
http://pondini.org/TM/A1.html

"Time Machine can't back up - sparsebundle error 1" question

Hi,
I'm getting the "Time Machine can't back up - sparsebundle error #1" message, and am trying to see if the fix posted below is the answer:
http://support.apple.com/kb/TS2048
So, when I installed Time Capsule, I gave it a password ("network password").
Fairly recently, I renamed the Airport. Now the Airport disk password and Airport base station password are the same as the network password, and the Airport network password is different.
Is this what the Apple support message I referenced is getting at? Are these passwords supposed to be the same... ???
Thanks for any help,
reluctantuser

I'm not sure what you mean by "We also used the Time capsule as a hard drive for backing up." after you've already mentioned that you use Time Machine to back up three Macs to the Time Capsule.
Check this Web page for advice on the space issue.

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.

Time Machine broken after 10.6 server upgrade

I recently upgraded our Mac Pro running 10.5 Leopard server to 10.6 Snow Leopard server, I just popped the disk in and ran the installer. The upgrade seemed to go fine, this is just a file server, and everything seems to function just as it had in OS 10.5, except for Time Machine. TM did not pickup where it left off with the internal TM drive for the server (not entirely unexpected). With no luck I've tried:
Erasing and repartitioning the drive (after turning TM off and deleting the preference file)
Removing the drive and erasing and partitioning on another computer, then trying TM through a USB connection (after turning TM off and deleting the preference file)
Below is the common error dialog and part of a log file. If I were to remove the folder/file listed in the log next time it would just be another file. What is consistent is that it doesn't seem to like what's in the Shared Items folder (the sharepoints users attach to).
Can anyone tell me how I might fix this?
--- Sample Log Exerpt ---
com.apple.backupd[23587] Error: (-41) SrcErr:NO Copying /Shared Items/OpenJobs/∂ Jamie's Jobs/misc./Flash/Ex_Files_FlashCS3_BTB/Exercise Files/Chapter 09/03/final/classes/com/lynda/audio/mp3/Mp3Player.as to /Volumes/Server_TM/Backups.backupdb/travelxserve/2011-06-07-091921.inProgress/D 895F019-A328-45B1-A7D4-836231E1A817/ServerHD/Shared Items/OpenJobs/∂ Jamie's Jobs/misc./Flash/Ex_Files_FlashCS3_BTB/Exercise Files/Chapter 09/03/final/classes/com/lynda/audio/mp3
com.apple.backupd[23587] Copied 238 files (116.7 MB) from volume ServerHD.
com.apple.backupd[23587] Copy stage failed with error:11
servermgrd[81] servermgr_backup: TimeMachinePostBackupHook called.
servermgrd[81] servermgr_backup: TimeMachinePostBackupHook done.
com.apple.backupd[23587] Backup failed with error: 11

valoo wrote:
I deleted the newly created sparsebundle. I also realized that the computer name had been changed and I changed it back to the original one. Here's the new problem. The TM says that I only have 127 GB and the amount of space needed to back up the disk is 140GB. I don't understand. It almost seems like it is trying to duplicate the entire backup. And this time around, I don't even see any new sparsebundle. I am stuck here.
Something caused TM to decide to start a new "sequence" of backups, as if you'd gotten a new Mac. That means a new, full backup to start with. The only thing that seems to have worked for some folks is a Restart. So if you haven't done one since the latest changes and failed backup attempt, it's worth a try.
If it still wants to do a full backup, you can't prevent it.
Depending on how much space you have on the TM drive/partition, your only choice may be to delete the "old" sparse bundle and let TM start over.
You may be able to delete some of the older backups to make room for the new, full backup, but that's tedious and time-consuming (see item #12 of the Frequently Asked Questions *User Tip.)*
But that still leaves two problems: you'll have to manually "compact" the sparse bundle via Terminal to shrink it; and you'll have to continue to delete old backups this way (and manually compact them) to make room for new ones. Since TM is treating them as if they were from a different Mac, it won't delete them automatically, but will delete the oldest backups from the new set instead.

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 & BACKUP 3.2 FAILURES - SERVER 10.6.3

I have not been able to perform a complete backup using ANY Apple software since doing a clean install of Server 10.6.3.
Configuration: 4 Hard Drives in a Mac Pro 2x2.66. About 1.5 TB of data. 10.6.3. Connected to a DROBO via USB and/or Firewire. All issues fail in all interfaces.
If I use Backup 3.2, the data copies completely, but then the the "computing checksum" stage and it never clears, and of course as soon as you stop the backup the program deletes all transferred data.
If I use Time Machine, the process starts and then will copy some data and then just quit. Using TM Error Logger, I get this:
Error: (-41) SrcErr:NO Copying /.gem/ruby/1.8/cache to /Volumes...
com.apple.backupd[12768] failed with error 11
The Backup issue just hangs on the "computing checksum" no matter how big or small the backup is. I have done tests with 2GB files, and had the while 1.44TB backup fail... all with the same exact process. I have changed destination drives, and the same error messages show up on both programs.
I am ONLY trying to backup the data on the three data drives. I am not dealing with the boot drive.
I need to make sure the data is safe, hence the Drobo, but as it is right now I can't use any of the Apple Software to copy any of the data. This is a bit of a mess and any guidance would be appreciated.
I can copy manually files to an external FW drive, but we need to have automatic backups.

any updates on this? drobo on 10.6.3 via time machine doesn't work, and I think it may have corrupted the custom sparseimage

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 in Time Machine

I installed 10.5 on my Macbook Pro the standard way, nothing modified. Time Machine works just fine, backs up my data since a few days to an external usb-disk. no problems so far.
today i downloaded a big moviefile (800mb) from our fileserver over my webbrowser which took four hours or so (slow connection to that particular server).
the result: time machine backed up several copies of this moviefile during this time since the filesize grew over this time from zero to 800 mb.
since this moviefile is not important and just for a praesentation i deleted it after i downloaded to file.
now i tried to delete the file within the time machine interface ... i searched for it in the finder ... no result ... started time machine ... search ... result! i marked the file and choose "delete all backups of this file" from the submenue. time machine asked me if i really want to delete that files. i said yes.
and now ... it required me to input my password.
but: the box is sorta greyed out, no chance to "activate" the little verify-window. therefor i could not type my password in and therefor all instances of this file are still in time machines backup.
since i think manually deleting these files will corrupt the whole time machine database i decided to stay calm and wait for 10.5.1 ... and for apple to fix this bug!
any solutions?

Ge64 wrote:
Time Machine is set to backup to a disk connected to my AEBS
I hate to have to tell you this, but that's "iffy" and +*not supported by Apple.+* See [Using Time Machine with an Airport Extreme Air Disk|http://web.me.com/pondini/Time_Machine/Airport.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum). Follow the link there to see supported ways to back up.
but it isn't so it shouldn't find it. It doesn't crash every time TM tries to backup, but when it does crash it seems TM was trying to backup.
Did you +Disconnect All Users+ before unplugging the disk from the Airport?
Try Repairing the backups, per #A5 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum).
Also do a "full reset" per #A4.

[Bug][Tip]Time Machine "Select Disk" Button Greyed Out (But Still Operational)

Recipe:
1) Log in as a non-admin user which has Time Machine enabled
2) Open Time Machine Preferences
3) Unlock Settings and enter admin username and password
4) Notice that the Select Disk icon is greyed out
5) Click the Select Disk Icon anyway and change disks.
I discovered this because I carry my Mini between home and work and have a backup drive in each location. Time Machine is only able to remember one drive at a time (but it handles this setup just fine as long as you Select Disk when you get to a different drive).

Recipe:
1) Log in as a non-admin user which has Time Machine enabled
2) Open Time Machine Preferences
3) Unlock Settings and enter admin username and password
4) Notice that the Select Disk icon is greyed out
5) Click the Select Disk Icon anyway and change disks.
I discovered this because I carry my Mini between home and work and have a backup drive in each location. Time Machine is only able to remember one drive at a time (but it handles this setup just fine as long as you Select Disk when you get to a different drive).

Serious App Store Bug involving Time Machine

Here's the deal as far as I can figure out.
SOMEHOW, Mountain Lion has it in it's head that - even though I only bought my machine a month ago new and no one else has ever signed in, touched it or even so much as blinked at it or my apple ID - it thinks that I own an app that may have previously been backed up on the used drive I have attached to my machine even though that is not a real part of my system.See it is weird.. My App Store believes wrongly that I -> 1. Have an app installed that I have never had in my purchase history - but I must (sort of) still have within the bits on the time machine disk and 2. that my legitimately installed iLife apps brand new on the machine (iphoto included which currently is asking for an update also) were disseminated later in time and therefore the other ghost iLife apps on the unused portion of the timemachine backup were more legit by having simply been registered under another apple ID on someone else's rig before I did on mine with my own ID.. I now can't update my legit copies of iPhoto nor can I get rid of this solitaire app on my update list that I have never in fact seen or downloaded! It's not even in my purchases! I have tried every possible combo of logout, restart, I even stood on my head and spit rainbows out of my butt.. I cannot update iPhoto or do a darn thing! HELP!
JessanneS
Situation Summary:
Newly installed Time Machine with a used 1TB drive my friend gave me he didn't need.. this is the catalyst. -=>
The App Store is super CONVINCED I own an app (and I need to update it!) I've never bought or seen ever.. but MIGHT (this is my best guess!) have belonged to the last person using my newly installed and previously used as a time machine, 1tb Time Machine (get it?)
Also, The App Store is convinced that I have no way of updating iPhoto even though it came installed on my new machine last month and I am the only person who has signed into, set up, used an Apple ID on, or even touched my precious new iMac. So I can't update iPhoto (and that application seriously needs the update... so this *****! )
- my suspicion is that OSX Mountain Lion/App Store is convinced that the original person who had this used 1TB drive that I am now time machining with had iPhoto (and probably everything ever) backed up onto this drive and that somehow the OS is finding some type of registry codes (?) buried on it that it is interpretting as somehow more legitimate than my own currently.. maybe because they appeared first in time (as in before I even bought my new iMac?)
Anyway.. this is pretty seriously upsetting me at the moment. And I think a dev needs to look into this.
Thanks for any possible helpful suggestions. Please be kind, I'm sort of a newbie to Mac land.
JessanneS
Here is the annoying apple ID of the wrong person I don't even know who showing up.. it just so happens to have an email address local to my area so that is how I figured out that the drive I am using for Time Machine may be affecting my OS negatively..
<Edited By Host>

The MAS doesn't intend to peek on your network drives. As mentioned, it uses the spotlight indexing to see what's on your system. You can always re-index and mess around, but I wouldn't worry about it too much.
You may have noticed sometimes when mass storage is being indexed, this can take many hours. This is generally when people call AppleCare because they think Time Machine is broken It's not, it's just that millions of modes can take a while, even for a modern Mac.
I'll flag a moderator to move your image.

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.

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

Similar Messages

Maybe you are looking for