3

What are the risks of losing what's on my hard disc--especially programs--when I update Yosemite?

  • 1
    It is always advisable to do a backup before upgrading the OS, even if the procedure should (and usually does) leave user data and installed applications untouched. If you don't have a spare external drive, running at least your usual backup just before the upgrade should have you covered. – nohillside May 21 '15 at 12:24
  • The problem is that Time Machine won't protect apps like Adobe Design and Web Premium CS6. Will I need something like Carbon Copy Clone to save that sort of app? – David May 21 '15 at 12:44
  • 1
    TM backups applications stored in /Applications as well. – nohillside May 21 '15 at 15:18
1

Low as this does get tested before.

What is not tested as much is does each application work with the new OS. Apple can only test major apps it is the responsibility of the App's developer to test their app with the new OS and not all have the time to do this.

But as always with any computer change take backups as there is always a chance of something going wrong.

I assume that changing something will break something else. When it does I have to work out if it is worth living with that problem or revert to the old version.

Another example is professionally in enterprise software when I install a new version of my program I have to provide a tested process that will reverse the change as stopping something working can cost money

  • Like Mark said upgrading the O/S should not effect (or delete) any apps. And as long as they are compatible with the new O/S, it should work fine. As always, though, make a backup first just in case. – Steve Chambers May 21 '15 at 13:16
  • Amen to testing, backups and expecting/anticipating that things might not go swimmingly so that if they do, your mindset is already established. – bmike May 21 '15 at 13:21
0

The risks to a system being able to boot again are highest when you make fundamental changes to the OS as part of an upgrade.

This is due to three factors:

  • some parts of the code base are only called when swapping in and out a new system so those code paths don't run normally. Any degradation of the files (bit rot) will be discovered, but not necessarily caused at upgrade time.
  • any change has a very small chance of failing - more change, more chance
  • you run new migration steps from the vendor and they could run poorly or not anticipate the changes you have made to your system and cause data loss. This is mitigated by storage idioms like putting all user settings and app data in folders where the OS doesn't install any files. (i.e. the system is designed to not break thusly)

The risk to your data files is no higher during an upgrade than otherwise. If you don't care to back up the files anyhow, then you're always one disk error or drive failure away from losing data. If you have a good backup, you mitigate all the risk of upgrading other than the time you spend wiping and reinstalling the old system / old backup.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .