4. MS SQL Host Preperation for FCM Installation.

At this stage your DS8000 should be ready to be used with FCM, for more information on preparing your DS8000 to be used with FCM please go back to Section 3. This section will cover preparing your MS SQL Server for FCM installation. The environment used to prepare this guide as mentioned earlier was running Windows 2003 64-bit SP2 with MS SQL 2005 Server 64-bit SP3. Other versions of Windows & SQL should follow the same path of host preparation & FCM installation, but might require an additional SQL or Windows hotfixes.

This guide assumes that the reader is familiar with Microsoft Windows & MS SQL Server. It assumes that Microsoft SQL Server 2005 SP3 has been already setup on a Windows 2003 SP2 either in a stand alone or a clustered environment prior to proceeding any further with this document. This document as well assumes that IBM DS8000 Subsytem Device Driver (SDD) has been installed during the Windows preparation. The host preparation for FCM installation is very similar for clustered & stand alone environment. You should follow the step below to prepare your SQL hosts for FCM installation nonetheless of it being clustered or a stand alone SQL Server. Steps that are different between clustered & stand alone SQL Server is clearly marked in the following procedure. A high level of the steps required to prepare your SQL Server 2005 SP3 host for FCM installation:

  • Install the required hotfixes depending on your environment. (Section 4.1)
  • Download & Install IBM SystemStorage DS6000 & DS8000 Series DS Open API support for Microsoft Volume Shadow Copy Service and Virtual Disk Service package for Windows Server 2003 / 2008. (Section 4.2)
  • Optional: Install Windows Power Shell. (Section 4.3)

Note: As the backup is happening on the volume level, its recommend to have only databases which will be backed up at the same time on the same LUN. In many cases, you would want to have each database on its own lun & each database logfiles in their own LUN. By doing this, you will avoid databases having unnecessary I/O freeze when another database on the same volume is getting backed up or restored.

Back to: IBM Tivoli Storage FlashCopy Manager Tutorial Index

Leave a Reply