locked
PAS scalability and installation. RRS feed

  • Question

  • Hi all.

    We curently have a Proclarity Analytic Server 6.3 on a server.
    We're going on production and are setting up a backup server, in case the primary server fails.
    Actually we have the analytic server replicated on the backup server through SQLServer Replication.

    Our question is how to setup PAS on the backup server ? They're are a few options we're looking at, but don't know the best one.

    1 - Install PAS on the backup server and have it point to the primary database, using the "use existing database" durgin the installation steps. We're using aliases to point to primary server. When server fails, we change the ip alias and stop the replication. We then have the backup server pointing to the other database. Is that possible ?
    What will happen when we install the backup PAS server pointing on primary database ? Will it damage the actual production datas or does giving the right user and password preserve the database ? Especially since we update with the lastest patch ?
    Is it possible to run 2 servers on the same database without troubles ?

    2 - The other option, is to install PAS on the backup server, on a dummy database. When we need to switch, then stop replication, have the alias redirect to the  backup server. Then to go PAS administrative console and update the database connection to point to the replicated database.

    We're really wondering which is the right method. In administrative guide it's said that this is possible to run multiple pas on the same database under some conditions.

    Thanks for your help.

    Best Regards.
    Erwin.
    Monday, February 16, 2009 5:29 PM

All replies

  • Hi eriff,

    In response to your question #1: Yes you can have two PAS servers pointing to the same PAS database without any issues.  No data will be damaged or lost when pointing multiple PAS installs to an existing database.  Using a cname redirect works and then by editing the cname record you'll be directing traffic to another server.  One problem with this is the workstations that have the DNS entries cached will still be trying to contact the offline server.  Until the DNS cache purges you could have a problem with cached entries. 

    You could also create a failover cluster where if one server has a problem, the 2nd one will be brought online to pickup the same traffic on the same alias.  You might consider looking into this:  http://technet.microsoft.com/en-us/library/cc731844.aspx

    hth
    Microsoft ProClarity | This posting is provided "AS IS" with no warranties, and confers no rights.
    Thursday, February 19, 2009 4:07 PM