Post reply

Log Shipping from 2000 to 2005

  • March 28, 2006 at 4:18 pm

    #167539

    All,

    Does anybody know what the most effective method to Log Ship from SQL 2000 to SQL 2005 is?  The Enterprise Edition Log Shipping functionality doesn't allow you to do it thru the DB Maint Plan between these two versions?  Any "roll your own" suggestions?

    Thanks everyone,

    David

  • March 29, 2006 at 2:19 am

    #629394

     

    1. Set up a shared folder on the secondary server, accessible from the primary server.
    2. On the primary server, schedule SQL Backup to perform a transaction log backup periodically. Use the COPYTO option to copy the resulting backup files to the secondary server.
    3. On the secondary server, schedule SQL Backup to perform a transaction log restore using wildcards for file names and the MOVETO option to move the files to another folder after the restore process has completed.

    There is no need to set up a linked server, use SQL Server 2000 Enterprise Edition, nor write a single line of T-SQL script.

    I'm fairly certain other backup tools like Litespeed and Sonasoft have their own methods for log shipping as well.   Just trying to offer another alternative.  BTW doesn't SQL Server 2005 have a builtin feature like the COPYTO parameter in Red-gate's product? SQL Server 2005 lets you create mirrored backups and if these mirrored backups can be created on  shared network device maybe a scheduled job to to the restore can be used to do log shipping

  • March 30, 2006 at 3:21 am

    #629765

    Why on Earth would you have a backup system running on a different version of SQL Server?

    Did you do the same with 7/2000?

Viewing 3 posts - 1 through 2 (of 2 total)

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