Highly efficient native e-mail message data protection for office 365

A computer-implemented method of providing data protection for cloud-native electronic mail (e-mail) messages, comprising:

• accessing the e-mail message provided as a Software-as-a-Service (SaaS) product and stored in object-based storage format in object storage and including a globally unique identifier (ID) for each message;
• grouping e-mail messages together into a Container Data object of a container, wherein the container is configured to be a write once object, and holds up to 1024 e-mail messages, the container holding container data formatted as a number of documents indicator (NID) for messages in a data stream received through an application programming interface (API) of the SaaS product, a respective ID, and respective content data for each message;
• storing the Container Data object in a bucket located within a cloud computing account of a public cloud, and including a second BID entry referencing the NID;
• defining an Email Record to hold metadata and location information about each e-mail message to be used for partial restore and delete operations;
• defining a Container Record to hold metadata and location information about each container;
• defining a Backup Record consisting of a reference to a container, a bitmask and timestamp of a respective backup operation, wherein the backup operation is one of a full backup and an incremental backup, and including a third BID entry referencing the NID, the backup record containing one backup per container every backup point-in-time (PIT) to facilitate backup operations to the object store for any point in time;
• and
• first linking the Email Record to the Container Data through an index that references the data ID field and a respective BID/container ID field that references the NID field;
• second linking the Backup Record to the Container Data through a respective bucket ID/container ID field that references the NID field;
• and
• third linking the Container Record to the Container Data through a respective BID/container ID field that references the NID field.

A system providing data protection for cloud-native electronic mail (e-mail) messages, comprising:

• a Software-as-a-Service (SaaS) product providing native applications generating the-mail messages and stored in object-based storage format in object storage and including a globally unique identifier (ID) for each message;
• a Container Data object grouping e-mail messages together, wherein the container is configured to be a write once object, and holds up to 1024 e-mail messages;
• a bucket storing the Container Data object within a cloud computing account of a public cloud;
• an Email Record data structure to hold metadata and location information about each e-mail message to be used for partial restore and delete operations, the Email record indexing the container data through the ID, and including first bucket ID (BID) entry indicating location of a respective container and referencing the NID;
• a Container Record data structure to hold metadata and location information about each container, and including a second BID entry referencing the NID;
• a Backup Record data object consisting of a reference to a container, a bitmask and timestamp of a respective backup operation, wherein the backup operation is one of a full backup and an incremental backup, and including a third BID entry referencing the NID, the backup record containing one backup per container every backup point-in-time (PIT) to facilitate backup operations to the object store for any point in time;
• and
• a component grouping the e-mail messages together into a Container Data (CD) object of the container having e-mail message data respectively associated with a data ID field and the NID field, first linking the Email Record to the Container Data through an index that references the data ID field and a respective BID/container ID field that references the NID field, second linking the Backup Record to the Container Data through a respective BID/container ID field that references the NID field, and third linking the Container Record to the Container Data through a respective BID/container ID field that references the NID field.