Skip to main content

Salesforce writes up it's side of the story



Well it's pretty easy to blame your database vendor and assume that errors *just* occur on the system. When you say the cluster crashed, something DID go wrong!


The root cause of the intermittent access was a complex error in the database cluster that was not previously known to us or our database vendor. It surprised us because we had not made any changes to our system. The error just appeared.


and what steps are the folks taking?


s we previously announced to you, we are half way through the roll out of Mirrorforce, our new data center architecture. Contrary to some reports, the full deployment of Mirrorforce, which will happen in Q1, would not have prevented this problem. Mirrorforce is a standby, mirrored, replicated data center. If we lost the West Coast data center because of a major hardware failure, a natural or man-made disaster, or a terrorist attack, the new data center would automatically take over.

We are confident that once fully implemented, Mirrorforce will represent long term value to our customers. But an extremely rare, undocumented software issue is not something that even the most robust systems can prevent 100% of the time. No system has 100% performance, and no software is bug free.


Anyways I know that the DBA's are busy but I'm sure they're also happy to have finally got it heard. Read the rest of the statement here.

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more