StarWind Software

In fact ,it is necessary to store journal files on client when server is always overwhelmed.
I have a idea to do this.

server:
1. mkimage -sparse e:\disk.img 100G
2. mount disk.img, get a disk with patition F:
3. mkimage -sparse f:\file.img 90G
4. ibvolume image d:\ibv\disk.ibv 0 . e:\disk.img
5. issue disk.ibv with name disk

client:
1. initialize target disk, get a disk with patition F:
2. ibvolume image d:\ibv\local.ibv 0 . f:\file.img
3. issue local.ibv with name local
4. initialize target local(127.0.0.1), get a disk with patition G:

When copy files to G: , the client file d:\ibv\local_00000001.ibvd contains all changes.

My problem is, how to update files in file.img on server.
I try to update it, the client get a yellow error tip.

What you do is a totally wrong thing. You need initiator to track changes. Nobody currently implements this.

It works as soon as I do not change game.img.
I can do this when nobody connect.

You cannot have more then one "writer" connected at the same time.

wall wrote:It works as soon as I do not change game.img.
I can do this when nobody connect.

Hi!
I am still confused on this. I have my journals sent to a remote location, but I don't think these are all the required snapshot files that you refernce above. Is this not the point of placing the jornals in a different location?

Thanks,
Chris

Actually there is totally no point in doing this,
I would better recommend using remote replication(mirroring) feature for this scenario, and DPM for taking snapshots - if needed.
If you are really intersted in making this using only StarWind - I will ask if our developers have this idea in their roadmap.
Anyway, I would highly recommend to store the journals within the target server.

Thanks Max. I would really like to see this feature added and would be interested to know if its already a planned enhancement.

Thanks,
Chris

ctcline wrote:Thanks Max. I would really like to see this feature added and would be interested to know if its already a planned enhancement.

Thanks,
Chris

It is scheduled in the upcoming versions, we're working on this