How to move Discovery Accelerator and Analytics databases

Problem

How to move Discovery Accelerator and Analytics databases.

Cause

The Analytics feature of Enterprise Vault (EV) Discovery Accelerator (DA) uses the SQL full-text index catalog feature to index the data captured within the Case or Research Folder for which Analytics was enabled. The files used by the SQL full-text index catalog have the NDF file extension. Each Analytics enabled Case or Research Folder has its own set of full-text index catalog folders and files that can grow to be very large when several thousand or million items that have been captured within the Case or Research Folder.

Various issues can arise that necessitate the need to move a DA Customer database from one location to another, either on the same SQL server\instance or to a different SQL server\instance. For example, the drive containing the Customer database and its full-text index catalog files and folders may be running out of space and company policy would be to move the associated files and folders to a new SQL server and/or instance with its files and folders on a different, larger drive.

The preferred process to move a DA Customer database is to disable Analytics on all Analytics enabled Cases and Research Folders, but this may not always be feasible, given current business requirements. When Analytics must remain enabled, the database move process must include the associated full-text index catalog folders and files that are included in the applicable NDF file(s).

The following provides a guideline of the recommended actions needed to move a DA Customer database along with its full-text index catalog files and folders.

Note: It is recommended that all DA activity be completed prior to any moves. This includes:
- Legal Hold activity be completed.
- Searches and Exports be completed.
- Pending Acceptance Searches be Accepted or Rejected.
- Paused Searches be Resumed and Accepted or Rejected.
- Analytics processing (Data Collection, Conversation Analysis and Automatic Categorization) be completed.

If also moving Enterprise Vault and / or Compliance Accelerator databases, please refer to the following articles in the Related Articles section:
  • How to move the Enterprise Vault SQL databases
  • How to modify the configuration files after moving the Compliance Accelerator or Discovery Accelerator databases to different SQL server

Solution

As noted above, it is recommended to disable Analytics from all Cases and/or Research Folders prior to moving DA databases. When this is not feasible, the Analytics database files will also have to be moved and the Customer properties updated to reflect the new location.

There are certain prerequisites to moving the Customer and Analytics database files:
  • The VSA (Vault Service Account) must be the account used to perform all operations.
  • The VSA must have the same SQL permissions on the new SQL server\instance as on the original, if moving to another SQL server\instance. These are detailed in the DA Installation Guide and must be implemented before any further actions are taken.
  • Analytics folders and files must be on a local drive (for example, a physically attached drive or SAN attached drive referenced through a local drive letter).
  • Analytics folders and files must not be located at the root level of the local drive.
  • Analytics folders and files must be located on the same SQL server as the DA Customer database but can reside on a different drive than the DA Customer database.
  • The requirements and steps must be followed according to Microsoft's recommendations. Please refer to Microsoft's MSDN article 'Manage Metadata When Making a Database Available on Another Server Instance (SQL Sever)' https://msdn.microsoft.com/en-us/library/ms187580.aspx

How to move the DA Customer and Analytics database files to a new location on the same SQL server

1. Ensure that full-text indexing is not currently in the process of enabling/disabling any Case or Research Folder. The following query, run against the DA Customer database, should return no results before continuing with the move of databases:

SELECT CaseID, [Name], AnalyticsStatusID FROM tblCase WHERE AnalyticsStatusID NOT IN (851, 856);

2. Create folder locations on the new local drives for the database, transaction logs and Analytics files (the Analytics files may reside in the same location as the database files).

3. Stop the EVAMS (Enterprise Vault Accelerator Manager Service).

4. Execute the following steps to move the files to their new locations and update the database (modified from Microsoft article https://msdn.microsoft.com/en-us/library/ms345483.aspx):
4.1. Run the following query to obtain the current location information (replace <database_name> with the Customer database name):

SELECT Name AS Logical_Name, Physical_Name AS Current_Location, State_Desc AS Status
FROM sys.master_files
WHERE database_id = DB_ID(N'<database_name>');


4.2. Run the following command to prepare the database for the move (replace <database_name> with the Customer database name):

ALTER DATABASE <database_name> SET OFFLINE;

4.3. Move the file or files to the new location using Windows Explorer or another comparable utility.
4.4. To point the database to the new files' location, edit the following command and run the command for each file from step 1 that was moved:

-- Replace <database_name> with the Customer database name.
-- Replace <logical_name> with the logical name of the file as obtained in step 4.1.
-- Replace <new_path\file_name> with the new location of the file.

ALTER DATABASE <database_name>
MODIFY FILE (NAME = <logical_name>, FILENAME = '<new_path\file_name>');
 

4.5. After verifying all new file locations have been updated, run the following command to prepare the database for normal operations:

ALTER DATABASE database_name SET ONLINE;

4.6. Verify all file location changes are successful by re-running the step 4.1 query.

For example, if moving the files for Customer database named DACustomer01 with 3 Cases enabled for Analytics (CaseIDs 6, 7 and 8) from D:\Data and D:\Logs to E:\SQL\Data and E:\SQL\Logs:

- Step 4.1 query:

SELECT Name AS Logical_Name, Physical_Name AS Current_Location, State_Desc AS Status
FROM sys.master_files
WHERE database_id = DB_ID(N'DACustomer01');


Query results:
 
Logical_NameCurrent_LocationStatus
DACustomer01_DataD:\Data\DACustomer01_Data.MDFONLINE
DACustomer01_LogD:\Logs\DACustomer01_Log.LDFONLINE
AnalyticsCaseFile_DACustomer01_6D:\Data\AnalyticsCaseFile_DACustomer01_6.ndfONLINE
AnalyticsCaseFile_DACustomer01_7D:\Data\AnalyticsCaseFile_DACustomer01_7.ndfONLINE
AnalyticsCaseFile_DACustomer01_8D:\Data\AnalyticsCaseFile_DACustomer01_8.ndfONLINE

- Step 4.2 command:

ALTER DATABASE DACustomer01 SET OFFLINE;

- Step 4.4 commands:

ALTER DATABASE DACustomer01
MODIFY FILE (NAME = DACustomer01_Data, FILENAME = 'E:\SQL\Data\DACustomer01_Data.MDF');

ALTER DATABASE DACustomer01
MODIFY FILE (NAME = DACustomer01_Log, FILENAME = 'E:\SQL\Logs\DACustomer01_Log.LDF');

ALTER DATABASE DACustomer01
MODIFY FILE (NAME = AnalyticsCaseFile_DACustomer01_6, FILENAME = 'E:\SQL\Data\AnalyticsCaseFile_DACustomer01_6.ndf');

ALTER DATABASE DACustomer01
MODIFY FILE (NAME = AnalyticsCaseFile_DACustomer01_7, FILENAME = 'E:\SQL\Data\AnalyticsCaseFile_DACustomer01_7.ndf');

ALTER DATABASE DACustomer01
MODIFY FILE (NAME = AnalyticsCaseFile_DACustomer01_8, FILENAME = 'E:\SQL\Data\AnalyticsCaseFile_DACustomer01_8.ndf');


Command results:

The file "DACustomer01_Data" has been modified in the system catalog. The new path will be used the next time the database is started.
The file "DACustomer01_Log" has been modified in the system catalog. The new path will be used the next time the database is started.
The file "AnalyticsCaseFile_DACustomer01_6" has been modified in the system catalog. The new path will be used the next time the database is started.
The file "AnalyticsCaseFile_DACustomer01_7" has been modified in the system catalog. The new path will be used the next time the database is started.
The file "AnalyticsCaseFile_DACustomer01_8" has been modified in the system catalog. The new path will be used the next time the database is started.


- Step 4.5 command:

ALTER DATABASE DACustomer01 SET ONLINE;

- Step 4.6 results:
 
Logical_NameCurrent_Location Status
DACustomer01_DataE:\SQL\Data\DACustomer01_Data.MDF ONLINE
DACustomer01_LogE:\SQL\Logs\DACustomer01_Log.LDF ONLINE
AnalyticsCaseFile_DACustomer01_6 E:\SQL\Data\AnalyticsCaseFile_DACustomer01_6.ndf ONLINE
AnalyticsCaseFile_DACustomer01_7E:\SQL\Data\AnalyticsCaseFile_DACustomer01_7.ndf ONLINE
AnalyticsCaseFile_DACustomer01_8 E:\SQL\Data\AnalyticsCaseFile_DACustomer01_8.ndf ONLINE

5. Start the EVAMS.

6. Open the EVBAAdmin webpage on the DA server as the VSA.

7. Open the properties page of the DA customer.

8. Edit the SQL Server value in the Database Details section to the new SQL server name\instance.

9. Edit each Location value in the Database Locations For Analytics section to point to the new location:
9.1. Click the Edit button to the right of the first location.
9.2. Edit the location.
9.3. Click the OK button at the right of the location line.
9.4. Repeat for each location as needed.

10. When all locations have been updated, click the OK button at the bottom right of the Customer properties page.


How to move the DA Customer and Analytics database files to a new SQL server

Note: If moving to a new SQL server\instance, it is imperative the VSA must have the appropriate SQL permissions server\instance as on the original SQL server\instance. These are detailed in the DA Installation Guide and must be implemented before any further actions are taken.

1. Ensure that full-text indexing is not currently in the process of enabling/disabling any Case or Research Folder. The following query, run against the DA Customer database, should return no results before continuing with the move of databases:

SELECT CaseID, [Name], AnalyticsStatusID FROM tblCase WHERE AnalyticsStatusID NOT IN (851, 856);

2. Create folder locations on local drives on the new SQL server for the database, transaction logs and Analytics files (the Analytics files may reside in the same location as the database files).

3. Stop the Enterprise Vault Accelerator Manager Service (EVAMS).

4. At this point, there are multiple methods by which to move the databases.
4.1. The preferred method is to use SQL server's built-in features to Backup the database from the original SQL server and Restore the database to the new SQL server. The file locations may be specified during the Restore process. For specific steps, please refer to Microsoft articles:

- Create a Full Database Backup
https://msdn.microsoft.com/en-us/library/ms187510.aspx

- Restore a Database Backup
https://msdn.microsoft.com/en-us/library/ms177429.aspx

4.2. An alternate method is to use SQL server's built-in Detach and Attach features. For specific steps, please refer to Microsoft article:

- Move a Database Using Detach and Attach
https://msdn.microsoft.com/en-us/library/ms187858.aspx

Note: If Analytics is enabled on any Case or Research Folder, the CREATE DATABASE statement in the Microsoft article will need to be edited to include the Analytics files. Example command for DA Customer database named DACustomer01 with 3 Cases enabled for Analytics (CaseIDs 6, 7 and 8):

CREATE DATABASE DACustomer01
ON (FILENAME = 'E:\SQL\Data\DACustomer01_Data.MDF'),
(FILENAME = 'E:\SQL\Logs\DACustomer01_Log.LDF'),
(FILENAME = 'E:\SQL\Data\AnalyticsCaseFile_DACustomer01_6.ndf'),
(FILENAME = 'E:\SQL\Data\AnalyticsCaseFile_DACustomer01_7.ndf'),
(FILENAME = 'E:\SQL\Data\AnalyticsCaseFile_DACustomer01_8.ndf')
FOR ATTACH;


5. Update the configuration files to reflect the SQL server change. Follow the steps in article How to modify the configuration files after moving the Compliance Accelerator or Discovery Accelerator databases to different SQL server in the Related Articles section. Do not proceed until this step is complete. Starting the EVAMS before completing this step will result in the EVAMS stopping and logging Event Log errors.

6. Start the EVAMS.

7. Open the EVBAAdmin webpage on the DA server as the VSA.

8. Open the properties page of the DA customer.

9. Edit the SQL Server value in the Database Details section to the new SQL server name\instance.

10. If the physical location of Analytics files has changed, edit each Location value in the Database Locations For Analytics section to point to the new location:
10.1. Click the Edit button to the right of the first location.
10.2. Edit the location.
10.3. Click the OK button at the right of the location line.
10.4. Repeat for each location as needed.

11. When all locations have been updated, click the OK button at the bottom right of the Customer properties page.

12. Restart the EVAMS.
 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)