I'm looking to add my gaming SSD to the drivepool to take advantage of the duplication (in the event of some wierd SSD corruption, I still have latest game data and don't have to redownload).
Is there a way to add the SSD to drive, prevent it for being used as a drive to store duplicate data, and also ALWAYS force Steam or U-play or whatever to read/write from the SSD, and not try to "read stripe" and read/write files from the duplicated portion which is on a WD Red? Thanks! I also have another question, but it's totally unrelated so it's in a separate thread.
Lex
EDIT - How's this for a possible solution.... a little convaluted... but hear me out....
Add the SSD to the drivepool. Uncheck duplicated and unduplicated in Drive Usage Limiter, therefore (if this does what I think it'll do) keeping any files being written to that drive unless I manually go to the hidden directory and write the files myself. Then point Steam, U-play, and any other programs to the direct path (through the hidden directory) of THAT drive, not to the pooled letter. Therefore forcing them to access the SSD directly... but the contents of the SSD ALSO are viewable, and therefore able to be duplicated, by the larger drivepool? Does that seem like it'll work?
Question
sfalexi
I'm looking to add my gaming SSD to the drivepool to take advantage of the duplication (in the event of some wierd SSD corruption, I still have latest game data and don't have to redownload).
Is there a way to add the SSD to drive, prevent it for being used as a drive to store duplicate data, and also ALWAYS force Steam or U-play or whatever to read/write from the SSD, and not try to "read stripe" and read/write files from the duplicated portion which is on a WD Red? Thanks! I also have another question, but it's totally unrelated so it's in a separate thread.
Lex
EDIT - How's this for a possible solution.... a little convaluted... but hear me out....
Add the SSD to the drivepool. Uncheck duplicated and unduplicated in Drive Usage Limiter, therefore (if this does what I think it'll do) keeping any files being written to that drive unless I manually go to the hidden directory and write the files myself. Then point Steam, U-play, and any other programs to the direct path (through the hidden directory) of THAT drive, not to the pooled letter. Therefore forcing them to access the SSD directly... but the contents of the SSD ALSO are viewable, and therefore able to be duplicated, by the larger drivepool? Does that seem like it'll work?
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.