<?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: Estimated Time for Rebuilding Search indexes in Vault Forum</title>
    <link>https://forums.autodesk.com/t5/vault-forum/estimated-time-for-rebuilding-search-indexes/m-p/8801939#M23662</link>
    <description>&lt;P&gt;A server reboot kicked it back into gear, it took 4-5 days to finish the rebuild for reference. Setting up a separate instance would've been ideal, if the virtual infrastructure was able to support it.&amp;nbsp; I detached and attached the production vaults (not the knowledge master) due to performance issues, a purge history hang, backup being broken, and the filestore path being setup incorrectly. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Even though the filestore was on the same server as the ADMS, the filestore path was configured as a shared path to it. &amp;nbsp;The filestore was originally on a separate server, but moved to the ADMS server at some point (by my predecessor). That may have only impacted performance until IT changed something that broke the domain account (or it simply got corrupted) on the adms server. Both the server and vault wanted to see the domain account as a local instead of from the domain.&amp;nbsp; I didn’t see a need to continue fighting that battle if I could make it a local path and use the default account instead (working with the IT overlords is exasperating). I didn’t see a point to just “moving” the filestore with the other issues and that operation would lock people out of the vault entirely until it completed. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;David P&lt;/P&gt;</description>
    <pubDate>Mon, 20 May 2019 12:56:20 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2019-05-20T12:56:20Z</dc:date>
    <item>
      <title>Estimated Time for Rebuilding Search indexes</title>
      <link>https://forums.autodesk.com/t5/vault-forum/estimated-time-for-rebuilding-search-indexes/m-p/8788368#M23660</link>
      <description>&lt;P&gt;Is there any guidance from Autodesk on how long it should take to rebuild search indexes?&amp;nbsp; I haven't been able to find anything.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have a couple of very large databases that I would like to know the amount of time I should expect for a rebuild to take place.&amp;nbsp; One is a 65GB database with 1,150,855 files in the store (758GB size) and another that is&amp;nbsp; 34GB database with 683,777 files in the store (440GB size).&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;David P&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2019 20:04:48 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/estimated-time-for-rebuilding-search-indexes/m-p/8788368#M23660</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-13T20:04:48Z</dc:date>
    </item>
    <item>
      <title>Re: Estimated Time for Rebuilding Search indexes</title>
      <link>https://forums.autodesk.com/t5/vault-forum/estimated-time-for-rebuilding-search-indexes/m-p/8791032#M23661</link>
      <description>&lt;P&gt;Unfortunately, there are a lot of factors the come into play when you are looking at the time it takes to do this so there are not estimates that can be given.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One way to figure this out is to do this on a test system and get your timing as this will apply to your environment.&lt;/P&gt;
&lt;P&gt;Why are you rebuilding the search indexes? It should be rare that you need to do this.&lt;/P&gt;</description>
      <pubDate>Tue, 14 May 2019 20:31:10 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/estimated-time-for-rebuilding-search-indexes/m-p/8791032#M23661</guid>
      <dc:creator>ihayesjr</dc:creator>
      <dc:date>2019-05-14T20:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: Estimated Time for Rebuilding Search indexes</title>
      <link>https://forums.autodesk.com/t5/vault-forum/estimated-time-for-rebuilding-search-indexes/m-p/8801939#M23662</link>
      <description>&lt;P&gt;A server reboot kicked it back into gear, it took 4-5 days to finish the rebuild for reference. Setting up a separate instance would've been ideal, if the virtual infrastructure was able to support it.&amp;nbsp; I detached and attached the production vaults (not the knowledge master) due to performance issues, a purge history hang, backup being broken, and the filestore path being setup incorrectly. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Even though the filestore was on the same server as the ADMS, the filestore path was configured as a shared path to it. &amp;nbsp;The filestore was originally on a separate server, but moved to the ADMS server at some point (by my predecessor). That may have only impacted performance until IT changed something that broke the domain account (or it simply got corrupted) on the adms server. Both the server and vault wanted to see the domain account as a local instead of from the domain.&amp;nbsp; I didn’t see a need to continue fighting that battle if I could make it a local path and use the default account instead (working with the IT overlords is exasperating). I didn’t see a point to just “moving” the filestore with the other issues and that operation would lock people out of the vault entirely until it completed. &lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;David P&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2019 12:56:20 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/vault-forum/estimated-time-for-rebuilding-search-indexes/m-p/8801939#M23662</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-05-20T12:56:20Z</dc:date>
    </item>
  </channel>
</rss>

