Nexenta's new Namespace Cluster promises to scale out storage capacity and performance while also allowing users to connect to thousands of nodes to work together as one file system.
I'm trying to use WMI Explorer to query the root\MSCluster namespace on various hosts to obtain cluster resource group and resource object data. I can access the namespace with no issue on Win2K3 cluster nodes but am getting an access denied error attempting to connect to Win2K8 and Win2K8R2 nodes.
Software-defined storage (SDS) provider Nexenta announced the details of its new worldwide channel program June 3, with new channel chief Don Lopes stepping in to run the company’s international reseller business.
Nexenta, the OpenSolaris based distribution has released the fourth alpha of their server-oriented distribution. Nexenta uses Open Solaris as it's base and includes a number of Ubuntu software packages which make it a rather unique platform.
A report from Reuters says that Nexenta plans to IPO sometime in 2015. Nexenta is in the software-defined storage business. NexentaStor, the company’s core product, is built atop OpenSolaris/OpenStorage ZFS technology. The company also makes a free, full-featured, community supported edition called NexentaStor Community Edition.
I am trying to setup a failover cluster with two nodes. After running the validation tests, the storage sections had many warnings. The next step after creating the cluster with two nodes on the same domain is to add storage. I right click on storage and choose "add a disk", then I get the following error:
Anyone used Nexenta 4 and gotten it to work SMB2 with Mac OS X? No matter what I have tried, I can only ever get it to write to a share, never read from one. I have all the ACL's blasted with full permissions for my logged in user (and everyone@). I have the CIFS server joined to a workgroup and the CIFS server enabled.
We have a cluster with multiple ubuntu machines which are connected to a shared SAN storage. Initially we were using OCFS2 as file system but we were hit with so many issues and we couldn't find proper documentation or support therefore we have decided to move to another cluster system.