IT Troubleshooting – Part 3.

IT Troubleshooting

Now that you’ve learned all that our CEO can teach you about it  troubleshooting basics, it’s time to put you to the test. Eugene has assembled a set of questions for you, with the answers following. So, grab a pen and paper and and give the questionnaire a whirl!  We hope you’ve been paying attention, because this teacher doesn’t allow for any sleeping in class!

Questions

 

1. Just before rebooting a server, what are some of the critical things you should think about?

2. Name at least three important considerations with data backups?

3. Apart from Google, Stack Exchange and community forums, name at least three methods of how you can increase your knowledge?

4. Place the following terms in the correct order:

A. Establish if this pattern is intermittent

B. Recreate the problem in a lab environment

C. Simulate the problem

D. Find a workaround

E. Catch problems when they happen

F. Check the log file

G. Establish a pattern

H. Always find out exactly the first time the problem happened

5. Is it better to escalate or to solve the problem yourself?

6. What does the following MikroTik command do?

/system logging action set memory-lines=20000

7. What is a possible disadvantage of the command mentioned in question 6?

8. What Linux command line tool(s) can be used to effectively query a busy Linux log file, for example the log file of a mail server?

 


 

Answers

 

1. Just before rebooting a server, what are some of the critical things you should think about?

  • What is the worst case scenario if the server does not restart?
  • How valid are the backups?
  • When is the last time any of the backups were restored?
  • What redundancy do we have in place if the backups don’t restore?
  • How long will it take to restore the backup?
  • What is the business impact of the server not restarting?

2. Name at least three important considerations with data backups?

  • Without restoration testing you will never know if your backups are good. Just backing up is not good enough.
  • Backups need to be maintained on a daily basis. Check every day to see if the backup succeeded.
  • Restoration can take long if the data set is big. Plan for this.
  • Frequency of backups, e.g. you might lose 24 hours or more of data if you restore an old backup.
  • Know where your data is. Just because you’re backing up My Documents doesn’t mean that your email will also be backed up.

3. Apart from Google, Stack Exchange and community forums, name at least three methods of how you can increase your knowledge?

  • Self-study
  • CBT Nuggets (computer based training)
  • Instructor led courses
  • Speaking to your colleagues (teamwork)
  • Finding other specialists in the field
  • Experience and practice
  • Books / ebooks
  • Asking suppliers. They supply products and they normally have experts.
  • Mailing lists

4. Place the following terms in the correct order:

This is not an exact sequence but doing certain things before others is important.

E, H, F, C, G, A, B, D

Also be aware of when you should escalate. Don’t try to be a hero. You want to escalate AFTER you’ve done your homework.

5. Is it better to escalate or to solve the problem yourself?

Depends on the situation but in some environments YES, ALWAYS COMMUNICATE AND ESCALATE. Fast turnaround time is critical in today’s business environment. Also by escalating quickly you might learn something quicker than trying to do it yourself.

6. What does the following MikroTik command do?

Increases amount of information logged on console.

7. What is a possible disadvantage of the command mentioned in question 6?

Increased RAM usage.

8. What Linux command line tool(s) can be used to effectively query a busy Linux log file, for example the log file of a mail server?

tail -f in combination with egrep

tail 50%

tail + grep = 75% = grep only one thing

tail + egrep = 100% (egrep more than one thing, conditional OR)

You need to have answered both tail and egrep to get 100% on this question.

 

That concludes it troubleshooting part 3, we hope you found this both insightful and educating. If there is any topic you wish for our CEO to take on next give us a call on 021 880 2228 or drop us a comment below!

 

Snowball – Connecting Everything