wiki | forum | trac | otrs | joomla | tech blog | mailman | bewelcome Branches: test.bw | alpha.bw | www.bw Participate: download | get involved

Ticket #330 (new developer task)

Opened 10 months ago

Last modified 7 months ago

emergency plan, back-up

Reported by: bewelcome@think-future.de Assigned to: philipp hannu
Priority: critical Milestone: unassigned
Component: ServerSetup Version:
Keywords: technical: security, emergency, escalation Cc:
Follow up needed: none Frequently reported: 1
Announce on BW: 0

Description

Hey,

Probably most of you know the story about the reliability and availability of couchsurfing.com

So for BW to be on the safe side, start earliest possible to implement some basic parts of security:

What about backup plans?

What about Load balancing?

Decentralization?

Escalation plans?

Regular backup verification?

Database management? Backup here? Bkp verification?

Infrastructure for learning about drawbacks, failures etc?

Someone explicitely responsible for caring about emergency procedures? Reliable infrastructure for warranting operability of backoffice and contactability of emergency/escalation teams?

... more to come :)

Cheers,

Nils (runia)

Change History

01/16/08 17:58:44 changed by philipp

thanks for the reminder - you got a private message

02/25/08 23:52:44 changed by guaka

  • freq_reported set to 1.
  • show_on_bw changed.

I think this is way too general to leave this bug open.

02/25/08 23:53:32 changed by guaka

  • summary changed from technical background to emergency plan, back-up.

03/04/08 11:55:39 changed by philipp

  • owner set to philipp hannu.
  • type changed from new feature to developer task.
  • component changed from FrameWork to ServerSetup.

03/26/08 23:00:30 changed by feuerdaemon

  • milestone changed from unassigned to BigPicture.

04/23/08 11:50:39 changed by philipp

  • milestone changed from BigPicture to unassigned.

Milestone BigPicture? deleted

Trac Customization: trac stylesheet
SourceForge.net Logo