Hi everyone,
I’ve read a bit here about using a separate drives for OS/Programs and data.
Curious about the benefits with this approach with SAC and any recommendations of how to go about the process.
Is it safe to assume SAC uses very little HD resources?
Thank you!
Multiple drive advice Win 10
Moderator: Bob L
-
Nicholas R
- Member
- Posts: 18
- Joined: Tue Oct 25, 2022 3:02 am
Re: Multiple drive advice Win 10
Not really any advantage with SAC. There are some advantages for programs that store a lot of data like SAW Studio. Although other than having a potentially removable data drive and general organizational house keeping, none of the potential performance issues exist with modern computers.Nicholas R wrote:Hi everyone,
I***8217;ve read a bit here about using a separate drives for OS/Programs and data.
Curious about the benefits with this approach with SAC and any recommendations of how to go about the process.
Is it safe to assume SAC uses very little HD resources?
Thank you!
Personally I do keep separate data drives on all of my audio systems, but that is specifically to keep my DAW audio files on a drive that is easy to swap and backup.
Additionally it reduces the overall wear on the system drives which do have a lifespan that is affected by use (both mechanical and SSDs are effected long term by usage - different wear mechanisms but eventually all of them will fail)
---------------------------------------
Philip G.
Philip G.
Re: Multiple drive advice Win 10
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.
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 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.
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.
Your question, "Is it safe?" And my simple answer is, "Yes! Absolutely!!"
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!!"