As Steven and Milan have said, you don't need BackboneFast in your 3-switch triangle.
If your servers are connected to one switch, then make sure that switch is the Root Bridge in your Spanning Tree by running UplinkFast only on the other two switches. (If you run it on all three, there's no guarantee that the switch with the servers will be the Root Bridge.) This will give you a speedy recovery if you suffer a link failure on the forwarding link from the switch and the Root Bridge is working.
On any access port connecting to a PC, printer, server, or any kind of device that may be powered off and on frequently, run Spanning Tree PortFast. This will put the link into forwarding state sooner, and will prevent topology change notifications from being sent every time the link's status changes. NOTE: Do NOT run PortFast on the ports which connect the switches to each other.
If it's important to completely optimize your network, and you have only these 3 switches, you could reduce the STP Hello Time, Max Age, and Forward Delay parameters. Then, whenever the Root Bridge goes down, the election of a new Root Bridge would take half the time (14 to 24 seconds vs. 30 to 50 seconds). Don't change these parameters unless you understand exactly what you are doing, though; and keep in mind you will have to recalculate the values if you add switches later. Here's a link that explains it:
Understanding and Tuning Spanning Tree Protocol Timers
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...