Hello,
I am looking for information to reactivate dynamic disks programmatically
(I am aware that there is no documented or workaround API available). On
dump of LDM database shows “Volume state: ACTIVE” but where as disk
appears as inactive in disk mgmt wizard, on selecting “reactive” context
menu item makes all offline disk(s) active/online. On debugging found
reactive command calls “DoReactiveDisk” in dmdskmgr.dll which in-turn
calls other functions please see the attached assembly version of
DoReactiveDisk for more information, initially I was assuming that
reactive command is sending IOCTL to the driver(dmio) using
DeviceIocontrol to activate but seem it sets/clears some field in LDM
database which in-turn makes the disk active, I am trying hard to figure
out what exactly it’s doing so that I can write my own DoReactivate
function, would appreciate any help or some direction.
Veritas has an add-on product that enhances LDM, the Veritas Volume
Manager, that includes (perhaps for an additional fee,) an api for
programmatic access to some of the VM features. You should contact
Veritas. Anyone who knew the information that you are requesting would be
violating their license agreement with Veritas by disclosing it to you.
> Hello, > I am looking for information to reactivate dynamic disks > programmatically > (I am aware that there is no documented or workaround API available). > On > dump of LDM database shows “Volume state: ACTIVE” but where as disk > appears as inactive in disk mgmt wizard, on selecting “reactive” > context > menu item makes all offline disk(s) active/online. On debugging found > reactive command calls “DoReactiveDisk” in dmdskmgr.dll which in-turn > calls other functions please see the attached assembly version of > DoReactiveDisk for more information, initially I was assuming that > reactive command is sending IOCTL to the driver(dmio) using > DeviceIocontrol to activate but seem it sets/clears some field in LDM > database which in-turn makes the disk active, I am trying hard to > figure > out what exactly it’s doing so that I can write my own DoReactivate > function, would appreciate any help or some direction. > > Thanks in advance, > Anand > xxxxx@yahoo.com > > — > You are currently subscribed to ntdev as: xxxxx@hollistech.com > To unsubscribe send a blank email to %%email.unsub%%
Hi Mark,
First thanks for your response! Seems Vertitas stuff is kind of expensive
and also changes our current design/driver, we are thinking of going for
it for our next realese!
Found some work around (un-reliable some times) to bring offline disks, #Changed the start order for “dmload” driver to manual/on-demand start.
wrote a service application which loads the “dmload” after our driver
starts running/loaded.
Problem here is, on boot our driver attempts to retrieve the volumes
assigned to it from remote IP based storage it’s not predictable or
guaranteed when these volumes actually appear at the host, because of N/W
traffic and other issues, hence I cannot wait till all volumes appears and
if I trigger/start “dmload” just after out driver loads it activates
volumes that are discovered before the dmload started and any volumes
discovered after that are off-line!