Skip to main content
Commonmark migration
Source Link

###Background

Background

I have an old MBP which works fine right now. I have no immediate plans to change it.

But it is getting old, the discrete GPU died, and I expect it could die at any time. I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already. Considering that and not wanting to be tied to macOS due to not having a solid cross-platform backup, here's my current backup strategy to allow either a Mac or linux based OS to be my next computer for my current data.

###modified backups

modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

As you an see - I'm not decided what filesystem I should use to rsync as Time Machine backs up to HFS+ and since I haven't picked a Linux it's not clear if I want / can mount HFS+ to read the backup data.

What setup allows me to restore my data that is backed up with rsync to any Linux?

###Background

I have an old MBP which works fine right now. I have no immediate plans to change it.

But it is getting old, the discrete GPU died, and I expect it could die at any time. I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already. Considering that and not wanting to be tied to macOS due to not having a solid cross-platform backup, here's my current backup strategy to allow either a Mac or linux based OS to be my next computer for my current data.

###modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

As you an see - I'm not decided what filesystem I should use to rsync as Time Machine backs up to HFS+ and since I haven't picked a Linux it's not clear if I want / can mount HFS+ to read the backup data.

What setup allows me to restore my data that is backed up with rsync to any Linux?

Background

I have an old MBP which works fine right now. I have no immediate plans to change it.

But it is getting old, the discrete GPU died, and I expect it could die at any time. I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already. Considering that and not wanting to be tied to macOS due to not having a solid cross-platform backup, here's my current backup strategy to allow either a Mac or linux based OS to be my next computer for my current data.

modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

As you an see - I'm not decided what filesystem I should use to rsync as Time Machine backs up to HFS+ and since I haven't picked a Linux it's not clear if I want / can mount HFS+ to read the backup data.

What setup allows me to restore my data that is backed up with rsync to any Linux?

Post Reopened by Allan, bmike
cut to the core of the question - what backup strategy allows linux to read data
Source Link
bmike
  • 241.3k
  • 80
  • 433
  • 958

what's What's a good way to keep my options opensetup to leaveback up macOS when my current machine diesdata and restore to Linux?

###Background

I have an old MBP which works fine right now. I have no immediate plans to change it.

But it is getting old, the discrete GPU died, and I expect it could die at any time. I generally like Apple products and am quite fond of macOS. Not so fond of the price, and especially the lack of user serviceability, of newer MBPs. You can't swap any parts on them and I find a 500GB SSD to be really on the stingy side of storage space for professional use.

###What backup strategies do I need to adopt now to allow migrating to Linux later?

  I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already.

I might very well stick with Apple when I need Considering that and not wanting to replace this machinebe tied to macOS due to not having a solid cross-platform backup, it depends on their offering at the time. But I wanthere's my current backup strategy to keepallow either a Mac or linux based OS to be my options open and avoid lock-innext computer for my current data.

Would the following approach work in practice? Any experience to share?

###modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

  • any other advice? Linux installation is out of the scope of this question, which is only about how to have a portable backup that can be loaded onto Linux later.

As you an see - I'm not decided what filesystem I should use to rsync as Time Machine backs up to HFS+ and since I haven't picked a Linux it's not clear if I want / can mount HFS+ to read the backup data.

What setup allows me to restore my data that is backed up with rsync to any Linux?

what's a good way to keep my options open to leave macOS when my current machine dies?

###Background

I have an old MBP which works fine right now. I have no immediate plans to change it.

But it is getting old, the discrete GPU died, and I expect it could die at any time. I generally like Apple products and am quite fond of macOS. Not so fond of the price, and especially the lack of user serviceability, of newer MBPs. You can't swap any parts on them and I find a 500GB SSD to be really on the stingy side of storage space for professional use.

###What backup strategies do I need to adopt now to allow migrating to Linux later?

I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already.

I might very well stick with Apple when I need to replace this machine, it depends on their offering at the time. But I want to keep my options open and avoid lock-in.

Would the following approach work in practice? Any experience to share?

###modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

  • any other advice? Linux installation is out of the scope of this question, which is only about how to have a portable backup that can be loaded onto Linux later.

What's a good setup to back up macOS data and restore to Linux?

###Background

I have an old MBP which works fine right now. I have no immediate plans to change it.

But it is getting old, the discrete GPU died, and I expect it could die at any time.   I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already. Considering that and not wanting to be tied to macOS due to not having a solid cross-platform backup, here's my current backup strategy to allow either a Mac or linux based OS to be my next computer for my current data.

###modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

As you an see - I'm not decided what filesystem I should use to rsync as Time Machine backs up to HFS+ and since I haven't picked a Linux it's not clear if I want / can mount HFS+ to read the backup data.

What setup allows me to restore my data that is backed up with rsync to any Linux?

added 21 characters in body
Source Link
JL Peyret
  • 1.2k
  • 6
  • 13
  • 24

###Background

I have a reallyan old, 2011 MBP which works fine right now. 17", RAM 16GB, fast aftermarket SSD I have no immediate plans to change it.

But it is getting old, the discrete GPU died, and I expect it tocould die at any time. I generally like Apple products and am quite fond of macOS. Not so fond of the price, and especially the lack of user serviceability, of newer MBPs. You can't swap any parts on them and I find a 500GB SSD to be really on the stingy side of storage space for professional use.

###What backup strategies do I need to adopt now to allow migrating to Linux later?

I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already.

I might very well stick with Apple when I need to replace this machine, it depends on their offering at the time. But I want to keep my options open and avoid lock-in.

Would the following approach work in practice? Any experience to share?

###modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

  • any other advice? Linux installation is out of the scope of this question, which is only about how to have a portable backup that can be loaded onto Linux later.

###Background

I have a really old, 2011 MBP. 17", RAM 16GB, fast aftermarket SSD.

But it is getting old, the discrete GPU died, and I expect it to die at any time. I generally like Apple products and am quite fond of macOS. Not so fond of the price, and especially the lack of user serviceability, of newer MBPs. You can't swap any parts on them and I find a 500GB SSD to be really on the stingy side of storage space for professional use.

###What backup strategies do I need to adopt now to allow migrating to Linux later?

I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already.

I might very well stick with Apple when I need to replace this machine, it depends on their offering at the time. But I want to keep my options open and avoid lock-in.

Would the following approach work in practice? Any experience to share?

###modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

  • any other advice? Linux installation is out of the scope of this question, which is only about how to have a portable backup that can be loaded onto Linux later.

###Background

I have an old MBP which works fine right now. I have no immediate plans to change it.

But it is getting old, the discrete GPU died, and I expect it could die at any time. I generally like Apple products and am quite fond of macOS. Not so fond of the price, and especially the lack of user serviceability, of newer MBPs. You can't swap any parts on them and I find a 500GB SSD to be really on the stingy side of storage space for professional use.

###What backup strategies do I need to adopt now to allow migrating to Linux later?

I would like to keep my option open to move to a Linux laptop when this machine dies. Most of the software I use is either open source or runs on Linux as well and I rely heavily on Terminal/bash already.

I might very well stick with Apple when I need to replace this machine, it depends on their offering at the time. But I want to keep my options open and avoid lock-in.

Would the following approach work in practice? Any experience to share?

###modified backups

  • keep frequent backups, but, rather than relying only on Time Machine, backup /Users/ via rsync as well. (what file system is my best bet here?)

  • run preliminary trials on restoring the rsync backups into a test Linux VM.

  • any other advice? Linux installation is out of the scope of this question, which is only about how to have a portable backup that can be loaded onto Linux later.

deleted 123 characters in body
Source Link
JL Peyret
  • 1.2k
  • 6
  • 13
  • 24
Loading
Post Closed as "Needs more focus" by fsb, mmmmmm, user11633, bmike
Source Link
JL Peyret
  • 1.2k
  • 6
  • 13
  • 24
Loading