Fortunately it wasn't THAT drastic. Everything was back up in about 10 minutes but there is nothing like the sinking feeling brought on by realizing you screwed up the production server.
Josh Patten Assistant Network Administrator Brazos County IT Dept. (979) 361-4676 On 7/22/2010 12:54 PM, Tony Graziano wrote: > "... database delete..." > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > ----- Original Message ----- > From: [email protected] > <[email protected]> > To: [email protected]<[email protected]> > Sent: Thu Jul 22 13:45:49 2010 > Subject: [sipx-users] A word of the wise.... > > Just in case it happens to someone else: When entering in commands via > SSH on a test sipX server make sure that you are typing those commands > in the test servers SSH session, not the production servers SSH session. > > I'll leave it to your imagination to figure out why I'm posting this. > _______________________________________________ > sipx-users mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
