Question Is it possible to have 2 disks, one writing and the other reading, synchronized?

[Santiago Andrea]

Is it possible to use two disks, one for reading and the other for writing and that they are synchronized, similar to mirrored RAID 1?

but I need little writing, so it would be a smaller disk

I have 2 disks
Disk A-Read Only (1TB)
Disk B-Write Only (120GB)

I read Windows Server WriteBack Cache somewhere, but there is very little information. Specifically, Disk A would redirect the writing to Disk B, without causing error

Thank you so much

 

[Santiago Andrea]

The objective being to make 9 other disks think they are the player's disk so 10 people can play the same game instead of only one person?

It is already working very well, only a couple of games want to write and they give an error, I saw something like writeback on Windows server, but I can't get more information

 

[Santiago Andrea]

The objective being to make 9 other disks think they are the player's disk so 10 people can play the same game instead of only one person?

It is already working very well, only a couple of games want to write and they give an error, I saw something like writeback on Windows server, but I can't get more information

 

[Santiago Andrea]

The objective being to make 9 other disks think they are the player's disk so 10 people can play the same game instead of only one person?

 

[USAFRet]

It is already working very well, only a couple of games want to write and they give an error, I saw something like writeback on Windows server, but I can't get more information

What, specifically, is this error?

 

[Moonstick2]

I saw something like writeback on Windows server, but I can't get more information

Writeback on Windows Server works like this:
1) You have a slow large disk and a fast small disk.
2) Your programs request writes to the slow large disk, (I believe) not knowing about the small fast disk.
3) Writeback writes the data to the fast small disk instead, because it's quicker. It then tells your programs the data has been written to the slow large disk.
4) When Writeback decides a file is too big or too old, it writes ("flushes") the file to the large hard disk.

It sounds like you've read a bit about this and think it sounds like exactly what you want, without realising about (4). "Too old" by the way can be a matter of seconds. Writeback is about speeding up write operations from the point of view of the user, but with the associated risk of data loss/corruption if (4) doesn't happen or gets interrupted, so the data isn't supposed to hang around on the small fast drive for too long.

Now, you might not care about these files the games are trying to write, but you're an edge case. For almost everybody else using Writeback, it's very important that the data finally ends up on the slow large disk when they've sent it. I find it hard to believe that Writeback would fail silently when trying to flush data to a read-only drive, and not instead throw up all sorts of alerts. Even if you know these game files to exist for a short enough time that they never reach the flush stage, I'm highly doubtful Writeback would connect happily to a read-only destination disk.

In short, you want to use Writeback to lose data, not keep it; the very opposite of what it's designed to do, which is probably why you can't find any information about that.

 

[Santiago Andrea]

I have no choice but to try a freezer software

 

[USAFRet]

I have no choice but to try a freezer software

And what is a "freezer software" ?

 

[Ralston18]

@Santiago Andrea

This software?

https://www.faronics.com/products/deep-freeze

And, if so, how do you understand that to work and how will you implement it?

 

[Santiago Andrea]

When freezing the iscsi disk of one PC, the other 9 PCs also show that it is frozen, testing Shadow Defender

 

[USAFRet]

When freezing the iscsi disk of one PC, the other 9 PCs also show that it is frozen, testing Shadow Defender

No.

That "deep freeze" is merely a saved Image.
Every night, or on whatever schedule, you write that saved Image back to the drive in question.
So that whatever write actions happened are then gone.


You are still not addressing the actual problem.

 

[Santiago Andrea]

I found a possible solution, with this software, https://www.ccdisk.com/