<?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 SQL out of place restore issue in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/141193#M11955</link>
    <description>&lt;P&gt;I opened a NetApp support ticket on this issue (Restore failed with error: The mount request was denied by the NFS server) and received the following information:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Restoring DBs to instances hosted on different ESX hosts is not currently supported and will result in the above error.&amp;nbsp; If the VMs hosting these instances are located on the same ESX host, there is a potential issue that we might be seeing."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my case, the SQL VMs were indeed on different hosts.&amp;nbsp; After migrating them to the same ESXi host I was able to perform the out-of-place database restore without issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I inquired as to when this operation might be supported and my tech explained&amp;nbsp;there is a BURT open for the feature and they are looking at adding it in a future release but no version for the release has been selected since it is a complex undertaking.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lynne&lt;/P&gt;</description>
    <pubDate>Thu, 28 Jun 2018 16:23:56 GMT</pubDate>
    <dc:creator>LynneP</dc:creator>
    <dc:date>2018-06-28T16:23:56Z</dc:date>
    <item>
      <title>SnapCenter SQL out of place restore issue</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/140926#M11934</link>
      <description>&lt;P&gt;I am able to successfully perform sql backups on both of my test SQL hosts in snapcenter, as well as "in place" sql database restores, however, I am having issues with restoring to an alternate host.&amp;nbsp; Error is as follows:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ob.vmfs.nfs.mount.error.perm.denied:NFS mount &amp;lt;arrayIP/datastorename&amp;gt; failed: The mount request was denied by the NFS server. Check that the export exists and that the client is permitted to mount it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are running SnapCenter v4.0p3.&amp;nbsp; The plug ins on both SQL hosts are running the same run-as credential.&amp;nbsp; The run-as credential has local admin access to each sql server, as well as SA access in SQL.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Wondering if anyone else has run into this issue and what I might investigate to resolve.&amp;nbsp; Thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lynne&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:36:41 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/140926#M11934</guid>
      <dc:creator>LynneP</dc:creator>
      <dc:date>2025-06-04T13:36:41Z</dc:date>
    </item>
    <item>
      <title>Re: SnapCenter SQL out of place restore issue</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/140961#M11938</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Never seen this specific error message. I think the issue is in the SCV plugin that cannot mount.&lt;/P&gt;
&lt;P&gt;my suggestion is to go through this &lt;A href="https://kb.vmware.com/s/article/1005948" target="_blank"&gt;https://kb.vmware.com/s/article/1005948&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;and try to add the SVM that is hosting the NFS datastore to SnapCenter&lt;/P&gt;</description>
      <pubDate>Mon, 18 Jun 2018 10:18:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/140961#M11938</guid>
      <dc:creator>matte</dc:creator>
      <dc:date>2018-06-18T10:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: SnapCenter SQL out of place restore issue</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/141193#M11955</link>
      <description>&lt;P&gt;I opened a NetApp support ticket on this issue (Restore failed with error: The mount request was denied by the NFS server) and received the following information:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;"Restoring DBs to instances hosted on different ESX hosts is not currently supported and will result in the above error.&amp;nbsp; If the VMs hosting these instances are located on the same ESX host, there is a potential issue that we might be seeing."&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In my case, the SQL VMs were indeed on different hosts.&amp;nbsp; After migrating them to the same ESXi host I was able to perform the out-of-place database restore without issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I inquired as to when this operation might be supported and my tech explained&amp;nbsp;there is a BURT open for the feature and they are looking at adding it in a future release but no version for the release has been selected since it is a complex undertaking.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lynne&lt;/P&gt;</description>
      <pubDate>Thu, 28 Jun 2018 16:23:56 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/141193#M11955</guid>
      <dc:creator>LynneP</dc:creator>
      <dc:date>2018-06-28T16:23:56Z</dc:date>
    </item>
    <item>
      <title>Re: SnapCenter SQL out of place restore issue</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/145261#M12216</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I understand this is an oldish post but thought i'd comment on this.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;I seem to have an inconsistent experience with out of place restores, I have successfully restored out of place to a VM on a different host several times even though the documentation claims they have to be on the same host. Then other times I experience the same error that you recieved.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I like SnapCenter but the documentation is often inconsistent or just plain wrong at times.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Dec 2018 15:31:34 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/145261#M12216</guid>
      <dc:creator>AshV</dc:creator>
      <dc:date>2018-12-06T15:31:34Z</dc:date>
    </item>
    <item>
      <title>Re: SnapCenter SQL out of place restore issue</title>
      <link>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/145264#M12217</link>
      <description>&lt;P&gt;AshV,&lt;/P&gt;
&lt;P&gt;Your timing is actually great.&amp;nbsp; This is now fixed in SnapCenter v4.1P3.&amp;nbsp; We just upgraded yesterday and verified we can now perform out-of-place SQL db restores without having both source and target VMs on the same ESX host.&lt;/P&gt;
&lt;P&gt;I agree there are still some challenges with SnapCenter, particularly with the scheduling piece, but hopefully that will be addressed in a future enhancement.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Lynne&lt;/P&gt;</description>
      <pubDate>Thu, 06 Dec 2018 17:07:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SnapCenter-SQL-out-of-place-restore-issue/m-p/145264#M12217</guid>
      <dc:creator>LynneP</dc:creator>
      <dc:date>2018-12-06T17:07:45Z</dc:date>
    </item>
  </channel>
</rss>

