Higher Education Endpoint Management User Group

 View Only

Altiris Disaster Recovery Tips (from Database failure) - NS, SWS, SD, WF, DS 

Jul 11, 2011 02:38 PM

Hey Everyone, we are testing out some disaster recovery scenarios based on a SQL database failure and I have tried to simulate how to reconnect all affected services as quickly as possible to the other SQL box which is using log shipping.  After spending some time, I wanted to share some tips to cut down on others time in case this was ever needed by anyone.  Essentially, Altiris products are pretty simple to modify once you know where to dig at.  At present, we are using two SQL servers which are mirroring all data in a log shipping configuration.  For the purposes below, you could simply restore a database file from backup to another SQL server and repoint based on the tips below.

NS (aka Notification Server and including dependencies for ServiceDesk and Workflow)

For Notification Server, here is what must be done:

 

Modify the registry underneath HKLM>Software>Altiris>eXpress>Notification Server and verify that this DBDsn regkey is

DRIVER={SQL Server};SERVER=FQDN\instance;DATABASE=Symantec_CMDB;

Then, underneath C:\Program Files\Altiris\Notification Server\Bin\Tools

Run NSConfigurator from inside an elevated Command Window.  Check under the 'Database Settings' in the left side. 

Modify DbServer so that it says FQDN\instance

Restart the server or all services including ServiceDesk or Workflow servers.

 

Servicedesk/Workflow

Inside C:\Program Files\Symantec\Workflow\ProcessManager

Modify web.config:

 

<DataAccessConfiguration>

    <add key="DefaultConnectionInstance" value="Default" />

    <add key="LoginAdminUser" value="admin@logicbase.com" />

    <add key="LoginAdminPassword" value="XXXXXX" />

    <ConnectionInstance>

      <add key="Name" value="Default" />

      <!--Please do not change this line in a checked in version-->

      <add key="ConnectionString" value="Data Source = FQDN\instance; Initial

 

Catalog=ProcessManager;Integrated Security=SSPI;Pooling=true;Connection Timeout=300" />

    </ConnectionInstance>

    <add key="ReportSnapshotsLocation" value="C:\Program Files\Symantec\Workflow\ProcessManager\ReportSnapshots" />

    <add key="DefaultReplicationConnectionInstance" value="ProcessManagerReplication" />

    <add key="DefaultOLAPConnectionInstance" value="OLAPDefault" />

    <ConnectionInstance>

      <add key="Name" value="OLAPDefault" />

      <add key="Type" value="OLAP" />

      <add key="ConnectionString" value="Data Source = FQDN\instance; Initial

 

Catalog=ProcessManagerAnalysis; Integrated Security=SSPI;" />

    </ConnectionInstance>

  </DataAccessConfiguration>

 

Change Symantec Workflow Server Service to logon with domain credentials.  Restart the service.

Inside IIS Manager, change the Application Pool for DefaultAppPool to use the same identity as above. 

Recycle the pool afterwards.

 

SWS (aka Appstream)

Navigate to:  C:\Program Files\Symantec\Workspace Streaming\Server\streamletEngine\da\conf\

 

Modify da.conf so that

 

# ===================================================================

#  Microsoft SQL Server 2005 Configuration

# ===================================================================

torque.database.appstream.adapter=mssql

appstream.database.host=SQL IP Address

appstream.database.port=1433

torque.dsfactory.appstream.connection.driver=net.sourceforge.jtds.jdbc.Driver

torque.dsfactory.appstream.connection.url=jdbc:jtds:sqlserver://${appstream.database.host}:

 

${appstream.database.port};DatabaseName=${appstream.database.name};instance=appstream

torque.dsfactory.appstream.connection.user=sa

#torque.dsfactory.appstream.connection.password = XXXXXX

torque.dsfactory.appstream.connection.password= XXXXXX

torque.dsfactory.appstream.connection.poolPreparedStatements=true

 

Also, on the SQL Server, make sure Mixed Mode Authentication is enabled as Appstream does not currently support NTLM..

 

DS (aka Deployment Server)

Inside the express share:

 

Modify default.cfg so that the SQLDatabaseName = SQL Server instance (SQLDatabaseName=FQDN\instance)

Change the ODBC connection to the same value above (FQDN\instance)

In Program Files, inside the Altiris/Deployment Solution folder, run configuration and restart services

Repoint all ODBC connections to the new server.

Remember, the name must be Altiris eXpress Database inside the System DSN connection.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.