First off I'm no DBA I'm an infrastructure guy.
I have a SQL server 2012 fail-over cluster with shared storage on a SAN. At the time of building I was advised to add the MSDTC resource to the cluster (i've never used MSDTC before).
Due to space issues I had to do some juggling of disks within the cluster so I had to move the DB and log locations ( I have a cluster disk each for logs, tempDB and all user and system DBs). I did this by presenting new disks to the cluster, shutting down
the SQL server resource itself (while keeping the disks online), copying the entire contents of each disk to the new one and then rename the drive letters on the new disks to that of the old. This worked fine when I moved the DB location but when I moved the
log location (which also had the MSDTC logs) and I tried to bring the cluster up it went into a failed state. Looking at the cluster it was only the MSDTC resource that was in a failed state so I removed it and cluster reported itself as being OK.
Unfortunately the user DBs are reporting all sorts of log inconsistency issues. Other than a full restore (which my disk juggling was trying to avoid) is there anything I can do?
Going forward I would still like to use the above disk juggling method so as to avoid a full restore - is this even possible?