This discussion is archived
17306 Views 125 Replies Latest reply: Oct 18, 2008 10:36 AM by Adriana Bo
Currently Being ModeratedMay 10, 2008 8:30 PM (in response to Nazir)Nazir:
Thanks for the detailed explanation. Your needs are reasonable, and I'm quite confidant that there is a good way to connect your equipment. Here are my recommendations:
First, connect the ADSL modem to the WAN port of the AEBSn. Connect the PC and the Linkstation to the Ethernet LAN ports of the AEBSn. Take the third Ethernet LAN port of the AEBSn and connect it to the WAN Ethernet port of your Time Capsule. Any remaining computers that need Ethernet networking can be connected to the Time Capsule, using a gigabit switch if extra ports are needed.
Now for the network configuration: based on your posts, your AEBSn should already have Connection Sharing set to "Share a Public IP address". If not, use the AirPort Utility to set this accordingly. For wireless, set the AEBSn Radio Mode to 802.11b/g compatible, and give it a Network Name (ex: "NazirNet"). On the Time Capsule, set Connection Sharing to "Off (Bridge Mode)". For wireless, set the Time Capsule Radio Mode to "802.11n only (5 GHz)", and give it a different Network Name from your AEBSn (ex: "NazirNet-n").
Next, for the initial Time Machine backup, connect each of your Macs via Ethernet cable to the Time Capsule, and perform the first backup. It is very important to use a wired network for the first backup. It may take a few hours - that's perfectly normal. Once the initial Time Machine backup is complete, you can do the subsequent backups via wireless.
Finally, any Mac that supports 802.11n networking should use "NazirNet-n" rather than the older "NazirNet" connection.
I think this will solve all your issues. Please give this a try and post back with your results. Good luck!iMac, MacBook, Mac OS X (10.5.2)
Currently Being ModeratedMay 11, 2008 2:50 AM (in response to gglockner)Ahhh, I no longer have the AEBSn. Sold it when I purchased a Time Capsule. If I had known, I would have kept this.
Secondly, I need WDS as the PS3 is in another room, so the AX is used to boost the signal.
As regards initial backup, I have indeed done the first via wired (a few hours) and subsequent ones via wireless (quick updates). Its just that after about a week, the Time Machine updates "hang". I believe they are related to the Time Capsule's wireless mode slowing down. For some reason, i think this ends up corrupting the sparsebundle file and the only solution is a delete of this file and then a new backup sequence. Sort of defeats the idea of a Time Machine where one can go back hours/days/months.MacBook Pro 2.0GHz; MacBook 2.0GHz C2D; MacBook 1.8GHz; PowerBook G4 1.25GHz, Mac OS X (10.5.2), Canon iP4000R; TC 1TB; AX; Win XP; Win 2K; Win Vista; PS3
Currently Being ModeratedMay 11, 2008 5:46 AM (in response to Nazir)Nazir:
OK, got it. Best option would be to get another 802.11g router and connect that to the ADSL modem as described above. Since that router is connected to the PCs, you could either use an Apple AirPort or a less expensive router.
Until you can do that, I suggest you try Ethernet whenever your Time Machine backup is getting stuck. I haven't had any failures of Time Machine backups when using Ethernet on our two iMacs, but I did have a failure a few days ago on my MacBook. After I connected the MacBook via Ethernet, I initialized a Time Machine backup, and it completed. I have been able to do all subsequent backups via 802.11n.
Good luck.iMac, MacBook, Mac OS X (10.5.2)
Currently Being ModeratedMay 11, 2008 8:54 AM (in response to Nazir)Nazir:
Although I've experienced the slow initial backup, I don't think that the problem is with TC per se. The reason being is this:
Frustrated because it would take something along the lines of three days to do my inital backup of my Macbook Pro, largely because of a gigantic (40GB) iTunes library, I bought Personal Backup X5 and started using that. My backups were fairly swift. As a benchmark, I decided to backup just the iTunes library using TM and then using X5.
For X5 the time was about 14 hours to complete.
For Time Machine it was about 25 hours to complete. For the same forty gigs mind you!
Now, to me, that speaks to a software issue more than a hardware issue. That said, I'm giving TM one last chance. I'm in hour 13 of a backup that I estimate will take approximately 3 days to complete (133GB) which I'm doing over the wireless.
Is that a ludicrous amount of time, given that the entire network is wireless draft N? Yes, it should be much, much faster than that. I've optimized the network as much as I can right now (there's one thing I really should have done which is force wireless N but I wanted my iPhone to be able to connect to the wireless) and that's something to address. However, Time Capsule itself is NOT necessarily a flawed product. Keep in mind that there was almost a 100% difference in time to back-up the same data, going to the same TC, using different software.
If you don't believe me, download a trial version of Personal Backup X5, find your directory with the largest size and back that up. Then go into TM, exclude everything but that same directory and back that up. If you see something other than wildly different times let us know.
AjMacbook Pro 15" 2.4 Ghz Intel duo, Mac OS X (10.5.2), TC 500gb
Currently Being ModeratedMay 11, 2008 10:07 AM (in response to Nazir)I am have been having the same problem of having Time machine get caught spending enormous amounts of time "preparing" to back up using Time Capsule. I have tried a number of solutions. Today I tried to open the smartbundle for a backup directly, not using Time Machine. So far it has been running for several hours "Checking volumes.." So the problem may not be in Time Machine or Time Capsule, but the process of opening smart bundles somehow gets bogged down.Power book
Currently Being ModeratedMay 11, 2008 1:45 PM (in response to Graham Outterside)Hi,
I think I have some definitions of excrutiatingly slow. After running the first backup (of roughly 80G) over the ethernet link the following backups over airport needed an hour before they start (to back up a couple of MB). Now I did something nasty and installed the new iPhone developer release, downloaded some iTunes U lectures and waited to back up the new 1.3 G. After 3 days of non-stop networking I was at 380M backed up! The next morning the status of time machine was back to preparing (I don't know, if the backup was finished, but if it will use the same throughput, it clearly won't). This preparing state is now running for three days.
What for a backup solution is this for a laptop? I want to take my computer to work, but I fear, if I cancel the backup, I have to set it up all again from the start.
Is there a way to return the Time Capsule? It is clearly not working! I don't see if is saving anything; it is so slow that even if you copy all the data via the internet you will be faster, and it is not stable. Who want's a backup program that is not stable?
My configuration: I have an Airport Express base station connected to the internet and my stereo (so I can't swap it with the Time Capsule) and the Time Capsule replacing my old Airport Extreme UFO that also connects a Mini in the 2nd floor. The Mini by the way can surf the net via the Time Capsule without problems.MacBook Pro, Mac OS X (10.5.2)
Currently Being ModeratedMay 11, 2008 6:42 PM (in response to theorist)Graham:
I fully understand the frustration. I am now 24 hours into my TC/TM backup and have 37GB so far out of 130! Doing the math, that means I'm getting just about 1.5GB per hour (give or take) and that means that at this rate, it'll take 5 DAYS to do the initial backup over the wireless. Clearly unacceptable for a laptop backup solution since there's NOT going to be five days where I leave my laptop at home.
That said, I don't believe the fault lies in the TC itself. If it were in the hardware, I would expect that this slowness should show up irrespective of the backup software itself but as said in an earlier posting, using X5 my backups took what were reasonable times (50GB over a period of 14 hours is not extremely slow and about what I would expect more or less). That is a substantive difference over 37GB in almost precisely 24 hours. It means that I'm getting something close to 3GB per hour transfer using X5 and 1.5GB per hour using TM using the exact same harder (and with the TC erased both times so that there was no other data on the drive to be problematic). Now, I might be wrong but I don't think that I am. It seems a reasonable hypothesis that the fault lies in TM (software) and not TC (hardware).
ps. Is there anyone from Apple support reading these? Taking notes? Passing this on to your developers? This and the other TC/TM threads are a big red flag that I hope someone at Apple is paying some attention to.Macbook Pro 15" 2.4 Ghz Intel duo, Mac OS X (10.5.2), If I wanted to study computer viruses, I'd use Windows.
Currently Being ModeratedMay 14, 2008 2:52 PM (in response to dreadgeek)Some info for all of you who are also dissatisfied with the Time Machine (TM) - Time Capsule (TC) combination:
I did some testing with my 500 GB TC after I just couldn't seem to progress on the initial backup:
With _TM and TC via direct Ethernet_: 9 hours for 3 GB and going nowhere on my 90 GB harddisk - cancel that one.
With _Retrospect Express and TC via direct Ethernet_: 6 hours for all 90 GB!
With _TM and a 500 GB LaCie Quadra via FW 800 or eSATA_: Blasting at full throttle!
So there clearly is a problem with the combination of TC and TM - a shame for Apple and if I could, I would return my TC, since it's simply not usable this way.
It is very disappointing that Apple doesn't come out with an apology and a time schedule for a fix or rather a "your money back if not satisfied" offer.
For now I am using Retrospect for the TC and TM with the external LaCie.MacBook Pro (v3,1) 2.6 GHz, 800 MHz Bus, 2 GB RAM, Mac OS X (10.5.2), motherboard was upgraded from 2.2 to 2.6 GHz
Currently Being ModeratedMay 14, 2008 4:41 PM (in response to Christof Birkenmaier)I don't have an issue with the time taken to backup when it is working.
a) My initial backup is not wireless and via ethernet - so I see this as a sensible proposal and solution.
b) subsequent wireless UPDATES to the backup are fine but they only work for about a week before it has the propensity to get corrupted
My issue is that aside from the TM functionality, the TC as a wireless router is not behaving like the predecessor the AEBSn. This is my concern because it is not allowing me to stream video content to a PS3.MacBook Pro 2.0GHz; MacBook 2.0GHz C2D; MacBook 1.8GHz; PowerBook G4 1.25GHz, Mac OS X (10.5.2), Canon iP4000R; TC 1TB; AX; Win XP; Win 2K; Win Vista; PS3
Currently Being ModeratedMay 15, 2008 9:34 PM (in response to Nazir)Nazir-
I'm in complete agreement. This thread has morphed into handling Time Machine issues.
We should get back on target: Time Capsule is a poor wireless router. It does not behave like previous Airport products in that the performance is unacceptable. Features are great, performance isn't. This device is an anomaly.
Forget Time Machine. Forget the long backup processes. I'm concerned with everyday wireless usage: browsing, file sharing, iTunes downloads to Apple TV. These tasks are impossible without connecting the clients to Time Capsule's Ethernet ports.
I tested Time Capsule's speeds using TP Test (http://tptest.sourceforge.net/) from a MacBook Pro.
*Ethernet to broadband modem*
Highest Speed TCP: 866.04 kbit/s
Highest Speed UDP: 901.53 kbit/s
Available Broadband TCP/UDP: 96.1 %
Highest Speed TCP: 10.15 Mbit/s
Highest Speed UDP: 10.79 Mbit/s
Available Broadband TCP/UDP: 94.1 %
*Ethernet to Time Capsule*
Highest Speed TCP: 868.59 kbit/s
Highest Speed UDP: 905.42 kbit/s
Available Broadband TCP/UDP: 95.9 %
Highest Speed TCP: 10.11 Mbit/s
Highest Speed UDP: 10.82 Mbit/s
Available Broadband TCP/UDP: 93.5 %
*WiFi to Time Capsule*
Highest Speed TCP: 779.98 kbit/s
Highest Speed UDP: 904.48 kbit/s
Available Broadband TCP/UDP: 86.2 %
Highest Speed TCP: 186.04 kbit/s
Highest Speed UDP: 9.52 Mbit/s
Available Broadband TCP/UDP: 2.0 %
OK that the Ethernet slows slightly when routed through Time Capsule. That's acceptable. But clearly, WiFi routing from Time Capsule is not acceptable.
My Time Capsule network is setup like this:
MAC address access control
WPA wireless authentication
AEBS extending the WDS network, but it does not allow wireless clients (only Ethernet to an XBOX which is nearly always off)
Ethernet to an old PowerMac (nearly always off)
Scott2GHz MacBook Pro, Mac OS X (10.5.2), 2GB RAM, 7200RPM HDD
Currently Being ModeratedMay 15, 2008 10:12 PM (in response to Michael Essex)Well, from what I noticed previously preparing for backup doesn't really cause it to access the TC. On my first backup it was preparing for an hour or so (and I have only 30GB used on my MBP) and during that time I was looking at the traffic stats periodically and it was not even accessing the TC, so it could also be, that you have way too many files on the your HDD, that you want to backup.Macbook core duo & MBP SR 2.4 GHz, Mac OS X (10.5.2)
Currently Being ModeratedMay 16, 2008 4:04 PM (in response to Encabler)Scott
Thank you very much. This is what I've been trying to explain. I have not checked the numbers, but my experience tends to bear out this fact.
The WiFi routing seems severely constrained. I do hope it is a firmware fix because failing that, Apple may need to replace the circuit board.MacBook Pro 2.0GHz; MacBook 2.0GHz C2D; MacBook 1.8GHz; PowerBook G4 1.25GHz, Mac OS X (10.5.2), Canon iP4000R; TC 1TB; AX; Win XP; Win 2K; Win Vista; PS3
Currently Being ModeratedMay 17, 2008 9:43 AM (in response to Nazir)Anyone prepared to identify the problem or are we all going to sit around blaming others ?
I really don't want to start an argument but there are many of us for whom TC and TM function perfectly well, and for whom the wireless n system also works a treat ( I get 110Mbit out of a possible 130Mbit), so I dare suggest its not a 'fault' but one of configuration of the users Mac that is the driving factor.
One reason why Windoze gets such a bad press is that it has to cope with a multitude of software vendors, chips, motherboards yadda yadda yadda. Macs have always been more stable, as most if not all components come from Apple and the environment is much more stable.
Wireless networking is not an 'apple only' environment, so it could be that the problem lies with your non Apple components ? Who knows ? Not me for certain !
Much earlier in this thread, I asked for screenshots from Activity Monitor. This has been ignored and so its hardly likely that anyone is going to find the problem when all anyone does is ask questions. Try answering some sensible ones like;
'List all the activities running and active on your system'
If enough people who have a problem do this we may be able to find a common source. Unless we get more hard data, the problem is not going to spontaneously solve itself.
My problems went away when I bothered to use Activity Monitor to track down what was actually running, as opposed to what I THOUGHT was running. I don't believe most people with difficulties bother to do this.
Finally, on the subject of "Preparing to backup", the answer is pretty simple - your Mac is looking through the entire hard disc to see if any files have changed. This means reading the journal data for changes dates/times/checksums for every file on your system. Times will extend if your hard disc is either ;
- very slow
- has a lot of files (size is irrelevent to the Preparing phase)
- has applications running which change a lot of files
- has applications running which are continually updating large archive files which have to be scanned repeatedly.
I am trying to be helpful here - post your activity logs as requested and I can tell you which ones are active on my perfectly functional system. This may help you to narrow the issue down to that on your machine which is at fault.
In my case, I know it was a Sophos problem and how to stop it. And I've figured out why its doing what it does - and its logical, albeit annoyingly so.MacBook Pro 15", Mac OS X (10.5.2)