Cohesity Alta SaaS Protection 2.x.x Administrator's Guide
- Introduction to Cohesity Alta SaaS Protection
- API permissions
- Administrator portal (Web UI)
- Manage users and roles
- What is a connector?
- Configure credentials
- Pre-requisites for Microsoft 365 connectors
- Protect Microsoft 365 Multi-Geo tenant
- Protect Exchange Online data
- Protect SharePoint sites and data
- Protect Teams sites
- Protect OneDrive data
- Protect Teams chats
- Protect GoogleDrive data
- Protect Gmail data
- Protect Audit logs
- Protect Salesforce data and metada
- Protect Entra ID objects
- Protect Box data
- Protect Slack data
- Protect Email/Message data
- Configure Retention policies
- Perform backups
- View and share backed-up data
- Analytics
- Perform restores using Administration portal
- Restore SharePoint/OneDrive/Teams Sites and data
- Restore Teams chat messages and Teams channel conversations
- Restore Box data
- Restore Google Drive data
- About Salesforce Data, Metadata, and CRM Content restore and Sandbox seeding
- About Entra ID (Azure AD) objects and records restore
- Restore dashboard
- Install services and utilities
- About the Apps Consent Grant Utility
- Discovery
- Configure Tagging polices
- Configure Tiering policy
- Auditing
- Manage Stors (Storages)
Audit log connector limitations
The limitations of the Audit log connector are:
Cohesity Alta SaaS Protection uses the Search-UnifiedAuditLog PowerShell command to retrieve audit logs. The duration of this process may vary, ranging from a few minutes to several hours, depending on factors such as the volume of logs within the specified time interval. This may result in delays in the backup process.
The Search-UnifiedAuditLog command enforces a minimum query window of one second and imposes a maximum limit of 5,000 records per query. If the number of audit log records exceeds 5,000 within a single second, Cohesity Alta SaaS Protection will be unable to back up the audit log data for that specific second.
The user interface does not display progress information until audit logs for the specified hour have been fully collected and processed.
The Search-UnifiedAuditLog command has internal time-out limitations. To address this, Cohesity Alta SaaS Protection performs up to three retry attempts. If all retries return zero results, it is assumed that no data is available for the specified time range. It is important to note that this retry mechanism may contribute to increased backup duration.
Restoration of audit log records directly to a Microsoft server is not supported. Therefore, Cohesity Alta SaaS Protection allows restoration of audit log backup data only to a File server.
If, for any reason, the connector fails to process certain timeslots, those timeslots cannot be revisited for data collection. Several factors may contribute to timeslots being missed, including:
Failures in retrieving audit entries from Microsoft or errors encountered while uploading data to Cohesity Alta SaaS Protection.
The connector being unable to keep pace with the volume of data generated by the customer's Microsoft tenant.
The connector being inactive or in an erroneous condition, and hence not running as expected.