SQL Server Set up Guide When using MirrorView/S Replication

Can someone point me to  any set up documentation? I am trying to set this up from scratch. I have two SQL Server 2008 Database servers and the systems databases are on C installed on each one. My SAN Administrator has presented the LUNS to my PRIMARY server so I can restore my user databases on there. I beleve that replication is also set up. We plan on initiating a failover by taking down the PRIMARY and then changing the SECONDARY Server Name to be the same as the primary

Do I move the systems databases on PRIMARY server onto the replicated SAN?

When we fail over how do I ensure that the SECONDARY database looks at the 'replicated' system database in order to pick up all the correct infromation?

Do I need to do a controlled failover first in order to repoint the SQL Server to the 'replicated' system databases in order to initally set up the environments for first time use and then failback? And it is only then that my systems is ready?

I'm new to this (I only read up about MirrorView in the past hour!). All the work so far has been done by the systems guys and we have only just been handed the DBA tasks so I need to catch up quick. I cant seem to find any documentation that tells you "this is how you set up a SQL server PRIMARY\SECONDARY pair for use with MirrorView Replication"

UPDATE:

What I have done is allocate a Drive on the LUN (E) and moved all system databases on there. On the SECONDARY I have labelled a local disk as E and installed the system database on there as part of the SQL Install.

I am guessing that when we failover to SECONDARY I can simply Remove the E drive letter from the local disk (make it Z or something else thats unused). And re-label the Replicated Secondary LUN which contains the Systems DBs as E. Then we we rename the SECONDARY server to be the same name as the PRIMARY, SQL Server will pick up the replicated systems DBs and all should work fine

NOTE: Just to be clear the reason why I want to replicate the System databases is because the SQL Server is using SQL Replication to multiple subscribers so I want this to continue on failover by tricking the SQL Server in thinking its the original server on failover

Many thanks in advance

Siz