﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / Backups  / Backup FileGroup and Restore on Secondary Database / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sun, 26 May 2013 20:56:12 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Backup FileGroup and Restore on Secondary Database</title><link>http://www.sqlservercentral.com/Forums/Topic412470-357-1.aspx</link><description>hi, I ran a query into sys.database_files for both the databases and LSNs match but still I didnt restore. I think that is because the recovery plans are different in both the databases (which is unusual since I restored both with the same copy). FYI, if the secondary is in Standby then we can restore a diff backup from primary but it will be read-only but not fully recovered. Thanks for your time. I'm investigating and will update the thread.</description><pubDate>Fri, 19 Oct 2007 14:12:46 GMT</pubDate><dc:creator>Razi, M</dc:creator></item><item><title>RE: Backup FileGroup and Restore on Secondary Database</title><link>http://www.sqlservercentral.com/Forums/Topic412470-357-1.aspx</link><description>Yup - if you take an exact copy of the database and then make a change in one that isn't reflected exactly in the other, as far as SQL Server is concerned you've got two different databases with different last-LSNs.</description><pubDate>Fri, 19 Oct 2007 11:25:43 GMT</pubDate><dc:creator>Paul Randal</dc:creator></item><item><title>RE: Backup FileGroup and Restore on Secondary Database</title><link>http://www.sqlservercentral.com/Forums/Topic412470-357-1.aspx</link><description>Hi, Thanks for your response. Yes at one point in time the copies were identical. On the primary server I added few rows to a table on secondary file group, took a backup of that file group and tried to restore that backup on the secondary server. You mean to say that LSN changes the moment we add data to the primary and that wount match on the secondary.</description><pubDate>Fri, 19 Oct 2007 11:18:17 GMT</pubDate><dc:creator>Razi, M</dc:creator></item><item><title>RE: Backup FileGroup and Restore on Secondary Database</title><link>http://www.sqlservercentral.com/Forums/Topic412470-357-1.aspx</link><description>It can't be done unless the databases are identical copies of each other - otherwise the LSNs in the databases get out of sync. It's an often-requested feature of SQL Server that may come in a future release.</description><pubDate>Thu, 18 Oct 2007 18:16:48 GMT</pubDate><dc:creator>Paul Randal</dc:creator></item><item><title>Backup FileGroup and Restore on Secondary Database</title><link>http://www.sqlservercentral.com/Forums/Topic412470-357-1.aspx</link><description>HiI have two similar databases with identical filegroups(primary,secondary) but on different drives. At one-point in time both the databases are in sync. I created on a secondary filegroup and populated several thousand rows to grow the filesizeTook a backup of secondary filegroup and when I try to restore the secondary filegroup back on the secondary server I get the following error:USE MASTERGORESTORE DATABASE  RaziTest -- secondary databaseFILEGROUP = 'RaziTest_FileGRP2' --secondary filegroupFROM DISK ='H:\sqldata\TempRazi\RaziTest_FileGRP2.BAK' --backup of secondary filegroup from primary serverError:Msg 3116, Level 16, State 2, Line 1The supplied backup is not on the same recovery path as the database, and is ineligible for use for an online file restore.Msg 3013, Level 16, State 1, Line 1RESTORE DATABASE is terminating abnormally.Any help in getting around this is appreciated.</description><pubDate>Thu, 18 Oct 2007 16:34:03 GMT</pubDate><dc:creator>Razi, M</dc:creator></item></channel></rss>