Migrate Enterprise Vault Database to New SQL Server

Before beginning of database migration note down below important things

  1. SQL Server Name : –  SQL Server can be confirmed from the EV admin console and registry as below




Fingerprint database  :-  Run the “select *from FingerprintCatalogueDatabase” to check finger print database name


Vault store Database :-  expand directory database –> table –>  Right Click  dbo.vaultstoreGroup –> Select top 1000 Rows


Permission requirement on New sql Server

1. Confirm the Vault Service Account is a member of the local administrators group.

2. Confirm the Vault Service Account is assigned the dbcreator role.

            a. Open SQL Server Management Studio

            b. Expand Security Logins > right-click the Vault Service account and select Properties.

            c. Click Server Roles and confirm dbcreator is checked.

3. Grant the Vault Service account “Select” permissions on the following msdb tables:

  • sysjobs
  • sysjobschedules
  • sysjobservers
  • sysjobsteps.

Note: Use the following script to grant select permissions to the Vault Service Account over the MSDB tables. Replace DOMAIN\VSA by the Vault Service Account:



GRANT SELECT ON dbo.sysjobschedules TO “DOMAIN\VSA”

GRANT SELECT ON dbo.sysjobservers TO “DOMAIN\VSA”


4. Assign the database role “SQLAgentUserRole” to the Vault Service account.

5. Confirm TCP/IP and/or Named Pipes are enabled.

            a. Open SQL Server Configuration Manager

            b. Expand SQL Server Network Configuration and click Protocols for <instance name>.

            c. Confirm Named Pipes and/or TCP/IP is Enabled under the Status

  1. Check all other required permission from Enterprise vault installation and configuration guide

Backup and restore Database to new Server

Stop all the Enterprise Vault Service from all the EV Servers

Engage DBA (Database administrator) and backup and restore database to new sql Server

Now it’s time to update Entry for New SQL Server

Update the Fingerprint Database

Run attached script as mention in following article , https://www.veritas.com/docs/000035817

Update the Monitoring Database

1. Open SQL Server Management Studio

2. Run the following query, substituting the New_SQL_Server value with the hostname of the new SQL server:

USE EnterpriseVaultDirectory

UPDATE MonitoringSettings

SET SQLServer = ‘New_SQL_Server’

Update the Directory Database in the registry

his step is performed on the Enterprise Vault Server.

1. Click Start > Run , type regedit and click OK .

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.

Update the Vault Store Database

This step is performed on the Enterprise Vault Server.

1. Open the Vault Administration Console (VAC), right-click the name of the Vault Store and select Properties.

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

Update the Audit Database

This step is performed on the Enterprise Vault Server.

Note: No Enterprise Vault services need to be stopped for this step.

The EVAudit System DSN must be updated with the new location of the audit database.

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.

Resume EV operations using the New SQL Server

  1. Start all EV Services on check event viewer for any error connecting to database

Base Source :-


Enterprise Vault Installation and configuration guide

Nutanix Cluster Health Check

Nutanix is now become more and more popular as an hyperconverged solution and in my blogs I am trying to cover steps to conduct the health check for Nutanix Cluster

Basically for health check “ncc health_checks run_all” is sufficient to provide all the required information however  you can gather specific information for below mention components with the help of below commands

+Cluster Info

– Cluster name

– Uptime

– NOS Version

– Cluster ID

– Block serial number

– HW model

 Commands to Run

 ncli cluster info

ncli host ls


+ Storage pool list

– Name

– Capacity (logical used and total)

– IOPS and latency

+ Container Info

– Name

– Capacity (logical used and total)

– IOPS and latency

– Replication factor

 Commands to Run

 ncli sp ls

ncli ctr ls

IOPS and Perf metrics can be viewed from prism page


 + CVM

– Status of service for each CVM

– CVM memory and VCPU usage

– Uptime

– Network stats

– IP addresses of CVMs

– NIC errors

 Commands to Run

 cluster status

allssh uptime




+ Disk status

– Perf stats and usage

 All Perf IO metrics are available on prism


+ Currently set gflags

ncc health_checks system_checks gflags_diff_check


+ Hypervisor

– Hypervisor software and version

– Uptime

– Installed VMs

– Memory Usage

– Attached Datastore

This is independent to the hypervisor ,


+ Datastore Info

– Usage

– Capacity

– Name

information available in prism


+ Disk list

+ Domain fault tolerance states

ncli cluster get-domain-fault-tolerance-status type=node

+ Default gateway

+ SSH key list

+ SMTP config

+ NTP config

information available in prism


Top things to know about vSAN — vErmirHoxhaj

As we know so far VMware vSAN is a distributed layer of software that runs natively as a part of the ESXi hypervisor. vSAN aggregates local or direct-attached capacity devices of a host cluster and creates a single storage pool shared across all hosts in the vSAN cluster. While supporting VMware features that require shared storage, such as HA, vMotion, and DRS, vSAN eliminates the need […]

via Top things to know about vSAN — vErmirHoxhaj