Ok this is a bit complex - I run an OS volume on a machine that is a Hardware RAID controlled RAID 10 full of SSDs. This is also then backed up to another drive.
I am interested in installing some programs (mainly games) to a completely separate SATA internal SSD. In principle I know this won't be a problem, as the game files will just install to the SATA internal, and the OS on the RAID 10 will just call that data and run the game program.
What I AM concerned about though (something I always, always consider before hand given a bad data loss history) is what this will mean if any of the drives "die" and I have recover.
1. I know that installed programs, regardless of where the bulk of their files are actually saved, write some amount of data to the OS volume - in addition, I am fairly sure they edit the registry log of the OS to provide data pointers, and other meta-data that sits completely outside the program installation and the OS 'shortcut' to the installed data files.
2. When (rather than if) the OS volume FAILS (in my case its a RAID volume, but that shouldn't matter as the OS thinks its one disk anyway, so for these purposes it might as well, I believe, be considered a single SATA drive), I will have to rebuild it - presumably once the OS is either rebuilt or restored with an image, etc., the meta data written to the registry will be retained as well, allowing the program installs on the SATA internal to run.
3. Additionally, if the SATA internal drive were to FAIL, I'm wondering whether that will produce any issues for the OS volume, since assuming I get a new drive, and reinstall those programs, there will be 'leftover' registry files and probably residual other files on the OS which correspond to the new installation - I'm wondering whether there will be an installation conflict (or if the program will simply overwrite without incident).
4. Any other problems viz. backup and restoration that might be caused by having programs installed outside the OS volume that I can't think of?
I am interested in installing some programs (mainly games) to a completely separate SATA internal SSD. In principle I know this won't be a problem, as the game files will just install to the SATA internal, and the OS on the RAID 10 will just call that data and run the game program.
What I AM concerned about though (something I always, always consider before hand given a bad data loss history) is what this will mean if any of the drives "die" and I have recover.
1. I know that installed programs, regardless of where the bulk of their files are actually saved, write some amount of data to the OS volume - in addition, I am fairly sure they edit the registry log of the OS to provide data pointers, and other meta-data that sits completely outside the program installation and the OS 'shortcut' to the installed data files.
2. When (rather than if) the OS volume FAILS (in my case its a RAID volume, but that shouldn't matter as the OS thinks its one disk anyway, so for these purposes it might as well, I believe, be considered a single SATA drive), I will have to rebuild it - presumably once the OS is either rebuilt or restored with an image, etc., the meta data written to the registry will be retained as well, allowing the program installs on the SATA internal to run.
3. Additionally, if the SATA internal drive were to FAIL, I'm wondering whether that will produce any issues for the OS volume, since assuming I get a new drive, and reinstall those programs, there will be 'leftover' registry files and probably residual other files on the OS which correspond to the new installation - I'm wondering whether there will be an installation conflict (or if the program will simply overwrite without incident).
4. Any other problems viz. backup and restoration that might be caused by having programs installed outside the OS volume that I can't think of?