Does EV9 to EV10 upgrade require recreating Index

[Leo_]

Do I have to recreate my Index or can I simply point the new server to the current Index?

I am running EV9 on a 32bit Windows 2003 server.

I am installing EV10 on a 64bit Windows 2008 server.

thank you

[ZeRoC00L]

You can copy the exisiting indexes to the new server by using the Enterprise Vault Server Settings Migration wizard:

http://www.symantec.com/business/support/index?page=content&id=HOWTO42445

[TonySterling · Accepted solution]

Slight correction, the Server Settings doesn't copy the indexes over.  You need to either copy the indexes over or make the exsisting location available to the new EV Server.  Where are your indexes currently stored?

In the referenced document look at the following section:

Migrating locally stored Enterprise Vault data

If you store any data locally on the source Enterprise Vault server, you must ensure that the data is available to the target server when you import the migration package.

You can use any of the following options to make the data available to the target server:

• Copy or move the data directly to the target server using the same paths that existed on the source server. For example, if your vault store partitions are on the E:\ drive on the source server, you can copy the partitions to the E:\ drive on the target server. When you import the migration package on the target server, the Server Settings Migration wizard first looks for Enterprise Vault data in the same paths that were used on the source server.

• Copy or move the data to another location such as network attached storage. For example, you can copy your locally stored vault store partitions to \\Server1\EVpartitions\. When you import the migration package on the target server, specify the new location for the vault store partitions using its UNC path.

• Leave the locally stored data on the source server and use it as a file server. In this case, share the folders that contain Enterprise Vault data. When you import the migration package on the target server, specify the location for the data locations using UNC paths.

  You must make the following data available to the target server:

• Vault store partitions

• Index locations

• Locations for temporary files that are used in Centera collections

• Shopping service locations

[Chris_Alleman]

Assuming that you are keeping the server same/alias the same, you should be able to follow this TechNote (http://www.symantec.com/docs/TECH35596) and change the location in SQL of the moved indexes.

Note: if you keep the same drive letter/path on the new server, all you should need to do is copy the old indexes.

[AWMorris]

You don't need to make any changes in SQL if the drive letter changes.  The server settings migration wizard will allow you to change the path to the indexes.

[Mark_Solutions]

Agree with the above comments in the main - just make all data available on the new server (an exact copy of indexes, vault stores, shopping, cache) and then use the migration wizard and all will be fine

The vault store and index locations on the new server become UNC paths to the admin shares so it doesnt matter where you put them on the new server.

Do have a new index location available for the 64 bit indexes though and add that into the index service before starting it.

To answer your initial question - at least what i think you were getting at - your current index is 32 bit, this will remain on the new EV10 server but will be used for searching only - no more data will be written to your old indexes.

All 32 bit indexes will be frozen and no more data writtent to them - each user will get a new 64 bit index on the new server and everything archived in the future will go in the 64 bit indexes

When you have time you can convert your 32 bit indexes to 64 bit (this reindexes everything so effectively rebuilds the index and in doing so moves it all to the 64 bit index.

Upon successful completion the 32 bit index will be deleted

Hope this helps