FAQs

FAQs

DataBakup is a simple data backup & recovery solution tailor-made for all Salesforce customers that support Sales Cloud, Service Cloud, and Custom solutions.

DataBakup can be used by Salesforce customers to overcome data loss challenges arising from any human or application error to not only safeguard your data but also ensure it is highly secured within your cloud infrastructure.

Yes, you can schedule the backup job on an hourly, daily, or weekly basis.

Simply schedule your backup or take an on-demand backup whenever required. Also, the solution supports full & incremental backup.

Yes. You can restore the backup data whenever you want.

To know more about the pricing details, please get in touch with us.

DataBakup offers two types of data backup options to the Salesforce customers: Manual data backup & Scheduled data backup. 

Yes, the data backup function is object-wise. In order to perform a full org data backup, while configuring all the objects in the org should be configured and set as active. Now, whenever the backup or restore process runs, DataBakup will take care of all objects itself.

No, when using DataBakup, each record is backed up separately. Therefore it’s a single object backup mechanism. 

No, DataBakup supports the back up of the entire object’s data so there is no need to apply any type of filter criteria. 

In DataBakup, the batch process to backup the data happens outside of the Salesforce ecosystem, so there is no impact of Salesforce governance limit on the backup process.

Yes, DataBakup supports the backup of Custom Salesforce objects.

Full Backup: When performing a full backup, the application backs up the entire data of a particular object.

Differential Backup: In differential backup, only the updated or new data of a particular object is backed up. 

DataBakup is an admin-only application, but the related list component on the page layout of a particular object helps non-admin users also to recover a particular record back to Salesforce.

The backup data can be restored back manually, either at the object level or record level.

When using DataBakup, the data is backed up to AWS S3 storage in flat-file format (.csv). 

The backup data is stored in flat-file format and these files are stored in AWS S3 bucket only.

The schedule data backup runs on all the objects whose configuration is set to Active.

No, in case there are no new changes in the data the differential data backup will not pull any data.

No, in DataBakup there is no limit regarding the number of objects that can be backed up.

The AWS S3 bucket will have two different folders, one created with the name Full Backup and the other with the name Differential Backup. Under these folders, there will be multiple folders created per object.

Backup data is just the copy of the original data, the original still resides in Salesforce data storage on which the standard Salesforce reporting can still be performed. 

Yes. Every time a backup job is completed, the user will receive an email notification for the same. The user will also have the option of unsubscribing to this service. 

Using the related list component in DataBakup, the backup data can be viewed and accessed alongside the live Salesforce data.

Even when the backup data is restored, a copy of the backup data is always present in the backup storage. 

Upon recovery, the system field data will be populated with the details of the current user who is restoring the process. DataBakup does not update the System field data in any manner while restoring.

Only the object whose configuration is set as ‘active’, after clicking the Active button, will be backed up in the manual or scheduled backup process. At any time, users can change the configuration to ‘inactive’ by clicking the De-active button. 

There is no metadata syncing process running in DataBakup. All the fields will be backed up when the data backup process is run because the application does not maintain any database to store the data.

In case the backup process fails due to any reason, DataBakup will notify the user with an error message. On the next run if the issue is fixed, the application will successfully backup the data.