crash brought about statistics LOSS’s protracted outage in advance this week precipitated facts loss.

An replace on the corporation’s reputation page dated can also 12, 2016 20:00 UTC says records “written to the NA14 instance between nine:fifty three UTC and 13:29 UTC on may additionally 10, 2016 cannot be restored.”

there may be a tiny ray of sunshine in that assertion, due to the fact previous updates stated information written between 9:fifty three UTC and 14:53 UTC had evaporated. fortunate you, N14 users: you simply were given 84 mins of records back. Now to find the opposite 216 mins’ really worth.

The N14 example that triggered the trouble remains a large number: Salesforce says it “maintains to function in a degraded country” with features inclusive of weekly exports and sandbox replica functionality suspended temporarily.

Salesforce says it is nevertheless looking to determine out precisely what went wrong. For now, it says “a database failure on the NA14 example, which added a file integrity issue in the NA14 database” turned into the perpetrator. there was a backup however it looks like that become incomplete.

whatever the cause of the problem, it appears clean that Salesforce’s recovery point objectives may need to be reviewed.

The agency’s master Subscription settlement (PDF) pledges, at phase three.1, to “use commercially reasonable efforts to make the online services to be had 24 hours a day, 7 days every week” unless acts of God, government motion, natural failures, ISP SNAFUs, civil unrest or DDOS attacks intrude.

At section three.2 the report promises “we are able to maintain administrative, physical, and technical safeguards for safety of the safety, confidentiality and integrity of Your records”.

The sign in suspects folks with sharper prison minds than ours are presently poring over the pleasant print of that report, and Salesforce’s different contracts, to figure out what customers have to do next if their records proves totally irretrievable. ®