Basic Sys Admin

SYAD02
Basic System Administration
Gary Nakayama, CPA

SAP Labs
¤ SAP Labs, Inc. SAP TechEd 2000 June 20–23, 2000 SYAD02.ppt/ 1
Agenda
z Who is the Speaker?

z Guidelines and Murphy’s Law and Corollaries
z Disaster Recovery
z Keep your System Running
z Summary
z Q&A
z Drawing (must be present to win)
Who is the Speaker?
Training
• Certified Public Accountant
• BBA in Accounting and MIS, MBA in MIS
Experience
• 20+ years in financial and business systems
• 6 years working on R/3
• FI/CO as a functional analyst
• BASIS as a System Administrator
• Currently System Administration developer in the
Simplification Group at SAP Labs
Publications
• System Administration Made Easy guidebook
Two editions; R/3 release 4.0B and 4.6A/B
Agenda

z Disaster Recovery
z Summary
z Q&A
z Drawing
Guidelines
z No such thing as a dumb question

z Network with other users and consultants, every time you can
z Protect “your” system
z RTMF – Read The Manual First
z KISS – Keep It Short and Simple
z Document everything and use checklists
z Use the appropriate tool for the job
z Don’t change what you don’t have to
z Communicate with your users
z Don’t make changes during critical periods
z Better to be safe than sorry
z A “quick fix” is the longest hardest method to fix a problem
Murphy‘s Law
Anything that can go wrong . . .
. . . will
Corollaries to Murphy’s Law
z Common sense…is not common

z Disasters always strike at the worst time
…at 2am…and when you are not prepared
z When the power fails
…you “discover” that the battery in your UPS is DEAD
…or your UPS itself is DEAD (mine)
z If you only have one tape drive…it will fail
z The one time you did not check the backup log
…will be when the backup failed
z Someone needs a network jumper cable
…and will remove it from your server
z Someone will load test data into the production system
z Companies will spend $5,000 in consulting to avoid a $1,000
hardware purchase
Agenda

z Disaster Recovery
z Summary
z Q&A
z Drawing
Are You Prepared for a Disaster?
z Is your resume updated?
z If you have not been through a disaster…you will
Consequences of a Disaster
Issues:
• Who owes you money?
• Who are your customers?
• What orders do you have?
• Will the competitors take away your customers?
Result:
Your company could go out of business…
…if your company is gone…so is your job.
Disaster Planning
z Plan for the worse, hope for the best

z Disaster Plan
• have one
• if you don’t have one, start working on one
• Ass-U-Me nothing
z Test the Plan … or does your plan really work?
Sample High Level DR Plan
z Recovery script or process (flow chart)

z Define when/who declares a disaster
z Damage control procedures, minimize the damage
z Disaster Scenarios and procedures
z Expected recovery times
z Recovery group (personnel)
z Crash kit
Agenda

z Disaster Recovery
z Summary
z Q&A
z Drawing
Keep the System Running
Topics
z Documentation
z Use checklists
z Tasks that Need to be done
z Monitor your System
z Security
z Change Management
z Help! I have a problem
Documentation
z Document everything
• What exists; hardware, cables, configuration, etc.
• What you do; procedures, changes, etc
• Where things are kept; documentation, passwords, keys, crash
kit, etc.
z Documentation is complete only if someone else can do your
job, or the tasks that needs to be done,
by only using the documentation you wrote (no coaching)
Why Document
z People forget, memory is not reliable

• especially at 2am…
z Train new people.
z For others to do the task
• vacation, disaster
z If task is complex, critical or done infrequently
z The consequence of making a mistake is severe (disaster)
z You may need to “undo” what you did
Checklists – what and why
What are checklists

z Simple form of documentation for procedural tasks
Why you should use them

z Scheduled tasks
… so you remember to do them
z Specific tasks
… to guide you through ALL the steps in the task
z When tasks are complex, critical or done infrequently
Examples of checklists
z Scheduled tasks:
• daily; critical and regular
• weekly
• monthly
z Specific tasks:
• start and stop R/3
• restoring the system
• adding a user
• performing a transport
• performing a client copy
Critical Daily Tasks
When:
z These tasks are done first thing in the morning, or when you
get into the office
Tasks:
z Is R/3 running?
z Check that last nights backups ran successfully
Daily Tasks
z Do critical tasks
z Check that all application servers are up (SM51)
z Check the CCMS alert monitor (RZ20)
z Check for update terminates (SM13)
z Check logs for problems or unusual activity:
R/3, database, operating system, security, etc.
Other Important Tasks
z Monitor usage and free space in database and file system (daily,
weekly)
z Perform preventive maintenance
• Clean the tape drive (weekly)
• Check battery capacity of UPS (monthly)
z Test your alert monitor/paging system
z Monitor your inventory of spare parts and consumable supplies
(backup tapes, toner cartridges, batteries, etc) (weekly)
z Archive backup tapes according to defined retention procedure for
required period of time (monthly, quarterly, annual)
Monitor the System
If you don’t monitor the system, you won’t know if there is a

problem
z CCMS Alert Monitor (RZ20)
z Update Terminate (SM13), for failed updates
z System log (SM21), for problems and unusual entries
z Database and operating system logs, for problems
z Locks (SM12), for old/long locks
z Active Users (AL08), unusual combinations of user, terminal,
transaction
z Background Jobs (SM37), for canceled or failed jobs
Security
z One definition of security:

• Preservation and protection of your companies data assets
z Security in Layers
z Must strike a balance between control and practical
operations
z User administration
z Audits; financial and computer
z Audit Tools; Audit log and Audit Information System
Change Management
z Change control process and procedures

• Control what is done to each system in your R/3 landscape
• Everyone is aware of what is happening to the system
z Transport Management System – TMS (STMS)
• Transports done completely within R/3
• No longer have to “tp import k912345678 PRD cleint=100”
Help! I have a Problem
Topics:
z What to do
z Where to get help
What to do / Problem Solving
z Calm down…so you can think

z Collect data (including read documentation)
z Identify the problem, not the symptom
z Determine alternatives
z Apply the selected alternative
z Evaluate the results
(this is standard problem solving technique)
Where to get help
z RTMF – Read the documentation; SAP online docs, manuals,

books, etc. (guideline #4)
z SAPnet (service.sap.com)
z Simplification Group web site
(www.saplabs.com/simple and www.saplabs.com/sysadmin)
z Your network of contacts (guideline #2)
z SAP hot line
z Various independent SAP web sites
z Your implementation partners (vendors and consultants)
Some Other Important Topics
z Security
z User Administration
z Changing System Profiles
z Support Packages (aka Hot Packages)
z Kernel Upgrade
z Client Copy
z Production Refresh Strategies
z Remote services; SAPnet, sapserv, EarlyWatch, etc.
z Operations
z Output Management
Agenda

z Disaster Recovery
z Summary
z Q&A
z Drawing
Summary
z System administration is a lot of common sense

z Read the documentation !!!
z BE CAREFUL
z Be ready for a disaster
z Document everything and use checklists whenever possible
z Problem solving in R/3 is the same as any other problem
solving
z Expand your network of resources
Resource for this presentation
z System Administration Made Easy guidebook

for R/3 release 4.6A/B, downloadable at:
www.saplabs.com/sysadmin
z SAP Technical Core Competency classes
www.sap.com/training
Agenda

z Disaster Recovery
z Summary
z Q&A
z Drawing
Question & Answer
There is no such thing as a dumb question
I will be available after the presentation is over

I am available for evening discussions
Drawing
(You must be present to win)
Please complete your session
evaluation and drop it in the
box on your way out.
Be courteous — deposit your trash,
and do not take the handouts for
the following session.
The SAP TechEd 2000 Staff


Basic Sys Admin

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Basic Sys Admin

Hochgeladen von

Copyright:

Verfügbare Formate

SYAD02

Basic System Administration

Gary Nakayama, CPA

z Who is the Speaker?

z Who is the Speaker?

z No such thing as a dumb question

Anything that can go wrong . . .

z Common sense…is not common

z Who is the Speaker?

z Is your resume updated?

z If you have not been through a disaster…you will

z Plan for the worse, hope for the best

z Recovery script or process (flow chart)

z Who is the Speaker?

z People forget, memory is not reliable

What are checklists

Why you should use them

If you don’t monitor the system, you won’t know if there is a

z One definition of security:

z Change control process and procedures

z Calm down…so you can think

(this is standard problem solving technique)

z RTMF – Read the documentation; SAP online docs, manuals,

z Who is the Speaker?

z System administration is a lot of common sense

z System Administration Made Easy guidebook

z SAP Technical Core Competency classes

z Who is the Speaker?

There is no such thing as a dumb question

I will be available after the presentation is over

(You must be present to win)

The SAP TechEd 2000 Staff

Das könnte Ihnen auch gefallen