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:
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 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 ASP Content location where the files should be sourced from. All files and folders beneath this directory will be considered for data retrieval.
s3TargetLocation
The target location from the AWS s3 bucket where the files should be sourced from. All files and folders beneath this directory will be considered for data retrieval.
Note:
One of the parameters from targetLocation and s3TargetLocation can be empty or null, if both parameters are given then the priority will be given to s3TargetLocation.
1. targetLocation: Copy the path from the ASP Content portal.
Examples:
New connector
New connector\AdeleV@M365x49242125.OnMicrosoft.com
2. s3TargetLocation: Copy the path from S3 bucket.
Examples: EWSAllUsersVPNSP.Location_7736/admin@vpnsp.onmicrosoft.com.Location_7758/Active Mailbox.Location_7987/Inbox.Location_8001"
fileName
A name similar to the files you want to retrieve.
Cohesity will share the custom utility with you.
You need to install the custom utility.
Create a JSON file with the required parameters as follow:
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.
Proxy Details:
Do not include below fields if proxy is not enabled for the Web service or keep the field values as Null.
ProxyHost: The Proxy Host property for the web service.
Example: proxy.mycompany.com:8080
ProxyBypassList: The proxy bypass list.
Example: localhost;127.0.0.1; *.mycompany.local
ProxyAuthenticationUserName: Proxy Authentication username.
ProxyAuthenticationPassword: The decrypted password. Not serialized.
Once the custom utility is installed, launch the Command Prompt from the C:\Program Files (x86)\HubStor\Custom folder.
Run the commands with a series of arguments, each separated by a space. Refer to the following examples:
To get the target location from the Cohesity Alta SaaS Protection Administration portal, go to the page. Select the required item or folder, click the info i icon, go to the section, and from the section, copy the path.
Hubstor.Utilities.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\EDBCompliance Data Retrieval" targetLocation="Dan NewExchange Connector\admin@M365x04142374.onmicrosoft.com"
To get the target location from S3, go to the S3 Browser. Click the required bucket, click the folder. Browse to the item that needs to be restored, and copy the path starting from the connector name. Do not copy the at the end.
Hubstor.Utilities.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\EDBCompliance Data Retrieval" targetLocation="" S3TargetLocation = "EWSAllUsersVPNSP.Location_7736/admin@vpnsp.onmicrosoft.com.Location_7758/Active Mailbox.Location_7987/Inbox.Location_8001"
