One should cluster the SQL Server on replication. While implementing replicating, SQL Server cluster participates as Publisher and a Distributor. Use a file share located on cluster disk as the snapshot folder. This will failover replication if SQL Server fails.

When configuring a clustered SQL Server as a Distributor, SQL Server needs access to to a snapshot folder as a temporary holding. To escape all this, make the SQL Server a Publisher and not a Distributor. Locate Distributor on a non clustered SQL Server. His enables snapshot folder to exit on a non SQL Server negating the above said.

SQL Server - implications of server clustering on replication - May 05, 2009 at 22:00 PM by Rajmeet Ghai

Explain the implications of server clustering on replication.

Server clustering on replication involves many manual and tedious tasks. The required folder on shared disk resource needs to be created with appropriate share with appropriate permissions. Using the cluster Admin, the shared folder needs to be configured as a clustered shared folder.

SQL Server - implications of server clustering on replication - June 21, 2009 at 09:00 AM by Amit Satpute

Clustering involves a lot of complexities

If replication has to be implemented and the SQL Server cluster has to be involved as a Publisher and a Distributor, a file share located on the cluster disk resource should be used as the snapshot folder. By doing so, the replication will failover when SQL Server fails over.

A folder needs to be created manually on a shared disk resource along with granting the necessary permissions. Also, the shared folder needs to be configured using the cluster administrator as a cluster shared folder.