Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

Storage Cluster for vmware

Pages: 1 2

Hi,

I'm new to PetaSAN and looking for some kind of tutorial/howto to setup a storage cluster for vmware.

For my private lab i'm looking for a shared virtual storage solution.

i would like to have to storage nodes that are replicating like a RAID1 over the network. one iscsi path goes to the first node, the second to the second node.

if one node fails, the other takes over.

is there any howto on this?

tia

harald

look at the documentation, we have a quick start guide + a guide for vmware setup. Note that we do not support running PetaSAN as virtualized vms.

You do not need to worry or do anything special about high availability as it is built-in.

I already did this.

One thing is not clear to me:

I have 200GB on 2 nodes for testing.

The Cluster is reporting 400GB, shouldn't it be 200GB if it is a cluster?

The dashboard pie chart you see is the global "raw" available storage. If you write 1 GB from your vm, this value will decrease to 398 GB. Look at the Pool pages, you can create various pool with different replication factors such as 3x, 4x or EC pools, each will consume a different overhead from the global value.

As a side note, storage is thin provisioned, so you can create iSCSI disks whose total capacity exceeds global physical storage capacity, but as you fill your iSCSI disks you will need to add physical disks.

OK, then PetaSAN is already doing what i wanted.

 

But now I have the next problem.

the automatic discovery is not finding any target on the nodes.

I have another iscsi drive on the same subnet, so the network itself is working correct.

I'm using vmware 6.7.

any suggestion?

you mean you created 2 iscsi disks, the esxi can discover 1 but not the other ?

it is discovering an qnap iscsi target, but not the PetaSAN target.

did you use a dynamic ip assigned to the disk ? if yes can you ping the ip ?

Just tested, no ping possible.

can I access the cli to see the mapping of the nics?

sometimes vmware mix up the nics.

I checked the Mac addresses and mapping of the interfaces, all are correct.

the only interface that answers to ping is management.

none of the other interfaces is answering.

I'm pinging from the same subnet, so no routing involved.

any suggestions?

Pages: 1 2