4 ms·

Seems like a funny policy to not backup production paying customers photos & metadata. Think of all the photos, comments, followers, etc that just got nuked! Se

Seems like a funny policy to not backup production paying customers photos & metadata. Think of all the photos, comments, followers, etc that just got nuked! Seems like they rely on RAID or having multiple copies of the data spread around for disaster recovery. Sure it protects you from a server/raid/hardware failure but when a user/admin does something dumb it can really hurt! Doing a quick google search turns up this gem: Staff - heather says: "When an account is deleted, photos and any metadata associated with account is queued and deleted. If not instantaneous, it's removed within minutes." [1] http://www.flickr.com/help/forum/47365/ http://www.flickr.com/help/forum/47365/

cosmicray 16y ago
How about ... RAID isn't backup. RAID is there for system interruption protection. RAID is there to keep flickr cruising along without interruption. If they delete content from a volume covered by RAID, then all the mirrored copies go poof simultaneously. What you are suggesting is a higher level content management system. Apparently (from the drift of the comments) that is something flickr doesn't want to get involved with.
buro9 16y ago
Yup, sounds like it. They need to learn the mantra: "Replication is not backup, DROP DATABASE replicates pretty well.".
gnaffle 16y ago
It seems like a _very_ good policy from a privacy perspective, if I accidentally uploaded some pictures that I really didn't want online (easy to do with an upload tool pointed at a directory), then I'd feel much more assured if Flickr would tell me that they didn't keep any copies of my pictures floating around "just in case". Of course, deleting a complete account without any means of rectifying it sounds like a very bad idea and shouldn't have been possible. At the very least there should have been red warning signs flashing when the support person deleted a pro account with 4K+ pictures in it.

cosmicray 16y ago

How about ... RAID isn't backup. RAID is there for system interruption protection. RAID is there to keep flickr cruising along without interruption. If they delete content from a volume covered by RAID, then all the mirrored copies go poof simultaneously. What you are suggesting is a higher level content management system. Apparently (from the drift of the comments) that is something flickr doesn't want to get involved with.

buro9 16y ago

Yup, sounds like it. They need to learn the mantra: "Replication is not backup, DROP DATABASE replicates pretty well.".

gnaffle 16y ago

It seems like a _very_ good policy from a privacy perspective, if I accidentally uploaded some pictures that I really didn't want online (easy to do with an upload tool pointed at a directory), then I'd feel much more assured if Flickr would tell me that they didn't keep any copies of my pictures floating around "just in case". Of course, deleting a complete account without any means of rectifying it sounds like a very bad idea and shouldn't have been possible. At the very least there should have been red warning signs flashing when the support person deleted a pro account with 4K+ pictures in it.