I currently have fiber vlan trunks between all of our buildings. We are adding another ip camera server and am looking to segregate traffic. I am thinking of dedicating a fiber link and putting it on the specific ip camera vlan so traffic for the cameras in those buildings would only use that fiber and not the fiber trunk back to the main office. I have attached a a drawing of the current layout plus additional links to be added. What is the best way to do this.
The short answer is, your proposed additional fiber in the diagram will not gain you any real advantage for VLAN 3.
All traffic from Packaging or Fiberglass, destined to the server in Shipping on VLAN 3, will still traverse the Core. (Presuming that you have already properly tuned your Spanning Tree settings to make the Core switch stack the root bridge.)
This is due to the Dell 5500 series switches only supporting regular 802.1D Spanning Tree and 802.1w Rapid Spanning Tree. What this means, is that in your entire switched domain in the diagram, there is only one Spanning Tree for all VLANs.
If you are set on adding additional links, and dealing with VLAN 3 in this way, you have several alternatives (viable or not, depending on your circumstances):
Install switches capable of running MST (Multiple Spanning Tree), which allows you to create VLAN to Spanning Tree mappings. (Your core switches (Dell 7048P) DO support MST, but the 5548P switches do not.) You could assign all other VLANS to MST Instance 1, and then assign VLAN 3 to MST Instance 3 (instance numberings are just for example). Then you would tune the settings so that the root bridge for MST Instance 1 is your core stack, and root bridge for MST Instance 3 is the Shipping switch.
Install another vendor's switches which are capable of creating a Spanning Tree instance for each VLAN. It is called different things by different vendors, PVST+ in Cisco, VLAN Spanning Tree in Juniper, etc. Similar to MST, tune the Per VLAN Spanning Tree instance for VLAN 3 to make the Shipping switch the root bridge for that instance.
With all of that said, there are still one main concern in my mind.
Why locate the server in the building with the Shipping switch? You would be better served by placing it in the main location with your Core switches.
If it MUST be attached to the Shipping switch, and you can't make changes to the switches to get a more robust Spanning Tree configuration, you still have a few options.
You could increase your bandwidth to each switch in order to handle the hair-pining of VLAN 3 traffic through the core. All of your Dell switches support LACP link aggregation, this would allow you to gain bandwidth easily between the switches to support the IP-Cameras.