This article describes how to move the Enterprise Vault (EV) databases to a different SQL server or a new version of MS SQL Server for EV.
For EV 12.0 and above please refer to the Enterprise Vault PowerShell Cmdlets guide regarding Get-EVDatabaseDetail and Set-EVDatabaseDetail to move databases.
To watch a video on this process see below.
Note: At minute 1:33 and 1:58, there is a tab called "Indexers" that is not shown. This is new in versions 10 and above. We are only concerned with the Database tab for this tutorial.
CauseThe occasion can exist where the Enterprise Vault databases must be moved from one SQL Server to another. Examples include, but not limited to:
- Upgrade of the SQL Server version (ex.: SQL Server 2008 R2 to SQL Server 2012 R2).
- Upgrade of the SQL Server hardware.
- Distribution of databases to allow for more processing power to be applied to each database.
Note that if Compliance Accelerator and / or Discovery Accelerator are also installed in the environment and their databases are to be moved to a different SQL Server and / or SQL Server instance and / or SQL Server TCP Port, refer the the following articles in the Related Articles section of this article:
- How to modify the configuration files after moving the Compliance Accelerator or Discovery Accelerator databases to different SQL server
- How to move Discovery Accelerator and Analytics databases
This process will consist of the following steps.
a. Right click Enterprise Vault at the root level and select Properties
3. Grant the Vault Service account "Select" permissions on the following msdb tables:
GRANT SELECT ON dbo.sysjobs TO "DOMAIN\VSA"
GRANT SELECT ON dbo.sysjobschedules TO "DOMAIN\VSA"
GRANT SELECT ON dbo.sysjobservers TO "DOMAIN\VSA"
GRANT SELECT ON dbo.sysjobsteps TO "DOMAIN\VSA"
use MasterGRANT VIEW SERVER STATE TO "domain\vsa_account"GRANT ALTER ANY LOGIN TO "domain\vsa_account"GRANT VIEW ANY DEFINITION TO "domain\vsa_account"GO
2. Copy the backup files to the new SQL server.
1. Use the instructions and prewritten SQL script in the following article: https://www.veritas.com/docs/000035817
2. Repeat for each Fingerprint database.
2. Run the following query, substituting the New_SQL_Server value with the hostname of the new SQL server:
SET SQLServer = 'New_SQL_Server'
For 32bit systems, HKEY_LOCAL_MACHINE\Software\KVS\Enterprise Vault\Directory\DirectoryService.
For 64bit systems, HKEY_LOCAL_MACHINE\Software\Wow6432Node\KVS\Enterprise Vault\Directory\DirectoryService
2. Double-click the SQLServer Name string value.
3. Enter the name of the new SQL server in the value data field and click OK.
4. Start the Enterprise Vault Directory Service, this will also start the Admin Service.
5. Review the Event logs to ensure both services have started without error
2. Select the Database tab.
3. Next to SQL Server, enter the name of the new SQL server and click OK.
4. Repeat steps 1-3 for any remaining Vault Stores.
5. Start the remaining Enterprise Vault services.
6. Confirm in Veritas Enterprise Vault Event Logs that there are no errors starting services.
1. For 32bit systems, Open Data Sources (ODBC) from the Administrative Tools panel on the Enterprise Vault Server. For 64bit systems, browse to %systemroot%\syswow64\odbcad32.exe
2. Select the System DSN tab.
3. Select the EVAudit entry.
4. Click the Configure button.
5. On the first page of the wizard, under Which SQL Server do you want to connect to?, enter the name of the new SQL server.
6. Continue through the wizard and click Finish to apply the changes.
Note: If TLS 1.0 and 1.1 is disabled and TLS 1.2 is enabled this will fail with the following:
Connection failed: SQLState: '01000' SQL Server Error: 1 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (SECCreateCredentials()). Connection failed: SQLState: '08001' SQL Server Error: 18 [Microsoft][ODBC SQL Server Driver][DBNETLIB]SSL Security error
This error occurs because TLS 1.2 uses Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL) and ODBC driver than ODBC Data Source Administrator (32-bit) Microsoft OLE DB Provider for SQL Server (SQLOLEDB) for their drivers.
To work around this issue perform the following:
- Open ODBC Data Source Administrator (32-bit) Select
- System DSN tab
- Select the Add button
- Select the SQL Server Driver => Finish
- Name: Audit DB name
- Server: SQL Server
- Select Finish.
- Do not do any test connections as they will fail.
2. Check the Event Viewer for errors connecting to databases.
3. Check the locations of the Directory, Fingerprint, and Vault Store databases again, as in Step 1. They should all display the name of the new SQL Server.
4. Do not forget to update any scheduled backup jobs so that they backup the new SQL Server. It is recommended that the copies of the EV databases on the old SQL Server not be removed until a full backup of the databases on the new SQL Server has been completed.
Related Knowledge Base Articles
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):