Re: Yosemite - Time Machine backup

2014-10-21 Thread Severin Crisp
It runs in the family!   After installing Yosemite, my backup has increased 
from 630GB to 1.3TB!
Severin Crisp

 On 21 Oct 2014, at 1:20 pm, Ronni Brown ro...@mac.com wrote:
 
 Hi Peter,
 
 I then shut down iTunes in readiness for kicking off the backup. When I 
 switched on TM, it commences by Preparing Backup, I expected this to take 
 a while and it did. A while later I got an error message saying backup drive 
 too small for this backup. I was expecting an incremental backup not a full 
 backup of the ~720GB of data I have all over again. I thought here we go 
 again. 
 
 I took a look in Finder at the Sparesebundle file and there was a 4.5GB 
 sparsebundle file there and no sign of the previous ~630GB Mavericks based 
 Sparesebundle. 
 
 I've never known anyone to have so many problems/issues with Time Machine 
 backups / Time Capsule as you're experienced.
 I have used Time Machine first on a 2TB Time Capsule before changing to a 3TB 
 Time Capsule with my current backups history going back to January 2012.
 I've never had any problems with my 'Simultaneous Dual-Band 802.11n Wi-Fi 
 Network' or 'Time Machine backups' to either Time Capsule.
 
 I did a final SD Bootable Backup  a TM Backup prior to installing Yosemite 
 (as I always do before any upgrade of the OS).
 I kept TWO copies of the 5.17GB  Install OS X Yosemite.app - one on my 
 Desktop that I used to install Yosemite and another copy in my Installers 
 Folder.
 After installation completed I went through the normal steps of signing in to 
 Apple ID/iCloud/Messages etc - updating databases (by opening all Apple 
 Apps), upgrading applications, repairing permissions, and testing that 
 everything worked correctly for a couple of days before turning on Time 
 Machine to backup.
 
 Time Machine 'Preparing Backup' took a bit longer than normal (as expected) 
 as it read the new operating system, plus TM had not backed up for two days. 
 The backup went ahead and completed without any problem. The backup was 
 31.90GB (which is what I expected).
 I tested the backup to see the changes I had made working for two days and 
 all was correct.
 
 So I don't have any idea 'why' or  'how' your previous  ~630GB Mavericks Time 
 Machine backup  'Sparsebundle' was deleted... A Sparsebundle does not delete 
 itself!!
 And what the heck is the 4.5GB Sparsebundle?  did you have anything 
 connected to your Mac?
 
 Your son's 13GB sounds fair - the Yosemite operating system is 8-10GB, I 
 noticed my HD 'Used': space had increased quite significantly after the 
 installation.
 
 Cheers,
 Ronni
 
 17 MacBook Pro 2.3GHz Quad-Core i7 “Thunderbolt
 2.3GHz / 8GB / 750GB @ 7200rpm HD
 
 OS X 10.10 Yosemite
 Windows 7 Ultimate (under sufferance)
 
 
 On 20 Oct 2014, at 3:08 pm, petercr...@westnet.com.au 
 mailto:petercr...@westnet.com.au wrote:
 
 Hi, across the weekend I did the Yosemite upgrade and it all went seamlessly 
 onto my 2014 MBP 13 Retina. As some may recall, I have previously had a 
 couple of issues with Time Machine backups during non-related activities. 
 Prior to doing the upgrade to Yosemite, I forced a backup with the TC which 
 completed successfully. I then turned off Time Machine.
 
 Then I did the Update process with the machine connected via my recently 
 acquired Ethernet adapter. All this went fine. After the download and prior 
 to doing the install, I dragged the dmg file to my desktop so it wouldn't 
 auto delete and then copied the dmg to a drive connected via my USB hub 
 attached to my TC. All ok to here, no issues. Then did the update of the MBP 
 to Yosemite, this also ran with no issues (backup still turned off). Sign in 
 to iCloud all went fine too. Then i did the iTunes update, a nice new front 
 end UI, long overdue though.
 
 Then I trashed the Yosemite dmg from the desktop so as not to have a further 
 5GB included in the backup when I had held over another copy of it 
 independently.
 
 I then shut down iTunes in readiness for kicking off the backup. When I 
 switched on TM, it commences by Preparing Backup, I expected this to take 
 a while and it did. A while later I got an error message saying backup drive 
 too small for this backup. I was expecting an incremental backup not a full 
 backup of the ~720GB of data I have all over again. I thought here we go 
 again. 
 
 I took a look in Finder at the Sparesebundle file and there was a 4.5GB 
 sparsebundle file there and no sign of the previous ~630GB Mavericks based 
 Sparesebundle. 
 
 I probably did something wrong but wasn't too bothered as the Sparsebundle 
 was only a month old having previously deleted the Sparesebundle and rebuilt 
 from scratch just a month ago when I had the previous problem following a 
 Dropbox/Backup clash I caused.
 
 I am curious to know if there is anyone else who had a similar experience 
 with the Yosemite backup or might have a clue as to what I did wrong. .
 
 By contrast my 11yo son, did his update (on his 2012,13 MBP non-retina) 

Re: Yosemite - Time Machine backup

2014-10-21 Thread petercrisp
Ok, thanks for that Ronni. Yes I feel too that I have a
disproportionate number of issues and likely to be caused by me. My
Dad also indicated a doubling in size of his Saprsebundle (700GB to
~1.4TB) following the first backup following his Yosemite upgrade.
I had my external drive attached as I always do which contains my
iTunes and iPhoto libraries. Perhaps if I did a MBP backup first
WITHOUT the external drive attached and then introduced the external
drive afterwards that may have made a difference.  
Fortunately it is all academic now as I blew away the Sparesbundle and
in the process of rebuilding from scratch (it was in the process still
this morning when I left for work (at around 550 of 725GB)) so
hopefully completed when I return home tonight.
On the upside I like the refreshing new look of Yosemite and the
lovely mountain scenes from Yosemite National Park included in the
desktop image library.
Regards
Pete...

- Original Message -
From: wamug@wamug.org.au
To:WAMUG 
Cc:
Sent:Tue, 21 Oct 2014 13:20:50 +0800
Subject:Re: Yosemite - Time Machine backup

 Hi Peter, 
  I then shut down iTunes in readiness for kicking off the backup.
When I switched on TM, it commences by Preparing Backup, I expected
this to take a while and it did. A while later I got an error message
saying backup drive too small for this backup. I was expecting an
incremental backup not a full backup of the ~720GB of data I have all
over again. I thought here we go again.  
 I took a look in Finder at the Sparesebundle file and there was a
4.5GB sparsebundle file there and no sign of the previous ~630GB
Mavericks based Sparesebundle.   
 I've never known anyone to have so many problems/issues with Time
Machine backups / Time Capsule as you're experienced. I have used Time
Machine first on a 2TB Time Capsule before changing to a 3TB Time
Capsule with my current backups history going back to January 2012.
I've never had any problems with my 'Simultaneous Dual-Band 802.11n
Wi-Fi Network' or 'Time Machine backups' to either Time Capsule. 
 I did a final SD Bootable Backup  a TM Backup prior to installing
Yosemite (as I always do before any upgrade of the OS). I kept TWO
copies of the 5.17GB  Install OS X Yosemite.app - one on my Desktop
that I used to install Yosemite and another copy in my Installers
Folder. After installation completed I went through the normal steps
of signing in to Apple ID/iCloud/Messages etc - updating databases (by
opening all Apple Apps), upgrading applications, repairing
permissions, and testing that everything worked correctly for a couple
of days before turning on Time Machine to backup. 
 Time Machine 'Preparing Backup' took a bit longer than normal (as
expected) as it read the new operating system, plus TM had not backed
up for two days. The backup went ahead and completed without any
problem. The backup was 31.90GB (which is what I expected). I tested
the backup to see the changes I had made working for two days and all
was correct. 
 So I don't have any idea 'why' or  'how' your previous  ~630GB
Mavericks Time Machine backup  'Sparsebundle' was deleted... A
Sparsebundle does not delete itself!! And what the heck is the 4.5GB
Sparsebundle?  did you have anything connected to your Mac? 
 Your son's 13GB sounds fair - the Yosemite operating system is
8-10GB, I noticed my HD 'Used': space had increased quite
significantly after the installation. 
 Cheers,   Ronni

17 MacBook Pro 2.3GHz Quad-Core i7 “Thunderbolt
2.3GHz / 8GB / 750GB @ 7200rpm HD

OS X 1010 Yosemite
Windows 7 Ultimate (under sufferance)

 On 20 Oct 2014, at 3:08 pm, petercr...@westnet.com.au [1] wrote: 
Hi, across the weekend I did the Yosemite upgrade and it all went
seamlessly onto my 2014 MBP 13 Retina. As some may recall, I have
previously had a couple of issues with Time Machine backups during
non-related activities. Prior to doing the upgrade to Yosemite, I
forced a backup with the TC which completed successfully. I then
turned off Time Machine.
 Then I did the Update process with the machine connected via my
recently acquired Ethernet adapter. All this went fine. After the
download and prior to doing the install, I dragged the dmg file to my
desktop so it wouldn't auto delete and then _copied _the dmg to a
drive connected via my USB hub attached to my TC. All ok to here, no
issues. Then did the update of the MBP to Yosemite, this also ran with
no issues (backup still turned off). Sign in to iCloud all went fine
too. Then i did the iTunes update, a nice new front end UI, long
overdue though. 
 Then I trashed the Yosemite dmg from the desktop so as not to have a
further 5GB included in the backup when I had held over another copy
of it independently. 
 I then shut down iTunes in readiness for kicking off the backup. When
I switched on TM, it commences by Preparing Backup, I expected this
to take a while and it did. A while later I got an error message
saying backup drive too small for this backup. I was expecting an

Airport/ Time Machine Wireless network not working.

2014-10-21 Thread Brian Risbey
Hi all,
I replaced an older Telstra provided SpeedStream modem and replaced with a 
Netgear modem ( just modem no wireless capabilities).
Internet works when directly plugged into the MBPro via yellow cable - good. 
Also works through cable via airports.
But,
My wireless airport/ time-machines now don’t show up:
error message:
Wi-Fi has the self-assigned IP address 169.254.7.247 and will not be able to 
connect to the Internet.

Neither show up in the Airport utility, except under other WiFi devices and 
they won’t connect from there.

I have tried both soft and hard reset on the Airports.
Have I missed something?
Where have has my wireless network gone?

Brian
-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Settings  Unsubscribe - http://lists.wamug.org.au/listinfo/wamug.org.au-wamug

Airport/ Time Machine Wireless network not working.

2014-10-21 Thread Brian Risbey
Hi all,
I replaced an older Telstra provided SpeedStream modem and replaced with a 
Netgear modem ( just modem no wireless capabilities).
Internet works when directly plugged into the MBPro via yellow cable - good. 
Also works through cable via airports.
But,
My wireless airport/ time-machines now don’t show up:
error message:
Wi-Fi has the self-assigned IP address 169.254.7.247 and will not be able to 
connect to the Internet.

Neither show up in the Airport utility, except under other WiFi devices and 
they won’t connect from there.

I have tried both soft and hard reset on the Airports.
Have I missed something?
Where have has my wireless network gone?

Brian
-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Settings  Unsubscribe - http://lists.wamug.org.au/listinfo/wamug.org.au-wamug

Re: Airport/ Time Machine Wireless network not working.

2014-10-21 Thread Daniel Kerr
Hi Brian

Check you have the cable plugged into the correct port on the Airport. (as they 
have two,…one WAN port and some Ethernet ports). It should be the one that 
looks like a circle.
Possibly also, the new Netgear may not do DNS relay (I'm sure that's not the 
right term,.but I have a headache, so bear with me).
As it's only a one port modem, it expects to hand one just one IP address. 
Normally a wireless one will do DHCP and hand out IP addresses to all connected 
devices, as it knows you're going to have more then one.
And you've probably got the Airport DHCP set to Bridge mode.
(under Airport Utility the Network. Router Mode set to Off (Bridge Mode).

What you'll need to do in the above is change this to something like DHCP Only 
or DHCP and NAT.

I would imagine,..and I'm guessing here without seeing it,…so again bear with 
me,…
The Netgear Router will be something like 192.168.0.1
When you plug in your computer your IP address will most likely be 192.168.0.2

If you can confirm that you're getting an IP address like that, and it's not 
changing (or that the Netgear doesn't do DHCP), then that will point you in the 
right direction as well. (as it only expects to hand out one number ever).
So if that is the case, then you can set the Airport to do DHCP Only. Set the 
DHCP range to something like 192.168.0.5 through to 192.168.0.200
Then click Update in the Airport Utility.

This then means you can still get to the Netgear on 192.168.0.1, and all other 
devices will be in the range from 192.168.0.5 onwards. 
So the modem is just doing the internet, and the Airport is handing out it's 
numbers to connected machines.

Hope that helps. (I've assumed a few details there without knowing exact models 
of things, or seeing the network),…but hopefully should get you started on the 
right track.

Kind regards
Daniel

---
Daniel Kerr
MacWizardry

Phone: 0414 795 960
Email: daniel AT macwizardry.com.au
Web:   http://www.macwizardry.com.au


**For everything Apple**

NOTE: Any information provided in this email may be my personal opinion and as 
such should be taken accordingly, and may not be the views of MacWizardry. Any 
information provided does not offer or warrant any form of warranty or accept 
liability. It would be appreciated that if any information in this email is to 
be disseminated, distributed or copied, that permission by the author be 
requested. 

On 21/10/2014, at 8:05 PM, Brian Risbey risb...@bigpond.com wrote:

 Hi all,
 I replaced an older Telstra provided SpeedStream modem and replaced with a 
 Netgear modem ( just modem no wireless capabilities).
 Internet works when directly plugged into the MBPro via yellow cable - good. 
 Also works through cable via airports.
 But,
 My wireless airport/ time-machines now don’t show up:
 error message:
 Wi-Fi has the self-assigned IP address 169.254.7.247 and will not be able to 
 connect to the Internet.
 
 Neither show up in the Airport utility, except under other WiFi devices and 
 they won’t connect from there.
 
 I have tried both soft and hard reset on the Airports.
 Have I missed something?
 Where have has my wireless network gone?
 
 Brian
 -- The WA Macintosh User Group Mailing List --
 Archives - http://www.wamug.org.au/mailinglist/archives.shtml
 Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
 Settings  Unsubscribe - 
 http://lists.wamug.org.au/listinfo/wamug.org.au-wamug

-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Settings  Unsubscribe - http://lists.wamug.org.au/listinfo/wamug.org.au-wamug

Re: Airport/ Time Machine Wireless network not working.

2014-10-21 Thread Brian Risbey
Thank you Daniel I shall work through this extensive  list.


Brian
Sent from my iPhone6 Plus
iOS 8

On 21 Oct 2014, at 20:14, Daniel Kerr wa...@macwizardry.com.au wrote:

Hi Brian

Check you have the cable plugged into the correct port on the Airport. (as they 
have two,…one WAN port and some Ethernet ports). It should be the one that 
looks like a circle.
Possibly also, the new Netgear may not do DNS relay (I'm sure that's not the 
right term,.but I have a headache, so bear with me).
As it's only a one port modem, it expects to hand one just one IP address. 
Normally a wireless one will do DHCP and hand out IP addresses to all connected 
devices, as it knows you're going to have more then one.
And you've probably got the Airport DHCP set to Bridge mode.
(under Airport Utility the Network. Router Mode set to Off (Bridge Mode).

What you'll need to do in the above is change this to something like DHCP Only 
or DHCP and NAT.

I would imagine,..and I'm guessing here without seeing it,…so again bear with 
me,…
The Netgear Router will be something like 192.168.0.1
When you plug in your computer your IP address will most likely be 192.168.0.2

If you can confirm that you're getting an IP address like that, and it's not 
changing (or that the Netgear doesn't do DHCP), then that will point you in the 
right direction as well. (as it only expects to hand out one number ever).
So if that is the case, then you can set the Airport to do DHCP Only. Set the 
DHCP range to something like 192.168.0.5 through to 192.168.0.200
Then click Update in the Airport Utility.

This then means you can still get to the Netgear on 192.168.0.1, and all other 
devices will be in the range from 192.168.0.5 onwards. 
So the modem is just doing the internet, and the Airport is handing out it's 
numbers to connected machines.

Hope that helps. (I've assumed a few details there without knowing exact models 
of things, or seeing the network),…but hopefully should get you started on the 
right track.

Kind regards
Daniel

---
Daniel Kerr
MacWizardry

Phone: 0414 795 960
Email: daniel AT macwizardry.com.au
Web:   http://www.macwizardry.com.au


**For everything Apple**

NOTE: Any information provided in this email may be my personal opinion and as 
such should be taken accordingly, and may not be the views of MacWizardry. Any 
information provided does not offer or warrant any form of warranty or accept 
liability. It would be appreciated that if any information in this email is to 
be disseminated, distributed or copied, that permission by the author be 
requested. 

 On 21/10/2014, at 8:05 PM, Brian Risbey risb...@bigpond.com wrote:
 
 Hi all,
 I replaced an older Telstra provided SpeedStream modem and replaced with a 
 Netgear modem ( just modem no wireless capabilities).
 Internet works when directly plugged into the MBPro via yellow cable - good. 
 Also works through cable via airports.
 But,
 My wireless airport/ time-machines now don’t show up:
 error message:
 Wi-Fi has the self-assigned IP address 169.254.7.247 and will not be able to 
 connect to the Internet.
 
 Neither show up in the Airport utility, except under other WiFi devices and 
 they won’t connect from there.
 
 I have tried both soft and hard reset on the Airports.
 Have I missed something?
 Where have has my wireless network gone?
 
 Brian
 -- The WA Macintosh User Group Mailing List --
 Archives - http://www.wamug.org.au/mailinglist/archives.shtml
 Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
 Settings  Unsubscribe - 
 http://lists.wamug.org.au/listinfo/wamug.org.au-wamug

-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Settings  Unsubscribe - http://lists.wamug.org.au/listinfo/wamug.org.au-wamug-- The WA Macintosh User Group Mailing List --
Archives - http://www.wamug.org.au/mailinglist/archives.shtml
Guidelines - http://www.wamug.org.au/mailinglist/guidelines.shtml
Settings  Unsubscribe - http://lists.wamug.org.au/listinfo/wamug.org.au-wamug