Hi @NielsS,

I'll try to break down the topics in your post and give my thoughts based on the information provided.  Ultimately, you're responsible for your network, so do your own research before taking actions based on anyone's comments (even mine).

1. NAS Setup
   • It's probably best to use the NAS as the NAS and not try to dual purpose your Windows Server for SQL and file sharing.
   • I think LACP is more performant, but the aggregated links must connect to the same physical switch.  I'm not sure if this is required with the Adaptive Load Balancing, so maybe it would make it more reliable if one of the 3428s failed.  A 3428 failure would cause a lot of issues anyway, so I think I'd just go with LACP.
2. Connecting Switches
   • It doesn't sound like your sure about the current state of your network, so don't assume you can just start moving wires and nothing will break.
   • If your switches are already connected, then connecting them via the 10G port instead of the 1G port would work as before with the higher bandwidth only if you configure the 10G port to match the existing port's configuration.
3. Trunked Connection
   • This has nothing to do with 10G, but it's best to use the fastest and/or most reliable link to connect the switches.
   • With VLANs, the the trunk ports are configured as tagged members.
   • Refer to How to Configure VLAN on TP-Link Switch to view and update the VLAN config.
4. Need more than one VLAN
   • Refer to Common Questions About 802.1Q VLAN or other resources to see why you would want to use VLANs.
   • Verify your VLAN configuration.  Based on your comments, it's not 100% clear what this is.
   • If you don't have VLANs, consider the following.
     • VOIP, guest networks, security cameras commonly get their own VLAN.
     • It's common to have a management VLAN.
     • It looks like you AC is on it's own network, so that probably needs it's own VLAN
     • User's would get a VLAN.
     • Servers and/or printers could have their own VLAN.  This might be overkill for you and could stay on the user VLAN.
5. Router Concerns
   • It's not just for the intranet, it's also intranet routing, firewall (I hope) and likely other services (DHCP?).
   • Increasing the number of VLANs and adding approprate firewall rules to protect them will require more processing by the router.  Even with additional VLANs, your router should be fine as your network doesn't appear that big.
   • If your router is currently a bottleneck, you may want to consider an upgrade.

If you have specific questions about the the TP-Link switch configurations, it would be best to start a dedicated thread with as many details as possible.

  @D-C 

I would definately not just rewire the setup without also changing the settings. I just meant that rewireing is the easy bit.

The switches are currently not connected to eachother directly. They both connect to the router (as in my drawing).

I want to upgrade the connecten between them by conecting them to eachother (the red line in my drawing).
But for that to work, setup changes must be made and that's where I struggle.

Is it enough to set the SPF+ ports (#25-28) as Tagged for it to work (on both switches)? And then rewire...

Because thas't what it looks like on that link you gave. LAGS is only available on ports 1-8.

I'm hessitant to add a bunch of vlan's because as is, it works just fine. And when putting clients on one vlan and server/nas on another, they still need to reach eachother, so why bother putting them on separate vlan's?

I have to dig a bit deeper into the NAS to see about load balancing/LACP/failover.
I thought I found somewhere that you could connect to 2 switches rather than hooking both NAS ports to 1 switch to make it a "2GB connection".

Thanks sofar,

Niels

  @NielsS 

Is it enough to set the SPF+ ports (#25-28) as Tagged for it to work (on both switches)? And then rewire...

Setting ports as Tagged is a vague statement as you can not just tag a port.  You can make one or more VLANs tagged members of a port.  If you're 100% sure that you do not use VLANs, there is nothing to tag.  Otherwise you need to know which VLAN ids to make tagged members.

LAGS is only available on ports 1-8.

No. Each switch may have limitations on it's LAGG configuration and is documented in the user manual for each individual switch.

I'm hessitant to add a bunch of vlan's because as is, it works just fine.

Totally your decision if/when to make such changes.

And when putting clients on one vlan and server/nas on another, they still need to reach eachother, so why bother putting them on separate vlan's?

I mentioned that doing that "might be overkill for you."  Putting them in a different VLAN doesn't mean that they can not reach each other, but they can not reach each other by default which is a security benefit.  This and other reasons for using VLANs are in the Purposes section in Common Questions About 802.1Q VLAN doc.

I thought I found somewhere that you could connect to 2 switches rather than hooking both NAS ports to 1 switch to make it a "2GB connection".

LAGG w/ LACP in your case would be connecting both ports on the NAS to two ports on the same switch.  The total theoretical bandwidth is the sum of the links in the LAGG so 2G in this case.  An individual connection would be limited to the physical bandwidth of one LAGG member (1G).  Because your clients are all 1G connections, they would not exceed the physical limit on the 1G LAGG member anyway.

@D-C Hi, the tagged SPF ports are on vlan 1, far as i know. As you can see in the screenshot.

Should i add, at least, a vlan 10 instead? And that ID would need to be on both switches and on the router? And possibly on the AP too (if it even has a vlan option)?

Tia,

Niels