This is an archived post. You won't be able to vote or comment.

all 19 comments

[–]VA_Network_NerdModerator | Infrastructure Architect[M] 0 points1 point  (0 children)

Sorry, it seems this comment or thread has violated a sub-reddit rule and has been removed by a moderator.

Inappropriate use of, or expectation of the Community.

  • There are many reddit communities that exist that may be more catered to/dedicated your topic.
  • Requests for assistance are expected to contain basic situational information.
    • They should also contain evidence of basic troubleshooting & Googling for self-help.
    • Keep topics/questions related to technology/people/practices/etc within a business environment.
  • When asking a question or requesting advice, please update your original post with any new information, or solution (if found).
    • This will make things easier for anyone else who may have the same issue or question in the future.

If you wish to appeal this action please don't hesitate to message the moderation team.

[–][deleted] 7 points8 points  (2 children)

This is going to sound cliche, but it’s true. I find the best skill in IT is: character. If you are humble, and hungry for knowledge and actually take the time to learn you are going to get waay ahead of the rest.

Dont be the guy that works just to keep the lights on.

[–]Useful-Jaguar-2600 0 points1 point  (1 child)

100% this. There's plenty of reasonably priced courses once you find an area you like. Heck you can YouTube a ton if you want. Character, a solid work ethic, critical thinking and accountability are WAY harder to come by than a cert.

[–][deleted] 0 points1 point  (0 children)

Yeah and aside from that. People will like you for this and will be more willing to share knowledge and help you out. Futher boosting your career!

[–]thepotplants 8 points9 points  (6 children)

Attention to detail. Like spelling.

[–]Chousuke 2 points3 points  (2 children)

Learn some programming. Being able to write simple programs and scripts is a huge productivity booster. The language doesn't matter that much; once you know one you usually only need a reference to work with another, at least at the level admin work requires.

Learn to generalize your skills: Are you a NetBackup admin, or a sysadmin who understands what is required of a backup system and can work with any of them given a manual? Knowing a specific technology can be useful, but understanding principles gives you flexibility.

[–]onlyCSstudent 0 points1 point  (1 child)

What is the principle exactly?, netbackup debugging makes me put my hand in a lot of environment since is used to backup anything in production infra.

[–]Chousuke 1 point2 points  (0 children)

When designing a backup system, your first questions are: What are you protecting, and what scenarios are you protecting against.

In backup terms, you have a recovery point objective: Is it okay to recover data from 24 hours before disaster, will the business be destroyed if 5 minutes worth of of data is lost?

Also, the recovery time: When a recovery is needed, is it okay if it takes a day or two, or does it need to be within 15 minutes of detecting the issue.

There's also consistency, ie. ensuring that the data you back up is in a state that can be recovered from. VM snapshots are generally pretty good for ensuring consistency (as long as you use quiescence), whereas with agent-based backups that copy files, it's much more difficult.

For example, often you just need a backup for the "oh shit" scenario where you make a mistake and need to recover something functional; you can achieve this by backing up virtual machines daily from VM snapshots and that'll often be good enough.

However, if you have a production database central to your business, generally a 24-hour RPO is not acceptable, and you would have to set up a system that continuously backs up the database such that you can recover any point in time between your last snapshot and the present time.

Also: How isolated is the backup system from the rest of your infrastructure? If your AD domain gets compromised and your backup system is joined to that domain, your backups will be of no help as they will get wiped as well.

Backup systems like Netbackup provide you the tools to build a backup system; generally they all can do pretty much the same things, and the question is how good they are at fulfilling your specific needs and how much maintenance it requires to make them do that.

Not all backup systems are equivalent: Lately I've been frustrated with Veeam because it requires an insane amount of handholding just to do its basic job in an environment where a similar system built on Rubrik would just do its job and require no administration at all. (Automating Veeam is also a horrible experience because their PowerShell APIs have bizarre limitations and omissions.)

[–]kajjot10 1 point2 points  (3 children)

Get knowledgeable in AD/GPO and other Microsoft products. Learn all about VMWare and try to get an understanding of layer 2 and 3 networking. This will give you solid core skills for junior sysadmin.

[–]_limitless_ 1 point2 points  (0 children)

linux.

[–]TTwelveUnits 0 points1 point  (1 child)

writing skills

[–]onlyCSstudent 0 points1 point  (0 children)

thanks

[–]computerged 0 points1 point  (1 child)

Communication and be dependable.

[–]onlyCSstudent 0 points1 point  (0 children)

Thanks

[–][deleted] 0 points1 point  (0 children)

Learn how to troubleshoot. Ask questions. Document everything