Yes, both cloud and/or on-premise backup storage options are offered. We have the ONLY product that offers both on-premise and Cloud deployment for backup and recovery. There is no surcharge for Cloud storage.
For the transport of data between SFDC and storage location, the Salesforce Partner API uses SSL and is approved by Salesforce.com. We are a certified product, and have been since 2005. There are many DBMS’s that offer SSL SQL connections.
For data at rest, if you chose the on-premise deployment, the database security is up to you. In our Cloud offering, the back end database is the encrypted Enterprise version of SQL Server on a server with no public access in an IBM data center. You do not have any access to even your own data in our Cloud offering.
As far as the auditability of security, if you use the on-premise deployment, you own the security. You can lock down your server so you have to log in to the server to access even the web user interface. If you use our Cloud deployment option, you have no access to anything. Recovery is done via a webinar in consultative mode where our professional services team does the actual recovery.
Yes. The only thing you’ll have to do is provide the URL of the Sandbox instance in the configuration. Product pricing is based on Production Salesforce orgs, so this is not even a factor.
Relational Junction for Salesforce backs up and will restore typically any Salesforce object that is allowed by the Salesforce API and security rules. You cannot create certain objects in Salesforce, such as AccountHistory, because it’s just not allowed by the Salesforce application. There are no issues with handling binary data, such as Attachments an Documents and ContentVersion.
It would be easier to tell you what Relational Junction for Salesforce doesn’t copy. This is a list of current objects that cannot be backed up because they are not “real” objects or have specific technical limitations of the API in copying records without some sort of specific qualifier.
ActivityHistory AggregateResult AssetTokenEvent AttachedContentDocument CollaborationGroupRecord CombinedAttachment ContentDocumentLink ContentFolderItem ContentFolderMember DashBoardComponent DataStatistics DatacloudAddress DatacloudCompany DatacloudContact DatacloudDandBCompany EmailStatus EntityParticle FeedLike FeedTrackedChange FieldDefinition FlexQueueItem FolderedContentDocument IdeaComment ListViewChartInstance LookedUpFromActivity Name NoteAndAttachment OpenActivity OwnedContentDocument OwnerChangeOptionInfo PicklistValueInfo PlatformAction ProcessInstanceHistory RelationshipDomain RelationshipInfo SearchLayout UserEntityAccess UserFieldAccess UserProfileFeed UserRecordAccess Vote
The Cloud deployment option — where Sesame manages the service in our Cloud — offers no data access to you for reporting. This would be a security concern, as well as causing performance degradation in our multi-tenant environments.
The on-premise deployment option gives you a relational database with indexed relationship fields for all table joins. You can use any Business Intelligence or reporting product. You can run this on your on-premise servers, Amazon AWS, or anywhere.
Yes, Windows Scheduler or UNIX cron or any other job scheduler is normally used to initiate replication or integration jobs. The web client is used to set up and test the job, but is not for normal production job scheduling. The command line interface is very easy to run from any scheduling system.