On the Primary Server

  1. Power down the backup server so that there is no chance of simultaneous access to your shared storage.
  1. Use the Windows Disk Management tool to configure your disk resources and define the shared volumes that you want to use. (Be sure the volume size is adequate.)
  1. It is recommended that you use Windows Explorer to unshare from the network all volumes to be used by the SQL Server Instance.
  1. Configure your networking to support the LifeKeeper for Windows TCP/IP comm path(s) and, if applicable, the switchable IP address.
  1. Install the LifeKeeper for Windows Core software on a local disk, followed by the LifeKeeper for Windows SQL Server Recovery Kit.

On the Backup Server

  1. Bring up the backup server and use the Disk Management utility to assign the same drive letter to the shared volume as assigned on the primary server.
  1. Install the LifeKeeper for Windows Core software on a local disk, followed by the LifeKeeper for Windows SQL Server Recovery Kit.

On the Primary Server

Now that you have LifeKeeper for Windows installed on both servers, go back to the primary server and do the following:

  1. In LifeKeeper for Windows, create comm paths between the primary and backup servers.
  1. In LifeKeeper for Windows, create your volume resource and IP communication resource and extend them to the backup server. Later when you create your SQL Server resource hierarchy, LifeKeeper for Windows will automatically bring these resources into the hierarchy as dependencies.

Install the SQL Server Software

  1. If using shared volumes, bring the volume resource hierarchy In Service on the backup server using the LifeKeeper GUI.
  1. On the backup server, install Microsoft SQL Server using the following guidelines:
  • Install the database engine, along with any additional features. Configure the instance data and log files so that they are stored on volumes that are protected by the LifeKeeper for Windows.

  • Select “Mixed Mode” database authentication, and enter a non-blank password for the SA account. The passwords MUST be the same on all servers in the cluster.

When the installation is complete, use* Microsoft SQL Server Configuration Manager* to verify that SQL Server can start properly on the backup server. Stop all Microsoft SQL Services on the backup server.

For shared volumes, do the following steps.

  1. Bring the volume resource hierarchy In Service on the primary server.


  2. On the primary server, open Explorer and access the drive associated with the shared volume.


  3. Delete the directory where you previously installed the SQL data files. (You will re-install them in the next step).


  4. Install Microsoft SQL Server on the primary server EXACTLY as you did on the backup server (program files on the local disk and data files on the shared volume).

When the installation is complete, use Microsoft SQL Server Configuration Manager to verify that SQL Server can start properly on the primary server.

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