Cohesity Alta SaaS Protection 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 SearchUnifiedAuditLog PowerShell command to fetch audit logs. Depending on factors such as the number of logs within the specified interval, the process can take a few minutes to several hours.
SearchUnifiedAuditLog imposes a minimum window of 1 second and a maximum limit of 5000 records, data gaps may occur if the number of logs exceeds 5000 within a single second.
The UI does not display progress until the audit logs are fully collected and processed for the specified hour.
Backup does not happen if number of records exceeds 5,000 at any particular second.
The SearchUnifiedAuditLog command has internal time-out limitations. To handle this, Cohesity Alta SaaS Protection retries up to three times. If all retries return zero results, Cohesity Alta SaaS Protection assumes that no data is available in the specified time range. Note that this retry mechanism may increase backup time.
Cohesity Alta SaaS Protection supports restoring Audit Log backup data only to the File Server.
If any errors occur in the backup for any time range, Cohesity Alta SaaS Protection logs the error and proceeds with the backup but will not revisit the same time slot again in the current or the next backup. Examples of issues that can happen:
An error from Microsoft when retrieving audit entries.
An error while uploading data to Cohesity Alta SaaS Protection.
If an Audit log connector is unable to keep pace with the data generated by the customer's Microsoft tenant, Cohesity Alta SaaS Protection will not be able to back up all the data. For example, if backing up x days of data takes x + n days, then some data will be missed regularly. For example, if a connector is configured to back up the last three days, but it takes five days to complete the backup, then when the next backup starts, it will consider only the last three days and will miss two days of data.
If, for any reason, the connector is down for a few days, then depending on how the connector is configured and the performance received from Microsoft, data capture may be missed. For example, If a connector is configured to capture the last one day of data but is down for two days, then the next backup will capture only the last one day of data instead of the missing two days. As a result, one day of data will be lost.