Network Load Balance on Windows 2003

Step by Step for NLB

To create a NLB, below are some steps that can be followed (especially in the OS Windows 2003):

1. Prepare the servers will be used to NLB, including setting Directory

2. Copy the entire Web site will be made to the server NLB (exactly the same as the first website: can use the IIS Migration Tool to transfer from the IIS config, Install components used, the ODBC settings, etc.)

3. First testing each of the NLB servers results (can be made with the Public IP to control new first)

4. If every server that is used for NLB is running according to the origin, the next step is to create a NLB.

5. To create a NLB, NLB can select the menu in the OS menu

7. Create a public IP that will be used as the front door as the NLB Home (Virtual)

8. If step No. 7 was successful, then create a cluster from any other server.

9. From the menu select the menu add NLB cluster, and enter the external IP of the server that created NLB servers

10. so on until all the servers in NLB successfully add the main server.

SQL Server Error Message - Could not create an acceptable cursor

This is a solution for the errors that arise when using the LINK server between MSSQL database server. If you use the LINK server name it Server A and Server B, then created a procedure in Server A, where the procedure is to read the data available in the link server B.

At the time the procedure is run on server A and will update the server B (Insert / Update / Delete) but it appears the following error:

Server: Msg 16955, Level 16, State 2, Line 1
Could not create an acceptable cursor.
OLE DB provider "SQLNCLI" for linked server "xx.xx.xx.xx" returned message "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
 

That happens because the server used table B there is no Unique Index or Primary Key. So the solution can be given is:
- Tables are used in servers LINK B add Primary Key or Unique Index (Non-clustered).

If you've added, then the error will be resolved.

SAN Storage to Repair

Tgl 25 Jan lalu, sebenarnya akan ada pemasangan Harddisk baru untuk SAN Storage, tetapi ternyata di mesin SAN tersebut terdapat 2 harddisk yang error (amber).  Karena masih ada harddisk yang belum terpasang maka harddisk tersebut digunakan untuk menggantikan harddisk yang error tersebut.

Harddisk lama dicabut, dan dimasukkan/diganti dengan harddisk baru. Setelah melakukan sinkronisasi data selama kurang lebih 40 menit harddisk hasil sinkronisasi masih error (amber). Kemudian dilakukan hal serupa untuk harddisk yang error satunya lagi, kali ini hasilnya berhasil.

Namun dengan adanya harddisk yg error tersebut, pekerjaan pemasangan harddisk baru jadi tertunda, dan migrasi Server DB-nya ikut tertunda juga.