Recurly's Backup Mess Takes Days to Clean Up

A cascading hardware outage struck subscription payment provider Recurly last week, and that started a long example in how not to manage critical infrastructure. From the article: "Last Monday, the payment provider suffered an intermittent hardware failure, which prevented the company from processing either payments or refunds. The company says it serves over 1,000 customers, including Adobe, BrightCove, and Fox News Radio, processing recurring payments for subscriptions. By Friday, the company still hadn’t completely straightened out the mess, providing updates to customers using payment gateways such as Authorize.net and LinkPoint/First Data."

Reminds me of Authorize.net

[Mr. Kinky]

This case reminds me of our payment processor Authorize.net in 2009, when a fire took down the whole network and infrastructure for many days. It was only solved when one of the guys over at Authorize.net literally

Re:Reminds me of Authorize.net

[MetalliQaZ]

He would have finished the story but he had a cascading hardware failure that took out his network...

I would've been leery of...

[Anonymous Coward]

...a service provider named Recurly in the first place.

Same goes for any provider named Relarry, Remoe or Reshemp either for that matter.

Re:No backups

[Anonymous Coward]

They should have used RAID.