This content has been marked as final. Show 2 replies
You can clone virtual disks to different repos.
Physical attachments shouldn't be an issue. Just detach them from your VM guests before you clone the VM. Attach them in the proper order. You're not changing VM servers. So..... ASM disks shouldn't matter as asmlib (if you're using asmlib and you should be) does mark the ASM disks with the proper headers/names. It does not matter what order they appear. The asmlib will find the path to the disk. UNLESS, you have restricted ASMlib to only search for certain disk paths. Most of the time this is necessary unless you have a lot of disks attached.
I never use more than one virtual system disk per host. I've never found a reason to do such. Its all the same repo. Same IO path/ IO paths. Why would you use different disks for swap? You just create a swap partition for your hosts on the same system disk...
I wound up doing a "move" which is like a clone but it deletes the VM from the source location when it's done. One thing that did happen though like I mentioned above is that it reordered a couple disks. It's a good thing ASM writes signatures like Solaris's ZFS, otherwise it could have been ugly.
The reason I put swap on a different disk is that I deployed that VM from a template to keep all the VM's the same. I had a base config of 2G swap and then add more with other disks to make the amount of swap I need in the target VM- some of them have different requirements for swap than others and it's easier to keep a small base of 2gb swap. Thanks for your input and sharing of info on ASM- it helps!