Cohesity Alta SaaS Protection Administrator's Guide
- Introduction to Cohesity Alta SaaS Protection
- Cohesity Alta SaaS Protection Copilot (AI chatbot)
- Cohesity Alta SaaS Protection Administrator portal (Web UI)
- Supported SaaS workloads
- Workflow to protect data using Cohesity Alta SaaS Protection
- Manage users and roles
- API permissions
- What is a connector?
- What is a connector?
- About transient errors
- Overview of adding connectors
- Configure General settings
- Configure Capture scope
- Configure User filter
- Configure Group filter
- Configure Folder filter
- Configure credentials
- Configure Custom backup policy and guidelines
- Configure Delete policy for SharePoint Online and guidelines
- Configure Stubbing policy
- Guidelines to configure Stubbing policy for SharePoint Online
- Schedule a backup
- Configure email addresses to get notifications
- Review configuration and edit/save/initiate backup
- Connectors page
- Connector status
- Edit connector configuration
- Delete connectors
- Pre-requisites to setup protection for M365
- Protect Microsoft 365 Multi-Geo tenant
- Protect Exchange Online data
- Protect SharePoint sites and data
- Setting up SharePoint Online protection with Cohesity Alta SaaS Protection
- Backup and restore support for SharePoint Online
- End-user SharePoint data access in Cohesity Alta SaaS Protection
- Run the Delete and Stubbing policies to the SharePoint Online environment
- Backup limitations for SharePoint Online
- 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
- About analytics
- Analytics page and refresh behavior
- Aggregation buckets
- Gain insights into storage utilization
- Gain insights into storage utilization for Entra ID and Salesforce connectors
- Gain insights into blocked activities, most active users, and more
- Gain insights into data volume (size and item count) on legal hold
- Gain insights into data volume (size and item count) saved in different Enhanced cases
- Gain insights into data volume (size and count) under different policies
- Gain insights into data volume (size and item count) under different Tags
- Gain insights into data volume (size and item count) under different Tags behaviors
- Gain insights into storage savings after deduplication and compression
- Gain insights into data ingestion trends
- Perform restores using Administration portal
- About restore
- Prerequisites for restore
- Restore Exchange Online mailboxes
- Restore SharePoint/OneDrive/Teams Sites and data
- Restore Teams chat messages and Teams channel conversations
- Restore O365 audit logs
- Restore Box data
- Restore Google Drive data
- Restore Gmail data
- About Salesforce Data, Metadata, and CRM Content restore and Sandbox seeding
- Guidelines for Schema changes in Salesforce organization to prevent restore failures
- Restore Standard and Custom objects (Structured data restore)
- Custom Object restore - post processing steps
- Restore specific Records (Structured data) using Query filters
- Restore Salesforce CRM Content (Unstructured data restore)
- Restore Salesforce files/documents in Public/Shared libraries (Unstructured data restore)
- Limitations of Salesforce Data restore
- Salesforce Objects not supported for restore
- Key considerations for Salesforce Metadata restore
- Restore Salesforce Metadata
- Limitations of Salesforce Metadata backup and restore
- About Entra ID (Azure AD) objects and records restore
- Restore Slack data
- Restore data to File server
- Set default restore point
- Configure Restore all, Restore all versions, Point-in-time, and Specific range restore options
- Configure email addresses for notifications
- Downloading an item
- Restore dashboard
- Install services and utilities
- About services and utilities
- Pre-requisites to download and install services and utilities
- Downloading services and utilities
- Where to install the services and utilities
- Installing or upgrading services and utilities
- Configuring service accounts for services and utilities
- About the Apps Consent Grant Utility
- Discovery
- Configure Tagging polices
- Configure Tiering policy
- Auditing
- Manage Stors (Storages)
Extra Data Backup (EDB)
Cohesity Alta SaaS Protection has the Extra Data Backup (EDB) feature, enabling customers to create an additional copy of their backed-up data for enhanced redundancy and disaster recovery. This secondary backup is stored in a geographically separated location, ensuring maximum data protection and isolation. Extra Data Backup is a paid service, with costs based on the front-end terabytes (FETB) of data copied.
EDB is a secure, isolated copy of your SaaS application data, separate from the primary backup. This secondary copy remains inaccessible under normal circumstances and can only be used when necessary for data recovery.
To enable EDB for your environment, contact Cohesity Support.
For more details on supported devices, refer to the following link:
Veritas Extra Data Backup Configuration Guide
Cohesity Alta SaaS Protection Extra Data Backup
The following are the pre-requisites to configure S3 bucket to support EDB:
Table:
Actions | Options |
|---|---|
The options should be selected: | |
The check box and the other checkboxes under this section should be cleared: |
EDB can be configured on a per-Stor-type basis, letting you select specific data for backup. All associated backup data for the selected Stor types will be copied.
EDB supports all the workloads supported by Cohesity Alta SaaS Protection for protection except Salesforce and Entra ID.
When EDB is enabled for a workload, a replica of the data stored in those Stors is copied to the designated target location.
For example, copying all Exchange data would involve replicating all Exchange Stors. Similarly, all Teams chat Stors and site collection Stors would be copied for Teams data.
The Compliance EDB feature provides the capability to recover your data from EDB (currently EDB compliance is supported only for S3 on-premises EDB), ensuring data redundancy outside the hosted cloud environment. This feature ensures compliance by enabling secure data storage and retrieval options, giving users control and flexibility over their data management.
To enable EDB for your environment, contact Cohesity Support.
Self-service recoverability: You can recover data independently without needing to contact support.
Setup: You can initiate setup by opening a support ticket.
Licensing: An EDB license is required to access this feature.
You need to enter the required information in the JSON file with the following items:
InstanceID: A name to identify the application during run time.
AccessKeyID: The username / identity key for the application.
SecretAccessKey::The password for the application.
AWSRegion: The AWS Region associated with your EDB.
BucketName; The AWS bucket name associated with your EDB.
EndpointURL
UseHTTP: Specifies if HTTP should be used.
ForcePathStyle
IsOnPrem: Specifies if the application is on-premises.
You can use the following command line argument:
configFileLocation
The file path for the configuration file.
Example: "C:\ComplianceCopyConfigFiles\s3SourceConfig.json"
agentType
The Corresponding HubStor Type
Example: "S3Bucket_OnPrem"
earliestModificationTime
The earliest file modification time needs to be considered for the retrieval.
Example: "2024-02-01"
This argument is optional and can be left as: ""
latestModificationTime
The latest file modification time needs to be considered for the retrieval.
Example: "2024-06-03"
This argument is optional and can be left as: ""
earliestAccessTime
The earliest file access time needs to be considered for the retrieval.
Example: "2024-02-01"
This argument is optional and can be left as: ""
latestAccessTime
The earliest file access time needs to be considered for the retrieval Example: "2024-02-01"
This argument is optional and can be left as: ""
earliestCreationTime
The earliest file creation time needs to be considered for the retrieval.
Example: "2024-02-01"
This argument is optional and can be left as: ""
latestCreationTime
The earliest file creation time needs to be considered for the retrieval.
Example: "2024-02-01"
This argument is optional and can be left as: ""
storSiteID
The storSite number where the files should be sourced from Example: "1"
storID
The StorID number where the files should be sourced from Example: "2"
destinationDirectory
The path to the folder where the files will be housed.
Example: "C:\MyComplianceCopy\Retrieval\Destination"
targetLocation
The location where the files should be sourced from. All files and folders beneath this directory will be considered for data retrieval.
Example: "Dan NewExchange Connector\admin@M365x04142374.onmicrosoft.com
fileName
A name similar to the files you want to retrieve.
You must request the custom utility from the Veritas Support team and install it. Open the Command Prompt from the following path and run the command.
C:\Program Files (x86)\HubStor\Custom
C:\Program Files\EDBComplianceDataRetriever.exe configFileLocation="C:\ComplianceCopyConfigFiles\s3SourceConfig.json" storSiteID="1" storID="2" agentType="S3Bucket_OnPrem" earliestModificationTime="" latestModificationTime="" earliestAccessTime="" latestAccessTime="" earliestCreationTime="" latestCreationTime="" fileName="My File Name" destinationDirectory="C:\Temp\EDBCompliacne Data Retrieval" targetLocation="Dan NewExchange Connector\admin@M365x04142374.onmicrosoft.com"