Shared LUN for SQL Server Backup files I have a SQL Server 2012 instance running on a 2 Node Failover Cluster Instance. Both nodes are VMs running Windows 2012 Server R2.
The FCI has four shared LUNs: 1 for data files, 1 for log files, 1 for TempDB and 1 for Quorum. 

The Backup volume however is not a shared LUN. There’s a separate disk drive added on the VM (Node 1) for a backup drive. The other VM, Node 2 has its own local disk drive for backup location.

I use Ola Hallegren’s script for DB maintenance.

I am thinking about adding another shared LUN in the FCI and set it up as the backup location for both nodes. My thinking is that, this way if the SQL Server role fails over to Node 2, the backup files will still get saved on the same shared LUN for backup files. 

Question:
Are there any drawbacks, implication or gotchas with this setup? Any insights is much appreciated! Thank you.
Technically there should be no issue with backups being written to a shared LUN.  

As you are using 2012 you do have the option of sending backups to a network share as well which could reduce the complexity of the cluster if you have a fileserver that you can use just to reduce the overhead in a DR situation (as in not having to add the LUN to the cluster etc etc).

Looking at a couple of guides and articles around the place backup drives shared to the nodes is a common thing.

https://mssqltrek.com/2012/06/28/how-to-add-a-new-diskdrive-to-sql-server-failover-cluster/

Fairly verbose example of said process but confirms the validity of backups on shared storage in a cluster.