Telkom sabotage rumours

jes

jes

MyBroadband Alumnus
Joined
Nov 11, 2009
Messages
11,992
Reaction score
123
Telkom sabotage rumours

Telkom dismisses speculation which suggests that there may be something sinister behind a crash in its most vital business system
 
Last edited:
new telecoms minister was the spooks minister
coincidence ...
 
The system crashed was blamed on a radial server failure, with the backup server also failing. This is unusual, especially because the backup server is not hosted in the same location.
Click to expand...

Ouch.

I'm interested to know how said server failed. Was it overheating, RAID failure (quite common with RAID5 - more than one HDD in array failed), virus/trojan attack, rookie mistake, or simply a pissed-off sysadmin?
 
For the record, I won't attempt to sabotage a company's servers/infrastructure no matter how badly they treat me. It just is not worth it at the end of the day.
 
The_Librarian said:
Ouch.

I'm interested to know how said server failed. Was it overheating, RAID failure (quite common with RAID5 - more than one HDD in array failed), virus/trojan attack, rookie mistake, or simply a pissed-off sysadmin?
Click to expand...

Imagine that. Oh man that would be the funniest IT rage ever.
 
I've got an idea! Why don't we digitize and automate all the critical processes that keep society running!
 
They can deny all they want but this kind of failure (both Live site& DR site) is to coincidental. Also shows the kind of people who work at hellkom. @ the same time maybe if you betray a man's loyalty you can expect anything from there though this was extreme
 
kianm said:
They can deny all they want but this kind of failure (both Live site& DR site) is to coincidental. Also shows the kind of people who work at hellkom. @ the same time maybe if you betray a man's loyalty you can expect anything from there though this was extreme
Click to expand...

I think you'll find a lot of places with poor process where a DR system may exist but hasn't been properly tested and so when it's actually required it doesn't do what's needed. Plenty of people who think they have backups, but unless they've tried a proper restore it's worthless.

(examples for their DR issues could be: 1. not including all the services needed on the DR site, 2. a failure in the replication system that allowed the DR site to get out of date and no one noticed, 3. synchronization of data but not keeping the application versions in sync, that means for a few initial tests it would work but if a major version update came out that changed data structures it fails)
 
Last edited:
km2 said:
I think you'll find a lot of places with poor process where a DR system may exist but hasn't been properly tested and so when it's actually required it doesn't do what's needed. Plenty of people who think they have backups, but unless they've tried a proper restore it's worthless.

(examples for their DR issues could be: 1. not including all the services needed on the DR site, 2. a failure in the replication system that allowed the DR site to get out of date and no one noticed, 3. synchronization of data but not keeping the application versions in sync, that means for a few initial tests it would work but if a major version update came out that changed data structures it fails)
Click to expand...

That's a strong point there, lack of continous testing of backups and DR sites might have been their shortcoming. But I wonder if the intial failure was natural or 'man-made' lol :D
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X