by mr_es335 » Mon Nov 07, 2022 9:53 am
Nicholas,
A number of "things" here, Nicholas:
1. I have always recommended a "multi-partition" scheme - whether this scheme consists of 1) a single drive [not-as-preferable], or 2) multiple drives [more-preferable].
2. I have always considered systems as subsisting of two different types of "data stores" - 1) application data, and 2) user data. And from my perspective, the two should never be mixed.
- The question - at least in my book is "Why?" Well, there are two possible reasons for this "scheme"...
Reason #1: This scheme makes user data back much simpler - epically for the novice user
Reason #2: This scheme makes the use of disk imaging software much more efficient.
- I have a simple principle, "Image applications, backup user data".
- The former is more of an "administrative thing", whilst the latter, is more of a "user thing".
- I generally manage the disk imaging for my client's systems, whilst the client manages the backup of their personal data.
- This scheme also permits 1) applications to be stored where applications are required to be so often stored, and, 2) user data, where user data should be stored.
I apply this very same scheme to all of my systems and have continued to do so since the early 90's.
Therefore, in my SAC/SAW systems, I have an SSD for boot and an HDD [mechanical] for data.
- I am not sure about you, but I am still not convinced that SSD's are trustworthy enough for user data. If an SSD must be employed, then I always suggest "backing up often".
Operating Systems/applications predominantly consist of, at least to my understanding, read operations, whilst data is both read-and-write operations.
Again, the benefits are "disk imaging" and "data backup" - as two, separate-and-distinct functions.
- As to how to go about doing, I prefer talking in person.
Your question, "Is it safe?" And my simple answer is, "Yes! Absolutely!!"
[size=100]Nicholas,
A number of "things" here, Nicholas:
1. I have always recommended a "multi-partition" scheme - whether this scheme consists of 1) a single drive [not-as-preferable], or 2) multiple drives [more-preferable].
2. I have always considered systems as subsisting of two different types of "data stores" - 1) application data, and 2) user data. And from my perspective, the two should never be mixed.
[LIST]
[*]The question - at least in my book is "Why?" Well, there are two possible reasons for this "scheme"...
[/LIST]
Reason #1: This scheme makes user data back much simpler - epically for the novice user
Reason #2: This scheme makes the use of disk imaging software much more efficient.
[LIST]
[*]I have a simple principle, "Image applications, backup user data".
[*]The former is more of an "administrative thing", whilst the latter, is more of a "user thing".
[*]I generally manage the disk imaging for my client's systems, whilst the client manages the backup of their personal data.
[*]This scheme also permits 1) applications to be stored where applications are required to be so often stored, and, 2) user data, where user data should be stored.
[/LIST]
I apply this very same scheme to all of my systems and have continued to do so since the early 90's.
Therefore, in my SAC/SAW systems, I have an SSD for boot and an HDD [mechanical] for data.
[LIST]
[*]I am not sure about you, but I am still not convinced that SSD's are trustworthy enough for user data. If an SSD must be employed, then I always suggest "backing up often".
[/LIST]
Operating Systems/applications predominantly consist of, at least to my understanding, read operations, whilst data is both read-and-write operations.
Again, the benefits are "disk imaging" and "data backup" - as two, separate-and-distinct functions.
[LIST]
[*]As to how to go about doing, I prefer talking in person.
[/LIST]
Your question, "Is it safe?" And my simple answer is, "Yes! Absolutely!!"
[/size]
