| Unique Visitors |
[int64]$capcitykb = ($capacity * 1gb) / 1kb
into this
[int64]$capcitykb = $capacity * 1048576
Not sure why but that did the trick for me.
Cheers.
]]>Hi Davros, You could also use the Perl SDK or one of the other VMware SDK\’s to achieve the same thing, but the PowerShell CommandLets are very powerful once you figure out how to use them. I\’ve also checked and this still doesn\’t work in vSphere 5.5 Update 2, even though the problem was meant to be fixed.
]]>Is there a simpler way than above? Say I already had the disks created, setup as independent etc. All I actually need to do is set the values:
scsi1:0.sharing = multi-writer
scsi1:1.sharing = multi-writer
for a VM named env-test
Can anyone help?
]]>FYI — http://houseofbrick.com/esxi-5-5-multi-writer-bug/
That post is based off of the work they did for us on a PoC I am leading for Oracle RAC VMs.
]]>Hi Lenny,
I haven’t installed Update 2 for ESXi 5.5 yet, but that is my understanding. This was a bug and has now been fixed. Next bug I’m trying to track down is running more than 26 ASM disks in one VM.
]]>It looks like it's fixed in vSphere 5.5U2
]]>Hi Mike, Yes you are correct. You can't really take a snapshot of the VM's using VMware based snapshots. However you can take storage based snapshots, or you can use RMAN. The preferred method is still to use Oracle RMAN integrated technologies. VMware doesn't yet recognise multi-writer disks or clusters with regard to their snapshot technology or other technologies including provisioning operations, storage vMotion etc.
]]>