Mission critial data is stored in Salesforce. It just makes sense to keep a hot copy of the Salesforce data!
Keep a hot copy of Salesforce available for disaster recovery.
The question is: Are you ready to recover from a data disaster?
The CopyStorm database is not just for disaster recovery. Capstorm customers use their hot copy of Saleforce data! Here are a few examples:
Data loss and damage are a real concern. The integrity of the data in Salesforce depends on people.
Be empowered with an accessible, local, and hot copy of your Salesforce database .
Capstorm customers use their hot copy of Saleforce data! Here are a few examples:
SQLServer, Oracle, PostgreSQL, MySQL, and H2 are supported.
CopyStorm runs on Windows, Mac, and Linux.
The term "restore" often means creating CSV files and asking you to apply those files to Salesforce using a dataloader. Capstorm's Restore restores multiple tables and the relationships between records in a single pass without user intervention. For example, to restore a set of Accounts and their related Contacts, Attachments, Notes, Opportunities, Cases, etc. requires no intermediate action by a user after the restore operation is started! Yes, foreign keys are managed! Yes, related list records can be automatically restored! Yes, relationships are preserved!
A Salesforce backup is always a good idea. Using your Salesforce backup to super-charge your developer sandboxes is an even better idea!
From a CopyStorm/Restore customer 12/9/2014 - "Fantastic! I have already used the product to selectively restore data to our developer sandbox, so that our web developer can harmlessly test integration techiques with our new in-development Salesforce-integrated website. The product performed flawlessly!"
From CopyStorm/Restore customer Jeff Bauer - "...the product really hides the gory details and relinks things. I'm loving it."
How is "Restore" defined by the solution?
Restore may mean creating CSV files and then expecting you to apply them to Salesforce using a dataloader. Yikes!
Capstorm's CopyStorm/Restore restores multiple tables and the relationships between records in a single pass without user intervention!
Is the backup useful for anything but restoring?
CopyStorm is a full relational database.
Does the solution require intervention when the Salesforce structure changes?
CopyStorm automatically adjusts to all schema changes.
Can the production backup be used to load sandboxes?
CopyStorm/Restore can be trusted because you will use it often to load sandboxes with targeted production data.