Mirroring, aliases and failover woes

Hi, I have an SP2010 farm configured with SQL mirroring. I've added failoverserver entries for each of the databases to make SP mirroring aware. 
Everything works fine when I simply fail over from within SQL server management studio. I then shutdown the mirrored SQL node and SharePoint continues to work fine. On performing an iisreset the main web application becomes unavailable "cannot connect
to config db". At this point Central Administration is still accessible. It would seem that even though everything is failed over, that the SharePoint web app still wants to connect to the primary node in the connection string even though a failover partner
is set.
What tools can I use to diagnose this? In my ULS logs I see an entry that says "SQL Server failover connection detected. SQL Server <primary> failing over to SQL server <secondary>. This would suggest that the connection string is fine.
It may just be an issue with the config db.
Any pointers welcome.

Have you mirrored the Configuration database and configured it via PowerShell on SharePoint?
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Similar Messages

  • RE: Hard Failures, KeepAlive, and Failover --Follow-up

    Hi,
    It's a really challenging question. However, what do you want to do after
    the network crash? Failover or just stop the service? Should we assume
    that when the network is down, and so do your name service?
    One idea is to use externalconnection to "listen" to your external non-forte
    alarm, so do "whatever" after you receive the alarm instead of letting the
    "logical connection" to time out or hang.
    Regards,
    Peter Sham.
    -----Original Message-----
    From: Michael Lee [SMTP:[email protected]]
    Sent: Wednesday, June 16, 1999 12:44 AM
    To: [email protected]
    Subject: Hard Failures, KeepAlive, and Failover -- Follow-up
    I've gotten a handful of responses to my original post, and the suggested
    solutions are all variations on the same theme -- periodically ping remote
    nodes/partitions and then react when the node/partition goes down. In
    other circumstance this would work, but unless I'm missing something this
    solution doesn't solve the problem I'm running into.
    Some background...
    When a connection is set up between partitions on two different nodes,
    Forte is effectively establishing two connections: a "physical
    connection"
    over TCP/IP between two ports and a "logical connection" between the two
    partitions (running on top of the physical connection). Once a connection
    is established between two partitions Forte assumes the logical connection
    is valid until one of two things happen:
    1) The logical connection is broken (by shutting down a partition from
    Econsole/Escript, by killing a node manager, by terminating the ftexec,
    etc.)
    2) Forte detects that the physical connection is broken (via its KeepAlive
    functionality).
    If a physical connection is broken (via a cut cable or power-off
    condition), and Forte has not yet detected the situation (via a KeepAlive
    failure), the logical connection is still valid and Forte will still allow
    method calls on the remote partition. In effect, Forte thinks the remote
    partition is still up and running. In this situation, any method calls
    made after the physical connection has been broken will simply hang. No
    exceptions are generated and failover does not occur.
    However, once a KeepAlive failure is detected all is made right.
    Unfortunately, the lowest-bound latency of KeepAlive is greater than one
    second, and we need to detect and react to hard failures in the 250-500ms
    range. Using technology outside of Forte we are able to detect the hard
    failures within the required times, but we haven't been able to get Forte
    to react to this "outside" knowledge. Here's why:
    Since Forte has not yet detected a KeepAlive failure, the logical
    connection to the remote partition is still "valid". Although there are a
    number of mechanisms that would allow a logical connection to be broken,
    they all assume a valid physical connection -- which, of course, we don't
    have!
    It appears I'm in a "Catch-22" situation: In order to break a logical
    connection between partitions, I need a valid physical connection. But
    the
    reason I'm trying to break the logical connection in the first place is
    that I know (but Forte doesn't yet know) that the physical connection has
    been broken.
    If anyone knows a way around this Catch-22, please let me know.
    Mike
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Make sure you chose the right format, and as far as partitioning in concerned, you have to select at least one partition, which will be the entire drive.

  • I have a Mac G4 double mirrored model and everytime I shut it off it will not go on when I hit the power off button. However, if I unplug and plug in the power cord it boots fine and everything is OK. The PMU and logic board have been reset. Any ideas?

    I have a Power Mac G4 double mirrored model and everytime I shut it off it will not go on when I hit the power on/off button again. However, if I unplug and plug in the power cord it boots fine and everything is OK. The PMU and logic board have been reset. Sometimes my Mac goes on just by pressing the power on button but most times I have to pull the power cord and put it back in. Any ideas or help out there for this? Could it be a failing power supply? Apple Care says that this model is obsolete so there is no help from there. John
    <E-mail Edited by Host>

    Hi John,
    That's often a sign of a bsad Capacitor in the Power Supply, but...
    Might be time to replace the PRAM Battery, 4 years is close to their lifespan, far less if ever without AC power, & can cause strange startup problems...
    http://eshop.macsales.com/item/Newer%20Technology/BAA36VPRAM/ 

  • How to find out the primary and failover DNS name

    Hi;
    This sounds very stupid, but could some one please tell me how to find out the name/dns name of the primary and failover server without using the CDS console.
    any help is appreciated

    Is this what you want?
    $ /usr/lib/ldap/ldap_cachemgr -g
    cachemgr configuration:
    server debug level 0
    server log file "/var/ldap/cachemgr.log"
    number of calls to ldapcachemgr 12729
    cachemgr cache data statistics:
    Configuration refresh information:
    Previous refresh time: 2005/08/07 23:54:59
    Next refresh time: 2005/08/08 00:55:00
    Server information:
    Previous refresh time: 2005/08/14 15:15:00
    Next refresh time: 2005/08/15 03:15:00
    server: ldap1.example.com, status: UP
    server: ldap2.example.com, status: UP
    server: ldap3.example.com, status: UP
    Cache data information:
    Maximum cache entries: 256
    Number of cache entries: 0
    Gary

  • Turn off display mirroring once and for all ?

    Hi there,
    I have a 13'' macbook pro, recently upgraded to Snow Leopard. Now every time I connect my external screen (a DELL E198WFP connected with the DVI output) the display starts in "mirroring" mode. I have to manually turn mirroring off every time. According to the documentation, MacOS is supposed to "remember" my settings the next time I connect the screen but it doesn't work. Previously I had a Macbook Air with Leopard and I had not this issue (the screen would start with mirroring turned off when I connect it). Is there any possibility to disable mirroring once and for all, as I never use this feature ? Thanks

    Ok since you upgraded your system you might have a issue with your preference files for the displays. you need to Delete these two files reboot and Zap your PRAM. (Print this out)
    #1. Delete these files:
    /Library/Preferences/com.apple.windowserver and ~/Library/Preferences/ByHost/com.apple.windowserver"
    #2. Turn off Computer
    #3. Reset your PRAM by:
    (From Apples instruction page)
    Resetting PRAM and NVRAM
    Shut down the computer.
    Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.

  • Failover clusterign... How similar do the primary and failover instance need to be in a failover cluster?

    How similar do the primary and failover instance need to be in a failover cluster?
    Does the number of database have to match, naming, general config etc...
    Mr Shaw

    In failover clustering, you use shared storage so the number of databases is irrelevant since only one node can see/access the shared storage at any given point in time. Ideally, the server configuration should be the same on all of the nodes to minimize
    potential issues that may impact downtime. However, you need to consider licensing/# of CPU-cores and implementation cost, especially if you are only using the other nodes as standby. As far as licensing is concerned, the standby has to have the same or fewer
    number of CPU-cores as the primary node to be covered by licensing. Besides, you don't want your standby node to be more powerful than your primary node. This is why the option to have a hybrid deployment of having a physical server as the primary node and
    virtual machine for standby nodes is now supported.
    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog |
    Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course

  • Load balancing and Failover

    Hello,
    We are wondering how load-balancing and failover of tpcall() work with
    WTC:
    The scenario:
    We have one WLS Domain and two Tuxedo Domains. The Tuxedo Domains offer
    the same set of services.
    In the bdmconfig.xml, we specify connection_policy as 'ON_STARTUP' for
    both Remote Tuxedo Domains. We also Import (T_DM_IMPORT) the same
    Tuxedo Service from both Tuxedo Domains.
    Questions:
    1. Is there any load-balancing of the tpcall between the two Domains? If
    so, is it round-robin? If round-robin, what determines the order?
    2. If it is ONLY Failover, what determines the order of the tpcall? And,
    is the Failover automatic? Or do we need to code for retry on failure?
    3. ON_DEMAND vs ON_STARTUP: Does ON_DEMAND drop the connection to the
    remote domain upon tpterm? And does ON_STARTUP use a pool of
    TuxedoConnection objects?
    4. Are there any configuration parameters for
    'max_number-of_connections? What determines how many simultaneous
    connections can be made?
    Thanks,
    Suresh Mohan.

    Hi Suresh,
    The following are my answers to your questions.
    Suresh Mohan wrote:
    Hello,
    We are wondering how load-balancing and failover of tpcall() work with
    WTC:
    The scenario:
    We have one WLS Domain and two Tuxedo Domains. The Tuxedo Domains offer
    the same set of services.
    In the bdmconfig.xml, we specify connection_policy as 'ON_STARTUP' for
    both Remote Tuxedo Domains. We also Import (T_DM_IMPORT) the same
    Tuxedo Service from both Tuxedo Domains.
    Questions:
    1. Is there any load-balancing of the tpcall between the two Domains? If
    so, is it round-robin? If round-robin, what determines the order?Yes there is a load balancing between two remote Tuxedo TDomain Gateways.
    The algorithm is random, not RR. Over time this should give equal
    opportunities to both remote TDomain.
    >
    2. If it is ONLY Failover, what determines the order of the tpcall? And,
    is the Failover automatic? Or do we need to code for retry on failure?The load balancing is always there. The failover is automatic. When a
    connection to a remote TDomain encountered a problem (ie network) the remote
    domain will be put on retry open connection (in ON_STARTUP) and the load
    balancing will not select it until the connection re-established.
    However, the tpcall() that encountered the error will not be retried to send
    to different destination. It is up to the application to decide whether it
    want to resend. Any requests called after the error will not select the
    failed Remote TDomain.
    >
    3. ON_DEMAND vs ON_STARTUP: Does ON_DEMAND drop the connection to the
    remote domain upon tpterm? And does ON_STARTUP use a pool of
    TuxedoConnection objects?TPTERM() only terminate your application session to WTC. WTC still maintain
    a secured T-session to remote Tuxedo TDomain. WTC does not use a pool of
    TuxedoConnection Objects, the object stored in the JNDI refers to WTC.
    >
    4. Are there any configuration parameters for
    'max_number-of_connections? What determines how many simultaneous
    connections can be made?No. As described in #3, there is no need to use connection pool in WTC. WTC
    uses session and virtual circuit design concept as Tuxedo TDOMAIN, the
    logical pool is created/destroyed dynamically. That is the reason why you
    can have a lot of TPACALL() outstanding at the same time. (The limitation is
    the availability system resource.)
    >
    >
    Thanks,
    Suresh Mohan.Regards,
    Hong-Hsi :-)

  • Load Balancing and Failover with 10G Standard Edition

    Hi,
    I am new to Oracle Replication and need some help setting up replication for load balancing and failover. Is this possible using Oracle 10G Standard Edition? I plan on having all updates done on the master site and both databases will be for reads. In case of failure of the master site, I would need to be able to failover to the other database.
    Also, if anyone knows of any documention for Basic Replication in 10G, please let me know.
    Thanks.

    Simple nnapshot replication of data would require significant manual effort to configure to load balance or failover. One the load balancing side, you would generally be limited to to static load balancing-- assigning half the users to one machine and the other half of the users to the other machine, regardless of who is actively using the machine. Failover would be a significant manual effort, particularly to bring the failed machine back into the cluster. You would be implementing the guts of multi-master replication.
    Frankly, if you actually have a system which is valuable enough to need load balancing and disaster recovery, I'm going to wager that it will be far cheaper even in the short run to buy more boxes and/or enterprise edition licenses than to try to implement this sort of thing yourself. In the long run, it will be far cheaper, since it will be far easier to maintain. Building all this yourself would probably be penny wise and pound foolish.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Load balancing and failover in Embedded LDAP in weblogic

    How to handle load balancing and failover in Embedded LDAP in weblogic server?

    You should consider posting this to the Weblogic and/or LDAP support forums. This forum is meant for Sun Web Server questions.
    Thanks
    Manish

  • Network Load Balancing and failover for AFP Sharing

    Dear all,
    Somebody kindly teach me to use round robin DNS to perform the network load balancing, it's success but not the failover.
    I have 4 xserve and want to do the load balancing and failover at the same time.
    I have read the IP failover document and setup it successfully, but anyone know is it possible to do the IP failover for more than 2 server?
    For example, 4 server serving the AFP service at the same time, maybe I have 1 more extra server to do the IP failover for thoese 4 servers.
    As I know, IP failover require Firewire as the heartbeat detection. But one xserve only have 2 firewire ports. May I setting up the IP failover only by a ethernet port and an IP address? does it possible to detect and failover to any server after server down has been detected?
    I believe load balancer maybe the best solution but its cost is too high.
    Thanks any advance!
    Karllee

    well, u have 2 options here
    software load balancing
    request comes it foo.com -> ws7u2 hosting foo.com is configured to run as reverse proxy . this server sends any incoming requests to one of the four back end web server 7 handling your incoming request
    hardware load balancing (this you need to invest)
    request comes to hardware load balancer who responds for foo.com -> sends requests to four ws7 server hosting your application
    you could try out how software load balancing works out for you before you invest in hardware load balancing
    here is more instruction on configuring ws7 + reverse proxy (software load configuration)
    - install ws7 on foo.com
    - create a new configuration (choose port 80, disable java

  • I created a CD for a friend (with photos).  She got a blank CD with a message that it had only aliases and couldn't (of course) locate the originals.  What did I do wrong.  I've never had a problem preparing and burning CDs before.

    I created a CD for a friend (photos).  She received a blank CD with a message, something about aliases and no originals.   When I tried again, and dragged files to the CD they appeared only as aliases.  Of course they wouldn't open on another computer.  I've never had a problem preparing CDs before and haven't a clue what went wrong???  Thank you!!

    If you drag files to the CD they appear as aliases until you burn the CD. Verify the files as images after you burn the CD

  • When will Smartview support display both aliases and members?

    In the Essbase classic add-in, users had the ability to display both aliases and member names. When using Smartview with Essbase, this isn't supported. Are there plans to add this back? Thanks.

    I heard this is the most requested parity feature of the addin, that Oracle may be doing this sometime in 2010 since it is a complicated fix.

  • LB and Failover

    From the product brochure I understand the origin/edge
    architecture facilitates load balancing and fail over.
    I don't understand whether is possible - with a reasonable
    dev effort - to ensure a simple lb and failvoer also with FMS
    professional installed on two or more servers. Is there any support
    for this in FMS? I know an FMS can "talk" with another FMS, but is
    there something more out-of-the-box?
    Where can I get some addtional info about how LB and Failover
    is handled in the origin/edge architetcure?

    It depends on what content you want to deliver. If you have
    static content like FLV movies that you can copy on 2 servers then
    it's easy to have your client-SWF connect to either one of the two
    live servers. If you can't connect to 1 , try the other.
    If you'd have live content , being streamed to one server
    then you can't replicate that stream to your second server. If
    you'd use origin+edge then you can publish to 1 'master' server
    which would replicate your live stream to 2 or more 'slave' servers
    so your clients would have at least 2 sources for that live stream.
    As far as I know you have to develop the failover algoritme
    yourself. But it's not complicated. Just pick a random server from
    the list in your client-swf. Try if you can make a good connection
    to the random picked server, if not, retry until the client made a
    fine connection.
    But still you'd have a single point of failure, the master
    server. It won't be loaded as much as the slaves so it would be
    more stable in the end than a single server than receives a live
    stream AND has to publish it to 1000+ clients at the same time.

  • CSS 11503 adv-bal-stcky-srcip and failover question

    From the documentation I have read about failover (when a service fails) it lists several loadbalancing types, but the advanced-balance-sticky-srcip is not one of them. Is it possible to configure failover linear or failover next when using adv-bal-stcky-srcip? The CSS is configured for a kal (type=tcp / port=8080), but does not do anything when the service does not respond the kal.

    Let me add some clarity then. :) I am running PeopleSoft through the CSS (which is the reason for adv-bal sticky-srcip). I have two services in my content rule:
    service pplsft-web1
    ip 172.27.144.63
    port 8080
    kal tcp / 8080
    service pplsft-web2
    ip 172.27.144.63
    port 8080
    kal tcp / 8080
    When the KAL fails and the service is marked down, what is the CSS supposed to do?...you can configure the failover of a a service (ie: failover linear or failover next). In all the docs I have read, I read that 'failover linear' and 'failover next' were for regular load balancing techniques (ie: domain, url, srcip, destip, domainhash and urlhash). Can I use it if I have the advanced-balance sticky-srcip load balancing command on the content?
    Does that clarify any?
    I did get an answer from TAC...by default, 'failover linear' is enabled. But what may be happening is that because of the sticky config, the user ip is still in the sticky table, which over-rides load balancing. I have to define the settings for "sticky serer down failover" to either 'balance' or 'reject' entries in the sticky table and any requests that come in.

  • WebVPN Tunnel-Group Aliases and URLS

    Hi,
    <br />
    <br />I have a requirement to create a new group policy and a new tunnel-group and apply it to a webvpn user account
    <br />
    <br />
    <br />The web vpn is working fine without any issues when I give a new name under Group Aliases and URL
    <br />
    <br />My requirement is to use the existing Group Alias for this new tunnel-group. When I enter the existing alias it says it is already used by other tunnel-group
    <br />
    <br />Please help

    If you use the same group-alias for two tunnel-groups, then how will the firewall distinguish between the two? Let say, as per your requirement you want to have the group-alias 'securevpn' for two tunnel-groups, TG1 and TG2. Now how will the firewall map a user landing on this alias to a group? TG1 or TG2? round-robin? :). This is not possible AFAIK.
    Please rate if helpful.
    Regards
    Farrukh Haroon
    CCIE # 20184 (Security)

Maybe you are looking for