The following are the most commonly requested application related solutions.

Resource can not be extended after the Target node has been replaced

ISSUE:

The server (Target) from an existing 1×1, LifeKeeper for Windows configuration, was replaced, i.e. OS reinstalled, LifeKeeper reinstalled.

Error messages:

The SIOS DataKeeper Service on system {system name} cannot be contacted. Verify that the service is running. If {system name} is a Windows 2008 server, verify that the Local Security Policy setting called “Network Access: Let Everyone permissions apply to anonymous users” is enabled.

- canextend ({system name} {resource name}) – Script was terminated by a signal

Error – extmgr ({system name} {resource name}) -canextend failed

SOLUTION:

On the Source node, execute the following from an elevated/Administrator’s command prompt:

  • cd %LKBIN%
  • Type “eqv_list” to view all of the equivalencies

If any are present, those need to be removed:

  • Type “eqv_remove -t {name of the resource} -S {name of the other systems} -e SHARED

If you have a cluster with more than 2 nodes you MUST add some additional arguments to the eqv_remove command. Otherwise, equivalencies will be deleted for all systems.

--- eqv_remove -t {name of the resource} -S {name of the other systems} -e SHARED -s {name of the system you are running on} -o {name of the resource on the system you are running on}

The aforementioned needs to be repeated until all equivalencies have been removed. This can be verified by executing “eqv_list

Once completed, return to the LifeKeeper GUI, select the parent level resource on the Active/Source server and Extend Resource Hierarchy.

Guide for setting up a Basic SQL Cluster

LifeKeeper/SQL installation Cheat Sheet

After the SQL Server CD/DVD or ISO media has been installed . . . . .

Via the SQL Server Installation Center

  • Select New installation or add features to an existing installation
  • Select all the defaults for the “Setup Support Files”
  • For Setup Role select “ SQL Server Feature Installation”
  • On the Feature Selection screen, select the features of your choice
    • Note: Under “Shared feature Directory:” maintain the default installation path(s). During the LifeKeeper MS SQL Server installation the database will be directed to the mirrored volumes
  • Per the Instance Configuration select “Default instance”
  • Verify Disk Space Requirement, then select Next

Server Configuration:

  • In the dialogue box below, (bottom right) select “Use the same account for all SQL Server services”
  • For the Account Name and Password, a domain administrator or an account with elevated domain permission should be entered. NOTE: These credentials are required to be the same on other servers running SQL/LifeKeeper. Then select Next

Database Engine Configuration:

  • Authentication Mode
    • Select Mixed Mode (SQL Server authentication and Windows authentication)
    • Specify the SQL Server system administrator (sa) account password. NOTE: These credentials are required to be the same on other servers running SQL/LifeKeeper.
  • Specify SQL Server administrators
    • Choose “Add Current User” which is a domain administrator or an account with elevated permission. SAME as from the Server Configuration portion earlier.
  • Analysis Service Configuration
    • Choose “Add Current User” which is a domain administrator or an account with elevated permission. SAME as from the Server Configuration portion earlier

Reporting Services Configuration:

  • Install, but do not configure the report server

Error Reporting (Optional)

Ready to Install:

  • Select Install

LifeKeeper/SQL Server Resource Installation

Open the LifeKeeper Console:

  • Comm paths need to be established
  • Create Resource Hierarchy on the Source
  • Select the appropriate Primary/Backup Server
  • For the Application to protect, select the drop down box for “MS SQL Server”
  • Select Microsoft SQL Server Instance from the drop down box
  • Enter Administrative User Name for {Server name}
    • Typically this is the SA account you defined in the SQL installation or an account that has permissions to the SQL Master database
  • Current MSSQL Configuration for {Server name}. This is a list of all system and user defined database as they will be moved to the mirrored volumes. Select Continue
  • You will see an error message about “LifeKeeper has detected that one or more databases is located . . .”, select OK, and then Continue again
  • Select Destination Volume for Database Relocation
  • . . . Relocating Database(s) for {Server name}
  • Select Optional Services for Protection (OPTONAL)
  • Select Protected IP Address (If one has been reserved )
  • Select Named Pipes Alias, none
  • Microsoft SQL Server Resource Name, SQL.Default or change as needed, then select Create
  • Executing the pre-extend scripts, PreExtend checks were successful, select Next
  • Extend Wizard
    • Select a Backup Priority for the SQL Resource on the backup server. The Backup Priority of 10 is the default. Select Extend.

Upon completion, a SQL resource will be displayed in the Hierarchies navigation panel of the LifeKeeper console.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment