SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Preparing for System Disasters: Best Practices for Database Management

kaleb avatar
kaleb
21 diapositives · 382 Views · Sep 14, 2014

In "Halloween Revisited," Val Gunnell, a Senior Systems Analyst at Dynix, delves into the potential terrors of system failures, highlighting the importance of being prepared for unexpected disasters in IT environments. With 8 years of no DBMS backup and critical questions surrounding data loss and disaster recovery plans, this guide emphasizes developing solid strategies. It covers essential practices such as server compatibility, regular maintenance tasks, and the critical role of backups—ensuring your operations remain resilient, even in the face of unforeseen catastrophes.

Preparing for System Disasters: Best Practices for Database Management - slide 1
01 / 21Preparing for System Disasters: Best Practices for Database Management
1 / 17

Télécharger la présentation

Preparing for System Disasters: Best Practices for Database Management
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. SYSTEM ADMINISTRATION CODI / HUG 2004 Portland, Oregon Val Gunnell, Dynix Sr. Systems Analyst

  2. HALLOWEEN Revisited • What terrors lurk? • Natural disasters • System failures • Co-workers (Do they trip?) • Unexpected traumas • Examples • 3 hours -- no transaction backup • 8 years – no DBMS backup. • 2 years – no tape backup.

  3. Seek First To Understand… Building blocks of your servers • Database (Governed by DBMS ‘rules’) • DBMS (Runs on top of OS) • Operating System (The Base)

  4. OS / DBMS Operating System • Match your server operating system with compatible version of DBMS software and Horizon Database version. Database Management System (DBMS) • Keep your DBMS up-to-date.

  5. Ask yourself Critical Questions • How many servers do I support? --Horizon DB server --Information Portal Server (HIP) --Other servers, e.g. RPA, etc. • What are the server(s)’ operating systems? • How many databases do I support?

  6. More Questions • If my system fails, how much loss of data can I risk? (How long since the last backup?) • What disaster recovery plan have I developed? • How often have I reviewed my plan? • Can (or should) I simulate a test recovery? • Do I automate tasks or run them manually? • Do my automated backups write to disk or tape or both?

  7. System Databases (Sybase) • Sybase • Master (Info on all DB’s) • Model (Template) • Sybsystemprocs (System procedures) • Tempdb (Workspace) Do you manage these?

  8. System Databases (MS SQL) • MS SQL • Master (Info on all DB’s) • Model (Template) • MSDB (Jobs, alerts, backups) • Tempdb (Workspace) Do you manage these?

  9. SYSTEM PERFORMANCE Setup Issues (Dynix does this for you!) • Utilize multiple processors • Maximize hard drive use • RAID • Balance memory (RAM) issues

  10. SCHEDULED TASKS • DBCC • UPDATE STATISTICS • BACKUPS • Unix -- Cron • Windows -- Scheduled Tasks

  11. Database Consistency Check • DBCC (Database Consistency Checker) -- The database consistency checker (dbcc) provides commands for checking the logical and physical consistency of a database. Two major functions of dbcc are to: Check page linkage and data pointers at both the page level and the row level. Check page allocation.

  12. Update Statistics • ‘Runs Automatically’ -- keeps data retrieval at optimal levels. (Cron or Scheduled Tasks) • Accurate statistics are essential to the query optimization. The update statistics command updates the column-related statistics such as histograms and densities. • Running update statistics requires system resources. • Schedule when load on the server is light.

  13. BACKUPS • Full DBMS DB Backups (Daily?) • Incremental backups (transaction logs) (Hourly?) • Disk Backups (File system; OS backup) (Monthly?) • Tape Backups (Where do you keep tapes?) (Daily or weekly?)

  14. Maintenance Issues (You determine the frequency!) ‘Monthly’ Tasks: • Monitor Database free space (sp_helpdb <dbname>) • Run full Operating System Backup • Monitor Operating System directory(ies) free space.

  15. More issues ‘As Needed’ Tasks: • Reboot server (refresh) • Expand Database(s) • Record database changes (Customization Table)

  16. Test / Training Databases • Why have a test database? -- Test backup files (if same as horizon DB) -- Test any library procedure -- Test Horizon upgrades • How to maintain this DB -- Back up when needed

  17. ACT ON YOUR PLANS Regular Routine Maintenance keeps your servers running optimally and protects you against unexpected system failure. GOAL: Develop and Maintain your disaster recovery plan.

  18. SUMMARY • You’ve made it! • You made your plan • You worked your plan • You’re not afraid (even after Halloween!)

  19. Questions?

  20. Suggested References • System Administrator Handbook: Brains in a Book Marge Freeman LION (Lynchburg Information Online Network) CODI / HUG 2003