News for hackers. Stuff that matters.
Re:24 year old student lights match: Europe versus Facebook by kiiski on Wednesday October 19, 2011 @05:46AM (#3129416)
But if you delete something from the primary database, then I would assume it will eventually get deleted from others too. While it might never be intentionally deleted from backups, the backups will be overwritten with newer ones eventually.

(I'm talking about facebook here, not about the web in general)

Re:24 year old student lights match: Europe versus Facebook by dredmorbius on Wednesday October 19, 2011 @08:29PM (#3132804)
That depends on how the databases are architected and tiered.

If they're proper slaves / replications of one another, then yes.

If, as is commonly the case especially for marketing data, periodic cuts or dumps of the data are made at various points in time, and there's no mechanism for propagating deletions throughout the chain, then no, you're not assured of deletion. This isn't likely to be the case for a site's primary database, but could very well be the case for derived datasets. I can think of instances with, say, credit bureau reports in which erroneous data must be repeatedly deleted because it keeps getting re-injected into the system.

Facebook's September, 2010 outage in which cached data were being re-injected into the system exhibited a similar problem of cache coherence. http://www.facebook.com/note.php?note_id=431441338919

Re:24 year old student lights match: Europe versus Facebook by 0x12 on Wednesday October 19, 2011 @02:40PM (#3131452)
And at a minimum it should not longer be trivially accessible to the company via their 'normal' procedures.