RRinTetons
IS-IT--Management
I want to set up log shipping for and instance of SQL Server 2008 R2 (64-bit). Some things I am reading about set up contradict my recent experience with backup restores, so I wanted to get some clarification. If there is a good FAQ or other documentation resource which I can refer please point me towards it.
I was recently unsuccessful in an attempt to restore a backup from 64-bit SQL Server 2008 R2 to a 32-bit SQL Server 2008 Standard instance. The MSDN article on log shipping seems to suggest that there should be no problem with such a restore and that log shipping between a 64-bit 2008 Enterprise R2 instance and 32-bit Standard 2008 instance should be successful as a first step in setting up logging, and that logging would work overall with that configuration. Any suggestions?
I suspect the secondary server should ideally be an exact mirror, hardware and software, to the primary server. Is that strictly necessary? Highly preferable? What parameters do I need to consider in selecting and configuring a secondary server?
I have some 300 client computers pointed at the primary server with a connection string that references a CNAME that points at the primary server. It is my belief that coming up on the secondary server might be as simple as changing DNS so that the CNAME points at the secondary server and having all clients log out and back into the application. I suppose I might need to force a DNS flush on the clients in case they have stored references to the primary server. Does that make sense?
Does anyone with experience in this area have any warnings of landmines I should be on the lookout for in getting the setup?
-
Richard Ray
Jackson Hole Mountain Resort
I was recently unsuccessful in an attempt to restore a backup from 64-bit SQL Server 2008 R2 to a 32-bit SQL Server 2008 Standard instance. The MSDN article on log shipping seems to suggest that there should be no problem with such a restore and that log shipping between a 64-bit 2008 Enterprise R2 instance and 32-bit Standard 2008 instance should be successful as a first step in setting up logging, and that logging would work overall with that configuration. Any suggestions?
I suspect the secondary server should ideally be an exact mirror, hardware and software, to the primary server. Is that strictly necessary? Highly preferable? What parameters do I need to consider in selecting and configuring a secondary server?
I have some 300 client computers pointed at the primary server with a connection string that references a CNAME that points at the primary server. It is my belief that coming up on the secondary server might be as simple as changing DNS so that the CNAME points at the secondary server and having all clients log out and back into the application. I suppose I might need to force a DNS flush on the clients in case they have stored references to the primary server. Does that make sense?
Does anyone with experience in this area have any warnings of landmines I should be on the lookout for in getting the setup?
-
Richard Ray
Jackson Hole Mountain Resort