Post reply

LOG SHIPPING by two different systemt architecture?

  • January 8, 2013 at 3:32 am

    #272640

    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

  • January 8, 2013 at 3:46 am

    #1574705

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

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

  • January 8, 2013 at 3:50 am

    #1574710

    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

  • January 8, 2013 at 3:52 am

    #1574713

    ananda.murugesan (1/8/2013)

    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

    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?

  • January 8, 2013 at 4:05 am

    #1574718

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

  • January 8, 2013 at 4:13 am

    #1574724

    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,

  • January 22, 2013 at 8:21 am

    #1579659

    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 ?

  • January 22, 2013 at 8:30 am

    #1579663

    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

  • January 22, 2013 at 8:44 am

    #1579672

    Thanks for your reponse.

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

  • January 22, 2013 at 8:45 am

    #1579674

    Yes, or downgrade your secondary to 2008 R2.

  • September 16, 2015 at 8:56 pm

    #1827289

    Team dba,

    I just need a clarification if I have my primary server a standard edition of sql server 2008 r2 and my secondary server is sql server 2008 r2 enterprise ..in this case is log shipping possible...because I have said no to my boss that in this scenario log shipping is not possible...:-)

  • September 17, 2015 at 2:40 am

    #1827309

    Providing the database doesn't contain persistent enterprise-only features (compression, partitioning, etc), then it is possible.

    Please in future post new questions in a new thread.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 12 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Login to reply