<?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 SnapManager for SQL Restore of VMDK / NFS from Snapvault destination in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SnapManager-for-SQL-Restore-of-VMDK-NFS-from-Snapvault-destination/m-p/121242#M10929</link>
    <description>&lt;P&gt;Hi there&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SMSQL supports data placed in VMDK files on a NFS datastore.&lt;/P&gt;&lt;P&gt;Placing the data in VMDK files has some management bennefits, yet when you add on a Snapvault destination, if becomes a different story in regards to restores.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a AFF8060 cDot 8.3 system where the primary data is placed, we use the above approach using NFS, and placing our SQL data in VMDK virtual disks.&lt;/P&gt;&lt;P&gt;Of cause we take case to create a specific datastore for DB+LOG, and one for SnapInfo.&lt;/P&gt;&lt;P&gt;We then create a snapvault relation on the volumes to a secondary system.&lt;/P&gt;&lt;P&gt;We would like to keep one weeks worth of snapshots on the primary system, and 12 months on the secondary system.&lt;/P&gt;&lt;P&gt;This is all setup and works just fine... &amp;nbsp;SnapDrive talks to VSC and snapshots are coordinated with VMware etc.. &amp;nbsp;and even the Snapvault (Archive) option is avaliable inside SnapManager.&lt;/P&gt;&lt;P&gt;And it works just as expected when doing backups.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It besomes a bit more complicated when we want to restore databases older than one week, where we have to access the data on the secondary system.&lt;/P&gt;&lt;P&gt;First of all the backups on the secondary system are not shown inside SMSQL when choosing the Restore option.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are also unable to mount the datastore from SnapDrive... I suspect that SD tries to mount this as a LUN, and it failes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Only option that is left is:&lt;/P&gt;&lt;P&gt;1. Create Flexclone on the Secondary system&lt;/P&gt;&lt;P&gt;2. Export the Flexclone to the VM Cluster&lt;/P&gt;&lt;P&gt;3. Mount the datastore in vSphere&lt;/P&gt;&lt;P&gt;4. Attach VMDK to the SQL server&lt;/P&gt;&lt;P&gt;5. Copy the database and log files to the primary volume&lt;/P&gt;&lt;P&gt;6. Attach database in SQL&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All the above are manual operations, of cause they can be scriptet, but it becomes even more complicated if you would like to do a up to the minute restore, ie. use the logfiles to roll forward.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to know if any one has found another, and smarter way to deal with this?&lt;/P&gt;&lt;P&gt;Are there some new feature on the way from NetApp which "solves" this ? &amp;nbsp;(Snap Center maybe? &amp;nbsp;Yet I doubt it)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Only other way is to move to LUNs and attach via FC or iSCSI, which then gives us the restore of snapvault snapshots back in the GUI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or... (which is entirely possible) have I missed something in the setup?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/BM&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jun 2025 19:58:35 GMT</pubDate>
    <dc:creator>Beardmann</dc:creator>
    <dc:date>2025-06-04T19:58:35Z</dc:date>
    <item>
      <title>SnapManager for SQL Restore of VMDK / NFS from Snapvault destination</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapManager-for-SQL-Restore-of-VMDK-NFS-from-Snapvault-destination/m-p/121242#M10929</link>
      <description>&lt;P&gt;Hi there&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SMSQL supports data placed in VMDK files on a NFS datastore.&lt;/P&gt;&lt;P&gt;Placing the data in VMDK files has some management bennefits, yet when you add on a Snapvault destination, if becomes a different story in regards to restores.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a AFF8060 cDot 8.3 system where the primary data is placed, we use the above approach using NFS, and placing our SQL data in VMDK virtual disks.&lt;/P&gt;&lt;P&gt;Of cause we take case to create a specific datastore for DB+LOG, and one for SnapInfo.&lt;/P&gt;&lt;P&gt;We then create a snapvault relation on the volumes to a secondary system.&lt;/P&gt;&lt;P&gt;We would like to keep one weeks worth of snapshots on the primary system, and 12 months on the secondary system.&lt;/P&gt;&lt;P&gt;This is all setup and works just fine... &amp;nbsp;SnapDrive talks to VSC and snapshots are coordinated with VMware etc.. &amp;nbsp;and even the Snapvault (Archive) option is avaliable inside SnapManager.&lt;/P&gt;&lt;P&gt;And it works just as expected when doing backups.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It besomes a bit more complicated when we want to restore databases older than one week, where we have to access the data on the secondary system.&lt;/P&gt;&lt;P&gt;First of all the backups on the secondary system are not shown inside SMSQL when choosing the Restore option.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You are also unable to mount the datastore from SnapDrive... I suspect that SD tries to mount this as a LUN, and it failes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Only option that is left is:&lt;/P&gt;&lt;P&gt;1. Create Flexclone on the Secondary system&lt;/P&gt;&lt;P&gt;2. Export the Flexclone to the VM Cluster&lt;/P&gt;&lt;P&gt;3. Mount the datastore in vSphere&lt;/P&gt;&lt;P&gt;4. Attach VMDK to the SQL server&lt;/P&gt;&lt;P&gt;5. Copy the database and log files to the primary volume&lt;/P&gt;&lt;P&gt;6. Attach database in SQL&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;All the above are manual operations, of cause they can be scriptet, but it becomes even more complicated if you would like to do a up to the minute restore, ie. use the logfiles to roll forward.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I would like to know if any one has found another, and smarter way to deal with this?&lt;/P&gt;&lt;P&gt;Are there some new feature on the way from NetApp which "solves" this ? &amp;nbsp;(Snap Center maybe? &amp;nbsp;Yet I doubt it)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Only other way is to move to LUNs and attach via FC or iSCSI, which then gives us the restore of snapvault snapshots back in the GUI.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Or... (which is entirely possible) have I missed something in the setup?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;/BM&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 19:58:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapManager-for-SQL-Restore-of-VMDK-NFS-from-Snapvault-destination/m-p/121242#M10929</guid>
      <dc:creator>Beardmann</dc:creator>
      <dc:date>2025-06-04T19:58:35Z</dc:date>
    </item>
  </channel>
</rss>

