Please enter search query.
Search <book_title>...
Veritas Data Insight Administrator's Guide
Last Published:
2020-07-14
Product(s):
Data Insight (6.1.5)
- Section I. Getting started
- Introduction to Veritas Data Insight administration
- Configuring Data Insight global settings
- Overview of Data Insight licensing
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Data Insight integration with Symantec Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About bulk assignment of custodians
- Section II. Configuring Data Insight
- Configuring Data Insight product users
- Configuring Data Insight product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Configuring containers
- Section III. Configuring native file systems in Data Insight
- Configuring NetApp file server monitoring
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Data Insight and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Veritas File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Data Insight web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding SharePoint Online accounts
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Section VI. Configuring ECM data sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Section IX. Remediation
- Section X. Reference
- Appendix A. Backing up and restoring data
- Appendix B. Data Insight health checks
- Appendix C. Command File Reference
- Appendix D. Data Insight jobs
- Appendix E. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Migrating the data directory to a new location
The data directory is the location where a Data Insight server stores the product data. You specify the location of the data directory during the Data Insight installation. You can find out the current location of the data directory by reading the datadir.conf
file that is located at C:\Program Files\Veritas\DataInsight\
.
To move the data directory from its current location
- Stop all the Data Insight services that are running on the server.
- Navigate to
C:\Program Files\Veritas\DataInsight\
and open the filedatadir.conf
in a text editor. Note the current location of the data directory. For example,matrix.datadir=C:/DataInsight/data.
- Edit the value for the parameter matrix.datadir to indicate the new location of the data directory. For example,
matrix.datadir=E:/DataInsight/data.
- Copy the folder,
$DATADIR/data
, from the old location to the new location. For example, copy the folder from the original locationC:/DataInsight
to the new locationE:/DataInsight
.Note:
If you choose to rename the data directory, do not use any space in the filename. Doing so will prevent the Data Insight services from starting.
- Navigate to
C:\Program Files\Veritas\DataInsight\bin
using the command prompt. Execute the following command:configdb -c
- Verify that the command output points to the new data directory location.
- Execute the command configdb -p -T node.
Verify that the command output lists all the Data Insight servers that are in your deployment.
- Start the Data Insight services on the server.
- After all Data Insight services start successfully, delete the original data directory.