1. Copyright © 2015 Sesame Software, Inc. All rights reserved. Satisfying Regulatory Compliance for Salesforce.com Data

2. Copyright © 2015 Sesame Software, Inc. All rights reserved. Regulatory Environment Federal Laws and Rules require a robust Compliance solution Public US Companies: Sarbanes-Oxley Medical: HIPPA and 21 CFR Part 11 Securities: SEC Rule 17A Europe: Data Protection Act Have a Job-Saving Disaster Recover Plan What happens to your career if your company loses data and you can’t recover it?

3. Copyright © 2015 Sesame Software, Inc. All rights reserved. Compliance Problems to Solve Backup  All Cloud data  Retain for 7 years  Keep deleted records in backup set  Permanent Audit trail of all changes to all fields in all records Recovery  Full – least likely scenario  Partial – selective restore of some records or some objects  Restore deleted data  Restore corrupted data to a point-in-time  Recover relationships between records

4. Copyright © 2015 Sesame Software, Inc. All rights reserved. What can go wrong? Likely scenarios  Malicious employees  Careless employees  Employees covering up mistakes  Salesforce Administrative errors (mass destruction)  Misuse of vendor tools (mass destruction)  Update errors by automated processes  Inability to trace who did it We get calls all the time from Salesforce administrators with these problems!

5. Copyright © 2015 Sesame Software, Inc. All rights reserved. Native no-cost feature of Salesforce.com User-initiated Maximum frequency once per week Recovery requires Salesforce Data Loader Can’t handle parent-child or recursive relationships Can’t handle Attachments or Documents No point-in-time consistency Not scalable Salesforce.com Backup Technologies Level 1: Full weekly copy to CSV text files

6. Copyright © 2015 Sesame Software, Inc. All rights reserved. Basically the same as Salesforce CSV backup Maximum frequency once per day Requires product purchase Full backup – not incremental Uses up daily API calls, which are limited by Salesforce Recovery uses Salesforce Data Loader Can’t handle parent-child or recursive relationships Can’t handle Attachments or Documents Can’t restore data spanning multiple versions since the schema can change between versions Backup only contains active records, so recovery of deleted records is possible only in the current backup version Not scalable Disk storage requirement = Salesforce size x # copies Salesforce.com Backup Technologies Level 2: Full daily copy to CSV text files

7. Copyright © 2015 Sesame Software, Inc. All rights reserved. Salesforce Warehouse Many products will back up Salesforce to an on-premise or cloud relational database. This provides a reporting warehouse or integration hub, as well as a convenient recovery database. Salesforce.com Backup Technologies Level 3: Incremental copy to a database Replication Tool

8. Copyright © 2015 Sesame Software, Inc. All rights reserved. Cost  Requires product purchase Requires bi-directional  Some products can backup but lack bi-directional support -- backup is useless for recovery! Automation  Handles database schema changes as they are made in Salesforce Scalability  Handles query timeouts on large datasets on the initial load or if many records are changed between replication cycles  Salesforce queries will time out if > 1-2 million records Only one backup version available for each record  If you overwrite the backup with bad data, you don’t have a backup of the good data Almost all products can’t handle recovery of parent-child or recursive relationships  Child records orphaned or not loaded during recovery since parents have new ID’s Salesforce.com Backup Technologies Level 3: Incremental copy to a database

9. Copyright © 2015 Sesame Software, Inc. All rights reserved. Salesforce Warehouse Without multiple-versioned history, there is only a single recovery point – the last time Salesforce was backed up. Even if a backup is taken just before the corrupting process runs, the need for recovery may not be apparent for days, making a point-in- time recovery impossible. Many products do not even have a recovery capability yet claim to be a “compliance solution.” Replication Tool Salesforce.com Backup Technologies Level 3: Incremental copy to a database No Point- in-Time Recovery

10. Copyright © 2015 Sesame Software, Inc. All rights reserved. Salesforce Warehouse Relational Junction is also the only product that can handle unlimited data volumes with its patented time-segmentation process, and uses patented parallel read-write processes to achieve blazing speeds. Salesforce History Salesforce.com Backup Technologies Level 4: Time-Segmented Incremental Versioned Database Relational Junction’s unique History Tracking feature that makes a copy of the warehouse record before the record is updated by the Salesforce-to- Warehouse replication. This can be turned on for all objects with a single check-box.

11. Copyright © 2015 Sesame Software, Inc. All rights reserved. Salesforce Warehouse Customizable recovery makes it possible to select records in the Salesforce Warehouse or Salesforce History for recovery by restoring the oldest record before a specified point in time Salesforce History Point-in-Time Recovery Relational Junction for Salesforce Selection criteria can be filtered by Last Updated User or any other criteria as well, preventing good data from being overwritten by obsolete date. Individual fields can also be selected instead of the entire record, ensuring that only corrupted fields are overwritten by the recovery.

12. Copyright © 2015 Sesame Software, Inc. All rights reserved. Satisfying Compliance Regulations Satisfies Federal Compliance Regulations SEC Rule 17a for Securities Broker-Dealers HIPAA / FDA for healthcare organizations Requires data retention, historical tracking, rapid data recovery Heavy fines for violation Relational Junction Best in Class Compliance Database records are archived, but never physically deleted Captures who changed or deleted records, and when Archived records fully recoverable Handles recovery of parent-child relationships Tracks change history for all fields in all tables – native Salesforce.com History Tracking can only capture 60 fields per object Patented scalability

13. Copyright © 2015 Sesame Software, Inc. All rights reserved. How it Works Scalability United States Patent 8,122,040 enables replication of massive amounts of data by breaking down the replication process into smaller data sets by ranges of time stamps in the source data. Otherwise, queries of > 1 million records will time out. Sesame has filed 4 patents on parallel scalability techniques employed in the product for massive performance making it much faster than the Bulk API. No other vendor can do that.8,122,040 Recovery of hierarchically related data United States Patent 8,375,010 provides a way to create or recover related records in the database and replicate them to Salesforce.com in one pass with the parent-child relationships intact. This makes it possible to recover or clone an entire Salesforce org. Database triggers and supporting indexes that are generated ahead of time (United States Patent 8,745,029) are knowledgeable of the relationships in the data model, and look for related records with the old key, updating the key values where found before the child table is loaded. No other vendor can do that.8,375,0108,745,029

14. Copyright © 2015 Sesame Software, Inc. All rights reserved. How it Works Recovery of Recursive Relationships Relational Junction can load recursive relationships in an object by storing the old ID in a separate column (LEGACY_ID) loading the records except for the parent pointer column (PARENT_ID) running a SQL update to update PARENT_ID with the new ID where LEGACY_ID = PARENT_ID running an update load for just the PARENT_ID column History Archive for Audit and Point in Time Recovery Relational Junction optionally creates a history table for every primary table without unique indexes. This history table contains the prior image of every record before the main primary table is updated, giving you a complete audit trail and a point-in-time recovery capability (Patent Pending). No other vendor has this.

15. Copyright © 2015 Sesame Software, Inc. All rights reserved. Cautions Understand your use cases What are the actual scenarios that would require recovery? Do you need full recovery or selective? Do you need point in time recovery? Ask the hard questions Who are the vendor’s customers? Have any of them actually done a recovery? Can it recovery parent-child relationships? Can it handle recursive relationships? Can it handle Attachments and Documents? What are scalability limits? Avoid solutions that look too easy The magic one-button recovery could destroy new, good data Think before you push that button! Work through the recovery with another person to check assumptions

16. Copyright © 2015 Sesame Software, Inc. All rights reserved. Next Steps www.sesamesoftware.com info@sesamesoftware.com (866) 474-7575 Get a free evaluation started today