none
Luns gets shifted in the clustered environment

    Question

  • We have 2 SqlServers running in a clustered environment in 2 servers with 3 luns in the sanstorage. By default all the 3 luns are mounted in Node-1. A shared folder was created in one of the luns(SQLData) by an application user. The result was that

    the lun got moved to the second node. However the Sql instance was up.  When we tried to move the lun back to node-1

    we found that it was not possible. Is creating a shared folder in any of the lun a violation. What is the solution for creating

    a shared folder in any of the luns with out the luns getting moved to the other nodes.

    Wednesday, October 30, 2013 6:17 AM

Answers


  • the lun got moved to the second node. However the Sql instance was up.  When we tried to move the lun back to node-1

    we found that it was not possible. Is creating a shared folder in any of the lun a violation. What is the solution for creating

    a shared folder in any of the luns with out the luns getting moved to the other nodes.

    Hi ,

    When failover happens from node 1 to node 2 sharing for a folder is removed.

    Creating a shared folder cannot in anyway stop the proper failover of nodes.Now what I am guessing is its not related to shared folder but some issue with cluster configuration.

    Can you please share errorlogs.


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Wednesday, October 30, 2013 6:42 AM
  • check your cluster configrations and logs. Should be some issue with the configrations

    Please click the Mark as answer button and vote as helpful if this reply solves your problem

    Wednesday, October 30, 2013 6:54 AM
  • Eventviewer is the first place where you need to check and is it will most useful information. However cluster logs will be a bit hard to understand for a new user.

    Chandoo

    Wednesday, October 30, 2013 6:57 AM

All replies


  • the lun got moved to the second node. However the Sql instance was up.  When we tried to move the lun back to node-1

    we found that it was not possible. Is creating a shared folder in any of the lun a violation. What is the solution for creating

    a shared folder in any of the luns with out the luns getting moved to the other nodes.

    Hi ,

    When failover happens from node 1 to node 2 sharing for a folder is removed.

    Creating a shared folder cannot in anyway stop the proper failover of nodes.Now what I am guessing is its not related to shared folder but some issue with cluster configuration.

    Can you please share errorlogs.


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Wednesday, October 30, 2013 6:42 AM
  • check your cluster configrations and logs. Should be some issue with the configrations

    Please click the Mark as answer button and vote as helpful if this reply solves your problem

    Wednesday, October 30, 2013 6:54 AM
  • Eventviewer is the first place where you need to check and is it will most useful information. However cluster logs will be a bit hard to understand for a new user.

    Chandoo

    Wednesday, October 30, 2013 6:57 AM
  • Hi,

    These are the Logs from event viewer. 

    1)Cluster file server resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' failed a health check.
     This was because some of its shared folders were inaccessible.
    Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this
    cluster node using Server Manager and look for other events related to the Server service on this cluster node.

    2)Cluster resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    3)Cluster file server resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' cannot be brought online. The resource failed to
    create file share 'old daw' associated with network name 'SRV-SQL-VIR'. The error code was '2'. Verify that the folders exist
    and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for
    other related events on this cluster node. It may be necessary to restart the network name resource 'SRV-SQL-VIR' in this clustered service
    or application.

    4)Cluster resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    5)The Cluster service failed to bring clustered service or application 'SQL Server (MSSQLSERVER)' completely online or offline.
    One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

    6)Cluster resource 'SQL Server' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    7)The SQL Server (MSSQLSERVER) service terminated unexpectedly.  It has done this 1 time(s).

    Wednesday, October 30, 2013 7:06 AM
  • Hi

    These are the logs from event viewer.

    1)Cluster file server resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' failed a health check.
     This was because some of its shared folders were inaccessible.
    Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this
    cluster node using Server Manager and look for other events related to the Server service on this cluster node.

    2)Cluster resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    3)Cluster file server resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' cannot be brought online. The resource failed to
    create file share 'old daw' associated with network name 'SRV-SQL-VIR'. The error code was '2'. Verify that the folders exist
    and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for
    other related events on this cluster node. It may be necessary to restart the network name resource 'SRV-SQL-VIR' in this clustered service
    or application.

    4)Cluster resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    5)The Cluster service failed to bring clustered service or application 'SQL Server (MSSQLSERVER)' completely online or offline.
    One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

    6)Cluster resource 'SQL Server' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    7)The SQL Server (MSSQLSERVER) service terminated unexpectedly.  It has done this 1 time(s).

    Wednesday, October 30, 2013 7:06 AM
  • Hi,

    These are the logs from event viewer

    1)Cluster file server resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' failed a health check.
     This was because some of its shared folders were inaccessible.
    Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this
    cluster node using Server Manager and look for other events related to the Server service on this cluster node.

    2)Cluster resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    3)Cluster file server resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' cannot be brought online. The resource failed to
    create file share 'old daw' associated with network name 'SRV-SQL-VIR'. The error code was '2'. Verify that the folders exist
    and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for
    other related events on this cluster node. It may be necessary to restart the network name resource 'SRV-SQL-VIR' in this clustered service
    or application.

    4)Cluster resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    5)The Cluster service failed to bring clustered service or application 'SQL Server (MSSQLSERVER)' completely online or offline.
    One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

    6)Cluster resource 'SQL Server' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    7)The SQL Server (MSSQLSERVER) service terminated unexpectedly.  It has done this 1 time(s).

    Wednesday, October 30, 2013 7:07 AM
  • Hi,

    These are the logs from event viewer

    1)Cluster file server resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' failed a health check.
     This was because some of its shared folders were inaccessible.
    Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this
    cluster node using Server Manager and look for other events related to the Server service on this cluster node.

    2)Cluster resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    3)Cluster file server resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' cannot be brought online. The resource failed to
    create file share 'old daw' associated with network name 'SRV-SQL-VIR'. The error code was '2'. Verify that the folders exist
    and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for
    other related events on this cluster node. It may be necessary to restart the network name resource 'SRV-SQL-VIR' in this clustered service
    or application.

    4)Cluster resource 'FileServer-(SRV-SQL-VIR)(SQL Data)' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    5)The Cluster service failed to bring clustered service or application 'SQL Server (MSSQLSERVER)' completely online or offline.
    One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

    6)Cluster resource 'SQL Server' in clustered service or application 'SQL Server (MSSQLSERVER)' failed.

    7)The SQL Server (MSSQLSERVER) service terminated unexpectedly.  It has done this 1 time(s).

    Hello Binny,

    refer to these links

    http://technet.microsoft.com/en-us/library/ee830313(v=ws.10).aspx

    For detailed even id check this lick,see if any event ID is mentioned in error log

    http://technet.microsoft.com/en-us/library/dd354056(v=ws.10).aspx

    Erro code of 2 means system cannot find the path specified.


    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

    Wednesday, October 30, 2013 7:59 AM