OwnBackup FAQs

OwnBackup aims to provide its clients with a Full & Complete backup of all the Data, Metadata, Attachments, Content Document & Knowledgebase Articles. In order to ensure that - OwnBackup will automatically analyze the field-level-security upon completion of every Full Backup. If unreadable fields are detected due to changes made to profiles and/or permission, a warning will be shown on the service's dashboard that the data has been excluded with a link to a new tab ("Permissions Report") containing the report. OwnBackup also provides an actionable remediation tool. When selecting “see report”, the option exists to export the Field Level Security Report as an XML for Profile updates. This enables admins to update any profile with missing field/object permissions using Force.com IDE and other similar tools. In order to fix those gaps within Salesforce, please follow the instructions below: Authenticated User must have the "Modify All Data" permission A license of any installed package (that requires a license in order to access its data) must be assigned to the Authenticated User At least Read Access to all Standard & Custom fields (can be configured from the Field Level Security page) In case, you are using the Salesforce Knowledge Base module (KB Articles), the Authenticated User must be a Knowledge User *Authenticated User = The user that connects OwnBackup to the client's Salesforce org.

OwnBackup aims to provide its clients with a Full & Complete backup of all the Data, Metadata, Attachments, Content Document & Knowledgebase Articles. OwnBackup leverages the Salesforce API, therefore, in order to achieve this goal, please make sure that the Authenticated User has the required permissions as listed below: Authenticated User must have the "Modify All Data" permission A license of any installed package (that requires a license in order to access its data) must be assigned to the Authenticated User At least Read Access to all Standard & Custom fields (can be configured from the Field Level Security page) In case, you are using the Salesforce Knowledge Base module (KB Articles), the Authenticated User must be a Knowledge User *Authenticated User = The user that connects OwnBackup to the client's Salesforce org.

ContentFolder represents a folder in a content library for adding files. Therefore, OwnBackup will query Libraries as ContentFolder object. If you are looking for a specific Library that has been added or deleted. The change will be shown under the ContentFolder object in OwnBackup. * To access Libraries in Salesforce, Salesforce CRM Content must be enabled on the user profile. All users with a content feature license can modify folders in their personal library in Salesforce.

In order to find your metadata components (aka. search layouts, record types, list views, validation rules, etc.) for any given data object, please follow the steps below: 1. Click on your metadata service 2. Click on backup history 3. Click on the backup you wish to access 4. Look for “Custom Object” and download that by clicking on the number of records to the right 5. Unzip the file and open the CustomObject folder 6. Open the objects folder 7. Locate the object in question (ie: Account) and open the file using any text editor

OwnBackup Storage System upgrade OwnBackup is in the process of migrating its underlying long-term storage system from AWS's Elastic Block Storage (EBS) to AWS's Simple Storage System (S3). This migration will enable OwnBackup to better support our continued growth as we scale and add new data-center options such as Australia, Canada and GovCloud. The new storage system will use AWS's S3, a highly-scalable, highly-reliable (99.999999999%) object storage service in conjunction with AWS's FIPS 140-2 certified Key Management System (KMS). Additional Notes: Data residency - unchanged: while data is migrated from EBS to S3 it will at all times remain in the same region (both during and after the migration). E.g., data that resides on our EMEA1 region (located in Frankfurt, Germany) will remain in that region. Encryption in transit and at rest: in accordance with our current data-encryption policies, during the migration process the data will be encrypted in transit (using TLS 1.2), and encrypted at rest (using AES256 bit encryption) via AWS's KMS (SSE-KMS-CMK). Information Security Controls: we updated our security controls to match our new S3-based architecture, and maintain our best-of-breed security and data protection. These controls include aspects such as data segregation, network access control, access and audit logs, data replication, segregation of duties and more. SLA: Our market-leading SLAs will remain unchanged during and after the migration process. OwnBackup SLA is available at www.ownbackup.com/SLA FAQ: Q: Does this migration affect customers using OwnBackup's Azure regions? A: No, at this time only customers hosted on AWS are affected by this change. Q: Does this migration affect customers using OwnBackup's AKM (Advanced Key Management) A: No, at this time customers using AKM will not be affected by this process. Q: Do customers have to do anything during or after the data migration? A: No, this migration does not require any user actions at any time. Q: Can a customer use their own AWS S3 bucket or AWS KMS Key for storing or encrypting their data respectively? A: This option may be available in the future

This link contains the full list: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_unsupported_types.htm

OwnBackup compares backup snapshots between two points in time - if the record existed in the previous backup and it does NOT exist in the newer backup, OwnBackup will identify it as Deleted. To expand a bit further, if the IsDeleted checkbox is True, it means the record is deleted and resides in the Salesforce Recycle Bin. OwnBackup does not back up the records in the recycle bin. Therefore, there is no situation where the IsDeleted field will be True in the backups.

Clients of OwnBackup can use the Find tool to search for all attachments for any given record using the following steps: Click on the Find tab Select Records, select a service to search in and hit Next Step Select a time frame option to search in and hit Next Step Type in the following search term - RecordID sObject:attachment (insert the actual record id for RecordID) and hit Next Step Click Find You will be presented will all attachments for that particular record. If you click the Downloads button and select All Latest, you will be able to download all the files to your desktop. Additional examples: Search for all contacts for any given account using the following steps: Click on the Find tab Select Records, select a service to search in and hit Next Step Select a time frame option to search in and hit Next Step Type in the following search term - RecordID sObject:contact (insert the actual record id for RecordID) and hit Next Step Click Find You will be presented will all contacts for that particular account. If you click the Downloads button and select All Latest, you will be able to download all the files to your desktop. Search for all versions for any given record in the past 30 days using the following steps: Click on the Find tab Select Records, select a service to search in and hit Next Step Select the Backup range option to search in, select your latest backup for the To date and an older backup for the From date and hit Next Step Type in the RecordID you are looking for (or if you know the name of the Account/Contact/etc) and hit Next Step Click Find You will be presented will all contacts for that particular account. If you click the Downloads button and select All Versions, you will be able to download all the files to your desktop. By unzipping that file, you will now get separate CSVs for each time the record appears in your snapshots, showing all the different changes across the various files. Search for a file based on a specific keyword using the following steps: Click on the Find tab Select Attachments, select a service to search in and hit Next Step All backups will be selected by default, so hit Next Step Type in the keyword you are looking for and hit Next Step Click Find You will be presented will all files where the keyword appears in either the title or the body. To download a particular file, simply click on the title.

OwnBackup’s Smart Alerts supports alerting based on statistical outliers detection in your data and/or to define thresholds and set alerts based on More Than/Less Than scenarios. This capability allows users to receive alerts on their object(s) of choice whenever a significant outlier from the distribution of the added, removed or changed record counts is detected. Outlier detection is a key element of modern statistics. The scientific community uses statistical outlier detection for a wide range of applications ranging from determining new trend beginnings through detecting sensor malfunctions and more. At their core, Outliers are major deviations from the general trend of your data. Major changes in the added, removed or changed record counts could indicate a data loss or data corruption event that you should be aware of. In the services page, choose a service you would like to add an alert for. Click on the “Smart Alerts” option in the left menu tab. Set Alert when to “statistical outlier” and select an object from the drop down menu. Click Add Alert. Make sure the alert was added to the alerts list under the Alerts tab.

By default, OwnBackup Data Backup Service will back up all the queryable (queryable=true) Objects in the Salesforce Org. The OwnBackup admin can configure the backup services to include or exclude *History, *Share and *Feed Objects. In general, the data backup will include: Standard & Custom Salesforce objects (including Standard and Custom fields) OwnBackup will query and backup all the fields in a given sObject barring some exceptions. The backup agent uses the Describe() API call to learn about all the fields that are available in a given sObject. Files (Attachments, Content Documents, etc.) Chatter Feeds & Attachments Knowledge Base Articles * Note that Metadata components will be backed up as part of the OwnBackup MetaData Backup Service The following Objects that are not queryable or are not fully supported by the API: AccountUserTerritory2Views, ApexLimitEvents, BackgroundOperationResults, CollaborationGroupRecords, ContentFolderItems, ContentFolderMembers, ContentHubItems, Datacloud*, DataStatistics, DcSocialProfile*, EngagementHistories, EntityDefinitions, EntityParticles, FieldDefinitions, FlexQueueItems, IdeaComments, ListViewChartInstances, LoginEvents, NetworkUserHistoryRecents, OauthTokens, OutgoingEmails, OutgoingEmailRelations, OwnerChangeOptionInfos, PicklistValueInfos, PlatformActions, RelationshipDomains, RelationshipInfos, SalesOrder__xes, SearchLayouts, TenantUsageEntitlements, UserAppMenuItems, UserEntityAccesses, UserFieldAccesses, UserProfileFeeds, UserRecordAccess, Votes, *__b (BigObjects), *__mdt (Custom Metadata), and *__x (External sObjects).

For app1.ownbackup.com 52.71.225.201 52.71.168.217 For hipaa1.ownbackup.com 52.4.24.63 52.0.123.243 For emea1.ownbackup.com 52.28.163.240 52.28.160.154 For ca1.ownbackup.com 35.182.9.40 35.182.46.254 For usgov2.ownbackup.com 52.61.196.250 52.61.16.244 For au1.ownbackup.com 13.236.99.148 13.211.16.11 For emea4.ownbackup.com 13.81.98.210 52.166.143.26

The time and date are in UTC. Make sure to adjust the time accordingly

What is the API consumption for archiving a record? 21 APIs calls per 1000 records archived. (this will likely to go down in the future) What is the API consumption for archiving attachments? 1 API calls per attachment What is the API consumption for unarchiving a record? depends on the records and its children between 1 to 5 (this is the minimum possible using SF API) What is the API consumption for viewing a list of archived records on the Visualforce page in a record? No Salesforce API What is the API consumption for viewing details (preview) of an archived record by clicking on the eyeball? 1 call

Yes, via a support case. SLA 5 business days

Today archiving 100K records takes 15 minutes. Larger data set can be calculated accordingly. Archiving time highly depends on the retrieval of attachments. If one archive significant number of attachments as part of the policy, one should expect archival time increases

If there is a trigger that is activated on a delete operation of an archive record (the root record), the trigger will be activated. If there is a trigger that prevents a delete operation of an archive record (the root record), the archive operation of this record will fail. If there is a trigger on a child/ related record that is activated on a delete operation, the trigger will not be activated (according to Salesforce documentation)

That is actually exactly what we would expect to see. While Salesforce counts most record sizes as 2K (There are some exceptions like EmailMessage records that are larger), OwnBackup counts the actual data usage. Therefore, there may be a difference in sObject sizes in Salesforce and at OwnBackup. While this is not something that salesforce makes public, it has been discussed on a number of expert blogs such as: http://www.cloudsuccess.com/blog/how-do-salesforce-calculate-data-storage/

In order to minimize API calls (to avoid hitting salesforce quota limits), OwnBackup downloads and backs up your attachments incrementally at a default rate of 2,000 files per day (you can throttle the number of files per day through the Options page). Once all your files have been successfully backed-up, only files that have changed since the last backup will be downloaded (incrementally). For example, if your Salesforce Org has 4,500 file attachments, backup of your attachments will complete within three days. From then on, your new (or modified) attachments will be incrementally downloaded and backed-up.

The following object types are supported: AccountSettings, ActionLinkGroupTemplate, ActionOverride, ActivitiesSettings, AddressSettings, AnalyticSnapshot, ApexClass, ApexComponent, ApexPage, ApexTrigger, AppMenu, ApprovalProcess, ArticleType, AssignmentRules, AuthProvider, AuraDefinitionBundle, AutoResponseRules, BaseSharingRule, BusinessHoursSettings, BusinessProcess, CallCenter, CaseSettings, ChatterAnswersSettings, CompanySettings, Community (Zone), CompactLayout, ConnectedApp, ContractSettings, CorsWhitelistOrigin, CriteriaBasedSharingRule, CustomApplication, CustomApplicationComponent, CustomField, CustomLabel, Custom Metadata Types (CustomObject), CustomMetadata, CustomLabels, CustomObject, CustomObjectTranslation, CustomPageWebLink, CustomPermission, CustomSite, CustomTab, Dashboard, DataCategoryGroup, EmailTemplate, EntitlementProcess, EntitlementSettings, EntitlementTemplate, ExternalDataSource, FieldSet, FlexiPage, Flow, Folder, FolderShare, ForecastingSettings, Group, HomePageComponent, HomePageLayout, IdeasSettings, InstalledPackage, KnowledgeSettings, Layout, Letterhead, ListView, LiveAgentSettings, LiveChatAgentConfig, LiveChatButton, LiveChatDeployment, ManagedTopics, MatchingRule, Metadata, MetadataWithContent, MilestoneType, MobileSettings, NamedCredential, NamedFilter, NameSettings, Network, Network Branding, OpportunitySettings, OrderSettings, OwnerSharingRule, Package, PathAssistant, PathAssistantSettings, PermissionSet, Picklist (Including Dependent Picklist), Portal, PostTemplate, ProductSettings, Profile, Queue, QuickAction, QuoteSettings, RecordType, RemoteSiteSetting, Report, ReportType, Role, SamlSsoConfig, Scontrol, SearchLayouts, SecuritySettings, SharingBaseRule, SharingReason, SharingRecalculation, SharingRules, SharingSet, SiteDotCom, Skill, StaticResource, SynonymDictionary, Territory, Territory2, Territory2Model, Territory2Rule, Territory2Settings, Territory2Type, Translations, ValidationRule, WebLink, Workflow. To learn more about the various objects, please visit the Metadata API Developer’s Guide.

Yes, we perform ongoing monitoring and analysis of logs to detect suspicious activity and to ensure the system is working as expected. Logs are gathered via syslog from the various instances and tiers (application, network and OS events) and then reviewed and analyzed from a central server.

Passwords can contain any combination of printable ASCII characters and must contain a minimum of 8 characters, 1 upper case character, 1 lower case character and 1 special character Passwords can't begin or end with a whitespace character. Passwords can’t contain the username or email address Repeating characters and known poor passwords (such as “password”) may also be blocked

In the event of a data breach relating to your account, OwnBackup will immediately suspend your account and contact OwnBackup’s point of contact at your firm via e-mail and/or phone. We recommend that you provide us with direct incident response contact information to ensure around-the-clock availability for urgent matters.

As a Data Controller, what do I need to be asking my SaaS backup Data Processors before GDPR enforcement begins May 25th? When third parties process data on your behalf, you’re obligated to ensure they have sufficient guarantees and technical measures in place to protect the rights of the Data Subject. Consider the following areas when engaging third parties: How are your vendors meeting the necessary standards for data security and privacy? This includes both contractual and regulatory obligations. Are your vendors able to demonstrate robust privacy, data protection, and other security practices around their network and infrastructure? How are your vendors able to support a culture of privacy by design? How do your vendors help you manage your obligations as a Data Controller? Should US and Non-European companies be concerned about GDPR? Yes! If you are capturing and storing personal data of European Data Subjects, you must to pay attention to GDPR. Whether that data is stored in the EU or not, your company will be held liable under the GDPR requirements. In other words, if you offer goods and services to, market to, or process citizens of EU member states, capturing EU Data Subject personal information, you will be impacted by this regulation. How do I find and access Data Subjects information that may reside in my data backups? As Data Controllers, you’re responsible for maintaining an inventory of personal data, including the data in your archives. This can be one of the more difficult obligations of a Data Controller, particularly because you must not only furnish your Data Subject(s) with details of how their data is handled, shared, and used, but also provide notification without undue delay. Data Controllers using OwnBackup will be able to perform global personal data searches across their archives, identifying the region and attachments in which the Personal Data resides. This will be possible on-demand and within minutes. As a Data Controller, how long do I need to keep backups for? When you consider determining your retention period, you need to account for what category of data you have captured, your legal right to maintain it, and any regulations that would impact the retention of this data. As a Data Controller, based on your business’ risk tolerance, privacy impact assessment, and compliance obligation(s), you can decide whether it’s appropriate to retain data, for example, for 6 months or for 6 years. OwnBackup supports custom retention policies to match the length of period you need without compromising your ability to meet your regulatory data retention strategies. As the regulatory body that will enforce GDPR, how has the Information Commissioner's Office (ICO) defined "privacy by design"? “Privacy by design” requires that privacy and data protection controls are the common thread that has been weaved into each aspect of your technology stack from code development, to product features, to the risks of how you process data and retain data. How well these factors tie together determine your compliance with the rights and freedoms afforded EU individuals under GDPR.

OwnBackup is committed to complying with the EU General Data Protection Regulation (GDPR) and helping our customers comply with "Right of Access", “Right to Rectification” and "Right to Erasure" requests related to GDPR. The attached guide provides information about the remediation process that OwnBackup customers can use in their environments if they receive GDPR-related requests from EU Data Subjects and need to apply them to their OwnBackup backups and archives. As a data processor, OwnBackup seeks to ensure Controllers have the tools needed to facilitate Data Subject Requests within their OwnBackup backups and archives.

Yes, we keep log and usage data across all areas of the service and actively monitor for security anomalies.

The preferred way to report a suspected security breach is via the [email protected] email address. Incoming email is forwarded to the team in charge of security and incident response at OwnBackup who are monitoring emails 24/7. Once received, OwnBackup will commence a prompt investigation of the report by following the Incident Response plan. For additional information, please visit OwnBackup security page.

Here is a step by step example of how to run this scenario and find the field changes on the records via sample data. 1. Click on the backup in question (either from the Smart Alert report or via the Dashboard/Backup History) 2. Find the object in question (in this case Accounts) and select "Start a Compare job..." 3. When the compare job completes, select "show changes" 4. Navigate the object's columns from left to right to find the fields which show changes and see what those are. If needed, a Restore job can be initiated directly from this step as well for your convenience.

OwnBackup can backup Salesforce's weekly exports. This is done by adding Weekly exports as an additional service. What can I do with this type of service? The use case for Weekly Exports is to be able to run Compare jobs between this service and any other service.

You can schedule the backup service start time through the Options page: At the middle of the page, you’ll see an option to edit the Start Backups time. Also – Please make sure that your timezone is configured correctly. At the top of the page, click the down arrow next to your username ? Click on Edit Profile ? Edit your Time Zone. Lastly, please be aware that you can use the "Force backup now" option to initiate a backup on demand at any time.

Yes, this can be provided.

The process is as follows: 1. After refreshing the Sandbox you should reauthenticate your user 2. A new Backup service will be created 3. You need to Archive the old Backup Services (from the Options Menu) * Please note that this process applies only to Sandbox environments.

In order for OwnBackup for Salesforce to successfully take daily snapshots of your Salesforce data and metadata, a valid Salesforce admin user is required both for the initial authentication as well as on ongoing basis to enable the daily backups to run. It appears that the Salesforce admin user that was utilized to authenticate the OwnBackup for Salesforce data or metadata service lacks the “Modify All Data” permission. In order to enable OwnBackup to resume properly backing up the data and metadata services, It is necessary to add the "Modify All Data" permission to the authenticated user.

Password changes in salesforce do not affect OwnBackup. OwnBackup uses a security token provided through OAuth which does not change when the password changes.

In order for OwnBackup for Salesforce to successfully take daily snapshots of your Salesforce data and metadata, a valid Salesforce admin user is required both for the initial authentication as well as on ongoing basis to enable the daily backups to run. In the event that you deactivated the Salesforce admin account used for initial authentication, then you will need to re-authenticate the relevant service(s) with an active Salesforce admin user. Please login to OwnBackup.com, click on the failing backup service(s), then click "Re-authenticate Service" and follow the on-screen instructions. Be sure to authenticate using an admin user that has "Modify All Data" permissions in order to enable the backups to work properly.

Yes, OwnBackup has the ability to shut-down all the servers and storage in case of a breach. Having said that, this is an unlikely scenario that will only be executed in very rare instances.

Yes, OwnBackup supports both 2-factor authentication and IP-based restriction per account.

Follow these steps to setup IP Address restrictions in the OwnBackup web application: Click on your username > Account Settings Go to the “IP Restrictions” Tab and enter your own IP Address first so you don’t lose access to the application. You must enter a subnet Mask which you can calculate here if you don’t know it: http://www.aboutmyip.com/ Click “Add Network” and add any additional IP Addresses from which you would like your users to access the application. Click the “Enable IP restrictions” check box.

APP1 - US Sign up Log in HIPAA Compliant Sign up Log in EMEA1 - EU Sign up Log in Canada Sign up Log in US Government Sign up Log in AU1 - Australia Sign up Log in

Clients may inadvertently convert leads prior to their qualification and wish to restore them to their previous status. Unfortunately, Salesforce will not allow users to restore leads, and users are left with unwanted Accounts, Contacts, and Opportunities. With OwnBackup, there is a simple workaround to get those leads back to the previous status. Please follow the steps below: Ensure the leads are backed up prior to conversion. Back up data after conversions. Delete the Accounts, Contacts and Opportunities created by the lead conversion. Delete Converted Leads using the Mass Delete Option. (Filter on Converted equals True) Empty the Salesforce Recycle Bin Force another Backup of your Salesforce Org Restore Lead records from the OwnBackup snapshot created prior to conversion.

We will be charged a foreign transaction fee that we will add on to the invoice. And there are different wire instructions. This is different for every bank, and it’s not something we will know in advance. Therefore we generally want to avoid foreign

One of the important uses cases for backup is in case you decide to leave salesforce, or in case salesforce goes down. You don't want to have to depend on them to access your backups. If you're managing backups for multiple orgs you'll have to use log in and out multiple times. With OwnBackup you can manage all of your backups in a single pain of glass Eventually you're going to hit your limit on custom tabs and you don't want to waste tabs on apps that you might not use very often It is easier to control user access to an external web app

Use SQL statements to return a collection of records that match your criteria. Filter all Account records where the ‘IsPartner’ field is checked: isPartner = ‘true’ Note that the IsPartner field on the Account object will be available only in Orgs where partner relationship management (partner portal) is enabled. Only keep records that have two specific Record Types: RecordTypeId in (‘01235000001BJrlAAW’, ‘01215000001BJrLAAW’) Only keep records that their name field contains the word ‘acme’: Name LIKE ‘%acme%’ Only keep records where a custom field (i.e., ‘Value__c’) is empty: Value__c = ‘’ Only keep records that have a value between 2 values (i.e., between 100 and 200): cast(Value__c as integer) > 100 AND cast(Value__c as integer) 15 AND cast(Width as integer) = 10 Keep records that do not match: Country != ‘USA’ Replicate Accounts based on a checkbox and bring the parent account of those accounts: WHERE CopyToDev__c = ‘true’ OR Id IN (SELECT ParentId FROM Account WHERE CopyToDev__c = ‘true’) Only keep records that were created on a specific date (i.e. November 27, 2017): CreatedDate = ‘2017-11-27’ Only keep records that were NOT created on a specific date: CreatedDate != ‘2017-11-27’ Find all records added after a specific date: CreatedDate > '2019-09-16T00:00:00.000Z' Note: that you will need to update the date above to whichever date is applicable. Replicate a subset of record for each RecordType, for example, 5 records of each of my 3 Accounts RecordType Id IN (SELECT Id FROM Account WHERE RecordTypeId=‘A’ LIMIT 5) OR Id IN (SELECT Id FROM Account WHERE RecordTypeId=‘B’ LIMIT 5) OR Id IN (SELECT Id FROM Account WHERE RecordTypeId=‘C’ LIMIT 5) Replicate a subset of records where we have 2 Parents and related Junction Object To illustrate that example, let’s consider we have Account and Survey as a Parent object and an object called Survey_Answer that is our Junction Object. On the Replicate Job, select Account and Survey Click on the gear next to Account and select a subset of date you would like Click on the gear next to the Parent Object Survey and run the following query: Id in (SELECT Survey__c FROM Account$Survey_Answer__c) Click on the gear of Survey_Answer (Under the object Survey) and run the query: Id in (Select Id from Account$Survey_Answer__c) Comparison Operators = Equals != Not equals Greater than >= Greater than or equal to LIKE Like IN In NOT IN Not In Considerations and Limitations Field names are case-insensitive, so (IsPartner = ispartner) When using the ‘IN’ operator with record IDs, you must use the 18-char version (not the 15 char) When using the ‘LIKE’ operator with records IDs, you can use the 15-char format, because this looks for a partial match The ‘%%’ operator is case insensitive

Build vs. Buy Analysis: Building your own backup solution has many hidden costs that you should take into consideration Implementing auto-discover to support custom objects and fields Keeping up with new API versions Implementing a notification system that alerts when a backup fails or completes with errors Troubleshooting backup failures and errors Making sure that the backup is efficient in terms of runtime and consumption Maintaining all of this code Maintaining the on-premise storage and backup files Opportunity cost: Focus your energies on your core business, rather than developing a backup and restore tool - that’s why you moved to the cloud to begin with. Restore - How would you recover from your backed up data? How will you identify the changes or deletions across your backups? (assuming you have many custom objects and applications, and a lot of data, this could be tricky to do). Will your restore strategy work with parent-child relationships (resulting from cascade-delete)? Given that you can’t set a record’s ID via the Salesforce APIs/tools, and relationships are based on the record ID, this can be very complex. How granular will your restore tool be? would it support bulk updates and inserts? will you be able to easily extract only the corruption that had started and ended last month without overwriting all the unaffected data? would it support metadata?

Ensure that you have added an OwnBackup for Salesforce service for both your production and sandbox environments. Verify that at least 1 backup has completed successfully for each service. Next, in OwnBackup's "Replicate" tab, use the "Full Org", "Full Org with Delete" or "Multiple Parent Objects" methods to replicate data onto a Sandbox. Select which service you would like to search within & click "Next". Start by selecting one of the options listed above. When selecting "Multiple Parent Objects", keep in mind to select the parent objects to be replicated as well as selecting the hierarchy depth to control the number of related records to be replicated with the parent objects. Select a backup date to pull data from within the backups from. Finally, select the sandbox to be the destination org. Follow the on-screen instructions which will allow you to preview the data that, upon your approval, will be replicated to the destination environment. Note: that differing size limits between production and sandbox environments may impact the success of the cross-environment replication operation.

You may wish to try one of the following CSV viewer tools: http://delimitware.com/ (there's a free-trial version) Open office has an excel like tool called 'Calc' https://www.openoffice.org/download/ UltraEdit It won't display the CSV in 'tabular' fashion, but it should allow you to search for the OwnerID, and copy paste the record to a separate file. Notepad++

Data Anonymization OwnBackup supports automatic data anonymization capabilities as part of the Sandbox Seeding tool. This capability allows users to automatically anonymize several fields that may contain private/sensitive/identifiable information. OwnBackup will anonymize fields in the selected sObject(s) based on their Type, MaskType or Label and will use the appropriate anonymization functions to match that fields’ value format. For example, email type fields will be anonymized to values in email format. Technical Notes Retaining Distribution and Data Integrity In order to maximize the data quality, a given value that is anonymized will be anonymized to the same value when encountered again on the same field type in the same Replicate Job, thus preserving the original distribution of values & data integrity. For example, if in a certain Replicate Job, the Country field value was originally ‘Cuba’ and was anonymized to ‘Peru’, any future occurrences of ‘Cuba’ in a Country field for the duration of that Replication Job will remain ‘Peru’. Blank Values The following values are never anonymized: Blank (empty string), NA, [not provided] Field Type Identification As Salesforce’s schema does not provide identification for all fields containing sensitive information, OwnBackup will use the following process to determine which fields to anonymize (and the appropriate matching anonymization functions): Address fields: Street, City, State, Country, and Postal Code fields will be determined by their Label. Names: Account Name field will use a company name anonymization. Contact Name field will be anonymized via a person names anonymization function. Other Name fields will be anonymized as regular strings. FirstName and LastName field names will be anonymized accordingly. Personal identifiable information: Email, Phone and URL fields are identified by their corresponding field types. National ID numbers: Social Security Number, Social Insurance Number, National Insurance Number are identified via the “MaskType” property. The ‘all’ MaskType field types are anonymized via the SIN anonymization function. Financial Credit card fields are identified via the ‘creditCard’ MaskType. Other: All encrypted string field types are also anonymized as string fields, according to their original length. Usage: Once the Replicate Job Preview tree is ready, click the ‘advanced option’ icon next to a parent sObject element. Next, check the box next to the ‘Anonymize’ option. The records in the selected step (for example 10 Tasks associated with Contacts) will be anonymized upon clicking “Update Preview”. Click “Start Replicate” to push all previewed data directly to the destination Org. Field History Tracking: When using the OwnBackup Anonymization tool, OwnBackup will be able to anonymize the records in the selected Salesforce Sandbox. This does not manipulate the Field History Tracking in Salesforce as History tables are Read-Only. If Anonymizing data in a Sandbox with OwnBackup, it is recommended to disable Field History Tracking and re-enabling if required. You can turn off field-history tracking from the object’s management settings. Below is a Salesforce Article on how to disable Field History Tracking in your Sandbox. https://help.salesforce.com/articleView?id=tracking_field_history_disabling.htm&type=5

Putting aside the costs and laboriousness associated with maintaining a local server, storage and assuring the backups are successful, we recommend your team address the following relevant questions in order to determine whether they can rely on this approach for backup and restore: How frequently is the data pulled from Salesforce? How frequently is the local database backed up? What is the retention policy of those local backups? Does your local database include your Salesforce.com attachments? Does your backup include your Salesforce.com Metadata (e.g., Reports, Layouts, AppexCode, Workflows, Dashboards, etc.)? How would you restore from a user-inflicted Salesforce data loss scenario? Would a potential Salesforce data corruption or deletion propagate to your local database (thus corrupting the local database)? If so, would the restore process then involve an additional step of first restoring a good snapshot from the backup to local database before ultimately restoring from the local database to a Salesforce Org? How long will it take to complete this two-phase restore procedure? Can you easily practice your DR procedure? Does your local database include a sandbox environment for DR testing purposes? How would you restore from a parent->child (cascading delete) scenario? How would you restore your Metadata?

OwnBackup is able to backup the data tables including standard and custom objects. However, it does not support metadata backup. In order for customers with no API access to restore data, they must submit a request to salesforce support to have their APIs temporarily enabled. Please reference this salesforce knowledge article: https://help.salesforce.com/HTViewSolution?id=000005140&language=en_US

Please note that OwnBackup allows you to restore/replicate all data from one org to another, but in regards to metadata, it doesn't support Full metadata restore/replication. In order to clone data & metadata from one org to another, please follow the steps below: Replicate the metadata components via Force.com IDE tool (attached is the "Ownbackup - Metadata Restore with WorkBench" guide) Backup the destination org with the new metadata Replicate all the data by using the Data Replicate tool (attached is the Admin guide for more instructions)

If a cascading deletion has occurred in your Salesforce environment, you will need to run a Data Restore. You may have already used the compare tool or dashboard statistics chart to identify the extent of the data loss. Please see the ‘Compare Tool’ section of this guide for information on how to compare data sets. Follow these instructions to recover the deleted records: Login to your OwnBackup account. Choose the backup service for the org in which the data loss occurred. Click Back Up Now (Note: if you have a backup snapshot from after the data loss incident, you may skip this step). Wait for the backup to complete. Click on the Restore tab, then Data Restore. Select Repair data loss, and the Org that suffered the data loss. Select all of the parent objects where data loss occurred (you can type in the object rather than scrolling to search). Select the two snapshots for Before and After the data loss. The ‘Before’ snapshot will contain the records you want to restore, and the ‘After’ snapshot should be the backup that identifies those records as being ‘Removed’. Select Same environment if restoring these records back into Salesforce. Select Different environment if you want to restore deleted records into a sandbox. Review the details you selected, then click Preview Restore to generate a complete preview. Once the initial processing of the data is complete, you will be presented with additional on-screen instructions. Make sure to disable any workflow rules, validation rules, and triggers in the destination environment that could affect a mass import on the objects you are restoring. You can either restore all deleted records, a subset of records by uploading a custom CSV file, or a subset of records filtered by a SQL where clause. If you modify the CSV, make sure to delete the entire rows you do not want to restore, rather than simply clearing the values from the cells. Save the file in CSV format and UTF-8 encoding. Upload the file to the job in OwnBackup. Check the I have adapted my Salesforce environment for this job box when you are ready, then ‘Resume’.