Question & Answer
Question
The Full Text Indexes are not being relocated with the specified /RELOCATEDir parameter. Why are these indexes being restored with the data instead of being relocated?
Cause
The Full Text Catalog for SQL Server 2008 and 2012 is either a logical or virtual object that contains a group of full-text indexes. This full-text catalog does not have a physical path. The indexes within the full-text catalog will be stored in a file group, normally the same SQL Server filegroup as the data. APAR IT01694 addresses the documentation to describe the differences in the Full Text Indexes for the different versions of the SQL Server.
Answer
The following Microsoft document talks about the full text catalog and the fact that they are logical in nature and will be placed in the file group with the data:
https://technet.microsoft.com/en-us/library/ms142511%28v=sql.110%29.aspx
This document also indicates you can determine which file groups contain full text indexes and then backup these file groups (not a full database backup), such that you could then restore the file groups as desired. Since the Full Text Index is not a physical file, it is not possible to relocate this using the Data Protection RELOCATEDIR parameter.
When performing a restore, it is not possible to separate the different file groups from a full database backup. It is necessary to perform a file group backup in order to relocate the full text indexes during a restore. The FlashCopy Manager or Data Protection SQL has the ability to backup at the file group level. For example, in the MMC GUI Protect tab for the backup, select the "View: Files", this will list the Group Name for the databases. Highlight the Database/File Group that you want to backup and then under the Actions pane, select the "Group Backup to TSM" option.
Product Synonym
TSM FCM
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21978846