Install Muliti Instances On SQL 2005 Cluster With The Same Server Name
Mar 29, 2007
I am trying to install multi instances on my server cluster 2003 R2 Sp2. Because of the compatibility issues with my services I need to install both SQL 2000 and 2005. With 2000 I can easily specify the instance and servername. The server name can be the same, but the instance has to be different. Is this true for 2005? I have found so far that for every new instance that you create that you need to have a different virtual server name. How can you utilize the same virtual name and have multi insances
Hello all: looking for some general advice on proper approach. looking to move databases off of a clustered instance to a new (non-clustered) server. Got several issues i'd like some advice on.
1. This is an OLTP instance that's been around for a while & it's pretty well encrusted with apps & processes that attach to it. Therefore it would be a very good thing if we didn't need to change the connection information in several hundred places after the move. I've tested one approach to this that seems to work: moved the instance to a server which has the same name as the cluster resource associated with the clustered instance and an instance that has the same name as the clustered instance. For example: cluster install is aiproddbproduction, moved it to a box called aiproddb with a named instance called "production". There's a bunch of tedious network stuff that has to be done to make this work (binding an IP address to the MAC address of the new box and some murky DHCP reservation fiddling), but after the network crew got done cursing me it did finally work. Does this seem like a reasonable approach?
2. What's the best way to transfer security info to the new instance? I used the transfer Logins DTS widget but had some problems with it not being able to find some groups in AD.
3. what's the best way to transfer DTS packages?
4. is it necessary for the new instance to be at the same patch level as the old instance? the old clustered instance is still at SP3 and i threw the latest SP4 on the new location. good/bad/indifferent?
5. i was planning on taking a full backup & restoring it to the new machine. Is there a better way? Is the wizard for copying databases a good thing?
Those are these issues i'm aware of and have given some thought to. There are probably things about this i haven't considered and would appreciate some word on.
We have 5 instances on our clients old machine with SQL 2005, now they want us to move on cluster environment with SQL 2012.
Once I have installed and configured SQL cluster with single instance, but how to install SQL Cluster environment for Multiple instances.
Should I install all the instances first and than have to configure cluster ? OR Is there any way that first I will install cluster and than we can add the instances ?
I have found no real documentation on this, so any links would be greatly appreciated.
We have an existing 2 node active active cluster.
A default and and named instance SS2005 Enterprise Edition are installed on the cluster.
Recently we acquired new hardware, 2 servers, which we added to the cluster so we now have a 4 node cluster.
The 2 new nodes have OS etc installed.
Now i have installed sql on a new multi node cluster, i have upgraded sql server in an existing cluster BUT i have never installed sql on an existing cluster for new nodes for multiple instances.
Now i presume you simply run the install on one of the new nodes, do this for a default instance, selecting both 2 new nodes to installl on. And do this again for the named instance.
But in the past I have never been promoted for which nodes to install sql on, it simply does all the nodes BUT i do not want this.
And how will the cluster know where the binary files are for each instance on the new nodes?
In a nutshell, how do i install sql server 2005 for 2 new nodes in an existing 4 node cluster for multiple instances ?
I am trying to install SQL 2005 in a 2-node virtual Windows 2003 cluster. I set the cluster up through Virtual Server 2005 with 2 virtual nodes and one virtual domain. The nodes can connect to each other as well as the physical machine. When I try to install a fresh copy of SQL 2005 on my cluster, I get an error every time. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
******************************************* Setup Consistency Check Report for Machine: --SERVERNAME-- ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: IIS Feature Requirement, Result: Warning Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled Article: Pending Reboot Requirement, Result: CheckPassed Article: Performance Monitor Counter Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed Article: Minimum MDAC Version Requirement, Result: CheckPassed <Func Name='PerformDetections'> 1 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run: Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache Source File Name: datastoreclusterinfocollector.cpp Compiler Timestamp: Fri Sep 16 13:20:12 2005 Function Name: ClusterInfoCollector::collectClusterVSInfo Source Line Number: 883 ---------------------------------------------------------- Failed to detect VS info due to datastore exception. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56 ---------------------------------------------------------- Failed to find a cluster group that owned shared disk: J: WinException : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56
I have a cluster with 4 sql server 2000 instances and would like to upgrade 2 of these to sql server 2005 - is there any document or list of things to ensure I do
I would like to install SQL server 2005 cluster on Windows 2003 cluster. Is domain controller (AD and DNS) necessary for the SQL server 2005 cluster? If yes, may I install it on one of the SQL server 2005 cluster nodes? Thanks in advance
Hello All, I am trying the following script to upgrade SQL Server 2005 SP1 to SP2. I have an Active Passive cluster configuration. I have default instances of SQL Server. I am using the following script.
The sql server install fails to run. When I used the above command with just
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /quiet still the summary.txt file came with authentication success and that is all. I changed the above script and did
start /wait c:1sqlserversp2SQLSERVER2005SP2-KB921896-x86-ENU.exe /instancename=instancename of the cluster
This worked, however the install patched the passive node (DB engine, all the cluster unaware components) but failed to patch the DB engine on the Active node. I had to run the SQL Server sp2 install manually but still it did not patch the DB engine on the primary node
1. Can someone please help me with this issue as I want the unattended install to work. so it installs both active and passive node. I will post the final output and also the ADS script to do this as a bonus if this works.
Here is the summary.txt file.
********************************************************************************** Processes Locking Files Process Name Feature Type User Name PID msftesql Database Services Service 5152 MSSQLSERVER Database Services Service 4412 ResrcMon.exe Database Services Application SHOMSCSService 4688 ********************************************************************************** Product Installation Status Product : Setup Support Files Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 2153 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29506 Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file D:Microsoft SQL ServerMSSQL.1MSSQLData for user sqlservice. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive. ---------------------------------------------------------------------------------- Product : Integration Services Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : SQL Server Native Client Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Client Components Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : MSXML 6.0 Parser Product Version (Previous): 1129 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : SQLXML4 Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Backward Compatibility Product Version (Previous): 2004 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- Product : Microsoft SQL Server VSS Writer Product Version (Previous): 3042 Product Version (Final) : Status : Not Selected Log File : Error Description : ---------------------------------------------------------------------------------- ********************************************************************************** Summary One or more products failed to install, see above for details Exit Code Returned: 29506
When I tried to SQL Server 2005 (Standard) to two-node Windows 2003 servers, the Remote Setup task on the 2nd node hang. Here is the SQL Setup log. Please help figure out the cause of the problem. Thanks in advance.
Microsoft SQL Server 2005 Setup beginning at Tue Apr 24 16:17:14 2007 Process ID : 2864 \irv144C$SQL2005Std-x64disc1setup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2007/3/24 16:17:14 Complete: LoadResourcesAction at: 2007/3/24 16:17:14, returned true Running: ParseBootstrapOptionsAction at: 2007/3/24 16:17:14 Loaded DLL:\irv144C$SQL2005Std-x64disc1xmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2007/3/24 16:17:14, returned false Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run: Could not parse command line due to datastore exception. Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Fri Jul 29 01:13:55 2005 Function Name: writeEncryptedString Source Line Number: 124 ---------------------------------------------------------- writeEncryptedString() failed Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Fri Jul 29 01:13:55 2005 Function Name: writeEncryptedString Source Line Number: 123 ---------------------------------------------------------- Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified.
Source File Name: cryptohelpercryptsameusersamemachine.cpp Compiler Timestamp: Mon Jun 13 14:30:00 2005 Function Name: sqls::CryptSameUserSameMachine:rotectData Source Line Number: 50
2 Could not skip Component update due to datastore exception. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "2864"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Running: ValidateWinNTAction at: 2007/3/24 16:17:14 Complete: ValidateWinNTAction at: 2007/3/24 16:17:14, returned true Running: ValidateMinOSAction at: 2007/3/24 16:17:14 Complete: ValidateMinOSAction at: 2007/3/24 16:17:14, returned true Running: PerformSCCAction at: 2007/3/24 16:17:14 Complete: PerformSCCAction at: 2007/3/24 16:17:14, returned true Running: ActivateLoggingAction at: 2007/3/24 16:17:14 Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run: Datastore exception while trying to write logging properties. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupStateScope.primaryLogFiles Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupStateScope" 0000000000EDAF90Unable to proceed with setup, there was a command line parsing error. : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44
I an involved in a project that will have five sql server instances on an NT cluster. I cannot find anywhere on Technet info on what happens when a single instance fails. Do they all have to fail over or just the failed instance. This is important so that we get the disk layout correct.
Can anybody help ? or point me to any docs on this.
We have a new failover cluster (Windows 2003 SP1, Microsoft SQL 2000 SP4) with each node of the cluster hosting 7 SQL Server instances in a 2-node active-active configuration connected to a SAN. We are planning to move some SQL Server Instances(from existing stand-alone servers) into this Cluster. Any insight into the process of moving SQL Servers into the cluster would be highly appreciated.
Is it possible to have more than one instance of SQL Server on a failover Active/Passive cluster? What are the concerns/ramifications if that indeed is possible?
I have YET to have a 100% CLEAN install of SQL 2005 in a clustered environment. SQL 2005 Std. was not so bad, I think I finally managed a 99% clean install (no script errors on patches) on the third try.
SQL 2005 EE keeps erroring off on 2153 patch install. The error logs are no help at all; they simply stop logging activity at about the point that the error occurs.
Process: Install OS Patch OS to SP1 Cluster OS on SAN Configure Cluster Groups (DBC01, DBC02, DBC03) with cluster disks Configure MSDTC (network access, configure cluster resources)
Start SQL Installation Install RTM Binaries on Node 1 for Default Instance Install Workstation and non-cluster components on remaining nodes Install RTM Binaries on Node 2 for Named Instance
Reboot all nodes
Install SP1 for all instances from node 1
Install SP1 for all local services/applications for all other nodes
While attempting to install the 2153 SQL patch/hotfix, the process will either: Hang while waiting for the first passive node for the default instance; or Crash immediately with no error messages in the logs.
This is no nearly detailed enough, I know. I'm missing error messages and more. It's snowing outside and I have to get home. I just think that the installation for this product in a clustered environment is very unstraightforward at best, and at worst is a real liability to an organization since it's practically impossible to get it clean the first time through.
When you try to re-apply SP2 for SQL 2005 on node added to cluster it continously fails?
Only way to apply SP2 is to shut down original node(with SP2 allready applied) and then apply SP2 and hotfixes on additional node!
I would like to see some reply from SQL support team for this 'issue'. Is this normal? This bring many issues when you have more than one sql on 2 node cluster....etc
IF you need to change the IP Address of a SQL Server Failover Cluster instance, here is the steps:
1. Open up Failover Cluster manager. 2. Expand the MS Cluster Instance that your SQL Cluster instance resides on. 3. Expand Services and applications. 4. Select the SQL Server Service. 5. In the main window pane (Middle Screen), you should see your SQL Server Cluster name, expand the plus to the left of it. 6. Under your SQL Server Cluster name, you should now see an 'IP address' section, right click on it and go to properties. 7. In the properties pane, you can change your IP address by entering a static IP.....or assigning a DHCP enabled IP.
We have a SQL 2014 active passive cluster with 5 instances. When the cluster was installed one of the nodes was a virtual machine. As we started to have problems and this is not a Microsoft supported configuration we decided to replace the virtual node with a phyiscal one. On 3 of these 5 instances we configured static ports (1433 TCP) this was required for applications and firewall implementation.
Now with the physical node joined to the cluster we have issues with these three instances. Whenever one of these instances is moved to the passive node the server authentication is changed from mixed to windows only. I'm no SQL expert at all but to me it looks like the configuration of the instances are not replicated to the passive node? I found some similar problems on the net but these are mostly under sql 2008.
I am having a problem installing the first instance in our two node cluster. We're running 64-bit 2003. I'm trying to install the database engine and client tools only, so of course I get the IIS warning for both nodes. This is expected because I don't want Reporting Services. So the install should still work. However, I'm also getting the ASP.net registration message on only one node.
"Failed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS)."
I suspect that I should be getting the error on both nodes because I don't have IIS installed on either node. But again, I only get a warning for one node. This is probably the cause of my failure because it sees the nodes as being out of sync. I'm not sure how to correct this though when it appears that the nodes are exactly the same. Does anybody have any ideas? Thanks in advance!
Do I have install sp2 on each node in the cluster or do I just need to install it on the active node and reboot? Do I need to pause the active node? I was looking for some documentation for this and didn't mention anything regarding pausing the active node in the cluster in order to apply the sp2 for sql 2005.
I am trying to install a new database onto a SQL 2005 cluster with installshield and am getting an error that I can not find any info on. The error is as follows.
"Cannot use program file ... for cluster server. Only 4 metafiles on which the cluster resources of the server has a dependency can be used."
I will confess to knowing very little about clustering so any help would be greatly appreciated.
Hi we have a two node windows 2003 x64 cluster, each running a SQL 2005 instance. I've added a new node to the cluster and am now trying to set up a new instance of SQL 2005 on the new node (node c). During the install i am getting a failure just after the stage where you choose the features to install. I'm selecting SQL database engine with Failover Cluster. When i click next i get a message which states:
"The drive specified cannot be used for program location. Program Files must be installed on a valid local disk available on all cluster nodes. The valid values are"
I've read a number of articles about possible causes for this and i've checked all the suggested causes but none of these have made a difference. The cluster disk resource is healthy and can be failed between all nodes in the cluster. No errors are generated. I am using an account which has domain admin rights and I can access all admin shares on all nodes. Some of the articles i have referenced are here:
http://support.microsoft.com/kb/907261
http://support.microsoft.com/?kbid=913815
http://blogs.technet.com/mbaher/archive/2007/03/23/clustering-sql-2005-and-administrative-shares.aspx I've tried uninstalling all components etc but still i can't get it to work. The next step is rebuilding the server completely so does anyone have any suggestions?
I have a Cluster environment that has SQL 2000 Enterprise installed. I would like to install SQL 2005 Enterprise as well. What should I watch out for. Do I need to specify a named instance for the 05 install, setup is giving me the option and does see the 2000 instance? Is there a document that walks through this installation?
While I installed on the active node I got the following error: A recently applied update, KB921896, failed to install
After that installation finished , but query the server version I get: SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
9.00.1399.06 RTM Standard Edition
On the Visual Studion Manager Help About I get 9.00.3042
Error logs are below. Can you please tell me how can I overcome this?
TIA.
I paste here the summary and the hotfix logs of the primary node. There is also the Redist9_Hotfix_KB921896_SqlSupport.msi.log but it is too long to paste here.
summary.txt:
Time: 07/29/2007 02:46:28.253 KB Number: KB921896 Machine: DB1 OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790) Package Language: 1033 (ENU) Package Platform: x86 Package SP Level: 2 Package Version: 3042 Command-line parameters specified: Cluster Installation: Yes Log Location on Passive Nodes: (DB1) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix (DB2) C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfix
********************************************************************************** Prerequisites Check & Status SQLSupport: Passed
********************************************************************************** Products Detected Language Level Patch Level Platform Edition Setup Support Files ENU 9.1.2047 x86 Database Services (MSSQLSERVER) ENU RTM 2005.090.1399.00 x86 STANDARD Integration Services ENU SP1 9.00.2047.00 x86 STANDARD SQL Server Native Client ENU 9.00.2047.00 x86 Client Components ENU SP1 9.1.2047 x86 STANDARD MSXML 6.0 Parser ENU 6.00.3883.8 x86 SQLXML4 ENU 9.00.2047.00 x86 Backward Compatibility ENU 8.05.1704 x86 Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86
I am tying to set up an SQL 2005, SP1 failover cluster on a new set of hardware. Everytime I try to run the install, I get this error
TITLE: Microsoft SQL Server 2005 Setup ------------------------------
Setup failed to start on the remote machine. Check the Task scheduler event log on the remote machine.
I've gone through this doc (http://msdn2.microsoft.com/en-us/library/ms189910.aspx) and checked all of the applicable cautions:
I don't have an antivirus package running.
All of the SQL setup pre-checks run fine.
I have a SQL Group created, with the shared drive as a resource.
NBT is disabled on both heartbeat NIC's.
NBT is explicitly enabled on both external NIC's.
While I do have DDNS running, just to be safe I've pre-created an A record for my SQL VR.
Both nodes are registered in DNS and Setup correctly finds the second node.
In the Application event log on the second node (the one failing...), I get MSI Installer 'Install Started' successes (and sometimes I even get "Product: Microsoft SQL Server 2005 -- Installation completed successfully.")
I am running the install as myself, a Domain Admin and am explicitly added to the Administrators group on both servers.
Remote Registry is running.
Task Scheduler is running.
There is plenty of space everywhere.
All of the Admin shares are enabled.
The node I am running the install from is the owner of all of the cluster groups and resources:
Cluster group
MSDTC group
SQL group
This is all that is in my setup log:
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790) Time : Tue Nov 06 16:45:52 2007
Task did not appear to start on machine: \ERLEW01B: 267013
I'm at a total loss and I'm getting very frustrated...
1.) Is it possible to install Analysis Services on multiple SQL Server 2000 instances? If it is, then can you instruct me as to how to perform the install. If it is not possible, then does one restrict access to cube data via the Database Role Manager?
ie. The host box is - DOILAB30 with Analysis Services & SP2 Instance - DOILAB30/DOILAB30_FIN (Can AS be installed here?)
Do I severely restrict the membership of OLAP Admins?
2). Re. AS maintenance. - How do I backup and restore OLAP dbs/cubes etc. Following a restore, what issues, such as cube users/permissions should I be aware of? (if any).
I am having an existing sql 2005 cluster on an active passive cluster. I need to add analysis service to this as a new component. I am having enough space available in the cluster disks. Following are my queries,
1) do i need a new virtual ip and virtual server name for the analysis services ?
2) do i need a seperate cluster resource group for analysis services with an additional disk added ?
If I install a new named instance of SQL Server 2008 R2 on a machine that already has 3 named instances that are upgraded to service pack 3, will the install of the new instance overwrite any of the current SP3 files? Will I have to re-apply SP 3 to the existing instances?
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
I have a need to add a second Sql instance to an existing cluster. However I read in this article http://www.sql-server-performance.com/articles/clustering/clustering_best_practices_p1.aspx
that this is not recommended. Does anyone know why this is or what problems I may encounter?
Its is running Sql 2005 on a 64 bit windows Server 2003.
