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 SharePoint Online account options
Use this dialog box to add a new SharePoint Online account to Veritas Data Insight or to edit the configuration of an existing account.
Table: Add/Edit SharePoint Online account options
Field | Description |
---|---|
SharePoint Online Account URL | Enter the URL of the SharePoint Online URL that you want Data Insight to
monitor. For example, |
Collector | Do the following:
Data Insight connects to the SharePoint server from the Collector node. It is recommended to choose the Collector worker node that is close in proximity to the SharePoint Online account server. Collector node should be running on Windows Server 2012 R2 or Windows Server 2016. |
Indexer | Do the following:
Events and metadata that are collected from the site collections are processed and stored on the Indexer node. |
Client ID Client Secret Key | The client ID is the unique application ID assigned when you create and register an app with Microsoft. Follow the procedure described in the following topic to get these details: See Registering Data Insight with Microsoft to enable SharePoint Online account monitoring . |
Authorize access | Do the following:
|
Automatically discover and add site collections in this SharePoint Online account | This check box is selected by default. This option allows you to automatically include all site collections in the selected Online account for the purpose of monitoring. Clear the check box to add site collections manually. You can do this from the Online account details page. Discovery of site collections takes place as soon as you add a SharePoint Online account and then twice each day at 2:00 A.M. and 2:00 P.M. |
Exclude following site collections from discovery | Enter the details of the site collections which should not be included during discovery. This option is available when you select . Specify comma separated patterns that you want to ignore. Patterns can have 0 or more wildcard * characters.For example, https://onlineaccount1/sites/test* ignores site collections https://onlineaccount1/sites/testsite1 and https://onlineaccount1/sites/testsite2. |
Monitor SharePoint accesses to this SharePoint Online account | By default, Microsoft SharePoint Event Monitoring is enabled. If disabled, select this check box to enable event monitoring on the SharePoint Online account. You must manually enable auditing in the Office 365 Admin Center to enable Data Insight to collect audit logs for the SharePoint Online account. From the SharePoint Online Credentials drop-down, select the credentials of a user with SharePoint administrator role which has been assigned the View-Only Audit Logs or Audit Logs privilege. Note: The user used for auditing of the SharePoint Online account should be set to username@DOMAIN.com instead of DOMAIN\username. Microsoft supports the User Principal Name (UPN) for connecting to a remote Exchange server. |
Enable Scanning for this SharePoint Online account | Select the check box to enable SharePoint account scanning according to the specified schedule. |
Scanning schedule (for full scans) | Select one of the following to define a scanning schedule for the SharePoint Online account:
Veritas Data Insight periodically scans site collections to obtain file metadata. Each Collector worker node by default initiates a full scan of 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 regular scan schedule. Scanning will still proceed only when scanning is permitted on the Collector node. |