Adding a new instance on a Active\Passive SQL2008 Cluster

Can any one point me to a microsoft paper that cleary highlights the memory requirements of the passive node. I want to confirm that it needs to have the same memoery avaliable in the machine as the active node. I have been told that I doesn't.

The current active node has 16gb of ram with 4gb allocated to the os and the other split across 3 sql instances. The passive node currently only has 8gb of RAM, wouldn't it need 16gb if that is what has been allocated.

Hi all

Storage engineers are planning to Upgrade storage Drive and that storage using for SQL Server 2005 Active /Passive cluster.

as DBA what action I have to take.

I am planning

1.Backup all Databases.(Inluding system)

2.Takning all Databases OFFLINE(make sure no body using Databases)

or

3.Stopping Instance and Agent .

which is the best way.

 

any advise is helpful for me.

---

SNIVAS

 

We have a SQL cluster server running with SQL 2005 Enterprise Edition SP2 on Windows 2003 Enterprise Edition.

Currently the cluster has 2 nodes with Active/Active. Now I need to add a new node as a Passive node. So after I have done it, the cluster will be a Active/Active/Passive cluster.

 

Because the cluster is a production server, I need to know exactly how I add a new node onto the current cluster without breaking anything. Also this is my first time to install a passive node, so it is difficult for me to understand how to install and configure it.

 

I have already added the physical node onto the cluster group so I can see the new node 'paused' from the Cluster Administrator.  Now I need to install the SQL but I am too nervous to run the installation p

Hi all,

I came again with couple question on SQL Server 2008 R2 side by side installation in Cluster(Active/passive on Windows 2003 SP2).

1.I have already have SQL Server 2000 SP4 Installation.
 
2.Can I start Installation(Side by Side) from Passive node ?

3.you want me give New SQL Server Netwrok name (Instance Configuration  Screen)?.

4.you want me give New Instance ID  name (Instance Configuration  Screen)?

5.Can I chose Excixting Clustore resource group or I need to Create New group which is the best ?

 

Thanks in advance

---

SNIVAS

Hello all

Part of Preparation for adding new Instance in Cluster I required

1. IP   - I got It

2. Network name    - I got It

3.free disk resources     - I got iSCSI drive but I have to intilize now.

Here my question is

I have to Intilize the "iSCSI" from Both ndoes or it is ok if I intilized from Active node.

Please advise me.

Thanks in Advance

---

SNIVAS

I upgraded the 1st node of a SQL2008 Cluster on Windows 2003 sp2, and this was after correcting a SQL2008 Cluster install by uninstalling and removing a node.   It was stable when I began the R2 install.  The first node went as planned, but it will not move past the setup phase where it does the install of the setup files, and the log shows this:

Running Action: PostMsiTimingConfigAction
2010-11-04 09:52:52 Slp: The object state property 'workflow' is null/empty.
2010-11-04 09:52:52 Slp: Error: Action "PostMsiTimingConfigAction" failed during execution.
2010-11-04 09:52:52 Slp: Completed Action: PostMsiTimingConfigAction, returned False

 

I had previously tried to install R2 which led to some corruption and required me to correct the 2008 install.  Following the instructions here :

http://msdn.microsoft.com/en-us/library/ms191295.aspx#BestPractices

 

In the past (SS 2005), I was able to apply patches to to the virtual cluster host and it automatically detected both nodes and applied the patch.  This incurred downtime due to a reboot, but i did not care since this was a new cluster build.

Now, in 2008, the information I am finding implies that you should apply on passive node, perform a failover and then apply on other node.  

I am curious if it is still possible to apply the patch like i did for SS 2005, where I just run the install a single time from the virtual cluster host, thereby letting the installer figure out  it is a cluster and apply to both nodes?

Hi all experts,

 

I pretty new in SQL database along with WinServ clustering, so please mind my knowledge level in the overall process.

http://s961.photobucket.com/albums/ae95/neoswo/?action=view&current=pic.jpg

Base on the screenshot above, we have currently a single cluster created base in which that is controlling DB1 and DB2. Primarily DB1 would be our Active node whereas DB2 would be our Passive, both have it's own designated Public and Private IP. After a small issue previously in which our cluster service failed, it seems that the failover has taken place in which at the moment is running on DB2, which bears the question now is would it be possible to have DB1 being the Active node without downtime? and what is the process flow to change reactivate it back?

Servers Details:

- Win2k3 Ent Application Server

- Win2k3 Ent DB1&2

- IBM DS5020 SAN Storage

On the disk management on each DB servers, we are not able to see the LUNs in DB1 (shown as Unreadable) whereas on DB2 it is shown as normal, in which we would assume that this is normal since DB2 is the active node.

Thanks for reading & most of my search base on this question ended up in this forum, which I would assume that this is the correct place to ask.

Regards.

What is meant by active/active clustering or active/passive clustering? and what is purpose of them  ( I am new to sql server)

I have set up many of the same clusters in the last few months, but this cluster specifically has been having lots of problems lately.  OS: Windows Server 2008 R2 latest patches SQL: SQL Server 2008 SP1 CU5 (version: 10.0.2746) Disks: VMAX SAN In the very beginning when I set up the cluster, the cluster validation kept failing when I tried to add a node.  Turned out that we had to unjoin the servers from the domain and rejoin.  Right after that the cluster validation succeeded, the second node joined the cluster, and quorum was changed to "Node and Disk Majority".  SQL was installed and set up as active/active (one sql instance on each node).  No issues then until SQL server was actually in use.  Symptoms: SQL server has heavy ETL processing plus being a subscriber of a sql replication.  The following errors first started on 4/24 when I set up sql replication (these servers are replication subscribers): EventID: 1127, Source: FailoverCluster, Task Category: Network Manager Cluster network interface 'man1fscl01a - Hartbeat to man1fscl91b' for cluster node 'man1fscl01a' on network 'ClusterHeartBeat' failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network comp

I have a production two-node cluster with sql server 2008 sp1 cu7 running over windows server 2008 sp2. If I were to install a new named instance on this live environment, would it impair the default sql server instance functionality? I'm not referring to processor/io while the install is in progress. My question specifically is would the install process by its nature bring down the default instance. I'm pretty sure it won't, but don't see any documentation that would confirm this. thanks.

I have successfully created a MSCS cluster and I have the SQL cluster up and running on the first node.   When I put the install cd in the second node and go through the install it fails with the error SQL Server Setup has encountered the following error:  Object reference not set to an instance of an object. I'm assuming I get this error because on the cluster node configuration screen the "cluster network name" box is blank.   It won't let me select a name or type a name. The SQL cluster is up and running on the first node.   I can ping the sql cluster network name from both boxes.   The setup shows the installed node and the node I"m trying to add, so I don't see any problem. I have Windows 2008 R2 on both nodes and I'm installing SQL Server 2008 R2.   Any idea how I can get past this error?    Thank you.

I've successfully used the upgrade functionality in SP 2010 to upgrade my list structures as needed. So far, these updates have been adding new fields to existing content types. Now, I have some new fields, content types and list instances to add, and am having trouble getting this accomplished. The scenario is this: - A new content type with a single custom field (also new), and a list instance for this new content type - A new field that is a lookup back to the new list instance defined above. This new field is added as an existing content type. - In my feature.xml, I have the Element Manifest specified with both new fields and an AddContentTypeField element for the new field being added to an existing content type:   <ApplyElementManifests> <ElementManifest Location="V1_04\Elements.xml"/> </ApplyElementManifests> <AddContentTypeField ContentTypeId="0x0100..." FieldId="{8028A1C8-1147-4DF7-B5C3-8A1F84A30360}" PushDown="TRUE"/> The result of running the update on this feature is: - My new field that is part of an existing content type is added - My new field that is part of a new content type/instance is added - My new content type and list instance is NOT created, therefore my lookup is broken Any idea why my new Content Type and List Instance is not being created? Do I need to specify there

we have a cluster with 2 nodes and we are thinking to add another instance so that node 1 takes care of instance 1 and node 2 takes care of instance 2, and at anytime they are watching each other's back. How is this done???? what is the procedure? thanks.  

I've successfully used the upgrade functionality in SP 2010 to upgrade my list structures as needed. So far, these updates have been adding new fields to existing content types. Now, I have some new fields, content types and list instances to add, and am having trouble getting this accomplished. The scenario is this: - A new content type with a single custom field (also new), and a list instance for this new content type - A new field that is a lookup back to the new list instance defined above. This new field is added as an existing content type. - In my feature.xml, I have the Element Manifest specified with both new fields and an AddContentTypeField element for the new field being added to an existing content type:   <ApplyElementManifests> <ElementManifest Location="V1_04\Elements.xml"/> </ApplyElementManifests> <AddContentTypeField ContentTypeId="0x0100..." FieldId="{8028A1C8-1147-4DF7-B5C3-8A1F84A30360}" PushDown="TRUE"/> The result of running the update on this feature is: - My new field that is part of an existing content type is added - My new field that is part of a new content type/instance is added - My new content type and list instance is NOT created, therefore my lookup is broken Any idea why my new Content Type and List Instance is not being created? Do I need to specify there

I am attempting to add a third node to a two node cluster. I am using the SS2K8 SP1 slipstream I used to successfully install the other two nodes. The new node of the cluster is:  Hardware: Dell R610 blade  OS: Windows Server 2008 R2 Enterprise 64 bit SQL: SQL Server 2008 SP1 64 bit Enterprise. The two node system has been running for months without problems. How do I fix a failure to add a file share for filestream because the value of group was null (Bold Italics below)? I have not found anything on the web that addresses this problem. Brad The bootstrap summary file woes content(s): Detailed results:   Feature:                       Database Engine Services   Status:                        Failed: see logs for details   MSI status:                    Passed   Configuration status:          Failed: see details below   Configuration error code:      0x11428655   Configuration error description: Value cannot be null.  Parameter name: group &nbs

Hi. I'm a sysadmin (or rather Jack of all trades) that also takes care of a MS SQL 2008 (standard) servercluster that is in an Active/Passive setup (2 servers, one active, one standby with files stored on a SAN with dual 10Gbps connection). We are currently hitting the limits of what a single SQL server (on our hardware) can handle. We are growing and our clients are as well. As such, we're starting to see slow-downs on SQL level (a part due to application design, but part simply due to capacity). I've been doing my best to read up on all options, where we can increase performance , yet maintain our current failover capacity . An ideal scenario would be to just make both nodes 'Active' and allow querying on both while their databases remain sync'ed in the event one of them were to fail. There is however no such thing as an "Active/Active" MS SQL 2008 cluster. I've been reading more and more about (Transactional) Replication, Mirroring, Log Shipping and so on, but either it does not really fit to our current situation, or it would require more hardware than I have at my disposal. I'm afraid I don't fully comprehend all the implications of the available technologies. Am I overlooking something? What solution would you suggest? The new setup must be capable of automatically failovering with no (or extremely minimal ) dataloss , yet get better performanc