Cannot decide between 1U servers for growing company
-
@dafyre said:
The Scale systems are excellent. I know NTG has one. I've worked with their systems a couple of years ago, and the performance was night & day VS VMware and a similarly sized SAN. And their systems work really well.
Scale especially kicks butt for Windows performance because of their stack.
-
@ntoxicator - yup, we do that too - 10gig out of band from the LAN path for storage stack handling and cluster self-awareness.
-
@ntoxicator said:
Could I get away with dual Synology 12-bay NAS units? (running in HA/replication).
Well here is the issue there.... If you are doing this as a traditional NAS (NFS or SMB) for file shares like mapped Windows drives or automounted home directories for Linux users this works reliably and beautifully. The failover is smooth and transparent.
From shops that have tested this with virtualization, the failover is not fast enough and the VMs typically fail so that you don't get the failover that you are hoping for but instead an outage with potential of corruption. The failover is just not fast enough (at least in real world tested scenarios) to use with VM HA.
-
@Aconboy said:
@ntoxicator - yup, we do that too - 10gig out of band from the LAN path for storage stack handling and cluster self-awareness.
Yeah, we have a 10GigE fiber switching stack just to handle our OOB Scale communications! Talk about throughput capabilities!
-
So if anyone can explain to me
To do away with centralized storage such as what we have now and I've been moving to. I suppose this is what I've grown use to.
In order to have localized storage at the node/hypervisor level. one or many of the hypervisors would be storing all the data and sharing out the NFS? Then its replicated between? probably with DRBD Storage.
however, would would this be done with Citrix Xen Server for instance?
-
@ntoxicator said:
Essentially What I was looking to do was KVM / VM with complete HA.
I'm uncertain about keeping data local to individual servers. maybe because I have no experience with localized storage in an HA environment? Its all been shared centralized storage.
But you don't HA today. At least not at the storage level.
-
@ntoxicator said:
shit me for getting torn to shreds on here. Pissing contest.
Its much easier to verbalize than type out exact specifics.
What i meant by "I just seen as Windows iSCSI initiator working much better; more manageable and not limited."
Am I currently using windows iSCSI initator? NO
Do I wish I was using it: Yes?Why: Because I feel it would be easier to manage and connect an iSCSI LUN as localized storage and data storage. The larger 2TB storage holds all the windows network shares and user profile data.... thats the problem.
So disconnect the LUN from the XenServer and connect it directly to ProxMox, then give that drive to the windows VM. does that not work in ProxMox?
-
@ntoxicator said:
So if anyone can explain to me
To do away with centralized storage such as what we have now and I've been moving to. I suppose this is what I've grown use to.
In order to have localized storage at the node/hypervisor level. one or many of the hypervisors would be storing all the data and sharing out the NFS? Then its replicated between? probably with DRBD Storage.
however, would would this be done with Citrix Xen Server for instance?
there are a couple of methods used there in the hyperconverged space. Two different schools of thought emerged on how best to simplify the architecture while maintaining the benefits of virtualization.
-
Simply virtualize the SAN and it's controllers - also known as pulling the SAN into the servers. The VSA or Virtual San Appliance approach was developed to move the SAN up into the host servers through the use of a virtual machine. This did in fact simplify things like implementation and management by eliminating the separate SAN. However, it didn't do much to simplify the data path or regain efficiency. The VSA consumed significant host resources (CPU and RAM), still used storage protocols, and complicated the path to disk by turning the IO path from application->RAM->Disk into application->RAM->hypervisor->RAM->SAN controller VM->RAM->hypervisor->RAM->write-cache SSD->Disk.
-
Eliminate the dedicated servers, storage protocol overhead, resources consumed and associated gear by moving the hypervisor directly into the OS of the storage platform as a set of kernel modules, thereby simplifying the architecture dramatically while regaining the efficiency originally promised by Virtualization.
-
-
@ntoxicator said:
So if anyone can explain to me
To do away with centralized storage such as what we have now and I've been moving to. I suppose this is what I've grown use to.
In order to have localized storage at the node/hypervisor level. one or many of the hypervisors would be storing all the data and sharing out the NFS? Then its replicated between? probably with DRBD Storage.
however, would would this be done with Citrix Xen Server for instance?
You could also look at Starwinds Virtual SAN. Which could do this as well.
-
@scottalanmiller said:
It is that it is on a LUN now that is limiting you. If it was on a NAS instead of a SAN, you'd have more options.
Scott, where's your link explaining the difference?
-
@Dashrender said:
@scottalanmiller said:
It is that it is on a LUN now that is limiting you. If it was on a NAS instead of a SAN, you'd have more options.
Scott, where's your link explaining the difference?
One is block the other is file?
-
@coliver said:
@Dashrender said:
@scottalanmiller said:
It is that it is on a LUN now that is limiting you. If it was on a NAS instead of a SAN, you'd have more options.
Scott, where's your link explaining the difference?
One is block the other is file?
The purpose of my post was to show that the OP was using his NAS as both NAS and SAN simultaneously to ensure Scott's point wasn't being lost when he was indicating the use of a SAN or NAS.
-
@ntoxicator said:
So if anyone can explain to me
To do away with centralized storage such as what we have now and I've been moving to. I suppose this is what I've grown use to.
In order to have localized storage at the node/hypervisor level. one or many of the hypervisors would be storing all the data and sharing out the NFS? Then its replicated between? probably with DRBD Storage.
however, would would this be done with Citrix Xen Server for instance?
No NFS, SMB, iSCSI or anything involved with the DRBD scenario. It's raw block storage replication all the way down in the stack. Never need to look at high level stuff. The storage is visible to both nodes at the same time locally. No sharing protocols at all.
With XenServer you could do this yourself but for best results you'd likely use HA-Lizard which is a set of tools around DRBD on XenServer handling all of the complication for you. Not only is it free, but the HA-Lizard team participates here in the community a little.
-
@Dashrender said:
@ntoxicator said:
shit me for getting torn to shreds on here. Pissing contest.
Its much easier to verbalize than type out exact specifics.
What i meant by "I just seen as Windows iSCSI initiator working much better; more manageable and not limited."
Am I currently using windows iSCSI initator? NO
Do I wish I was using it: Yes?Why: Because I feel it would be easier to manage and connect an iSCSI LUN as localized storage and data storage. The larger 2TB storage holds all the windows network shares and user profile data.... thats the problem.
So disconnect the LUN from the XenServer and connect it directly to ProxMox, then give that drive to the windows VM. does that not work in ProxMox?
SANs do not work that way.
-
@coliver said:
@ntoxicator said:
So if anyone can explain to me
To do away with centralized storage such as what we have now and I've been moving to. I suppose this is what I've grown use to.
In order to have localized storage at the node/hypervisor level. one or many of the hypervisors would be storing all the data and sharing out the NFS? Then its replicated between? probably with DRBD Storage.
however, would would this be done with Citrix Xen Server for instance?
You could also look at Starwinds Virtual SAN. Which could do this as well.
But is limited to Hyper-V for best results and can make due in the VMware world but is inferior (but you shouldn't be looking at ESXi anyway so not a big deal.)
-
@scottalanmiller said:
@Dashrender said:
@ntoxicator said:
shit me for getting torn to shreds on here. Pissing contest.
Its much easier to verbalize than type out exact specifics.
What i meant by "I just seen as Windows iSCSI initiator working much better; more manageable and not limited."
Am I currently using windows iSCSI initator? NO
Do I wish I was using it: Yes?Why: Because I feel it would be easier to manage and connect an iSCSI LUN as localized storage and data storage. The larger 2TB storage holds all the windows network shares and user profile data.... thats the problem.
So disconnect the LUN from the XenServer and connect it directly to ProxMox, then give that drive to the windows VM. does that not work in ProxMox?
SANs do not work that way.
Do we need another thread for an explanation of why not? I don't understand why not, at least not as stated.
-
@scottalanmiller said:
@coliver said:
@ntoxicator said:
So if anyone can explain to me
To do away with centralized storage such as what we have now and I've been moving to. I suppose this is what I've grown use to.
In order to have localized storage at the node/hypervisor level. one or many of the hypervisors would be storing all the data and sharing out the NFS? Then its replicated between? probably with DRBD Storage.
however, would would this be done with Citrix Xen Server for instance?
You could also look at Starwinds Virtual SAN. Which could do this as well.
But is limited to Hyper-V for best results and can make due in the VMware world but is inferior (but you shouldn't be looking at ESXi anyway so not a big deal.)
Doesn't work well with Xen? I thought they supported it.
-
@Dashrender said:
@scottalanmiller said:
It is that it is on a LUN now that is limiting you. If it was on a NAS instead of a SAN, you'd have more options.
Scott, where's your link explaining the difference?
-
@Dashrender said:
@scottalanmiller said:
@Dashrender said:
@ntoxicator said:
shit me for getting torn to shreds on here. Pissing contest.
Its much easier to verbalize than type out exact specifics.
What i meant by "I just seen as Windows iSCSI initiator working much better; more manageable and not limited."
Am I currently using windows iSCSI initator? NO
Do I wish I was using it: Yes?Why: Because I feel it would be easier to manage and connect an iSCSI LUN as localized storage and data storage. The larger 2TB storage holds all the windows network shares and user profile data.... thats the problem.
So disconnect the LUN from the XenServer and connect it directly to ProxMox, then give that drive to the windows VM. does that not work in ProxMox?
SANs do not work that way.
Do we need another thread for an explanation of why not? I don't understand why not, at least not as stated.
Sure, just ask the question and I'll respond. I'm racing to keep up today between busy site and kids all over the place and my dad visiting
Ask the full question about moving from Xen to KVM because that's where the rub is. -
as I think about it, the LUN disconnect / reconnect might work as it is Linux handling the connection on both ends. Assuming you have Xen with Linux, but that's a safe assumption.
