How to 'share drive', SCSI HD's on servers

Rodney is correct, your SAN or DAS solution must be in the
Windows Catalog for use on a cluster, but it's more than
just getting disks. How you carve them up is just as
important, because, for example, if you create one LUN but
plan to put multiple drives on it, that won't work.
You need to plan your disk layout carefully.
I am sorry for my lack of understanding here, but let's say if I have two
"regular" Compaq ML370, can I just add two more disks on each server and
let's say create a Raid1 and use that as the 'quorum' ? I've seen the list
of devices Rod listed OK, but I still don't understand how to configure the
disks on my servers to be used in a cluster (assume they are part of the MS
HCL).
"Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
news:575601c47470$953e6530$a601280a@.phx.gbl...
> Rodney is correct, your SAN or DAS solution must be in the
> Windows Catalog for use on a cluster, but it's more than
> just getting disks. How you carve them up is just as
> important, because, for example, if you create one LUN but
> plan to put multiple drives on it, that won't work.
> You need to plan your disk layout carefully.
|||I think you need to read this
http://www.microsoft.com/downloads/d...displaylang=en
its a step by step guide on cluster installations
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
news:OaEfxULdEHA.3916@.TK2MSFTNGP11.phx.gbl...
> I am sorry for my lack of understanding here, but let's say if I have two
> "regular" Compaq ML370, can I just add two more disks on each server and
> let's say create a Raid1 and use that as the 'quorum' ? I've seen the
list
> of devices Rod listed OK, but I still don't understand how to configure
the
> disks on my servers to be used in a cluster (assume they are part of the
MS
> HCL).
>
> "Allan Hirt" <anonymous@.discussions.microsoft.com> wrote in message
> news:575601c47470$953e6530$a601280a@.phx.gbl...
>
|||(...)
Actually it is what I didn't understand: From the text below I had the
impresson that "external disk storage unit connected to all computers" I
still can't see how my regular SCSI disks existing on both Compaq servers
can be configured as shared disks. It also says that the controller cannot
be the one used by the system drive...
Shared Disk Requirements:
An HCL-approved external disk storage unit connected to all
computers. This will be used as the clustered shared disk. Some type of a
hardware redundant array of independent disks (RAID) is recommended.
All shared disks, including the quorum disk, must be physically
attached to a shared bus.
Note: The requirement above does not hold true for Majority Node Set (MNS)
clusters, which are not covered in this guide.
Shared disks must be on a different controller then the one used
by the system drive.
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:uzdl$BMdEHA.384@.TK2MSFTNGP10.phx.gbl...
> I think you need to read this
>
http://www.microsoft.com/downloads/d...displaylang=en[vbcol=seagreen]
> its a step by step guide on cluster installations
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> "Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
> news:OaEfxULdEHA.3916@.TK2MSFTNGP11.phx.gbl...
two
> list
> the
> MS
>
|||Marlon, you have all the facts already. You need to buy or use an external
storage, on a different controller.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
news:uhsppKOdEHA.1652@.TK2MSFTNGP09.phx.gbl...
> (...)
> Actually it is what I didn't understand: From the text below I had the
> impresson that "external disk storage unit connected to all computers" I
> still can't see how my regular SCSI disks existing on both Compaq servers
> can be configured as shared disks. It also says that the controller cannot
> be the one used by the system drive...
>
> Shared Disk Requirements:
> An HCL-approved external disk storage unit connected to all
> computers. This will be used as the clustered shared disk. Some type of a
> hardware redundant array of independent disks (RAID) is recommended.
> All shared disks, including the quorum disk, must be physically
> attached to a shared bus.
> Note: The requirement above does not hold true for Majority Node Set (MNS)
> clusters, which are not covered in this guide.
> Shared disks must be on a different controller then the one used
> by the system drive.
> "Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
> message news:uzdl$BMdEHA.384@.TK2MSFTNGP10.phx.gbl...
>
http://www.microsoft.com/downloads/d...displaylang=en[vbcol=seagreen]
> two
and[vbcol=seagreen]
configure[vbcol=seagreen]
the
>
|||Marlon,
I am considering writing an entire book on disk=20
architecture/design for SQL Server, but I would also=20
suggest you look at the stuff I have in the existing SQL=20
2K HA book to understand what goes into making a cluster.
At a minimum, you need (presented at the OS level) for=20
your cluster:
* 1 quorum disk
* 1 for SQL Server (probably more; I'd say a minimum of=20
two for data and log, but it will depend on your=20
requirements)
* 1 for MS DTC (for W2K3 required, and recommended for W2K)
Each of these should reside on different physical LUNs on=20
an external drive array, whether DAS or SAN (*not* NAS. =20
The quorum LUN must not be on a disk with any other (many=20
find it a waste of space, but that's the way it is). Some=20
vendors allow you to carve up one chunk of disk, and then=20
do partitions, and that is not really what you should do.
Hope this helps.
Allan

>--Original Message--
>Marlon, you have all the facts already. You need to buy=20
or use an external[vbcol=seagreen]
>storage, on a different controller.
>Cheers,
>Rod
>MVP - Windows Server - Clustering
>http://www.nw-america.com - Clustering
>"Marlon Brown" <marlon_brown@.hotmail.com> wrote in message
>news:uhsppKOdEHA.1652@.TK2MSFTNGP09.phx.gbl...
below I had the[vbcol=seagreen]
all computers" I[vbcol=seagreen]
both Compaq servers[vbcol=seagreen]
the controller cannot[vbcol=seagreen]
connected to all[vbcol=seagreen]
disk. Some type of a[vbcol=seagreen]
recommended.[vbcol=seagreen]
must be physically[vbcol=seagreen]
Majority Node Set (MNS)[vbcol=seagreen]
controller then the one used[vbcol=seagreen]
america.com> wrote in
>http://www.microsoft.com/downloads/details.aspx?
FamilyID=3D96f76ed7-9634-4300-9159-
89638f4b4ef7&displaylang=3Den[vbcol=seagreen]
message[vbcol=seagreen]
let's say if I have[vbcol=seagreen]
disks on each server[vbcol=seagreen]
>and
the 'quorum' ? I've seen the[vbcol=seagreen]
understand how to[vbcol=seagreen]
>configure
they are part of[vbcol=seagreen]
>the
wrote in message[vbcol=seagreen]
be in the[vbcol=seagreen]
more than[vbcol=seagreen]
just as[vbcol=seagreen]
one LUN but[vbcol=seagreen]
work.
>
>.
>

how to setup Integration Services on SQL 2005 cluster

We have SQL Server 2005 cluster setup, active/passive, 2 nodes, on Windows
2003. If I try to add a maintenance task using sql management studio on my
pc I get error: "apply to target server failed for job". If I try it using
management studio while on the active node of the cluster I get error:
"failed to create the task, exception from hresult: 0xC0010014
Microsoft.SqlServer.DTSRuntimeWrap".
I installed Integration Services on both nodes and followed instructions in
document ms345193 to configure IS on the cluster, but I must have something
wrong.
Any ideas what I should look at to get this to work? Thanks!
Denise,
this you follow this http://msdn2.microsoft.com/en-us/library/ms345193.aspx
?
HTH,
_Edwin.
"denise" <denise@.discussions.microsoft.com> wrote in message
news:92A9C846-69CA-4B46-87FE-75E567904FD9@.microsoft.com...
> We have SQL Server 2005 cluster setup, active/passive, 2 nodes, on Windows
> 2003. If I try to add a maintenance task using sql management studio on
my
> pc I get error: "apply to target server failed for job". If I try it
using
> management studio while on the active node of the cluster I get error:
> "failed to create the task, exception from hresult: 0xC0010014
> Microsoft.SqlServer.DTSRuntimeWrap".
> I installed Integration Services on both nodes and followed instructions
in
> document ms345193 to configure IS on the cluster, but I must have
something
> wrong.
> Any ideas what I should look at to get this to work? Thanks!
|||Yes, I was a little unsure of which drives to use as the dependencies (should
all shared drives be there, we have several, I just picked one, E drive), and
the registry set up, in step 9, I just put what is in the document, then in
step 14 I put the shared drive where I copied the MsDtsSrvr.ini.xml file (I
used E drive).
Could someone talk me through what should be set in each step? Thanks!
"Edwin vMierlo" wrote:

> Denise,
> this you follow this http://msdn2.microsoft.com/en-us/library/ms345193.aspx
> ?
> HTH,
> _Edwin.
>
>
> "denise" <denise@.discussions.microsoft.com> wrote in message
> news:92A9C846-69CA-4B46-87FE-75E567904FD9@.microsoft.com...
> my
> using
> in
> something
>
>
|||
> Yes, I was a little unsure of which drives to use as the dependencies
(should
> all shared drives be there, we have several, I just picked one, E drive),
and
If the E drive is the only drive you use for the packages and file, than
that is OK, however if not sure you can add all drives.

> the registry set up, in step 9, I just put what is in the document, then
in
In step 9 you fill in the registry location (not the disk);
"SOFTWARE\Microsoft\MSDTS\ServiceConfigFile"

> step 14 I put the shared drive where I copied the MsDtsSrvr.ini.xml file
(I
> used E drive).
In step 14 you put in the fulname and directory path in the registry,
Example
E:\dir\subdir\MsDtsSrvr.ini.xml

> Could someone talk me through what should be set in each step? Thanks!
HTH,
_Edwin.
|||I have all this set up correctly. Any other ideas of what could be wrong?
Would it be affected by the MSDTS configuration set up on the cluster?
Thanks so much for your help.
"Edwin vMierlo" wrote:

> (should
> and
> If the E drive is the only drive you use for the packages and file, than
> that is OK, however if not sure you can add all drives.
> in
> In step 9 you fill in the registry location (not the disk);
> "SOFTWARE\Microsoft\MSDTS\ServiceConfigFile"
> (I
> In step 14 you put in the fulname and directory path in the registry,
> Example
> E:\dir\subdir\MsDtsSrvr.ini.xml
>
> HTH,
> _Edwin.
>
>

How to setup integration services on a cluster

Does anyone know how to install SQL 2005 integration services on a cluster machine?

I have an a-a cluster machine. Both nodes are using SQL 2005 naming instance. During the SQL installation, I did include integration services option as one of my setup items. The setup process was running fine but I can’t connect to integration services via MS SQL Server management studio. I see below errors:

“Invalid server name "TESTServer\B123". SSIS service does not support multi-instance, use just server name instead of "server name\instance".

Looks like I must use default instance for 2005 integration services. I re-ran the setup program and added a default instance on the same cluster node. (On that node I have one default instance and one naming instance). Now I can connect to the default SQL Server but when I click on “stored packages”, I don’t see file system and MSDB. It shows nothing at all. Any idea how to make integration services running on a cluster machine?

Thanks

I had the same error when I tried to view an SSIS package on my server with 2 instances but I had no default instance, so my case was a little different than yours. The way I resolved my problem was by hard coding both instances into my XML configuration file. I did not have a cluster in this case but the principle should be the same, you'll just have to play around with it a little bit. You may also have to modify the XML file on both nodes of your cluster.

<ServerName>my-server-01\instance1</ServerName>
<ServerName>my-server-01\instance2</ServerName>

If you have a default instance and a named instance you might try something like this:

<ServerName>my-server-01</ServerName>
<ServerName>my-server-01\instance1</ServerName>

Microsoft SQL Server 2005 Integration Services (SSIS) includes a configuration file for configuring the Integration Services service.

By default, the file is located in the folder, Program Files\Microsoft SQL Server\90\DTS\Binn, and the file name is MsDtsSrvr.ini.xml.

http://msdn2.microsoft.com/en-us/library/ms137789.aspx

|||

Microsoft has a document published on how to install Integration Services on a cluster.

http://msdn2.microsoft.com/en-us/library/ms345193.aspx

|||

I have the same problem in that I have set up SSIS on the cluster using the microsoft instructions. The SSIS service starts and fails over between nodes just fine. The problem is that I cannot see the MSDB or File System under Stored Packages. I've double (tripple) checked the path to the XML in the registry, the registry path in the cluster service properties, and the XML itself. Everything seems in order.

Any ideas?

|||

I'm in exactly the same situation. Did anyone resolve this problem ?

tia

bryn64

|||Have smae problem. Resolution?

How to setup integration services on a cluster

Does anyone know how to install SQL 2005 integration services on a cluster machine?

I have an a-a cluster machine. Both nodes are using SQL 2005 naming instance. During the SQL installation, I did include integration services option as one of my setup items. The setup process was running fine but I can’t connect to integration services via MS SQL Server management studio. I see below errors:

“Invalid server name "TESTServer\B123". SSIS service does not support multi-instance, use just server name instead of "server name\instance".

Looks like I must use default instance for 2005 integration services. I re-ran the setup program and added a default instance on the same cluster node. (On that node I have one default instance and one naming instance). Now I can connect to the default SQL Server but when I click on “stored packages”, I don’t see file system and MSDB. It shows nothing at all. Any idea how to make integration services running on a cluster machine?

Thanks

I had the same error when I tried to view an SSIS package on my server with 2 instances but I had no default instance, so my case was a little different than yours. The way I resolved my problem was by hard coding both instances into my XML configuration file. I did not have a cluster in this case but the principle should be the same, you'll just have to play around with it a little bit. You may also have to modify the XML file on both nodes of your cluster.

<ServerName>my-server-01\instance1</ServerName>
<ServerName>my-server-01\instance2</ServerName>

If you have a default instance and a named instance you might try something like this:

<ServerName>my-server-01</ServerName>
<ServerName>my-server-01\instance1</ServerName>

Microsoft SQL Server 2005 Integration Services (SSIS) includes a configuration file for configuring the Integration Services service.

By default, the file is located in the folder, Program Files\Microsoft SQL Server\90\DTS\Binn, and the file name is MsDtsSrvr.ini.xml.

http://msdn2.microsoft.com/en-us/library/ms137789.aspx

|||

Microsoft has a document published on how to install Integration Services on a cluster.

http://msdn2.microsoft.com/en-us/library/ms345193.aspx

|||

I have the same problem in that I have set up SSIS on the cluster using the microsoft instructions. The SSIS service starts and fails over between nodes just fine. The problem is that I cannot see the MSDB or File System under Stored Packages. I've double (tripple) checked the path to the XML in the registry, the registry path in the cluster service properties, and the XML itself. Everything seems in order.

Any ideas?

|||

I'm in exactly the same situation. Did anyone resolve this problem ?

tia

bryn64

|||Have smae problem. Resolution?sql

How to setup integration services on a cluster

Does anyone know how to install SQL 2005 integration services on a cluster machine?

I have an a-a cluster machine. Both nodes are using SQL 2005 naming instance. During the SQL installation, I did include integration services option as one of my setup items. The setup process was running fine but I can’t connect to integration services via MS SQL Server management studio. I see below errors:

“Invalid server name "TESTServer\B123". SSIS service does not support multi-instance, use just server name instead of "server name\instance".

Looks like I must use default instance for 2005 integration services. I re-ran the setup program and added a default instance on the same cluster node. (On that node I have one default instance and one naming instance). Now I can connect to the default SQL Server but when I click on “stored packages”, I don’t see file system and MSDB. It shows nothing at all. Any idea how to make integration services running on a cluster machine?

Thanks

I had the same error when I tried to view an SSIS package on my server with 2 instances but I had no default instance, so my case was a little different than yours. The way I resolved my problem was by hard coding both instances into my XML configuration file. I did not have a cluster in this case but the principle should be the same, you'll just have to play around with it a little bit. You may also have to modify the XML file on both nodes of your cluster.

<ServerName>my-server-01\instance1</ServerName>
<ServerName>my-server-01\instance2</ServerName>

If you have a default instance and a named instance you might try something like this:

<ServerName>my-server-01</ServerName>
<ServerName>my-server-01\instance1</ServerName>

Microsoft SQL Server 2005 Integration Services (SSIS) includes a configuration file for configuring the Integration Services service.

By default, the file is located in the folder, Program Files\Microsoft SQL Server\90\DTS\Binn, and the file name is MsDtsSrvr.ini.xml.

http://msdn2.microsoft.com/en-us/library/ms137789.aspx

|||

Microsoft has a document published on how to install Integration Services on a cluster.

http://msdn2.microsoft.com/en-us/library/ms345193.aspx

|||

I have the same problem in that I have set up SSIS on the cluster using the microsoft instructions. The SSIS service starts and fails over between nodes just fine. The problem is that I cannot see the MSDB or File System under Stored Packages. I've double (tripple) checked the path to the XML in the registry, the registry path in the cluster service properties, and the XML itself. Everything seems in order.

Any ideas?

|||

I'm in exactly the same situation. Did anyone resolve this problem ?

tia

bryn64

|||Have smae problem. Resolution?

How to setup cluster ?

Hi,
I've 3 PC. 2 x Win2K AS and 1 Win2K Pro. Is it possible to cluster the 2
Win2K AS as Primary & Secondary while the Win2K Pro serves as the shared disk
server ?
Do I need to get a Raid card for Win2K Pro PC ?
Advice pls.
You might be able to use iSCSI on the XP box, though I have not tested it.
Other then that, you are asking for instructions that probably don't exist,
and if they did would probably not be supported. If you are in need of a
test environment, may I suggest VS 2005?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Desmond" <Desmond@.discussions.microsoft.com> wrote in message
news:BD968661-3225-4791-A263-2AEC7212A1A4@.microsoft.com...
> Hi,
> I've 3 PC. 2 x Win2K AS and 1 Win2K Pro. Is it possible to cluster the 2
> Win2K AS as Primary & Secondary while the Win2K Pro serves as the shared
> disk
> server ?
> Do I need to get a Raid card for Win2K Pro PC ?
> Advice pls.
|||Forget about using the Win2K Pro as the 'shared disk server' (I took 'shared
disk server' to mean file server). Get an external RAID controller and some
disks to serve as the shared disks, and use the two Win2K AS as the nodes.
Linchi
"Desmond" <Desmond@.discussions.microsoft.com> wrote in message
news:BD968661-3225-4791-A263-2AEC7212A1A4@.microsoft.com...
> Hi,
> I've 3 PC. 2 x Win2K AS and 1 Win2K Pro. Is it possible to cluster the 2
> Win2K AS as Primary & Secondary while the Win2K Pro serves as the shared
> disk
> server ?
> Do I need to get a Raid card for Win2K Pro PC ?
> Advice pls.
|||If this is for production please be sure that you have read the following
KB article and are aware of the limitations of a non-dertified solution:
327518 INF: The Microsoft Support Policy for a SQL Server Failover Cluster
http://support.microsoft.com/?id=327518
To setup a test enviroment you will need at least one external SCSI drive
or ability to setup using iSCSI
Dave Whitney
SQL Support
This posting is provided "AS IS" with no warranties, and confers no rights.

How to setup a backup server for SQL Server2005 for production (in case the primary server fails

I currently have a SQL Server cluster setup with a Primary DB Server SERVER1 and the Standby server SERVER2. SERVER1 has been failing more than normal is the past few weeks and its takes upto 5 mins for SERVER2 realize that SERVER1 is down. I am looking for a better way to implement a backup server on production with minimum downtime. Please adivse..

you have two options one is Database mirroring and other is log shipping in sql 2005..........but i advise you to go with db mirroring as the downtime is less in high availability mode as you have a witness server and hence the failover will be automatic and within few seconds............but in log shipping only manual failover is possible........refer,

http://dumthata.com/sqlchn/articles/dbmrr.htm

http://dumthata.com/sqlchn/articles/lship.htm

Going forward pls post in the appropriate forum as it would be easier to read through and answer....