LOG SHIPPING by two different systemt architecture?

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2008 » SQL Server 2008 High Availability » LOG SHIPPING by two different systemt...

LOG SHIPPING by two different systemt architecture?

Rate Topic

Display Mode

Topic Options

Author

Message

ananda.murugesan

Posted Tuesday, January 08, 2013 3:32 AM

SSC Eights!

Group: General Forum Members
Last Login: Today @ 10:41 PM
Points: 827, Visits: 2,417

Hi,

Can we able to configure for LOG SHIPPING by two different systemt architecture?

source server
-------------
System type – windows 2008 R2 enterprise edition 64 bit operating system
Database – MS SQL SERVER 2008 Enterprise edition 64 bit

Destination server
--------------------
System type – windows 2008 enterprise edition 32 bit operating system
Database – MS SQL SERVER 2008 Enterprise edition 32 bit

Thanks
ananda

Post #1404096

anthony.green

Posted Tuesday, January 08, 2013 3:46 AM

SSCertifiable

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 2:40 AM
Points: 5,075, Visits: 4,833

Yes if the destination is of the same SQL version or higher.

Log shipping doesnt matter if its 32 bit or 64 bit.

Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1404104

ananda.murugesan

Posted Tuesday, January 08, 2013 3:50 AM

SSC Eights!

Group: General Forum Members
Last Login: Today @ 10:41 PM
Points: 827, Visits: 2,417

I have doubt, destination server - SQL 2008 32 bit enterprise edition, it is not higher then source server.

source server - SQL 2008 R2 64 bit enterprise edition.
Pl. confirm.

thanks

Post #1404109

anthony.green

Posted Tuesday, January 08, 2013 3:52 AM

SSCertifiable

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 2:40 AM
Points: 5,075, Visits: 4,833

ananda.murugesan (1/8/2013)

Your original post says that both SQL servers are SQL 2008 Enterprise, 1 is 64 bit 1 is 32bit.

You detail that the operating system is 2008R2 on one and 2008 on the other.

So what is it, are the SQL Servers different versions or is it just the OS, or is it both?

Post #1404112

ananda.murugesan

Posted Tuesday, January 08, 2013 4:05 AM

SSC Eights!

Group: General Forum Members
Last Login: Today @ 10:41 PM
Points: 827, Visits: 2,417

ok, Thanks...the same version can possible to configure for log shipping...not concern with 32 or 64 bits and 2008 R2

Post #1404118

anthony.green

Posted Tuesday, January 08, 2013 4:13 AM

SSCertifiable

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 2:40 AM
Points: 5,075, Visits: 4,833

Logshipping is basically doing backup and restore, so the same backup and restore rules apply, you can do it to the same version or a higher version.

But once you have restored to a higher version and made it active, you cannot logship back as you will be going from higer version to lower version which cannot be done.

So best in a logshipping environment to have the same edition and level of SQL on both source and destination.

Logshipping and backup restore doesn't care if the server is 32 bit or 64 bit.

SQL 2008 to SQL 2008, logshipping will work ok, can fail back
SQL 2008 R2 to SQL 2008 R2, logshipping will work ok, can fail back
SQL 2008 to SQL 2008 R2, logshipping will work ok, CANNOT fail back
SQL 2008 R2 to SQL 2008, logshipping will NOT work,

Post #1404125

renaud.quintin

Posted Tuesday, January 22, 2013 8:21 AM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, June 11, 2013 2:24 AM
Points: 3, Visits: 12

Hello,

Do you know if log shipping is functionning in this case :

SQL server 2008 R2 --> SQL server 2012 SP1 ?
In StandBy Mode

Because when i configure log shipping on my 2008 R2, i have this message for the first Full backup restore :

"System.Data.SqlClient.SqlError: This Backup cannot be restore with WITH STANDBY because it's need an update car la mise à niveau d'une base de données est nécessaire. Réexécutez RESTORE sans WITH STANDBY. (Microsoft.SqlServer.Smo)"

Any idear ?

Post #1410062

anthony.green

Posted Tuesday, January 22, 2013 8:30 AM

SSCertifiable

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 2:40 AM
Points: 5,075, Visits: 4,833

Yes, 2008 R2 to 2012 will work, but it can only be used for 1 way, once you make the 2012 instance active (WITH RECOVERY) you will no longer be able to logship back to 2008 R2 (role switching will not be allowed back to make 2008R2 primary).

You cannot put a database into STANDBY mode when crossing version, it has to be in NORECOVERY mode.

If you need the secondary copy to be in STANDBY then primary server will need to be 2012 or secondary server will need to be 2008 R2

Post #1410066

renaud.quintin

Posted Tuesday, January 22, 2013 8:44 AM

Forum Newbie

Group: General Forum Members
Last Login: Tuesday, June 11, 2013 2:24 AM
Points: 3, Visits: 12

Thanks for your reponse.

So i need upgrade my Primary to 2012 for my readOnly Database on my secondary server.

Post #1410077

anthony.green

Posted Tuesday, January 22, 2013 8:45 AM

SSCertifiable

Group: General Forum Members
Last Login: Wednesday, June 05, 2013 2:40 AM
Points: 5,075, Visits: 4,833

Yes, or downgrade your secondary to 2008 R2.

Post #1410079

« Prev Topic | Next Topic »

Permissions