I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt

You don't really need to have servers with identical names. What you can do
is create a DNS alias to point to the primary server and have your apps use
the alias. In the event of a disaster, you can update the DNS alias to
point to the DR site.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"md" <someone (AT) microsoft (DOT) com> wrote

I have to bring up a second set of clustered SQL servers at a DR Hotsite. To
avoid having to change any ODBC connections or application configurations
the SQL virtual server names will need to be the same at the hotsite as they
are at the normal location. The IP address scheme is different at the
hotsite. There will be a separate DNS server at the hotsite. The hotsite
will be connected to the network here at all times.

My question is, will SQL server allow identical virtual server names on the
same network at the same time? I tend to think not.

The other kicker to all this is there is a database (it's a VMWare database)
that I need to keep a constantly updated copy both here and at the hotsite.
That's why I would like to have both the hotsite and local clusters up at
the same time so I could do replication between the clusters.

Thanks for any help anyone can provide

Matt