Combine fracture VM folders
-
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
The issue is I don't have the server licenses. I would like to split these up like Dustin suggested.
Most of those workloads aren't things you'd want to use licenses for though, I would imagine. Network monitoring would basically always be a Linux or BSD workload item, I would think. I can't think of any reasonably competitive product that works or works as well on Windows. And if it isn't on Windows, no license needed.
I would agree for the longer term future. My linux/BSD knowledge is not quite up there yet but that is my goal for the year.
Monitoring is a good place to dip the proverbial toe, because if something goes wrong, only IT knows about it and the business isn't affected.
-
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
Microsoft Licensing is a very likely reason.
Your right on that.
Oh, I just went through, it is specifically SW Network Monitor. So that is Windows Server only, sorry missed that it was that specific tool.
Its all good. I want to get rid of that someday too if SodiumSuite is comparable? Do I have that correct?
-
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
Microsoft Licensing is a very likely reason.
Your right on that.
So an offset to this is you can easily setup a linux server to act as your file server. So you can "save" a license here. The other services, Email (I'm assuming exchange) has to be run on Windows as well does SW Network Monitor.
But you can easily replace SW network monitor with Zabbix or literally anything else, while using less system resources and not have to think about the licensing.
-
@dustinb3403 said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
Microsoft Licensing is a very likely reason.
Your right on that.
So an offset to this is you can easily setup a linux server to act as your file server. So you can "save" a license here. The other services, Email (I'm assuming exchange) has to be run on Windows as well does SW Network Monitor.
Email is Kerio Connect. Now GFI. They do have a Linux appliance but sometimes, if it ain't broke, don't fix it.
As for fileserver, I setup RBAC in AD and even with Samba 4.4, permissions are an issue. Like I mentioned to Scott, my lack of Linux knowledge could be the issue here.
But you can easily replace SW network monitor with Zabbix or literally anything else, while using less system resources and not have to think about the licensing.
I will look into Zabbix. It's just that SW network monitor does exactly what I need so I stuck with it.
-
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
Microsoft Licensing is a very likely reason.
Your right on that.
So an offset to this is you can easily setup a linux server to act as your file server. So you can "save" a license here. The other services, Email (I'm assuming exchange) has to be run on Windows as well does SW Network Monitor.
Email is Kerio Connect. Now GFI. They do have a Linux appliance but sometimes, if it ain't broke, don't fix it.
As for fileserver, I setup RBAC in AD and even with Samba 4.4, permissions are an issue. Like I mentioned to Scott, my lack of knowledge could be the issue here.
But you can easily replace SW network monitor with Zabbix or literally anything else, while using less system resources and not have to think about the licensing.
I will look into Zabbix. It's just that SW network monitor does exactly what I need so I stuck with it.
The biggest issue is it's forcing you to spend for Windows licensing which just doesn't make sense.
-
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
Microsoft Licensing is a very likely reason.
Your right on that.
Oh, I just went through, it is specifically SW Network Monitor. So that is Windows Server only, sorry missed that it was that specific tool.
Its all good. I want to get rid of that someday too if SodiumSuite is comparable? Do I have that correct?
SodiumSuite is awesome, but "comparable" would be a stretch. SS is developing rapidly and has some incredible management features about to release. It's agent based only currently (but there is a design to expand that) and so only monitors your smart endpoints like desktops and laptops today, not network devices like routers and switches. So there is overlap, but it's not complete overlap.
-
@dustinb3403 said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
Microsoft Licensing is a very likely reason.
Your right on that.
So an offset to this is you can easily setup a linux server to act as your file server. So you can "save" a license here. The other services, Email (I'm assuming exchange) has to be run on Windows as well does SW Network Monitor.
Email is Kerio Connect. Now GFI. They do have a Linux appliance but sometimes, if it ain't broke, don't fix it.
As for fileserver, I setup RBAC in AD and even with Samba 4.4, permissions are an issue. Like I mentioned to Scott, my lack of knowledge could be the issue here.
But you can easily replace SW network monitor with Zabbix or literally anything else, while using less system resources and not have to think about the licensing.
I will look into Zabbix. It's just that SW network monitor does exactly what I need so I stuck with it.
The biggest issue is it's forcing you to spend for Windows licensing which just doesn't make sense.
Yeah, Windows Server licensing, as it can't be used on a desktop OS. Not cheap, and it uses a fair amount of resources, so it's not generally a small VM. It can suck a large percentage of your platform IOPS.
-
@pmoncho said in Combine fracture VM folders:
I will look into Zabbix. It's just that SW network monitor does exactly what I need so I stuck with it.
Zabbix + SodiumSuite might be a nice combination. One for traditional network monitoring, one for the more robust tracking and reporting, helpdesk, and so forth.
-
@scottalanmiller said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
Microsoft Licensing is a very likely reason.
Your right on that.
So an offset to this is you can easily setup a linux server to act as your file server. So you can "save" a license here. The other services, Email (I'm assuming exchange) has to be run on Windows as well does SW Network Monitor.
Email is Kerio Connect. Now GFI. They do have a Linux appliance but sometimes, if it ain't broke, don't fix it.
As for fileserver, I setup RBAC in AD and even with Samba 4.4, permissions are an issue. Like I mentioned to Scott, my lack of knowledge could be the issue here.
But you can easily replace SW network monitor with Zabbix or literally anything else, while using less system resources and not have to think about the licensing.
I will look into Zabbix. It's just that SW network monitor does exactly what I need so I stuck with it.
The biggest issue is it's forcing you to spend for Windows licensing which just doesn't make sense.
Yeah, Windows Server licensing, as it can't be used on a desktop OS. Not cheap, and it uses a fair amount of resources, so it's not generally a small VM. It can suck a large percentage of your platform IOPS.
I did notice, a few versions ago, that it sucked up resources but with the latest release it has been pretty tame.
As for the Windows license, at the time, I had it already and the file/email server had the extra resources. So it didn't cost me anything but configuration time.
-
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
I will look into Zabbix. It's just that SW network monitor does exactly what I need so I stuck with it.
Zabbix + SodiumSuite might be a nice combination. One for traditional network monitoring, one for the more robust tracking and reporting, helpdesk, and so forth.
Will look into this after my current project.
-
@dustinb3403 said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@dustinb3403 said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
@pmoncho said in Combine fracture VM folders:
@scottalanmiller said in Combine fracture VM folders:
" via separate VMs
In this instance, it is a single VM doing three tasks.
This server does not get taxed very much. Network Monitor is more of a strain than email or file services.
I would highly recommend splitting these into three different VMs then. No reason not to, right?
Microsoft Licensing is a very likely reason.
Your right on that.
So an offset to this is you can easily setup a linux server to act as your file server. So you can "save" a license here. The other services, Email (I'm assuming exchange) has to be run on Windows as well does SW Network Monitor.
Email is Kerio Connect. Now GFI. They do have a Linux appliance but sometimes, if it ain't broke, don't fix it.
As for fileserver, I setup RBAC in AD and even with Samba 4.4, permissions are an issue. Like I mentioned to Scott, my lack of knowledge could be the issue here.
But you can easily replace SW network monitor with Zabbix or literally anything else, while using less system resources and not have to think about the licensing.
I will look into Zabbix. It's just that SW network monitor does exactly what I need so I stuck with it.
The biggest issue is it's forcing you to spend for Windows licensing which just doesn't make sense.
You are correct. That is why last year I started learning more Linux and create a goal for this year. I am tired of dealing with MS licensing for many little things.
Just Had a "Duh" moment.
Currently have vCenter 5.5 on a standalone W2K8 server license. That will be going away when I move to VCSA 6.5. This is not an OEM version so I can reuse that license. That will then provide me with the extra license to separate file server , email and SW.
The issue I have goes back to my original post in that I want to move the original fileserv1 VM folders to the local datastore. I want the NAS to only hold backup data only.
My current plan is, deal with current pressing issue of fileserv1 folders, my backup provider switches me to Veeam, I move to VCSA, upgrade ESXI Hosts to 6.5, and then begin to separate "roles" to multiple servers.
