But needed anyway in case of total disk lossĮxistence II: Preventing data loss The case for after-imaging. Changes to DB structure, or application code changes, may mean restored DB will not run with current application code. Restore database:prorestdbnamebackupfile. Restore DB backup file (and possibly other stuff) from removable media into scratch area. proquietdbname –C enable (pauses update activity). 
Large sites may wish to use mirror split (i.e.Then back up backup file, applications, and critical system files to removable media (and take them offsite).KISS: Use probkup (online or offline)probkup dbnamebackupfilename –com.Or the system data? User password database?.
What if you’re sick and the restore has to be done by someone else?.Have you actually tested your backup recently?.What challenges are there and how will you address them?.Your application must exist and be current.If it goes away, you must be able to get it back.Progress databases largely require no administration once set up (for small to medium users).Įxistence The database must exist, be current, and be usable.For most users, it’s easy to forget how to do these.Some tasks only need to be done occasionally.You should know how to do these, and when to do them.
Some tasks need to be done weekly, daily, or sometimes even hourly. Ensuring user actions are monitored and/or controlled Protecting the database from unauthorised access Complying with legislative requirements or other standardsĪgenda Existence Uptime Connectivity Security Auditing Performance What does it mean? The database must exist and be up to date and consistent It must be on-line when users need to connect Users must be able to connect DB operations should be fast enough, and other applications should not be unduly impacted What is the DBA responsible for? Availability Users must be able to connect to, read from, and update the database whenever they need to. Everyday DBA for Progress OpenEdge What You Need to Know, and When to Call for Help David Eddy
0 kommentar(er)
