LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 12-26-2004, 07:36 PM   #16
elfoozo
Member
 
Registered: Feb 2004
Location: MI
Distribution: debian unstable
Posts: 252

Rep: Reputation: 32

Ask many questions of the former admin - how they handled disaster recovery. Not just tape backup rotations either. Think up some scenarios and find out how they restored data that got corrupt or deleted. This could be really handy should it be something that happened routinely. And make sure the backup strategy worked. You don't want something going amuck 2 weeks after their gone and have no wait to keep the systems maintained while you're still sorting the systems out.
And be sure to get any backup software administrator or root passwords and any database passwords since they may not be the same as the regular root password.

Last edited by elfoozo; 12-26-2004 at 09:40 PM.
 
Old 12-26-2004, 08:34 PM   #17
mrcheeks
Senior Member
 
Registered: Mar 2004
Location: far enough
Distribution: OS X 10.6.7
Posts: 1,690

Rep: Reputation: 50
i've been a sysadmin few months ago and all i can say is :

- if you were not sure about all what he was talking about, it is not terrible. He might have talked about lots of things you never had to messed with. Focus on what installed tools/servers are intented to do. If you find better and don't have time move it to something else(don't change before having well tested the configuration of a testing pc).

- like one said backup passwords(keep a copy of all of them on a pc and at another location).
Often someone will ask you for a password, or you will need one that you have forgotten. If you can't find the passwords, there is a problem.

- make lots of backups with amanda, another backup server or cron scripts.

- look at your server logs often

- sometimes you don't know really what to do, take time to read the documentation about apache, mysql, etc... Use quick tutorials first and if it is not enough try the official documentation.

- if there is a problem, don't try to bring the "BEST" solution if it is very long and tough, make it work first and fast, to keep the network clients quiet. Afterwards apply the most suited configuration when you have time(find that time to do it or it will come to you after)

The documentation is really important. You will become a lazzy admin if you know it well, often you'll feel like there aren't much too do except when a client has a problem.
 
Old 12-27-2004, 01:08 PM   #18
dna9
Member
 
Registered: Nov 2004
Location: Colorado
Distribution: Ubuntu mostly...
Posts: 66

Rep: Reputation: 18
Talking Re: my first job as a network administrator - need advices

Quote:
Originally posted by ddaas

Please, give me some tips ! Where do I start from? What must be my first steps? What are most important first things I must do as the new admin? What are the most important things that I have to have clear in my mind ?
=====================================================================

RUN - RUN FOR THE HILLS!!!

hehe, but seriously take the "nestea plunge" and dig in and have fun. but, i agree with some of the other posts about "if it ain't broke - then don't fix it" theory...

<=== READ - READ ALOT!
 
Old 12-29-2004, 10:09 AM   #19
SteveK1979
Member
 
Registered: Feb 2004
Location: UK
Distribution: RHEL5/6, Solaris 10/11, NetBSD, OpenBSD, FreeBSD, MacOS
Posts: 221

Rep: Reputation: 40
Quote:
Originally posted by elfoozo
Ask many questions of the former admin - how they handled disaster recovery. Not just tape backup rotations either. Think up some scenarios and find out how they restored data that got corrupt or deleted. This could be really handy should it be something that happened routinely. And make sure the backup strategy worked. You don't want something going amuck 2 weeks after their gone and have no wait to keep the systems maintained while you're still sorting the systems out.
And be sure to get any backup software administrator or root passwords and any database passwords since they may not be the same as the regular root password.
And if you get chance, it's also a very good idea to test that the backups actually work!

We had the rather unenviable task of discovering that only the first 2G of a file system was being backed up when it came to restore after an 'incident'.....not fun

Cheers,

Steve
 
Old 12-30-2004, 06:26 AM   #20
Timur Sakayev
LQ Newbie
 
Registered: Dec 2004
Location: Fairfield, CT
Distribution: Mandrake, SUSE, RH
Posts: 21

Rep: Reputation: 15
similar situation

Well, at least the guy is helping you - i found myself in a similar situation a year ago when my boss quit on me without warning - just walked out one day and never came back - only e-mailed passwords ("password" for root on the ssh server that faces the world :-( ) a week later.

In any case, you already read - backup everything, but it's worth saying again - backup, backup, backup again. See if you can make an off-site backup for a disaster recovery. these days DVDs are cheap - it's well worth burning a bunch of them at the end of the month. And definitely test the backups. While the theory of "don't fix it if it is not broken" works fine at the beginning, but you do want to read up and find out more about the areas that seem to be unknown. I applied "if it's not broken don't fix it" concept to DNS server year ago, and now I am having all sorts of fun trying to figure out how the hell everything had been working.

Good luck!
 
Old 01-28-2005, 06:09 AM   #21
RomanG
Member
 
Registered: Jan 2005
Location: Russia, Kazan
Distribution: Mandrake 10.2, RedHat sometimes..
Posts: 110

Rep: Reputation: 15
I'm only a newby in Linux system administration, but maybe my advice will also help you. It concerns technology of backuping. I'm a [u]very very[u] lazy. I always try the ways not to do the work that computer can. In organization I worked before now, I had 2 linux servers. Every evening at 8:30 PM when servers are mostly free of work, their CD-trays opens (I do nothing, it is my shell script). I put 2 DVD+RW into trays, close, take them back to CD-case - that is all I do. All other work (backuping) script does. I had 14(+4) DVD+RWs and rotated them everyday. I mean for example on Monday I erase and rewrite disks, that I wrote last Monday. So I always have potential ability to restore some nessecery files or even the whole system to the state it was a week ago. Four additional disks were for making an extra copy every week on Sunday.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
my first job as an admin - need advices ddaas Red Hat 1 12-21-2004 11:22 AM
system administrator job linuxjobs Linux - General 2 08-23-2004 07:23 AM
Need a good network administrator for Mandrake 9.2 Danno13 Linux - Networking 5 10-21-2003 04:08 PM
Inheriting a network adminís job wedgeworth Linux - Software 1 10-10-2003 04:08 PM
Only For Network Administrator (Linux Expert) cpinyit Linux - Networking 1 06-29-2001 01:15 PM


All times are GMT -5. The time now is 12:40 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration