<?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 Re: Snapcenter 2.0 and MSSQL system databases in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/137493#M11757</link>
    <description>&lt;P&gt;I would love to know the answer to this too, as well as whether or not a SnapInfo LUN is needed for T-Log backups when using SnapCenter as it was for SnapManager.&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jan 2018 15:43:18 GMT</pubDate>
    <dc:creator>TMADOCTHOMAS</dc:creator>
    <dc:date>2018-01-22T15:43:18Z</dc:date>
    <item>
      <title>Snapcenter 2.0 and MSSQL system databases</title>
      <link>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/128124#M11239</link>
      <description>&lt;P&gt;I've just installed Snapcenter 2.0 and doing some testing and found something that puzzles me a bit.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Earlier using Snapmanager we have our system datases on a separate iSCSI LUN. When I do a backup of the system databases it does a streamed backup of them to the snapinfo folder on another iSCSI LUN.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But if I try to do a backup of the system databases in Snapcenter it will simply just to a regular snapshot of the iSCSI LUN where we have the system databases on. Is this really correct? I haven't been able to find any information in the documentation about database layout for the system databases other then they should be on a seperate LUN.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jimmy&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 15:27:10 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/128124#M11239</guid>
      <dc:creator>JIMMY_ERLANDSSON</dc:creator>
      <dc:date>2025-06-04T15:27:10Z</dc:date>
    </item>
    <item>
      <title>Re: Snapcenter 2.0 and MSSQL system databases</title>
      <link>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/137493#M11757</link>
      <description>&lt;P&gt;I would love to know the answer to this too, as well as whether or not a SnapInfo LUN is needed for T-Log backups when using SnapCenter as it was for SnapManager.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jan 2018 15:43:18 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/137493#M11757</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2018-01-22T15:43:18Z</dc:date>
    </item>
    <item>
      <title>Re: Snapcenter 2.0 and MSSQL system databases</title>
      <link>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/137592#M11762</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SnapManager for SQL Server (SMSQL) uses the SnapInfo directory as the main repository to store all metadata related to the SMSQL instance installed on a host (such as SnapManager&lt;BR /&gt;backup metadata, stream-based backups of system databases, and transaction log backups)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SnapCenter uses a host log directory to store transaction log backup data. This is at the host and instance level. Each SQL Server host used by SnapCenter needs to have a host log directory configured to perform log backups.SnapCenter has a database repository, so metadata related to backup, restore, or cloning operations is stored in a central database repository&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Backing up SQL Server system and user databases using SnapCenter requires that you choose the resource type, such as databases, SQL server instances, and Availability Groups (AG). &lt;STRONG&gt;Snapshot copy technology is leveraged&lt;/STRONG&gt; to create online, read-only copies of the volumes on which the resources reside&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;hope thie helps&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jan 2018 14:26:46 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/137592#M11762</guid>
      <dc:creator>matte</dc:creator>
      <dc:date>2018-01-25T14:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: Snapcenter 2.0 and MSSQL system databases</title>
      <link>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/137622#M11764</link>
      <description>&lt;P&gt;Thank you matte, that helps for me at least.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jan 2018 14:05:31 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/Snapcenter-2-0-and-MSSQL-system-databases/m-p/137622#M11764</guid>
      <dc:creator>TMADOCTHOMAS</dc:creator>
      <dc:date>2018-01-26T14:05:31Z</dc:date>
    </item>
  </channel>
</rss>

