1. Support
  2. Knowledge base
  3. 100050246

How To Create A OneDrive Connector using the Veritas Alta SaaS Protection Connector Service

Article: 100050246
Last Published: 2023-09-19
Ratings: 0 0
Product(s): Veritas Alta SaaS Protection

Description

 
This article will walk through the process of configuring a connector that will capture OneDrive Sites. These steps apply when configuring the connector from within the Veritas Alta SaaS Protection Connector Service application. 
 
A connector can also be created using a wizard from within the Veritas Alta SaaS Protection Admin Portal. For detailed information on this topic, refer to article:  https://www.veritas.com/content/support/en_US/article.100050380
 

Pre-requisites: 

  1. The connector must be created before these settings can be applied. For information on creating a connector, refer to the article:  How To Create Connectors In Veritas Alta SaaS Protection
  1. Steps outlined in the Preparing for O365 article must be completed.  
 

Configure Connector's General Settings

 
  1. Get Location ACLs -- This option will synchronize unique ACLs at the folder level. This option should be disabled.
  2. Get Item ACLs -- This option will synchronize unique ACLs at the item level and is disabled by default. 

Configure Connector Type Specific Settings

General Tab:  
 
 
Options should be set as seen above.  
  1. Auto-add SCOM Account as Site Collection Admins -- This option can automatically add user accounts as Site Collection Admins.  These user accounts are specified within the 'CSOM Auth' tab which will be discussed in more detail.  It is recommended to enable this option.  
  2. My Site/OneDrive Site Collection Base URL -- Enter the Base URL. Example: https://xyzcompany-my.sharepoint.com
  3. Admin Site URL -- Enter the URL for the Admin Site.  Example:  https://xyzcompany-admin.sharepoint.com
Options Tab:
 
 
  1. Continuous Data Protection -- CDP provides near-real time capture of new or changed items in SharePoint. For complete details regarding CDP and specific options, refer to article: How To Configure Continuous Data Protection
  2. Process Document Libraries Only -- When enabled, this option will exclude capturing of lists, blogs, wikis, etc.  
  3. Exclude System Lists -- These include the master page gallery for example.  Usually recommended enabling this option.
  4. Large List Threshold -- This setting should not be modified unless directed by a Veritas Alta SaaS Protection representative. 
  5. Retrieve OneDrive Site Collections Every N Days -- By default, this is set to 0 which is the recommended setting.  
  6. Get OneDrive Site Collections Using Powershell -- When enabled, it will not use the user profile service, but instead Get-SPOSite, with additional filtering so that only OneDrive site collections are returned.  Note that any ‘User Filter’ or ‘Site Collection Scopes’ will apply regardless of whether we are using the user profile service or PowerShell. It is highly recommended to use this option.  
CSOM Auth Tab:
 
 
There are two modes to choose from: 
 
  1. Basic -- This is the default setting where it utilizes service accounts that have been created as part of the Preparing for O365 process document of which will be automatically added as site collection admins if the option 'Auto-add SCOM Account as Site Collection Admins' is enabled.  
  2. Modern/OAuth -- This is the preferred method.  To use this setting, the fields are populated with information after creating the SharePoint Application.
  1. Choose either 'Use Autodiscovery' or 'Manually Set EWS URL' based on the O365 configuration.  
PowerShell Auth Tab:
Depending on which option was chosen in the previous step (Basic or Modern/OAuth), depends on how the below options are displayed.  
 
 
For Basic CSOM Auth, the settings are: 
  1. Enter the SMTP address and password for a user with the SharePoint administrator Role. 
For Modern/OAuth, the Client ID and Client Secret are the same as CSOM Auth settings above.  
 
 
User Filter Tab:  
 

  1. This tab allows filtering of OneDrive site collections based on an extended AD attribute.  This filtering can take the form of an exact match, a wildcard match, or even a regular expression.  In the example above, the connector will match those users whose ‘department’ is either Engineering, or something like ‘Executive’, which would match the regex specified. Additionally, a very powerful filter that can be used is the value of:  [null]  - when used as an extended AD attribute filter value, it will match exactly those users who have a null or missing value for the given attribute.

Site Collection Scope Tab:  
 
 
No Site Collection Scope (all site collections) -- This option will  process all site collections returned from SharePoint.
Rolling Site Collection Scope --  This rolling multi-instance mode will result in a given SharePoint connector only processing a certain number of site collections.  The goal is to allow really large O365 tenants to have the work distributed amongst multiple connectors and even multiple Stors. This option is available for the following 3 modes within the general tab: 
 
  1. All Site Collections
  2. All OneDrive Site Collections
  3. All Groups/Teams Site Collections
It is important to note when using Rolling Site Collection Scopes with multiple connectors, there must be a number specified in each connector.  For example, there are 20 thousand SP or OD sites to be split among 2 connectors.  The first connector will be configured with 10000 and the second connector configured with 10001.  If the second connector is not set with a rolling scope, it will capture all 20k sites.  
 
Restrict to Users With Specific Mail Domains --   It  allows for restricting which sites to collect based on user(s) who have an email address in a specific domain. 
 

Was this content helpful?

Article Languages