Redundancy Vworkspace

Denis,

Welcome to the Community.

As for your questions.

1.  IIS with Web Access/Secure Gateway can be setup in an NLB Cluster and I have this up and running now without issues.  We leave the NLB Cluster configuration up to the client as they may have standards set for this type of infrastructure.  With that said, we (Quest) may have something coming down the lines with a 'Web Access/Secure Gateway NLB Setup/Configruation' document.  This will be a setup which we (Quest) have tested and have it proving to work properly.

2. Database Mirroring is supported.  If you look at our Database, you will see that it has Private/Foreign keys all through it.  This should allow you to Mirror/Cluster it without any issues.  We leave this configuration/setup with the client as well.  I am not sure if we have anything in the lines as to a document for this type of setup on our Database though.

Hi Guys,

I also have a requirement for setting up DB Mirroring in SQL 2008 R2... Although I know how to do this in SQL, by folllowing published articles from MS, is there anything I need to change/do in vWorkspace to get this configured and working?

Hi Paul,

I'm personally looking at DB mirroring for HA purposes. The DR aspect can wait until we have the live production vWorkspace in place

Cheers,

Caleb,

Are you looking to provide a replicated DR site or high availability for the database?

Cheers

Paul

Hi Paul,

Yes clustering would be a good option but the costs are much greater. i.e. Enterprise OS requirements, shared storage etc... If I went down the Mirrored DB with a witness server, how do I go about configuring the vWorkspace components to use such an envirnonment?

Hi,

Now I've got my live environment tin shipped, racked and powered, I've started building the 'Live' environment. I've created a mirrored 'vWorkspace Database' but can't seem to see how the cleint connection, from connection brokers, TS, etc are configured?

Any ideas?

I am out of office and have limited access to email and voicemail, so please account for a delay in my replies. I will not be back before November 22. This email will not be forwarded.

Thank you.

Hi Caleb,

You are only able to configure one database in vWorkspace at a time.  For automatic fail over of the database you need clustering.  In your case the mirrored database would be sitting there as a "live backup" which would require a manual database configuration change for vWorkspace in the event of a database issue. (which could be scripted to speed the process up)

Paul

Hi Paul,

Not a problem as I don't envisage the 'live' DB to die frequently but some form of HA would be preferable than clustering SQL currently. Yorker is wrong when he says 'Database Mirroring is supported' then?

Okay, when I look at the System DSN on the servers through the ODBC Administrator, be it a Connection Broker role or a Terminal Server role I don't see anything. Where is the ODBC information for the DB held so I can script a change over?

Cheers,

Hi,

I do not know if this will help, but on lab, I mirrored sql (No witness yet ^ ^).

I created (on the broker) with ODBC Data source Administrator a systeme DSN for failover_Partner

And it work (when I failover manualy,pending witness).

I did not need to change the ODBC configuration from servers TS user test can connect (webaccess) after a failover sql.

screen of my draft doc

Denis

I continuing my test

any comments are welcome :-)

Caleb,

See if this .vbs script of mine helps but *please test before using* and modify as you see fit.  It will change the DSN and restart the required services.  Alternativly you could have both databases setup in the console on each broker and TS server.  You would then manully change the db (File > Database Configuration > Change DSN drop down) and restart the services.  I guess that would depend on how many servers you have though.

Paul

--------------------------------------------------------------------------------------------------

Const ERROR_SUCCESS = 0
Const ERROR_INSTALL_FAILURE = 1603
Const ERROR_FUNCTION_FAILED = 1627
Const CRITICAL_ERROR_ICON = 16

On Error Resume Next
   
'---------Restart Services-----------

MsgBox "Setting DSN", vbInformation + vbOKOnly

Dim oPNAdminSystem, sSQLServerName, sSAUserName, sSAPassword, sDatabaseName, sSQLLoginAccount, sSQLLoginPassword, sDataSourceName, sReturnMsg, oShell
  
Set oPNAdminSystem = CreateObject("pnadmin.system")

If wscript.agruments.count = 0 Then
     sSQLServerName = "SERVER\VWORKSPACE2"
     sDatabaseName = "vWorkspace_Database"
     sSQLLoginAccount = "pnadmin"
     sSQLLoginPassword = "password"
Else
     sSQLServerName = wscript.agruments(0)
     sDatabaseName = wscript.agruments(1)
     sSQLLoginAccount = wscript.agruments(2)
     sSQLLoginPassword = wscript.agruments(3)
End If
   
sDataSourceName = "vWorkspace Database"

If oPNAdminSystem.MiscFunctions.CreateDSN(sDataSourceName, sSQLServerName, sDatabaseName, sSQLLoginAccount, sSQLLoginPassword, sReturnMsg) Then
        Set oShell = CreateObject("WScript.Shell")
        oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\ODBC\ODBC.INI\ODBC Data Sources\" & sDataSourceName, "SQL Server", "REG_SZ"
        Set oShell = Nothing
        MsgBox "The data source was created successfully.", vbInformation + vbOKOnly, "Data Source Created Successfully"
Else  
        MsgBox "Failed to create the data source. Please verify that the specified connection parameters are correct.", vbExclamation + vbOKOnly, "Failed to Create Data Source"
End If
   
oPNAdminSystem.Disconnect

Set oPNAdminSystem = Nothing
 

'---------Restart Services-----------

Set objWMI = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
ArrSvcs = Array("pndcsvc", "pnregsvc", "pnbrksvc")
        
'Stop each service in the Array
For i = 0 to UBound(ArrSvcs) - 1
     Set colServices = objWMI.ExecQuery("Select * from Win32_Service where Name = '" & arrSvcs(i) & "'")
            
     For each service in colServices
         service.StopService()
     Next
  
     Do While numRet = "Stopped"
         numRet = funcCheckServiceState(objWMI, strSVCName)
         WScript.Sleep 1000   'check every second
     Loop
     WScript.Echo "Service " & ArrSvcs(i) & " has been stopped."
Next
  
'Start each service in the Array
For i = 0 to UBound(ArrSvcs) - 1
   Set colServices = objWMI.ExecQuery("Select * from Win32_Service where Name = '" & arrSvcs(i) & "'")
   For each service in colServices
      service.StartService()
   Next
  
   Do While numRet = "Started"
      numRet = funcCheckServiceState(objWMI, strSVCName)
      WScript.Sleep 1000   'check every second
   Loop
   WScript.Echo "Service " & ArrSvcs(i) & " has been started."
Next
  
Function funcCheckServiceState(objWMI, strSVCName)
   Set colServices = objWMI.ExecQuery("Select * from Win32_Service where Name = 'pndcsvc'")
   For each service in colServices
      funcCheckServiceState = service.State
   Next
End Function

WScript.Echo "Script has finsihed"

----------------------------------------------------------------------------------------------------------

Can you open the database mirror (after failover on principal) with you pnadmin account on the "sql management studio"  console?

your monitor mirroring is Synchronized?(no error?)

Denis

Hi Dennis,

Good stuff... I;ve tried this also using the SQL Native clien but after a failover, manual also, I cannot get the vWorkspace console to connect... Checking in the 32bit version of ODBC Admin it fails saying

I've added the PNADMIN account as an dbo on the mirrored "vworkspace_database" database and use "sa" as the account for mirroring.

Further help would be greatly received!

Hi,

After granting the PNADMIN account sysadmin role on the server the connection issue has gone, but now I get the:

error, which was posted here under the 'Changing vWorkspace Database' thread.

Any ideas?

Paul I'll look at the script after I've given up on this