--070303010507090703040805
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
My company is considering a new Itanium cluster in our production
environment. Our DR boxes are still 32-bit with no plans to replace
them with 64-bit boxes. We currently log ship our production DBs from
our 32-bit production clusters to our 32-bit DR cluster.
My boss asked me this week (as part of the Itanium considerations) if
we'll be able to still log ship the production DBs from our new 64-bit
SQL instances to our 32-bit DR SQL instances. After a little thought I
said it would probably work but I've never done it myself or read
anything from someone who had done it so I couldn't say definitively
that it would work. (I fired off the question to my TAM but haven't
heard back from him.)
The only potential problem I can think of would be during the restore
phase of the sync - will a backup from a 64-bit instance restore
properly to a 32-bit instance? Do they have different internal DB
structures like SQL 7.0 vs SQL 2000 for example? If so, will that
conversion happen automagically like SQL 7 -> 2000?
Has anyone done this before (log shipping from a primary 64-bit SQL
instance to a secondary 32-bit SQL instance)? Does it work? Is it
supported by Microsoft? Can the log shipping monitor run on a 32-bit
instance?
--
*mike hodgson*
blog: http://sqlnerd.blogspot.com
--070303010507090703040805
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>My company is considering a new Itanium cluster in our production
environment. Our DR boxes are still 32-bit with no plans to replace
them with 64-bit boxes. We currently log ship our production DBs from
our 32-bit production clusters to our 32-bit DR cluster.<br>
<br>
My boss asked me this week (as part of the Itanium considerations) if
we'll be able to still log ship the production DBs from our new 64-bit
SQL instances to our 32-bit DR SQL instances. After a little thought I
said it would probably work but I've never done it myself or read
anything from someone who had done it so I couldn't say definitively
that it would work. (I fired off the question to my TAM but haven't
heard back from him.)<br>
<br>
The only potential problem I can think of would be during the restore
phase of the sync - will a backup from a 64-bit instance restore
properly to a 32-bit instance? Do they have different internal DB
structures like SQL 7.0 vs SQL 2000 for example? If so, will that
conversion happen automagically like SQL 7 -> 2000?<br>
<br>
Has anyone done this before (log shipping from a primary 64-bit SQL
instance to a secondary 32-bit SQL instance)? Does it work? Is it
supported by Microsoft? Can the log shipping monitor run on a 32-bit
instance?<br>
</tt><tt></tt>
<div class="moz-signature">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2">blog:</font><font face="Tahoma" size="2"> <a
href="http://links.10026.com/?link=http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
</body>
</html>
--070303010507090703040805--This is a multi-part message in MIME format.
--=_NextPart_000_004C_01C5986D.BCCBB090
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Never tried it yet but it should work as far as I know. You can take a =32 bit backup or detached file and restore it or attach it to a 64 bit =and visa versa. So I see no reason why log shipping would not work. =The internal structures do not change.
-- Andrew J. Kelly SQL MVP
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message =news:uH9URVImFHA.1148@.TK2MSFTNGP12.phx.gbl...
My company is considering a new Itanium cluster in our production =environment. Our DR boxes are still 32-bit with no plans to replace =them with 64-bit boxes. We currently log ship our production DBs from =our 32-bit production clusters to our 32-bit DR cluster.
My boss asked me this week (as part of the Itanium considerations) if =we'll be able to still log ship the production DBs from our new 64-bit =SQL instances to our 32-bit DR SQL instances. After a little thought I =said it would probably work but I've never done it myself or read =anything from someone who had done it so I couldn't say definitively =that it would work. (I fired off the question to my TAM but haven't =heard back from him.)
The only potential problem I can think of would be during the restore =phase of the sync - will a backup from a 64-bit instance restore =properly to a 32-bit instance? Do they have different internal DB =structures like SQL 7.0 vs SQL 2000 for example? If so, will that =conversion happen automagically like SQL 7 -> 2000?
Has anyone done this before (log shipping from a primary 64-bit SQL =instance to a secondary 32-bit SQL instance)? Does it work? Is it =supported by Microsoft? Can the log shipping monitor run on a 32-bit =instance?
--
mike hodgson
blog: http://sqlnerd.blogspot.com=20
--=_NextPart_000_004C_01C5986D.BCCBB090
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Never tried it yet but it should work as far as I =know. You can take a 32 bit backup or detached file and restore it or attach =it to a 64 bit and visa versa. So I see no reason why log shipping would =not work. The internal structures do not change.
-- Andrew J. Kelly SQL MVP
"Mike Hodgson"
--mike =hodgsonblog: http://sqlnerd.blogspot.com
--=_NextPart_000_004C_01C5986D.BCCBB090--
