Veritas cluster windows 2008

So, on the first system, you install the Instance root directories on local disk e. When we get to the 'additional systems' section, I must admit that this section of the manual is very confusing:. If you choose to install the SQL database files to a shared disk in case of a shared storage configuration , ensure that the shared storage location is not the same as that used while installing SQL on the first system.

Do not overwrite the database directories created on the shared disk by the SQL installation on the first system. What I have done with SQL installations was to install on node 1, stop SQL, set Services to manual, deport the diskgroup on node 1, import the diskgroup on node 2 and map volume s to same drive letter s as node 1.

Rename the data directories on the shared drive that were created by node 1 installation, then repeat installation on node2 to match root and data directories.

Because everything is new, you can choose which data directories to keep. The contents should be identical. Where one should be very careful is when additional nodes are added once the Instance has gone into production with live data in the shared volumes. Here a 'dummy' or temporary volume should be used for initial installation on the new node. So, if the production instance has data on F-drive, then on the new node, mount a temporary volume to F-drive so that the instance can be installed to match the production instance paths exactly.

View solution in original post. On Netapp its an iGroup, where you put the wwn of both nodes in the iGroup and that determines who can mount the LUN on the system. Is this working? VCS is going to have to know how to bring the data luns online on the secondary system before it can update the SQL configuration on Node 2 to say that databases now exist on drive X. It makes sense, but there's not much information to go on.

Don't let the fact that they mention Netapp deter you, it will probably work very similarly in your environment. But this error is dispointing me, if I choose only the first node, the service group can be bring online. All databases are new, so there is no risk of overwriting production data.

The temp volume is only needed when you want to add another node once the instance has gone into production and you need to install to the same path without the risk of overwriting production databases. Communities View more. Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. Sign In. Go to solution. Jimb2k Level 4. Support Knowledge base Article: Last Published: Ratings: 0 0.

The following is logged for there source failure: System Event Log:. The following command will generatean up-to-date log:. Was this content helpful? Yes No Rating submitted. Please provide additional feedback optional :. Cancel Submit.