This financial firm needs top-notch operational IT performance and is willing to pay for it, reports a pilot fish in the know.
"To that end, they purchased a solid-state drive SAN for their SQL server data stores," fish says. "Following what any database administrator would consider best practices, they were doing their backups locally -- for speed -- and then copying the backup to a separate storage device.
"When they moved to the SSD SAN, the backups began failing immediately after running.
"They opened support cases with Microsoft and the SAN vendor that got gradually escalated up the ladders until it was the top engineers and developers at both companies talking to each other.
"After weeks of analysis, they determined that the backup completed so quickly that SQL Server hadn't had time to finish some of its background tasks, so it assumed that the rapid completion actually indicated a failure.
"The firm moved its backups to a slower storage device while the vendor engineers wrote a custom patch for them."
Hurry up and write to Sharky. Send me your true tale of IT life at email@example.com. You'll score a sharp Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.
Get your daily dose of out-takes from the IT Theater of the Absurd delivered directly to your Inbox. Subscribe now to the Daily Shark Newsletter.