Monitoring, Tuning, and Maintaining Your Informatics Environment. Workshop C5

Transcription

1 Monitoring, Tuning, and Maintaining Your Informatics Environment. Workshop C5 Gilles Bassard / Ömer Yilmaz 2011 Waters Corporation 1

2 Introduction Almost everything could be monitor, the time constraint and risk assessment should drive you to select the right thing to include in the Standard Monitoring. Be logical and pragmatic. The maintenance and Monitoring reduce the troubleshooting 2011 Waters Corporation 2

3 What to Monitor Infrastructure & Hardware : Routers, Servers, UPS. Processor usage, memory usage Application Key Components : Database Application activity Network Performance Application usage Project Size, Application Error, Buffering, Archive Waters Corporation 3

4 Infrastructure Monitoring This require a deep infrastructure knowledge. It s include the hardware peace associate with their physical location. (E.g., this router is use by lab QC, the UPS1 use for system 1 and 2). Most of the infrastructure device, like switch, router, server have building technology to Warm on issue. Consider SNMP / WMI 2011 Waters Corporation 4

5 Infrastructure Monitor What Can Go Wrong S.H.O.E. Software Hardware Operator Environment OS Servers Human Error Power Device Drivers Routers Sabotage Fire Name Resolution Hard Disks Mail storms Flood Authentication Memory Planning Earthquake Virus Remote Access Monitoring Heat System Limits Network HW Placement Dust Application Code Backup Devices Change Control Tornado 44 % Hardware, 32% People, 14% Software7% Virus, 3% Natural Diasters 2011 Waters Corporation 5

6 OS Monitoring Consider existing tools like Event viewer and dedicate log for hardware like HD controlers. Task Manager is not a monitoring Tools. Consider performance Monitoring 2011 Waters Corporation 6

7 Os Monitoring Periodic review of Event log from all machine is require to insure pro active action. Build a Microsoft MMC for lace 2011 Waters Corporation 7

8 OS Monitoring For large network consider Commercial solution to centralize your logs from all the machine in One place Waters Corporation 8

9 Network Monitoring Lot of tools exist on the market You can identify the up/down device, as well as monitoring performance. They will warm you on lost machine and high usage Waters Corporation 9

10 Database monitoring They is plenty of logs for oracle database : Listerner.log Alert.log Trace.log Backup.log. Since oracle 10g the Enterprise Management console is the central oracle monitoring tools Waters Corporation 10

11 OEM 2011 Waters Corporation 11

12 Alert and logs 2011 Waters Corporation 12

13 Tablespace size & status 2011 Waters Corporation 13

14 Datafiles size & status 2011 Waters Corporation 14

15 Use memory adviser to improve it 2011 Waters Corporation 15

16 Embeded Performance Monitoring 2011 Waters Corporation 16

17 Backups log Review them to ensure they complete. Part of your DRP you have to include a periodic restore test Waters Corporation 17

18 Application Log Message Center 2011 Waters Corporation 18

19 2011 Waters Corporation 19

20 2011 Waters Corporation 20

21 2011 Waters Corporation 21

22 2011 Waters Corporation 22

23 Empower3 FR2 Enhancement 2011 Waters Corporation 23

24 Monitoring Volume of DATA Managing the data volume is a key of the success put archiving procedure in place. Don t keep unnecessary data online Consider archiving automation using EDM or SDMS Waters Corporation 24

25 Best Practices Design Criteria Project size Setting limits o Project limits o Flat File size Periodic cleanup o Use the configuration manager to monitor the size of projects Size Decreasing Performance Data Volume Backup Size Stable Performance Not enough time to backup No space on the backup system Data Volume Unmanaged Not enough space Time Managed Backup 2011 Waters Corporation 25 Time

26 What is Your Audit Trail Trying to Tell You? The Audit Trail gives a good indication of the usage of Empower overall, and can highlight a number of issues 2011 Waters Corporation 26

27 Recover logs For buffering info on each lace you analyse the recover.log 2011 Waters Corporation 27

28 Best Practices Preventative Maintenance Test new hardware and software in a test bed first Burn new hardware in using load test software for a few weeks Schedule preventative maintenance down time Disk / DB defragmentation Monitor WLI Applications CPU over-utilization (consistently over 70%) Application performance metrics Memory utilization Network saturation I/O Metrics 2011 Waters Corporation 28

29 Questions 2011 Waters Corporation 29