After quite a while learning about IT, I considered that this is one of the toughest jobs I ever know. I never thought that working in IT could give you rough time, of course this is just my personal assumption, but I have good reasons for that. This is few things that can make working in IT tortuous at times.

• You get a lot of fingers pointed at you. When error messages pop up and system outages occur, people quickly start pointing fingers at IT and the pressure is intense to get things fixed quickly to keep users from losing productivity. That’s part of the job and you have to always be prepared for it and they really don’t care about your explanation, you have to fixed their problem. In fact, some IT pros even get an adrenaline rush from this type of high-pressure stakes. The problem is that IT pros hear loud and clear when things aren’t working, but they rarely get much appreciation during the other 99% of the time when systems are running smoothly.
• People assume you’re an expert in all things tech. When you’re an IT worker, non-techies  co-workers tend to assume that you know everything about all tech subjects. For example, if you’re a help desk technician you get questions about how to deal with spam and spyware on an employee’s machine. There are obviously tactful ways to handle this, but me, myself can’t help but get a little frustrated by this, or even feeling a little inadequate. Worse, because you’re an IT-guy, a lot of your co-workers will come to you for advice on buying PCs, digital cameras, and TVs. Some will even ask you to fix their PC for free or help troubleshoot a problem with their cable modem.
• You have to continually re-train, on your own dime. I think it’s fair for me to say that no profession on earth is changing faster than the IT field right now and that’s not likely to change any time soon. The pace of development and innovation in hardware and software products is staggering. As a result, the knowledge that it takes just to keep your current job is always growing and moving, and IT pros have to take responsibility for their continuing education or risk having their skills and knowledge become obsolete within a few short time. This is a constant struggle especially for someone that has no IT background like my self .

Well, I guess that’s all the things that you need to now about taking career as an IT-guy. Anyway instead of give up and walk away, I think, I’ll take may chance and deal with it, who knows someday…….

Disaster Recovery is simply planning ahead to avoid problems, and being prepared in the event problem occurs. From business perspective Disaster Recovery has three basic components referred to as :

• Business planning and preparation
• Business system and technology preparation
• Incident response planning

These three basic strategy address how to effective prepare and respond to unexpected shutdown. While technical and logistical aspects of Disaster Recovery can be very complex, the operational components can be boiled into three basic concepts :

• Knowing the risk
• Necessary step for potential problem
• Problem counter

A business recovery plan is sometimes referred to as a continuity plan, however a disaster recover plan is often characterized as being specifically for IT system within a specific location. Because the field of disaster management is still relatively early in its development, it is not always clear what is meant by terms such as “Business Continuity”, “Emergency Management” or “Disaster Recovery”

Business Continuity planning, Disaster Recovery planning and Risk Management are all concerned with proactive approach to protecting an organization from disruption by prevention, risk transferor loss mitigation.

Emergency management is concerned with management of event as they unfold during actual or impending situation that may cost injury, loss of life or destruction of property.

Business Recovery Management is concerned with the recovery business after the emergency has receded and the organization begin the process of rebuilding. All three areas of current thought advocate a methodical approach to the development of formal “pro-active” plans and follow similar lines :

• Define objectives and assumption
• Gather facts analyze requirements
• Design the strategies
• Create the plan
• Implement the plan
• Test the plan
• Review/Update/Maintain the plan

After the initial plan is complete and successfully tested, schedule quarterly or semi-annual tests to be sure changes of the business or environment have not rendered part or all of plan ineffective.

www.indoDRC.com

Biar saja ku tak sehebat matahari
Tapi ku slalu mencoba tuk menghangatkanmu
Biar saja ku tak setegar batu karang
Tapi ku slalu mencoba tuk melindungimu

Biar saja ku tak seharum bunga mawar
Tapi slalu kucoba tuk mengharumkanmu
Biar saja ku tak seelok langit sore
Tapi slalu kucoba tuk mengindahkanmu

Kupertahankan kau demi kehormatan bangsa
Kupertahankan kau demi tumpah darah
Semua pahlawan-pahlawanku

Merah putih teruslah kau berkibar
Di ujung tiang tertinggi di Indonesiaku ini
Merah putih teruslah kau berkibar
Di ujung tiang tertinggi di Indonesiaku ini
Merah putih teruslah kau berkibar
Ku kan selalu menjagamu                       _{(BENDERA-COKELAT)}