Fri Oct 01, 2010 1:46 pm
Damir, the beta has everything, but obviously features, functionality and performance can change between beta and release.
I'm not sure if I understand what you want to do correctly, but at the moment I don't know a way to do it without some downtime.
For a non-ha or ha img target, if you wanted to change the raid volume that the img was stored on, you'd have to remove the target, copy the img to the new raid volume, and then recreate the target. During that time the target wouldn't be accessible to clients.
Alternatively, you could create a new target on the new raid volume, connect your clients to it, and have the client move the data. The clients would see the new target as a new volume, even if you subsequently rename it to the old name. In windows, you can usually get away with this for non-boot volumes.
In a Hyper-V & CSV scenario, what I would do is create the new HA target, set it up as a new CSV volume, and do one of the following:
- create new VHDs and attach them to the VMs, and have the VMs migrate the data
- shut down the VMs and Export them to the new CSV, delete the old VM defnition and import the new one
- shut down the VMs, move the VHDs, change the location of the VHD in VM settings, start the VMs again - this will work if the definition of the VM is not moving
- Use the Quick Storage Migration feature of SCVMM - if all the VHDs are in the same location, and are moving all together to a new location, along with the VM definition, the VM will stay on-line for most of the migration. If not, the VM needs to be shut down first.
Migrating the location of the img whilst keeping the target online would be a VERY cool feature to have - if I am wrong and there is a way to do this, I'd really like to know how to do it!
cheers,
Aitor
