Started a new job and found out I'm replacing the current Sys Admin

[TheCanuck]

I've just been thrown into a TSM environment and the current admin will be leaving soon (immigration issues). I'm very new to TSM so I'm a little bit lost and it's like pulling teeth to get any answers on how the current environment is setup -- keep been told to just read the manuals (yeah rtfm, thanks alot). We have a TSM library manager, and 4 client TSM servers, 3584 LTO4 library and a few hundred servers to backup (windows, aix, linux) etc.

Anyway, I wanted to get the following in some sort of brief note form so I don't miss anything, but can't get any answers:

1)Daily tasks

2)Weekly / monthly maintenance tasks

3)Custom scripts run on each backup server

4)Typical manual backup procedures
a.Standard filesystems
b.Database backups
c.NDMP backups
d.Any additional procedures
5)Typical restore procedures (recent script examples)
a.Standard filesystem restores
b.Database restores
c.NDMP restores
d.Any additional procedures
6)DR Procedures
a.How often is TSM database backed up, procedures
b.Most Recent database vaulted daily?
c.Additional procedures for DR

7)Standard procedures for starting and stopping the TSM Servers

List of some typical issues that come up in the environment and what is done to resolve them.

9)List of processes (TSM , OS and hardware) that you monitor to ensure all systems are operating properly. How they are monitored (emailed scripts, gui, OS checks etc).

10)Summary of any schedules and automatic processes that have changed in the last architecture guide. Information on any schedules / processes that are outdated in the report.

I'm fairly experienced with unix but my backup systems weren't quite as complex as this one. I have no problem figuring things out on my own, but due to the complexity of the environment, I would feel better if I had a "cheat sheet".

So am I been a dick by asking these questions and requesting a brief write up? The admin fired back an email saying that everything has been covered (cc'd new boss as well) but
she's more interested in just doing the current job rather than actually showing me anything (figured that would happen anyway after I found out about the situation). I don't want to seem like a whiny beatch, but I was told I'd be trained thoroughly on the systems. I also don't want people to think the new guy is an ass and is too demanding.

 

[Homerboy]

Originally posted by: TheCanuck
I've just been thrown into a TSM environment and the current admin will be leaving soon (immigration issues). I'm very new to TSM so I'm a little bit lost and it's like pulling teeth to get any answers on how the current environment is setup -- keep been told to just read the manuals (yeah rtfm, thanks alot). We have a TSM library manager, and 4 client TSM servers, 3584 LTO4 library and a few hundred servers to backup (windows, aix, linux) etc.

Anyway, I wanted to get the following in some sort of brief note form so I don't miss anything, but can't get any answers:

1)Daily tasks

2)Weekly / monthly maintenance tasks

3)Custom scripts run on each backup server

4)Typical manual backup procedures
a.Standard filesystems
b.Database backups
c.NDMP backups
d.Any additional procedures
5)Typical restore procedures (recent script examples)
a.Standard filesystem restores
b.Database restores
c.NDMP restores
d.Any additional procedures
6)DR Procedures
a.How often is TSM database backed up, procedures
b.Most Recent database vaulted daily?
c.Additional procedures for DR

7)Standard procedures for starting and stopping the TSM Servers

List of some typical issues that come up in the environment and what is done to resolve them.

9)List of processes (TSM , OS and hardware) that you monitor to ensure all systems are operating properly. How they are monitored (emailed scripts, gui, OS checks etc).

10)Summary of any schedules and automatic processes that have changed in the last architecture guide. Information on any schedules / processes that are outdated in the report.

I'm fairly experienced with unix but my backup systems weren't quite as complex as this one. I have no problem figuring things out on my own, but due to the complexity of the environment, I would feel better if I had a "cheat sheet".

So am I been a dick by asking these questions and requesting a brief write up? The admin fired back an email saying that everything has been covered (cc'd new boss as well) but
she's more interested in just doing the current job rather than actually showing me anything (figured that would happen anyway after I found out about the situation). I don't want to seem like a whiny beatch, but I was told I'd be trained thoroughly on the systems. I also don't want people to think the new guy is an ass and is too demanding.

Entirely within your "rights" to ask for and EXPECT a run down of daily task, chores, the little nuances of the system etc etc etc. If the outgoing-admin wont do that with you, make sure your current boss is aware of that so when he's gone, and shit starts hitting the fan you can at least say "I ASKED FOR INFO AND NEVER GOT IT!!!...."

CYA (thats a "Cover Your Ass" not a "see ya")

 

[Chryso]

I would continue looking for work elsewhere. This sounds like a bad situation.

 

[skace]

What's TSM? In Netbackup, a lot of what you are asking for can just be pulled directly out of the application. I'm not saying that excuses a lack of training, but it would definitely be my starting point.

 

[Homerboy]

Originally posted by: Chryso
I would continue looking for work elsewhere. This sounds like a bad situation.

I forgot to add that part yes... sounds like a powder keg ready to blow up and you'll be the one in the line of fire. Not a good way to start out with nobody wanting to really help you.

 

[Homerboy]

Originally posted by: skace
What's TSM? In Netbackup, a lot of what you are asking for can just be pulled directly out of the application. I'm not saying that excuses a lack of training, but it would definitely be my starting point.

IBM - Tivoli Storage Manager

 

[clamum]

I don't think you're out-of-line for asking questions. If I was the guy leaving, however, I would've written up procedures like you're asking about previously to you starting so when you started the job you could read through them.

It's not the same job as yours, but before I left my last job as a web designer I wrote up all the websites I worked/work on, what the daily tasks were, a brief explanation of what I did, usernames/passwords, locations of relevent scripts/images/files. I mean it wasn't hard what I did, but there was a lot of information and things to remember so I figured it was a good idea to have a reference for the person taking over my duties.

 

[GT1999]

My job previous to the one I'm currently at (at a huge company, now) was for a small telco/ISP/web hosting firm where I managed Linux/Win2k3 servers and was in a situation EXACTLY like yours except the sys admin was working remotely. It did NOT end well. When it hit the fan, it was blamed on me, when the previous sys admin who set all of it up was still working on the system and not telling me the work that was being done. This caused firewall config issues when redundancy was cut, yet configs were still scp'd over. When one of the main clients was killed by the firewall config issue, I was brought into the owner's office later in the day and let go... mainly because they needed the original admin around since he was the one in power, and not willing to release information on the network.

I would look for work elsewhere. Look for a large company where you'll have proper documentation in-hand when you get to work your first day. Trust me on this one. Now that I'm at a larger company I have more freedom, a chain of co-workers that know about the work I do where procedures are followed, and I get paid an extra $12,000 /year to boot.

 

[pontifex]

i was hired to take over for my boss if anything should ever happen to him or if he retires. apparently, he must be scared of me taking over sooner than he wants me to because he hasn't shown me jack shit in the 3 years i've been here.

 

[clamum]

Wow Geekish, that is really dumb of them. Glad you made out well with the other company, though. :thumbsup:

 

[daniel1113]

I always made it a point to write out my daily tasks and necessary procedures when I left my summer IT jobs. I also took a good week or two at the end to go through everything with the other IT guys. Even though I was technically an intern, I always ended up doing/knowing more than the salaried guys, and they would have been dead in the water without my instructions.

So, in short, your request is not out of line. In fact, I would expect it from any decent company/employee.

 

[kranky]

Unfortunately, that's not unusual for admins to act that way. Sadly, you will be left holding the bag when the admin leaves and you don't have the information you want.

DO NOT BE SHY. Don't try to do this via email. The admin will supply bits and pieces of info to make it look as though she's cooperating but it won't be enough for you to know everything. Get the admin to walk you through the things you need to know, and if the admin won't do it, get the heck out of Dodge. Better to leave now instead of waiting for the inevitable meltdown, where you'll be killing yourself to fix something you don't know about, and then find out no one is happy with you.

When the meltdown arrives, it won't help you to say "I asked for information and never got it." Say it NOW. If the boss won't get the admin to help you, then tell the boss you will not be able to meet their expectations without the critical information that only the admin has and will not provide, so instead of getting further into a situation that will end badly, you're giving your two weeks notice because the promised briefing was not provided. Don't whine, just say it confidently and calmly.

If you won't say it now, don't say it later. It will sound like a lame excuse.

What makes me nervous is that the admin already told you "everything has been covered." That's code for "Quit bothering me, I have one foot out the door and could not care less about what happens after I leave."

 

[aceO07]

Originally posted by: TheCanuck
So am I been a dick by asking these questions and requesting a brief write up? The admin fired back an email saying that everything has been covered (cc'd new boss as well) but
she's more interested in just doing the current job rather than actually showing me anything (figured that would happen anyway after I found out about the situation). I don't want to seem like a whiny beatch, but I was told I'd be trained thoroughly on the systems. I also don't want people to think the new guy is an ass and is too demanding.

It is very reasonable for you to ask those questions.

Just reply back to all and say you did not receive the answers to your list of questions and to send thorough answers to you and a copy to your boss.

edit: I agree with kranky too. Make sure to have her go over each process with you so you can be sure to understand it.

When I left my previous job (on good terms with 2 month notice), I made a long document was made that outlined everything that I did and where information would be found or who else could help. I also went over my tasks with my replacement and asked many times if he had questions.

 

[Crazee]

This is very simple. Email the questions to the current admin and cc your boss.

 

[Platypus]

sounds like now would be a good time to exit stage left.

 

[GT1999]

Originally posted by: Platypus
sounds like now would be a good time to exit stage left.

I'd follow Crazee's advice first, but I agree.

Hit up Monster.com and all the big businesses you can think of in your area when you get home today, OP.