The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
If an IBVolume device uses an ImageFIle as its base image, the image is readonly for other users, as changing of it will lead to broken IBVolume data.ibn wrote:first I created an Image file a.img ,
then I tried to create an IBVolume file b.ibv "based on existing image"
but always received errors.
--------------
at last , I removed the device a.img, and trid again to create an IBVolume
image based on existing a.img, and I received no errors .
-------------
so, it seems that I can not use an IBVolume image file and its base image
at the same time.
is this an error or a designed tech?
--------------
I heard there're ways to use an IBVolume image file and its base image
at the same time. or I hope so.
got a little confused.valery (staff) wrote: --------------
...
To use your ImageFile after creation of an IBVolume based on it, use 'Advanced creation options' in the IBVolume creation dialog.
Then choose 'Create IBVolume Image' and in the next dialog use the 'Create based on an existing image' radio button to specify the image file to be used to initialize the new IBVolume.
ibn wrote:and someone else provide their own IBVolume.dll ,
which enables us to use an IBVolume file and its base
Imagefile at the same time. (not read only)
When the auto-recovered IBVolume clients reconnect
to the server , they get updated files on its base Imagefile.
I don't know whether they build their own IBVolume.dll
with your product Starwind SDK. or do you support this?

This mode is not supported by RDS.ibn wrote:and someone else provide their own IBVolume.dll ,
which enables us to use an IBVolume file and its base
Imagefile at the same time. (not read only)
When the auto-recovered IBVolume clients reconnect
to the server , they get updated files on its base Imagefile.
I don't know whether they build their own IBVolume.dll
with your product Starwind SDK. or do you support this?
valery (staff) wrote:
This mode is not supported by RDS.
The base image for IBVolumes must be RO, if the child IBVolume allows RW access.
ibn wrote:by someone unknown.anton (staff) wrote:
Who are "they" you're talking about?
after a risky try , I found it working well
if you'd like it and you don't know it , I think maybe I can send you a copy

The problem is if the base image is changed, the child IBVolumes being currently used by clients has no chances to keep their logical structure that may lead to client-side errors.ibn wrote:the child IBVolumes need RW access , but don't need to save any changes. They use auto-recover mode.
and,
with some other IBVolume.dll , the base image need not be RO
yes, auto-restore is the point.valery (staff) wrote: ...
But in the 'auto-restored snapshot' mode it may be not a problem to update the master-image online...
We'll take a look at the issue and probably add the feature to the next version of StarWind...
ibn wrote:yes, auto-restore is the point.valery (staff) wrote: ...
But in the 'auto-restored snapshot' mode it may be not a problem to update the master-image online...
We'll take a look at the issue and probably add the feature to the next version of StarWind...
in many cases this feature is useful.
Thank you for attention.

ibn wrote:Thanks , for your quick reply.anton (staff) wrote:OK, we'll add it in the next minor update of the StarWind.
It doesn't matter any more.anton (staff) wrote: You did not answer where you've got "alien" IBVolume.dll yet...
I want official version
