SQL Server Performance

specify to place other files in separate folder

Discussion in 'SQL Server Log Shipping' started by BikeBoy, Nov 22, 2005.

  1. BikeBoy New Member

    Hi all,

    I need to specify to place specific data files in separate folders when I set up the logshipping. For instance:

    FileGroup1 should go on D:FileGroup1 folder on the secondary
    FileGroup2 should go on D:FileGroup2 folder on the secondary, etc.

    I don't see that option in Logshiping wizzard, all data goes to the same directory. Is there aworkaround?

    Thanks
  2. SQLDBcontrol New Member

    Not sure I fully understand your question but do you mean that you want the secondary database to in seperate folders?<br /><br />If so, manually restore the primary database onto the secondary server using the WITH MOVE option and then set up logshipping to the existing database. Don't forget to restore using the NORECOVERY or STANDBY option too <img src='/community/emoticons/emotion-1.gif' alt=':)' /><br /><br />Karl Grambow<br /><br />www.sqldbcontrol.com
  3. BikeBoy New Member

    Karl, I actually tried that and encountered a recovery issue where the restore failed because logshipping was trying to restore the log file that was tool late (LSN is too old). I found that the cleanest way to set it up is to choose the automatic "create new database" and "back up database now" rather than applying logshipping to an existing db.

    It seems like the logshipping process can not automatically determine which logs to apply when I am setting it up to "existing database" and I need to apply the correct logs manually.

    Thanks all the same
  4. SQLDBcontrol New Member

    To be honest, I've almost never set up log shipping to anything but an existing database and this has never caused a problem.

    If you're getting the "LSN is too old" error then this is unlikely to have anything to with the location of the log files. If you get this error then it is likely that either a more recent log file has not being copied over or it was lost. In this case I would suggest re-syncing log shipping by backing up the primary database and restoring it again on the secondary server.



    quote:Originally posted by BikeBoy

    Karl, I actually tried that and encountered a recovery issue where the restore failed because logshipping was trying to restore the log file that was tool late (LSN is too old). I found that the cleanest way to set it up is to choose the automatic "create new database" and "back up database now" rather than applying logshipping to an existing db.

    It seems like the logshipping process can not automatically determine which logs to apply when I am setting it up to "existing database" and I need to apply the correct logs manually.

    Thanks all the same

    Karl Grambow

    www.sqldbcontrol.com
  5. satya Moderator

    In order to affect your changes you need to restore database on secondary server WITH MOVE option and then continue the log shipping wizard to take on the transaction log restores.

    Satya SKJ
    Contributing Editor & Forums Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page