<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SQL Server backups - differentials, copy_only, and the restore chain in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/sql-server-backups-differentials-copy-only-and-the-restore-chain/m-p/5874983#M5998</link>
    <description>&lt;P&gt;We currently are able to use the VSS with SAN/iQ to do shadow-copy-based backups of SQL Server databases.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We know that the databases are quiesced properly, because we can restore the databases from the copies just fine - we could not do that when we were copying the relevant drives without using the VSS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the copy is seen as a full backup by SQL Server, therefore the restore chain for our differential backups is broken (we prefer to retain a non-shadow-copy-based full weekend backup with daily differential backups against that).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand that Microsoft´s VSS framework does support the ¨copy_only¨ option of SQL Server backup, meaning that the restore chain for other backups is not affected - but how to get the SAN/iQ VSS provider to utilize it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else faced this issue, and how did you solve it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or, if you have not, what alternative backup strategies have you used that allow you to sidestep the issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Wed, 21 Nov 2012 21:43:14 GMT</pubDate>
    <dc:creator>keithmur</dc:creator>
    <dc:date>2012-11-21T21:43:14Z</dc:date>
    <item>
      <title>SQL Server backups - differentials, copy_only, and the restore chain</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/sql-server-backups-differentials-copy-only-and-the-restore-chain/m-p/5874983#M5998</link>
      <description>&lt;P&gt;We currently are able to use the VSS with SAN/iQ to do shadow-copy-based backups of SQL Server databases.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We know that the databases are quiesced properly, because we can restore the databases from the copies just fine - we could not do that when we were copying the relevant drives without using the VSS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But the copy is seen as a full backup by SQL Server, therefore the restore chain for our differential backups is broken (we prefer to retain a non-shadow-copy-based full weekend backup with daily differential backups against that).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I understand that Microsoft´s VSS framework does support the ¨copy_only¨ option of SQL Server backup, meaning that the restore chain for other backups is not affected - but how to get the SAN/iQ VSS provider to utilize it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else faced this issue, and how did you solve it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or, if you have not, what alternative backup strategies have you used that allow you to sidestep the issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 21 Nov 2012 21:43:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/sql-server-backups-differentials-copy-only-and-the-restore-chain/m-p/5874983#M5998</guid>
      <dc:creator>keithmur</dc:creator>
      <dc:date>2012-11-21T21:43:14Z</dc:date>
    </item>
  </channel>
</rss>

