Veritas Data Insight Administrator's Guide
- 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
Add/Edit web application options
Use this dialog box to add a new web application to Veritas Data Insight or to edit the configuration of an existing web application.
Table: Add/Edit web application options
Field | Description |
---|---|
Web Application URL | Enter the URL of the web application that you want Data Insight to monitor. |
Collector | Do the following:
Data Insight connects to the SharePoint server from Collector node. It is recommended that the Collector worker node share a fast network with the SharePoint server. |
Indexer | Do the following:
Events and metadata that are collected from the cluster are processed and stored on the Indexer node. |
Site Collection Administrator | Enter the credentials that Data Insight should use to provide authenticated access to the Data Insight web service on the SharePoint server. |
Test Credentials | Click to test the availability of network connection between the Collector worker node and the SharePoint server, and to test the validity of specified credentials. You must first ensure that the Data Insight web service is already installed on the SharePoint server. Veritas recommends that you verify the credentials before proceeding to ensure that Data Insight is able to connect to the SharePoint server. |
Automatically discover and add site collections in this Web application | This checkbox is selected by default. This option allows you to automatically include all site collections in the selected web application for the purpose of monitoring. Clear the check box to add site collections manually. You can do this from the web application details page. |
Exclude following site collections from discovery | Enter the details of the site collections which should not be included during discovery. This option is available if you select . Specify comma separated patterns that you want to ignore. Patterns can have 0 or more wildcard * characters.For example, https://webapp1/sites/test* ignores site collections https://webapp1/sites/testsite1 and https://webapp1/sites/testsite2. |
Monitor SharePoint accesses to this Web application | Select to enable monitoring of access events for the web application. |
Automatically enable auditing for site collections of the Web application | Select to automatically enable event monitoring for all site collections of this web application. You can also choose to manually enable auditing by logging in to the SharePoint server. For this purpose, you must have site collection administrator privileges on the SharePoint server. |
Delete Audit Logs from SharePoint Database after importing into Data Insight | Select to delete audit logs from SharePoint to prevent the web application database from growing too large. By default, Data Insight deletes audit logs that are older than two days from the SharePoint server once every 12 hours. You can configure this interval from the Advanced Settings page for the corresponding Collector. You can choose to customize how often Data Insight should delete old audit logs from the Data Insight Servers node on the Management Console. |
Enable scanning for this Web application | Select the checkbox to enable SharePoint scanning according to the specified schedule. |
Scanning schedule for full scans | Select one of the following to define a scanning schedule for the SharePoint servers in this farm:
Veritas Data Insight periodically scans site collections to obtain file metadata. Each Collector worker node by default initiates a full scan the SharePoint servers at 11:00 P.M. each night. Note: You can also customize the schedule for each site collection using the Add/Edit Site Collection dialog box. |
Scan newly added site collections immediately | Select this option to scan newly added site collections immediately, instead of waiting for the normal scan schedule. Scanning will still proceed only when scanning is permitted on the Collector node. |