After Server 4.1 update, Time Machine backups are huge

Hi,
After updating to Server 4.1, every one of my Time Machine backups for the machine (Late 2012 iMac) running OS X Server (which is backed up to a USB connected drive) is between 3GB and 7GB. When a backup finishes, I can immediately force a manual backup and it's >= 3GB.
Using the timedog utility, I narrowed the problem down to the OS X Server install, the largest file being:
/Library/Server/Wiki/Logs/postgres-xpg.log
Every 10 seconds, an entry similar to the following is added to this file:
2015-04-16 23:04:31 XPG.5941: matched path for pg_receivexlog file: /Library/Server/Wiki/Database.xpg/backup/000000010000006300000035.partial
This particular log file is around 3GB in size. It appears to have every log entry since I installed OS X Server December 2013. I find it odd this is happening in the Wiki directory as the Wiki service is disabled. I am using the following services:
Caching
Calendar
Contacts
File Sharing
Time Machine (for my Macbook backups)
I went into Time Machine (on the iMac) and deleted all the backups for /Library/Server/Wiki and that freed up 160GB. I could just exclude that from backups, but I don't want to do that. I would like to know why these entries keep getting put into that log and also why, if those entries are appropriate, the log is not rotated.
Any help would be appreciated!
Thanks, Patrick

Hi Patrick,
That particular log-file has had an issue for some time now.
Even when the wiki is not loaded the wiki proces generates errors which keeps on filling this log.
Exclude it from the backup simply solves your backup issue.
However there are some suggestions for "fixing" this enormous log around in the Apple Support Community.
I don't worry too much about it anymore, but you can generate a new file and throw out the old for instance.
As long as you have enough storage you're fine.
Some usefull steps for a fix are mentioned here:
http://apple.stackexchange.com/questions/113837/library-server-wiki-database-xpg -consuming-huge-amount-313gb-of-disk-space
Goodluck
Jeffrey

Similar Messages

After 10.5.6 update Time Machine Backup fails

After the 10.5.6 update today my backup is no longer recognized, and when trying to reselect the drive i get this error.
Quickpost this image to Myspace, Digg, Facebook, and others!
Looking at the Folder on the drive the iMac has the correct permissions
Quickpost this image to Myspace, Digg, Facebook, and others!
Message was edited by: GreggSymington

G. Cactus : it's not.
All my 4 external disks are located in the same place, and I can only (fortunately) backup on one of them, without any switch.
Pity the combo did not the trick for Gerrit.
I advise everyone to call Apple Care in your respective country, to hasten
a quick fix by Apple.
I'm not sure the thread on this forum would be sufficient for Big Apple, despite its excellent suppport,
to be warned about this bug in a timely manner.

After 10.5.6 Update : Time Machine Backup couldn't start

After upgrading to Leopard 10.5.6 my TM Backup (which Volume is served from OS X Server and worked successfully before upgrading to 10.5.6) failed. Errormessage like : "Backup volume couldn't activated because there's a problem with the Network-Username or -Password".
In the system.log file I found following messages:
"Dec 16 15:24:14 mammut /System/Library/CoreServices/backupd[221]: Backup failed with error: 29"
What mean's Error: 29? I can mount the TM Backup volume without any authentication problems, works well with Kerberos, i get successfully a Kerberos Ticket and have access to the TM client.sparsbundle Image.

G. Cactus : it's not.
All my 4 external disks are located in the same place, and I can only (fortunately) backup on one of them, without any switch.
Pity the combo did not the trick for Gerrit.
I advise everyone to call Apple Care in your respective country, to hasten
a quick fix by Apple.
I'm not sure the thread on this forum would be sufficient for Big Apple, despite its excellent suppport,
to be warned about this bug in a timely manner.

I just restored my 13" MBP i5 at the apple store to the newest version of Lion after issues with a previous Time Machine backup from Snow Leopard- this time I created a new account and just ported files and folders, and now MS Office doesn't work. Help?

I just restored my 13" MBP i5 at the apple store to the newest version of Lion after issues with a previous Time Machine backup from Snow Leopard- this time I created a new account and just ported files and folders, and now MS Office doesn't work.
^^ that's the main problem. Here's the full history.
I bought a new 13" i5 MBP, early 2011 edition. I had an old white Macbook 2.14 ghz core2duo on Snow Leopard. I attempted to port over my time machine backup, but encountered problems in that my User was inaccessible from the new computer after the import finished, and I had to go in and change the root password, etc, and for some reason or another, I couldn't install any programs at all from that administrator's account. By "couldn't" I mean I could install them, but upon installation they would never boot. So, I took it to the apple store and did a clean install from the most up to date Lion OSX. Then, I created a brand new admin account, instead of trying to import the old one, and things seemed great. Then, I just imported my old files from the TM backup, but not any system settings, permissions, or user data. Just my Docs, pics, vids, apps, and itunes stuff.
Here's where things get weird again. I imported this stuff under the name "old", but all of these folders have a red negative sign on them, marking them as restricted. So, from my main admin account, I cannot even peruse these folders. Since I didn't import user data, I can't sign in to the "old" account to change permissions. I already tried to change the permissions from system preferences, but that didn't change anything. And now, for whatever reason, of all the apps that were imported then, MS Office is the only set of apps that does not work. When I click on it, it just says there was a problem and asks if I'd like to send a report to apple. I tried reinstalling it to no avail. I'm an English student, so i really need access to Word. Can anyone help? The Apple store is a major detour for me and would like to fix this issue myself.

Most likely you have Office 2004 which are PPC-only applications and will not work in Lion. Upgrade to Office 2011. Other alternatives are:
Apple's iWork suite (Pages, Numbers, and Keynote.)
Open Office (Office 2007-like suite compatible with OS X.)
NeoOffice (similar to Open Office.)
LibreOffice (a new direction for the Open Office suite.)

Since upgrading to Lion, my time machine backups are failing - error message: The backup disk image "/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska's MacBook.sparsebundle" could not be accessed (error -1). Any ideas?

Since upgrading my Macbook to Lion, the time machine backups are failing - error message: "The backup disk image “/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska’s MacBook.sparsebundle” could not be accessed (error -1)." I have rebooted the TIme Capsule and it worked OK, but don't want to do that every time. Any suggestions? Thanks

Any new info on this?
I had the exact same problem and went crazy and spent a hecka lot of time trying to deal with my brand new 2TB Time Capsule and almost brand new MacBook Pro. Then I thought I fixed it...and I tried SO MANY things, I don't really know what did it...except taking out any apostrophe's in names of stuff that Apple puts in there...BUT...now it's back.
Grrr...

After 10.5.3 update, Time Machine disk getting set to read-only

"The Further Adventures of Time Machine..."
Since applying the 10.5.3 update, Time Machine (or something) seems to be randomly setting my backup disk (external Western Digital "My Book Studio Edition" 500GB) to read-only which, of course, brings Time Machine backups to a halt. I can generally just restart my MacBook Pro and all is well again but then after a few more hourly backups, it will go back to read-only status again. There's a couple of things about this that are odd:
1) Even if I open "Get Info" and try to reset the permissions on the drive, I'm locked out of doing so even though I'm the admin. What's even odder (more odd?), my user and "staff" show read & write but about the user name list, it states "You can only read"!?
2) I have this disk partitioned and even the partitions are read-only. Disk Utility reports the entire disk is locked.
Like I said, this has only start happening since 10.5.3 update.
Regards,
Terry

Here's the latest:
Also, the time machine back up drive had been smooth sailing since I hooked it up. Never had an ounce of problems until 10.5.3.
Format is Mac OS Extended.
Thanks.
CP
Last login: Mon Jun 9 18:36:23 on ttys000
cpstaley:~ cpstaley$ ls -aleO@ /Volumes/iMac\ Back-Up
total 9008
drwxrwxr-t@ 35 root admin - 1258 Jan 3 20:22 .
com.apple.FinderInfo 32
drwxrwxrwt@ 7 root admin hidden 238 Jun 5 21:04 ..
com.apple.FinderInfo 32
-r-------- 1 root wheel - 16 Dec 31 20:43 .0011243977f4
-rw-rw-r--@ 1 cpstaley admin hidden 12292 Feb 18 21:26 .DS_Store
com.apple.FinderInfo 32
-rw-rw-rw- 1 cpstaley cpstaley - 862 Dec 31 16:12 .MaxSyncConfig
drw------- 3 root admin hidden 102 Dec 31 20:43 .Spotlight-V100
drwxrwxrwt@ 3 cpstaley admin hidden 102 Jan 3 20:22 .TemporaryItems
com.apple.FinderInfo 32
d-wx-wx-wt 2 root admin hidden 68 Jun 5 16:46 .Trashes
-rw-r--r--@ 1 cpstaley admin hidden 135038 Jan 1 20:15 .VolumeIcon.icns
com.apple.FinderInfo 32
-rw-r--r-- 1 cpstaley admin - 59078 Aug 31 2007 .VolumeIcon.icns.candybarbackup
-rw-r--r-- 1 root admin - 0 Dec 31 19:52 .com.apple.timemachine.supported
drwx------ 96 root admin - 3264 Jun 5 03:30 .fseventsd
drwxrwxr-x@ 122 root admin - 4148 Dec 31 15:49 Applications
com.apple.FinderInfo 32
drwxr-xr-x+ 3 root admin - 102 Dec 31 20:44 Backups.backupdb
0: group:everyone deny addfile,delete,add_subdirectory,deletechild,writeattr,writeextattr,chown
-rw-r--r--@ 1 root cpstaley hidden 6656 Dec 31 19:50 Desktop DB
com.apple.FinderInfo 32
-rw-r--r--@ 1 root cpstaley hidden 11522 Dec 31 19:30 Desktop DF
com.apple.FinderInfo 32
drwxrwxr-t@ 48 root admin - 1632 Dec 31 15:49 Library
com.apple.FinderInfo 32
drwxr-xr-x 2 root wheel - 68 Dec 31 15:52 Network
drwxr-xr-x 4 root wheel - 136 Nov 26 2007 System
lrwxr-xr-x 1 root admin - 60 Dec 31 19:19 User Guides And Information -> /Library/Documentation/User Guides and Information.localized
drwxrwxr-t 7 root admin - 238 Dec 31 19:34 Users
drwxrwxrwt@ 3 root admin hidden 102 Dec 31 16:33 Volumes
com.apple.FinderInfo 32
drwxr-xr-x@ 4 root admin hidden 136 Aug 30 2007 automount
com.apple.FinderInfo 32
drwxr-xr-x@ 40 root wheel hidden 1360 Nov 26 2007 bin
com.apple.FinderInfo 32
drwxrwxr-t@ 2 root admin hidden 68 Mar 22 2005 cores
com.apple.FinderInfo 32
dr-xr-xr-x 2 root wheel - 68 Dec 31 15:51 dev
lrwxr-xr-x@ 1 root admin hidden 11 Dec 31 19:19 etc -> private/etc
com.apple.FinderInfo 32
-rw-r--r--@ 1 root wheel hidden 4352200 Oct 10 2007 mach_kernel
com.apple.FinderInfo 32
drwxr-xr-x@ 6 root wheel hidden 204 Dec 31 15:51 private
com.apple.FinderInfo 32
drwxr-xr-x@ 63 root wheel hidden 2142 Dec 26 13:32 sbin
com.apple.FinderInfo 32
lrwxr-xr-x@ 1 root admin hidden 11 Dec 31 19:19 tmp -> private/tmp
com.apple.FinderInfo 32
drwxr-xr-x@ 9 root wheel - 306 Sep 10 2007 usr
com.apple.FinderInfo 32
lrwxr-xr-x@ 1 root admin hidden 11 Dec 31 19:19 var -> private/var
com.apple.FinderInfo 32

After 10.8.3 update, time machine rebackups all the files in the home

Yesterday evening I have updated my MacBook Pro'11 from 10.8.2 to 10.8.3
Next time machine backup works for the whole night and now I can see that it rebackups the whole home user folder. It shows all the files in my home directory have been changed somehow. As a result, a huge amount of backup history is dropped on the time machine backup drive.
Is it okay? Why TM thinks my 350 GB of personal files have been changed after system update?

Ok, I didn't go in and check every file on the iMac last night when it did a full backup so will take your word for it. Doing this once with the new install seems reasonable to me, and with the large external drives I use is not a problem...well, except for the noise the drives make for such a long time will writing the backup
I am just happy knowing there is a good base for rebuilding the internal drive if I need it.

Can a Server install alter a Time Machine backup's permissions?

I'm trying to change a server from Advanced to Simple, so I'd planned to:
1) Run a final Time Machine backup
2) Shut the server down
3) Reinstall Leopard Server from scratch
4) Reinstall any/all needed apps or files using Time Machine.
The first snag I ran into was that after step 3) all files in the Time Machine backup seemed to have had their permissions altered so that I could not access the folders and could not make changes to the files.
Based on help from someone else I was able to find out that an ACL is in effect on these files.
I also had some files stored on the Time Machine Backups drive as regular files....these do not appear to have the ACL applied.
When I couldn't figure out how to deal with that I went ahead and did a Full Restore using the Leopard Server Install DVD. This went without a hitch and the Time Machine backup files no longer appeared to have the ACL applied.
So can installing Leopard Server using all defaults where possible (excl. server name and such) and using the Simple server options alter the existing backups on a Time Machine Backups disk like this? Is there something I can/should be doing differently to get this to work "correctly"? Reinstalling from scratch again is still an option if there's something different to try.
Thanks in advance!
-Matt
P.S. I was expecting to have to do some manual reconstruction on the mail server that runs on this box, but didn't expect issues like this so any help is appreciated!

Hi, if I understand correctly yes, but may I ask the purpose of doing so?

After 10.8.1 update, time machine is VERY slow

I have read in these rooms, as well as in tons of other forums, many time machine problems folks had after upgrading to ML. I did not have those problems. I use a regular external disk connected via USB. It's worked great for over a year. Since the upgrade to ML, my time machine did about half a dozen backups. They all worked at the "normal" speed that they always had. Today, I got the 10.8.1 patch, and when I started the time machine backup, it took forever. It looked like I suddenly inherited the problems everyone else had been having before. After 2 hours I had backed up about 200 MEG of the 27 GIG backup. I tried some forum-suggested tmdiagnose, and shutting Sophos, but nothing changed the situation.
Has anyone found anything that really fixes this? Or are we just stuck until Apple believes enough of us really got broken?
Thanks.

Re: OS X 10.8.2
Here are some rough comparative measurements of Time Machine/AFP throughput. Source machine is a modern iMac running OS X 10.8.2, connected through a Gigibit network to a modern Mac mini running 10.8.2 either as a stand-alone client or with Server 2.1.1. In Activity Monitor, I visually monitored the Network, getting a rough number for the average throughput. The Server software is installed on the mini's internal drive; the 10.8.2 client is installed on an external FW800 drive. The destination of the Time Machine backup is a freshly-erased 900 GB partition on another daisy-chained FW800 external drive. To switch targets, I merely restarted the mini using the correct startup volume, all other things being equal.
APF Target: OS X 10.8.2 (File Sharing Preference Panel):
1) Finder copy to a shared folder on the target's Startup Volume: 50 MB/sec
2) Finder copy to a folder on an external HD (connected to the target via FW800): 35 MB/sec
3) Time Machine: Create initial sparse bundle: 5 minutes.
4) Time Machine copy rate: < 5 MB/sec.
APF Target: OS X Server 10.8.2 (Server 2.1.1: Time Machine & File Sharing services enabled):
1) Finder copy to a shared folder on the target's Startup Volume: 100 MB/sec
2) Finder copy to a folder on an external HD (connected via FW800): 35 MB/sec
3) Time Machine: Create sparse bundle: 30 seconds
4) Time Machine copy rate: 35 MB/sec.
Notes:
1) Time Machine throughput to a 10.8.2 client is 5x slower than on Server 2.2.1.
2) Creating the sparse bundle takes 10x longer on 10.8.2 client than on 10.8.2 Server.
3) Time Machine throughput to a 10.8.2 client is 7x slower than a Finder copy to the same external volume on the same machine.
4) On 10.8.2 Server, AFP throughput to the Startup Volume is almost 3x faster than to an external FW 800 drive.
5) So worst-case Time Machine throughput to an external drive on a 10.8.2 client is 20x slower than the best-case Finder transfer to a startup-volume share on 10.8.2 Server.
Does anyone else see these throughput discrepencies?

10.5.5 Update - Time Machine Backup Stuck "Preparing" (How do I fix?)

I gave up on it with 10.5.4. Thought I would try since Apple fixed...it's still not working.
Background
1. This is my first backup. I've never been able to do a complete backup.
2. I have my laptop plugged in via ethernet to the TC.
3. I'm backing up about 90 gigs.
4. The firmware on my TC is 7.3.2.
5. Read/write access to the TC is working fine. I can access folders, create folders, copy files, delete files when accessing through finder.
Not sure what other info I can provide.
Please help. Thanks!

*Unmount the Backup Disk Image* #
It seems that one of the keys to successful Time Machine backups is a successful eject/unmount of the hard disk following the PREVIOUS backup. If the Console logs indicate that the previous, though successful, backup ended with something like:
Attempt to eject disk image failed with status: -47, dissenting pid: 0
Then the very next backup is likely to fail with “Unable to complete backup. An error occurred while creating the backup directory.”
A failed eject/unmount event usually means that your backup disk image is still visible on your desktop. If it is still there then unmount the backup disk image by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Clicking the drive icon on the desktop and selecting “Eject” from the contextual menu. Now try backing up again.
On the other hand, if after seeing this error message your backup disk image does NOT appear on the desktop, it doesn’t mean that this wasn’t the reason. You see, it is very likely that the current failed attempt to backup DID successfully eject/unmount the disk. In this case another attempt to backup will likely succeed.
*Excluding Primary Drive?*
Open the Time Machine preferences. Click "Options". Is your primary HD listed as one of the items to EXCLUDE from backup. If it is, remove it from the list and try again.
Another poster observed: “Had this myself but it was because for some strange reason my startup disk (the one I wanted to backup) was included in the 'don’t backup these items' list!”
Let us know if any of the suggestions above helped.

Can I Update Time Machine Backup Without Booting From The Source Drive

Greetings,
Can I update a time machine backup without booting from the original source drive?
My main Macbook Pro internal drive seemed to have died. I had not backed up in months so my Time Machine backup was old.
I replaced the drive with a new one and settled for restoring from the old TM backup because my latest info was on the dead drive and not backed up.
I just plugged the "broken" drive into a dock and it mounted.
It won't boot from the drive but I can mount it and copy from it so far.
I now want to update my Time Machine backup with the info on the 'broken" drive while it's able to be mounted.
How can I accomplish this without booting from the 'broken" drive and running time machine.
Recap...
I need to update a Time Machine backup using another hard drive without booting from the source (as I cannot). Both drives are connected via USB to my MBP and I am booted from another MBP. I want to end up with the newer info from the "broken" drive updating my older Time Machine backup.
Thank You,
SG

Hi
Time Machine will only be able to backup whilst booted into OSX, so unless you can mount the drive, and boot up the OS that is installed on the disk, then no, you will not be able to run a Time Machine backup of that drive.
You could image the drive onto another using Disk Utility
Cheers

File Sharing drops regularly, Time Machine Backups are delayed on OSX 10.7.3. Solution?

Hi there folks,
I'm having an issue with the new 10.7 server. We're running 10.7.3 Server on an Late 2006 XServe with 10GB RAM , connected to a Drobo Pro for Time Machine Backups of our 50+ users via our internal network.
Recently, Time Machine backups have been getting delayed, stating that they can't connect up to the backup drive (which is out Drobo Pro handling 16TB of space). The Drobo Pro hass not unmounted, and all the IP Addresses coming from and going to the Server handling the backups will still ping.
We've also be having trouble with Server resident drives and shared folders that people can mount using the ⌘+K shortcut or "Connect to Server" option in finder. People will choose the IP address, and finder will think for a few minutes then give an error stating that it cannot connect the the specified IP. The only way I can reestablish connection to the file sharing through a remote computer is to remote or physically login to the server, then go into System Preferences and turn "File Sharing" off, then on again. After that, the ⌘+K on a remote machine can find the drives again.
It's driving me crazy why this is ocurring. I don't know why, and people in the office are beginning to complain that they can't access certain files on the servers or are worried because their backups are not completeing.
It should also be known that a majority of the machines we have in the ofice are still running 10.6.8, with only a handful on 10.7, as we haven't had the time to make the major switchover yet.
I'm not the best when it comes to server software or Unix CLI managment (the office outsourced our Network Admin to the east coast), so I'm a bit stumped.
Does anyone have any suggestions to try? Is there a link between the number of Time Machine Users and the connection failures? Should I just tel the NetAdmin to create a script that will restart the File Sharing protocol on the server every couple of hours?
Hopefully someone will be able to help.
Thanks,
JYHASH

I started having connectivity issues to my 10.6.8 server from my 10.7 client immediately after updating the client to 10.7.3. FWIW. Takes forever to connect, when it does. After just milliconds before.

Time Machine backups are bigger than expected

Hi everyone,
I was wondering if anyone would know why, all of a sudden after a day or two ago, my Time Machine is suddenly insisting on backing up well over 4GB at a time? Before then my backups would almost always be below the 100MB mark. Has some update happened that would have caused this?
I have looked in Console but unfortunately am none the wiser. Is there some way of finding out a list of the files Time Machine is actually backing up? If so then I'd be able to track down this problem since I am fast running out of space on my Time Machine backup drive!
Many thanks for listening...
:-Joe

Jowie,
Consider the following info that I have gleaned, some of it may explain some it.
*Incremental Backups Seem Too Large!*
Time Machine performs backups at the file level. If a single bit in a large file is changed, the WHOLE file is backed up again. This is a problem for programs that save data to monolithic virtual disk files that are modified frequently. These include Parallels, VMware Fusion, Aperture vaults, or the databases that Entourage and Thunderbird create. These should be excluded from backup using the Time Machine Preference Exclusion list. You will, however, need to backup these files manually to another external disk.
One poster observed regarding Photoshop: “If you find yourself working with large files, you may discover that TM is suddenly backing up your scratch disk's temp files. This is useless, find out how to exclude these (I'm not actually sure here). Alternatively, turn off TM whilst you work in Photoshop.” (http://discussions.apple.com/thread.jspa?threadID=1209412)
If you do a lot of movie editing, unless these files are excluded, expect Time Machine to treat revised versions of a single movie as entirely new files.
If you frequently download software or video files that you only expect to keep for a short time, consider excluding the folder these are stored in from Time Machine backups.
Files or folders that are simply moved or renamed are counted as NEW files or folders. If you rename any file or folder, Time Machine will back up the ENTIRE file or folder again no matter how big or small it is.
George Schreyer may be describing what you are experiencing: “If you should want to do some massive rearrangement of your disk, Time Machine will interpret the rearranged files as new files and back them up again in their new locations. Just renaming a folder will cause this to happen. This is OK if you've got lots of room on your backup disk. Eventually, Time Machine will thin those backups and the space consumed will be recovered. However, if you really want recover the space in the backup volume immediately, you can. To do this, bring a Finder window to the front and then click the Time Machine icon on the dock. This will activate the Time Machine user interface. Navigate back in time to where the old stuff exists and select it. Then pull down the "action" menu (the gear thing) and select "delete all backups" and the older stuff vanishes.” (http://www.girr.org/mac_stuff/backups.html)
*FileVault / Boot Camp / iDisk Syncing*
Note: Leopard has changed the way it deals with FileVault disk images, so it is not necessary to exclude your Home folder it you have FileVault activated. Additionally, Time Machine ignores Boot Camp partitions as the manner in which they are formatted is incompatible. Finally, if you have your iDisk Synced to your desktop, it is not necessary to exclude the disk image file it creates as that has been changed to a sparsebundle as well in Leopard.

My Time Machine backups are significantly larger, and slower, over WiFi than Ethernet

My regular hourly backups from my Time Capsule began acting up a month ago. They were abnormally large (25-100 MBs) and took a long time--once, six hours.
I connected my Time Capsule to my MacBook Air through ethernet to repair the disk through Disk Utility, (I turned Airport off on the Air, but not the Time Capsule), and then to rebuild the Spotlight index for the Time Capsule.
Backups over ethernet work just fine now. The backup will happen in two parts, of around 200 KB each, and take two or two and a half minutes. But when I turn Airport on the Air back on, reconnect to the WiFi network, unplug the ethernet cable, and immediately start a new backup over WiFi, the two parts balloon to around 20 MB each, and the backup takes hours.
This is a backup over ethernet, which took 2 minutes, 21 seconds:
Starting standard backup
Attempting to mount network destination using URL: afp://Martin%[email protected]/External%20HD
Mounted network destination using URL: afp://Martin%[email protected]/External%20HD
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/External HD/Martin Fox’s MacBook Air.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
No pre-backup thinning needed: 1.70 GB requested (including padding), 733.41 GB available
Copied 1082 files (104 KB) from volume Macintosh HD.
No pre-backup thinning needed: 1.70 GB requested (including padding), 733.41 GB available
Copied 429 files (153 bytes) from volume Macintosh HD.
Starting post-backup thinning
Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Martin Fox’s MacBook Air/2012-05-11-225349: 733.41 GB now available
Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Martin Fox’s MacBook Air/2012-05-11-200538: 733.41 GB now available
Post-back up thinning complete: 2 expired backups removed
Backup completed successfully.
Ejected Time Machine disk image.
Ejected Time Machine network volume.
This is the second backup after that one, done over WiFi. (The first was incompletely recorded by Time Machine Buddy, but took around half an hour.) It took 1 hour, 54 minutes, 50 seconds:
Starting standard backup
Attempting to mount network destination using URL: afp://Martin%[email protected]/External%20HD
Mounted network destination using URL: afp://Martin%[email protected]/External%20HD
QUICKCHECK ONLY; FILESYSTEM CLEAN
Disk image /Volumes/External HD/Martin Fox’s MacBook Air.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
No pre-backup thinning needed: 100.0 MB requested (including padding), 733.41 GB available
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Waiting for index to be ready (101)
Copied 26 KB of 20.6 MB, 98 of 98 items
Copied 1485 files (22.0 MB) from volume Macintosh HD.
No pre-backup thinning needed: 1.72 GB requested (including padding), 733.41 GB available
Error: (-8084) SrcErr:YES Copying /Users/foxmarti/Library/Application Support/Firefox/Profiles/ehjqi949.default/places.sqlite-wal to (null)
Copied 1941 files (27.5 MB) from volume Macintosh HD.
Starting post-backup thinning
No post-back up thinning needed: no expired backups exist
Backup completed successfully.
Eject

slyfox1908 wrote:
I live in an apartment building so there are a number of WiFi networks around.
Not to mention cordless phones, microwaves, etc., any of which can interfere.
On iStumbler, my network shows up twice--once on channel 149, with signal strength of 50-65% and noise of 15%--and again on channel 10, with signal strength of that wildly varies from 20% to 90% and noise of 20%. Other networks in the building are on channels 1, 2, 6, and 11. The graph of channel 149 is very smooth, while the graph of channel 10 is choppy.
It's probably using 149, as those numbers are pretty good. Press Alt/Option before clicking the Airport icon in your menubar to see which band it's using.
Watch the band it's using while running a backup. Try other channels in the area of 149. Unfortunately, it's a bit of a "hit and miss" thing.
Why are there two networks? Is that part of the problem? My Time Capsule is located about three feet right and a foot below my desk, so I can't think of a reason why it wouldn't be 100% for both channels.
It's a dual-band router. As I understand it, OSX will pick the best signal.
I really want to know I have a clean, safe, accessible back-up before I replace it though. Right now I don't trust the Time Capsule.
Do at least your last backup via Ethernet.

How can I tell if my Time Machine backups are encrypted?

Hi - I would really appreciate it if someone could help me find out if my Time Machine backps are actually encrypted.
I know that there is an 'encryption' option when choosing a disc for Time Machine to backup to, but the problem is I cannot remember whether or not I actually ticked it (as it was a couple of years ago).
Other info that might be helpful:
- The disk I use Time Machine to backup to is actually a Apple Time Capsule
- I do have FileVault2 enabled on my mac
- I have never encrypted the Time Capsule disc itself (via Disk Utility or anything similar)
- One possible clue might be: When I go into Time Machine preferences, and click on 'Select Disk...' (as if to choose another disk to back up to), and select the disc that Time Machine currently backs up to (i.e. the Time Capsule disc), it does show an 'Encrypt backups' checkbox at the bottom of the window... however this checkbox is unchecked and also greyed out.
Thanks in advance
a_quinn

a_quinn wrote:
- Because I originally created this Time Machine Backup (to the Time Capsule) back in my 'OS X Lion' days,
I wondered; you posted in the Mountain Lion forum, but your profile still says Lion.
that means that my backups now (and moving forward) will continue to be un-encrypted
Correct (as of now, anyway). You cannot encrypt existing network backups. I doubt that will be available in the future, and would take forever.
- The only way to encyrpt my backups now, moving forward, is to remove this Time Capsule disc (from Time Machine Preferences), and start all over again ensuring that I check the checkbox next to 'Encrypt Backup' when selecting the Time Capsule's disc to backup to.
Well, in theory it's possible, but would take forever, squared.
You could archive the TC's contents to a USB drive connected to it, per #Q6 in Using Time Machine with a Time Capsule).
Then delete the original, start a backup with encryption, and as soon as the encrypted sparse bundle is created, cancel the backup.
Mount the sparse bundle, open the disk image, and delete the Backups.backupdb folder inside it.
Connect the USB drive to your Mac, mount that sparse bundle, open its disk image, and copy the Backups.backupdb folder to the one on the TC.
Depending on how large the sparse bundle is, that could easily take a couple of days, at least, even connected via Ethernet.
Just for testing one day, I encrypted a very small set of existing test backups on a F/W 800 drive - 6 dated backups using a whole 12 GB. Took an hour.
An alternative would be, just do the "archive" and keep the USB drive "on the shelf" for a while. You can always connect it to your Mac and access those backups via the Browse Other Backup Disks option.
Trying to keep a couple of years worth of backups usually isn't a good idea. It's a very complex structure, so the odds of damage increase, it takes much longer to populate the TM browser, and it works slower and slower, and if you didn't need something for 6 months, are you really going to need it in 2 years?

After Server 4.1 update, Time Machine backups are huge

Similar Messages

Maybe you are looking for