Colin Law wrote in post #1021900: > On 14 September 2011 12:39, Rajeev Kannav Sharma > <[email protected]> wrote: >> My mate did rake db:drop on producation , can any please help urgently any >> possible solution? > > Other than that I think you will have to restore from backup. If you > have not got one then possibly the web site host does.
Oh, and while you're at it... Fire your mate! :-) If you are able to recover from this, I'm guessing your next task is to implement a backup strategy. Remember, having one copy is not a sufficient backup policy. I don't consider data to be "backed up" until there is at minimum two full backups (the original, plus one local backup, plus 1 off-site backup). I created two command line scripts for my production server. One runs on the server using cron to perform a local mysqldump as a local backup. The second one runs under launchd on my main development Mac, which uses secure copy (scp) to download the backup file that was generated by the script that runs on the server. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
