MDB Durables in Cluster Servers

Hello,
          we have two managed servers in cluster WebLogic Server8.1 SP4. We need to use MDBÂ´s Durables whit distributed queues.
          I have read that there are problems whit distributed topics and MDBÂ´s durables, that only works if the MDBÂ´s have different jms-client-id in each node of cluster.
          There are the same problem whit distributed queues?, can we deployed the same MDB in cluster whit distrubuted queues?
          Thanks in advance, Lourdes Ruiz.

Hi,
          I think you're refering to "durable topic subscriptions". The issues surrounding using "durable topic subscriptions" with distributed topics do not apply to distributed queues.
          In general, the term "durable" in JMS specifically refers to "long-lived" topic subscriptions, not to queues or persistent messages. Queues don't have the concept of "durable consumers".
          Tom

Similar Messages

MDB/Topic/WLS cluster question

          Hi
          I was going through some WLS 8.1 docs on JMS and had a question abt Topics & WLS
          in cluster config where say I have 3 servers with say server#1 hosting the Topic
          [not a distributed destination]. I have an an ear file containing an MDB with
          no pool size limit. After deploying the ear in the cluster - lets say that each
          server on the cluster has 5 instances of the MDB [just an example] and a message
          is published on the Topic.
          Q1>Will all the 3 servers get a [one and only one] copy of that message? [my guess
          is yes]
          Q2>Only 1 instance [out of 5] of the MDB/per server will get the message - right?
          Q3> Had I had a separate deployment of the same MDB class in the EAR file for
          the same Topic - thats just going to get treated as a completely separate subscriber
          independent of the first MDB though the implementing class is the same - right?
          thanks
          Anamitra


          Anamitra wrote:
          > Hi
          > I was going through some WLS 8.1 docs on JMS and had a question abt Topics & WLS
          > in cluster config where say I have 3 servers with say server#1 hosting the Topic
          > [not a distributed destination]. I have an an ear file containing an MDB with
          > no pool size limit. After deploying the ear in the cluster - lets say that each
          > server on the cluster has 5 instances of the MDB [just an example] and a message
          > is published on the Topic.
          >
          > Q1>Will all the 3 servers get a [one and only one] copy of that message? [my guess
          > is yes]
          Yes.
          > Q2>Only 1 instance [out of 5] of the MDB/per server will get the message - right?
          Yes.
          > Q3> Had I had a separate deployment of the same MDB class in the EAR file for
          > the same Topic - thats just going to get treated as a completely separate subscriber
          > independent of the first MDB though the implementing class is the same - right?
          Yes.
          >
          > thanks
          > Anamitra
          >
          For a little more information, I'm attaching notes on durable
          subscriber MDBs.
          A JMS durable subscription is uniquely identified within a cluster by a combination of "connection-id" and "subscription-id". Only one active connection may use a particular "connection-id" within a WebLogic cluster.
          In WebLogic 8.1 and previous, a durable topic subscriber MDB uses its name to generate its client-id. Since JMS enforces uniqueness on this client-id, this means that if a durable subscriber MDB is deployed to multiple servers only one server will be able to connect. Some applications want a different behavior where
          each MDB pool on each server gets its own durable subscription.
          The MDB connection id, which is unique within a cluster, comes from:
          1) The "ClientId" attribute configured on the WebLogic connection factory.
          This defaults to null. Note that if the ClientId is set on a connection
          factory, only one connection created by the factory
          may be active at a time.
          2) If (1) is not set, then, as with the subscriber-id,
          the connection-id is derived from jms-client-id descriptor attribute:
          <jms-client-id>MyClientID</jms-client-id>
          (the weblogic dtd)
          3) If (1) and (2) are not set, then, as with the subscriber-id,
          the connection-id is derived from the ejb name.
          The MDB durable subscription id, which must be unique on its topic, comes from:
          1) <jms-client-id>MyClientID</jms-client-id>
          (the weblogic dtd)
          2) if (1) is not set then the client-id
          comes from the ejb name.
          The above prevents a durable topic subscriber MDB from running on multiple servers. When an instance of the MDB starts on another server, it deploys successfully, but a conflict is detected and the MDB fails to fully connect to JMS. The work-around is the following:
          A) Create a custom connection-factory for each server:
          1) configure "JNDIName" to the same value across all servers
          ("myMDBCF" in this example)
          2) configure "ClientId" to a unique value per server
          3) enable "UserTransactionsEnabled"
          4) enable "XAConnectionFactoryEnabled"
          5) set "AcknowledgePolicy" to "ACKNOWLEDGE_PREVIOUS"
          6) target the CF at a single WebLogic server
          (Number 5 is required for non-transactional topic MDBs)
          B) In the MDB's weblogic-ejb-jar.xml descriptor, set the MDB's connection
          factory to the JNDI name of the custom connection factories configured in
          (A). Optionally, also specify the subscriber-id via the jms-client-id
          attribute.
          <weblogic-ejb-jar>
          <weblogic-enterprise-bean>
          <ejb-name>exampleBean</ejb-name>
          <message-driven-descriptor>
          <connection-factory-jndi-name>myMDBCF</connection-factory-jndi-name>
          <jms-client-id>myClientID</jms-client-id>
          </message-driven-descriptor>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
          C) Target the application at the same servers that have the custom connection
          factories targeted at them.
          Notes/Limitations:
          1) If the MDB is moved from one server to another, the MDB's corresponding
          connection-factory must be moved with it.
          2) This work-around will not work if the destination is not in the same
          cluster as the MDB. (The MDB can not use the local connection factory, which
          contains the connection-id, as connection factories do not work unless they
          are in the same cluster as the destination.)
          3) This work-around will not work for non-WebLogic JMS topics.
          4) A copy of each message is sent to each to each server's MDB pool.

MDB in a Cluster using Local JMS Queue (not distributed)

          Can I create a MDB that receives messages from a Local JMS Queue (created on each
          node) rather than a distributed queue?
          When I try to deploy such an MDB I get the following exception:
          weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException:
          activate failed for TestLocalMDBCluster Module: TestLocalMDBCluster Error: Exception
          activating module: EJBModule(TestLocalMDBCluster,status=PREPARED) Unable to deploy
          EJB: AsyncProcessor from TestLocalMDBCluster.jar: [EJB:011046]Unable to create
          EJBRuntimeMBean. javax.management.InstanceAlreadyExistsException: mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,Location=Node2,Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,ServerRuntime=Node2,Type=MessageDrivenEJBRuntime
          at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
          at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
          at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
          at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
          at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
          at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
          at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
          at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
          at weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.java:33)
          at weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:30)
          at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDrivenBeanPoolInfoImpl.java:182)
          at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.activate(MessageDrivenBeanPoolInfoImpl.java:245)
          at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.activatePoolInfo(MessageDrivenBeanInfoImpl.java:474)
          at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanInfoImpl.java:440)
          at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1327) at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
          at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
          at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
          at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
          at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
          at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
          at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
          at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
          at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Is there any way to do this?


I assume you are using queues.
          I truly wonder what you are doing different. Since the
          error is occuring outside of JMS and in the EJB - before JMS is called -
          I suggest posting to the ejb newsgroup.
          Note that yours is a standard use case which distributed destinations
          are actually specifically designed for (if you
          are using customer connection factories, just
          make sure ServerAffinity is enabled on the connection factory to
          ensure that clients always connect to the local physical destination,
          configure the MDB to refer to the JNDI name of the distributed
          destination, and then target the MDB to the cluster - an MDB pool
          will then automatically be dedicated to each physical destination).
          Tom
          Mark Colwell wrote:
          > Nope. It happens every time we try the scenario no matter what the application
          > is or which cluster. It always happens if we try to deploy even just a single
          > MDB (no other beans in the jar) to a cluster where the queue specified in the
          > deployment descripter is a local queue created on each node in the cluster. When
          > the jar is deployed we get the error.
          >
          > We have a strange situation were we really need the queue to be local and not
          > distributed but existing on every node. We can create all the local queues no
          > problem but trying to then deploy the application goes boom.
          >
          > Thanks for the response!
          >
          > Cheers,
          > Mark
          >
          > Tom Barnes <[email protected].bea.com>
          > wrote:
          >
          >>Mark Colwell wrote:
          >>
          >>
          >>>Can I create a MDB that receives messages from a Local JMS Queue (created
          >>
          >>on each
          >>
          >>>node) rather than a distributed queue?
          >>
          >>Yes. In fact this is the most common use case.
          >>
          >>
          >>>When I try to deploy such an MDB I get the following exception:
          >>
          >>I don't recall seeing this exception before. It looks like a naming
          >>conflict - it appears that somehow something is already running with
          >>the same name. Are you somehow deploying the same app twice?
          >>
          >>javax.management.InstanceAlreadyExistsException:
          >>mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,
          >>EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,
          >>Location=Node2,
          >>Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,
          >>ServerRuntime=Node2,
          >>Type=MessageDrivenEJBRuntime
          >>
          >>FYI: As of one or two weeks ago, the MDB section of the
          >>EJB docs has been heavily updated. I highly recommend
          >>reading it.
          >>
          >>
          >>>weblogic.management.DeploymentException: Exception:weblogic.management.ApplicationException:
          >>>activate failed for TestLocalMDBCluster Module: TestLocalMDBCluster
          >>
          >>Error: Exception
          >>
          >>>activating module: EJBModule(TestLocalMDBCluster,status=PREPARED) Unable
          >>
          >>to deploy
          >>
          >>>EJB: AsyncProcessor from TestLocalMDBCluster.jar: [EJB:011046]Unable
          >>
          >>to create
          >>
          >>>EJBRuntimeMBean. javax.management.InstanceAlreadyExistsException: mydomain:ApplicationRuntime=Node2_TestLocalMDBCluster,EJBComponentRuntime=Node2_TestLocalMDBCluster_TestLocalMDBCluster,Location=Node2,Name=Node2_TestLocalMDBCluster_TestLocalMDBCluster_AsyncProcessor_jms/myserver,ServerRuntime=Node2,Type=MessageDrivenEJBRuntime
          >>>at com.sun.management.jmx.RepositorySupport.addMBean(RepositorySupport.java:134)
          >>>at com.sun.management.jmx.MBeanServerImpl.internal_addObject(MBeanServerImpl.java:2371)
          >>>at com.sun.management.jmx.MBeanServerImpl.registerMBean(MBeanServerImpl.java:876)
          >>>at weblogic.management.internal.RemoteMBeanServerImpl.private_registerMBean(RemoteMBeanServerImpl.java:582)
          >>>at weblogic.management.internal.RemoteMBeanServerImpl.registerMBean(RemoteMBeanServerImpl.java:524)
          >>>at weblogic.management.runtime.RuntimeMBeanDelegate.register(RuntimeMBeanDelegate.java:166)
          >>>at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:122)
          >>>at weblogic.management.runtime.RuntimeMBeanDelegate.<init>(RuntimeMBeanDelegate.java:85)
          >>>at weblogic.ejb20.monitoring.EJBRuntimeMBeanImpl.<init>(EJBRuntimeMBeanImpl.java:33)
          >>>at weblogic.ejb20.monitoring.MessageDrivenEJBRuntimeMBeanImpl.<init>(MessageDrivenEJBRuntimeMBeanImpl.java:30)
          >>>at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.initPool(MessageDrivenBeanPoolInfoImpl.java:182)
          >>>at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.activate(MessageDrivenBeanPoolInfoImpl.java:245)
          >>>at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.activatePoolInfo(MessageDrivenBeanInfoImpl.java:474)
          >>>at weblogic.ejb20.deployer.MessageDrivenBeanInfoImpl.deploy(MessageDrivenBeanInfoImpl.java:440)
          >>>at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1327)
          >>
          >>at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:610)
          >>
          >>>at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:3127)
          >>>at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2081)
          >>>at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2062)
          >>>at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.activateContainer(SlaveDeployer.java:2592)
          >>>at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.doCommit(SlaveDeployer.java:2515)
          >>>at weblogic.management.deploy.slave.SlaveDeployer$Task.commit(SlaveDeployer.java:2317)
          >>>at weblogic.management.deploy.slave.SlaveDeployer.commitUpdate(SlaveDeployer.java:608)
          >>>at weblogic.drs.internal.SlaveCallbackHandler$2.execute(SlaveCallbackHandler.java:35)
          >>>at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at
          >>
          >>weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >>
          >>>Is there any way to do this?
          >>
          >

Deploying MDB in a cluster...

Have any one been successful at deploying a Message Driven Bean in a
          cluster. The problem I am running in to is that on the second machine the
          MDB tries to deploy but does not find the name of the queue in the JNDI
          space. This is due to the fact that the JNDI replication has not occured
          when the second server is starting up. Later, when the JNDI replication has
          occured, the queue name DOES appear in the JNDI tree, but it's too late for
          the MDB which failed to deploy.
          Has any one gotten around this problem? Surely, there must be someone out
          there who is also trying to deploy MDB in a cluster.
          Thanks.
          -AP_


Have any one been successful at deploying a Message Driven Bean in a
          cluster. The problem I am running in to is that on the second machine the
          MDB tries to deploy but does not find the name of the queue in the JNDI
          space. This is due to the fact that the JNDI replication has not occured
          when the second server is starting up. Later, when the JNDI replication has
          occured, the queue name DOES appear in the JNDI tree, but it's too late for
          the MDB which failed to deploy.
          Has any one gotten around this problem? Surely, there must be someone out
          there who is also trying to deploy MDB in a cluster.
          Thanks.
          -AP_

Best Practice when deploying a single mdb into a cluster

At a high level, we are converting all of our components to Weblogic processes that use Stateless Session Beans and Message Driven Beans. All of the weblogic processes will be clustered, and all of the topic queues will be distributed (Uniform Distributed Topics / Queues).
          We have one component that is a single MDB reading from a single queue on 1 machine. It is a requirement that the JMS messages on that queue be processed in order, and the processing of messages frequently requires that the same row in the DB be updated. Does anyone have any thoughts on the best design for that in our clustered environment?
          One possible solution we have come up with (not working):
          Possible Solution 1: Use a distributed topic and enforce a single client via client-id on the connection factory, causing a single consumer.
          1.Deploy a uniform-distributed Topic to the cluster.
          2.Create a connection factory with a client-id.
          3.Deploy a single FooMDB to the cluster.
          Problem with Solution 1: WL allows multiple consumers on Topic with same client-id
          1.Start (2) servers in cluster
          2.FooMDB running on Server_A connects to Topic
          3.FooMDB running on Server_B fails with unique id exception (yeah).
          4.Send messages - Messages are processed only once by FooMDB on Server_A (yeah).
          5.Stop Server_A.
          6.FooMDB running on Server_B connects automatically to Topic.
          7.Send messages - Messages are processed by FooMDB on Server_B (yeah).
          8.Start Server_A
          9.FooMDB successfully connects to Topic, even though FooMDB on Server_B is already connected (bad). Is this a WL bug or our config bug??
          10.Send messages - Messages are processed by both FooMDB on Server_A and Server_B (bad). Is this a WL bug or our config bug??
          Conclusion: Does anyone have any thoughts on the best design for that in our clustered environment? and if the above solution is doable, what mistake might we have made?
          Thank you in advance for your help!
          kb

Thanks for the helpful info Tom.
          Kevin - It seems that for both the MDB, and the JMS provider, there are (manual or scripted) actions to be taken during any failure event + failure probes possibly required to launch these actions...?
          In the case of the JMS provider, the JMS destination needs to be migrated in the event of managed-server or host failure; if this host is the one that also runs the Admin server then the Admin server also needs to be restarted on a new host too, in order that it can become available to receive the migration instructions and thus update the config of the managed server which is to be newly targetted to serve the JMS destination.
          In the case of the MDB, a deployment action of some sort would need to take place on another managed-server, in the event of a failure of the managed server or the host, where the original MDB had been initally deployed.
          The JMS Destination migration actions can be totally avoided by the use of another JMS implementation which has a design philosophy of "failover" built into it (for example, Tibco EMS has totally automatic JMS failover features) and could be accessed gracefully by using Weblogic foreign JMS. The sinlge MDB deployed on one of the Weblogic managed servers in the cluster would still need some kind of (possibly scripted) redeployment action, and on top of this, there would need to be some kind of health check process to establish if this re-deployment action was actually required to be launched. It is possible that the logic and actions required just to establish the true functional health of this MDB could themsevles be as difficult as the original design requirement :-)
          All of this suggests that for the given requirement; the BEA environment is not well suited; and if no other environment or JMS provider is available at your site, then a manipulation of process itself may be required to enable it to be handled in a highly-available way which can be gracefully administered in a Weblogic cluster.
          We have not discussed the message payload design and the reasons that message order must be respected - by changing the message payload design and possibly adding additional data, this requirement "can", "in certain circumstances", be avoided.
          If you can't do that, I suggest you buy a 2 node Sun Cluster with shared HA storage and use this to monitor a simple JMS client java program that periodically checks for items on the Queue. The Tibco EMS servers could also be configured on this platform and give totally automatic failover protection for both process and host failure scenarios. With the spare money we can go to the pub.
          P.S. I don't work for Tibco or Sun and am a BIG Weblogic fan :-)

MDB deployment in cluster

i have an MDB deployed to a weblogic cluster(weblogic10).
My requirement is i need MDB failover in case one server goes down. so i have no choice of deploying the MDB to any of the manged server. i ahve set the maximum pool size as 1 for MDB,but the MDB is instantiated from each managed server. I need only one MDB to service the queue ,but needs failover in case the any of the servere fails. Any option to do this in weblogic server.If not possible by waht way i can accomplish this task.

Is there any special reason why you only want one MDB to consume messages fro the queue?

Upgrade process for SQL server 2005 service pack4 on stand alone and cluster servers

Hi All,
We have iniated a process of upgarding sp4 for all sql 2005 stand alone and clusters servers.
Please provide me the step by step process for installing sp4 and roll back paln for sql 2005 servers.And before proceeding with sp installation what are the pre check/pro active things that we need to take care.
Maheshwar Reddy

Hello,
For applying SP to SQL 2005 cluster environment/standalone please refer to below link
http://www.sqlcoffee.com/Tips0007.htm
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Sizing of WebLogic Cluster Servers

I have an application that needs to be implemented in BEA WebLogic 5.1 (
JSP, Servlet, EJB) and deployed on Solaris 8 talking to Oracle
8.0/Solaris (in clustered environment).
I am in the process of sizing the application. Following are some of the
basic sizing information:
No of users: 6000
Usage Pattern: High during evenings in US time zone
Concurrent users: 300
EJBs types: 200 entity and 50 session beans ( stateless), 4 stateful
session beans
State Per User: 2K
Database Tables: 100
No of screens: 80
Data Accessed per User Request: 20K
Cluster: Yes
No of Machines in Cluster: 2
Clustering Type: Recommended 2- tier ( with Web Server on a different
machine)
What kind of SUN machine should I be buying?
I mean, ES 220 or ES 450 ...or a higher end machines? What should be the
swap space, RAM, no. of processors?
Any existing documentation or specification will be very valuable.
Thanks,
Hari

Hi,
First of all weblogic server has ONLY one Admin Sever per Domian which should be used for administrative work, hence we cannot have have a backup of Admin server.
Weblogic Server Architecture
Yes, the best way is to use horizontal clustering as shown below where all the managed servers are in a cluster.
Machine-1
- Admin Server
- MS-1
- MS-3
Machine-2
- MS-2
- MS-4
HTTP Servers Architecture
Assuming you would be using Apache HTTP server, hence using weblogic Apache plugin you would be able to communicate with weblogic servers. In hhtpd.conf file you have to load the module and in if-module block you would have to give all the information about the weblogic server which would then try to connect with weblogic servers as well as will load-balance between them.
For more information check the below link for Apache HTTP server.
Topic:Installing and Configuring the Apache HTTP Server Plug-In
http://download.oracle.com/docs/cd/E15051_01/wls/docs103/plugins/apache.html#wp131399
Topic:General Parameters for Web Server Plug-Ins
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143055
Hope this helps you.
Regards,
Ravish Mody

Cluster servers (file servers)

Hello,
We are looking to use Windows 2012 servers as a file server. We want high availability so we like the concept of the cluster. We like the ability to take one server down for maintenance and still be able to provide files to end users. I have
read scattered information around the net (links below). We also want to incorporate the deduplication feature offers from Windows 2012. Our storage will be from Amazon S3 (iSCSI volume using gateway-cache). Our Windows 2012 Servers will
be virtual machines.
http://clusteringformeremortals.com/2012/12/31/windows-server-2012-clustering-step-by-step/
http://technet.microsoft.com/en-us/library/gg232621%28v=ws.10%29.aspx
From the information provided, what should I be aware of before I take this journey of building and testing? Our client machines are mostly Windows 7.
Thanks ahead,
TT

That's a pretty straight forward task. See a bunch of links below on how to create a failover file servers. See:
Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster
http://technet.microsoft.com/en-us/library/cc731844(v=ws.10).aspx
Create a Clustered File Server
http://technet.microsoft.com/en-us/library/cc753969.aspx
HA File Server for SMB NAS
http://www.starwindsoftware.com/configuring-ha-file-server-for-smb-nas
(ignore StarWind replacing it with your S3 shared storage, Windows-related config part of the PDF is the same for all storages)
Using Windows 7 does not support SMB 3.0 so no Transparent Failover which is part of SMB 3.0 and up. I'd strongly suggest to upgrade to Windows 8 for your clients if you can. See:
Which SMB version?
http://blogs.technet.com/b/josebda/archive/2013/10/02/windows-server-2012-r2-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-smb-3-0-or-smb-3-02-you-are-using.aspx
Windows
7 and SMB3
http://windowsitpro.com/windows-7/smb-30-windows-7
Good luck!
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

One of AD RMS cluster servers always asks for credential

I have created AD RMS cluster on Windows Server 2012 R2.
and I have configured NLB between the two servers but when users try to connect to second cluster server they cannot connect to it as it always ask for credentials.
I have put cluster name as trusted site on all clients.
Also I have noticed that AD RMS logging service doesn't exist any more on Windows Servers 2012 R2.
a

Hi Ahmed-Mahmoud,
Please try to populate the IE local intranet sites with the appropriate URLs, credentials not automatically sent to RMS unless cluster/server names are in the IE Local Intranet
sites.
Active Directory RMS Stop entering user's credential when opening files
https://social.technet.microsoft.com/Forums/en-US/2af38d78-bc2f-4882-ab4f-b155f08c30c1/active-directory-rms-stop-entering-users-credential-when-opening-files?forum=rms
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

In a Sharepoint 2013 Server farm how far away can the backup of failover cluster servers be located away from the primary servers

Hello Community
    When you setup a Sharepoint 2013 Server farm
if you want to provide failover clustering, can
the servers that the Sharepoint 2013 Server farm
failover to be located off-site in a different
location (i.e. how far away can the servers the
the primary server in the Sharepoint 2013 Server
farm be away from the failover cluster of backup
Sharepoint 2013 Server farm servers in distance?
    Thank you
    Shabeaut

Hiya,
this article describes in detail the different aspects of creating a highly available SharePoint 2013 server farm.
Create a high availability architecture and strategy for SharePoint 2013
http://technet.microsoft.com/en-us/library/cc748824%28v=office.15%29.aspx

How to install SSAS Cluster instance with Always On availability group(Standalone database instance) in same windows cluster servers

We have requirement like to Install the SSAS as Cluster instance where SQL Server Database engine was installed with Always On availability group.Please help me to how configure it
Currently we have following configuration in Current steup.
Node1 and Node2 are in windows cluster
Node1 has SQL Server Database engine Instance1 as Standalone
Node2 has SQL Server Database engine Instance2 as Standalone
Instance1 and Instance2 configured for Always On availability group with Listener.
Now we have to steup SSAS instance with High availibilty. I know we have only option is to install cluster SSAS instance.
Can some one provide information below.
1. How to steup Cluster SSAS instance in this servers.
2. Is this will have any dependancy on exisiting Listner name.
3. Is this affects the availiblity groups, if SSAS instance failed over to another node.
Thanks in Advance
Sriram

You will need to have SSAS installed as a clustered instance with shared storage. Refer to the whitepaper from this MSDN article
How To Cluster SQL Server Analysis Services
Availability Group is in it's own Role/Resource Group. When you create the clustered SSAS, it will create its own Role/Resource Group. This means that it will require its own virtual network name and virtual IP address and will not affect the existing Availability
Group. You can also have it on the existing Availability Group if you want to. However, you need to decide if you want SSAS to failover with the Availability Group or not. Your design choices will depend on that decision.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

How to deploy a MDBean into cluster with only one JMS server instance running on one of the cluster servers

          I am trying to deploy a MDBean in my cluster ( two servers). The MDBean requires
          the destinestion has to each cluster server. It means that I have to deploy my
          JMS server over the cluster. This will result multiple destinations (queue or
          topic) are created.
          Is there a way to run one JMS server with a clustered MDBean?
          Thanks,
          Taohe


Check out my posting from 4-3 in this thread.
http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=5&jump=true
I think I may have answered your question before you asked it.
In that example I use the picture control to manipulate a bunch of rectangular images of booleans.
I hope this helps,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Can I cluster servers on one machine?

          If I started a few WebLogic servers on one machine (each with a different port
          number), can I put them in a cluster (since they do not have the same port number)?
          If yes, how can I address the cluster?
          Thanks!
          --Zhenxin Wang
          [email protected]


see my previous post for steps on how to setup clusters on single nt server.
          "Mike Reiche" <[email protected]> wrote in message
          news:3b09d0c9$[email protected]..
          >
          > Yes you can have a cluster of wls servers running on a single machine.
          >
          > No, you cannot do it by running them on different port numbers - they must
          use
          > the same port number and a different IP address.
          >
          > On Solaris, you can add IP addresses using the ipconfig command.
          >
          > Mike
          >
          >
          > "Zhenxin Wang" <[email protected]> wrote:
          > >
          > >If I started a few WebLogic servers on one machine (each with a different
          > >port
          > >number), can I put them in a cluster (since they do not have the same
          > >port number)?
          > >If yes, how can I address the cluster?
          > >Thanks!
          > >
          > >--Zhenxin Wang
          > > [email protected]
          >

Can I make cluster servers auto reload html files without redeploy applications?

For example, I have some html files under application directory, these html
          files were
          generated and synchronized to all clustered servers by other external
          programsfrom time to time¡£ But with weblogic, I have to redeploy these html
          files to enable these files been viewed via browser.
          Is there any way to let weblogic auto refresh these files without redeploy?


OS X Lion- About Auto Save and Versions
Handles this automatically. Otherwise, such frequent backups will overtax the drive and probably cause some slowdowns, but you can change the interval using the freeware utility, TimeMachineEditor 3.0.3.

MDB Durables in Cluster Servers

Similar Messages

Maybe you are looking for