Home
Consultants
Larry Karnis
Andrew Weisz
David Rutherford
Projects
Interests
Marketing
Consulting Philosophy
Installation
Complete Install Guide
Database Upgrades
Installation Methodology
Version Upgrades
Programming
CIM Interface
Data Migration
Q/LinQ
Go Linux
Testimonlials
Yung Le
Dana Karnis
Tammy Grimard
Go Linux
Tech Notes
Links
Mailing Lists
Site Map
Contact Us
|
Upgrading MFG/Pro Databases
A-High B-Medium C-Low | Likelihood |
| A | B | C |
I m p a c t | A | A-A | A-B | A-C |
| B | A-B | B-B | B-C |
| C | A-C | B-C | C-C |
|
When doing a risk assessment of an event there are two issues that are considered:
- What is the likelihood the event will happen.
- What would the impact of that event be.
A-A issues should be given highest priority, followed by the rest of the A-?'s in order, and so on.
|
This has a huge bearing on migrating the production database. It is very likely that something unforseen will happen during migration. Losing the production database will also have a huge impact. If something unforseen does happen and you have to restore from backup; you have lost valuable time and, more importantly, you may lose the confidence of management.
So, it is extremely important to minimize the chance of unexpected occurences. That is why it is essential to perform a test migration and meticulously document the process.
We minimize our vulnerabilities.
Migrating Production Databases
- Verify a complete backup of the system.
- Create a test version of the production database.
- Migrate the test version - keeping detailed notes and working out any bugs in the process. What happens if the power goes out. What are the phone numbers of important contacts. When do the nightly batches, scripts, backups, etc run.
- Perform another backup and verification.
- Migrate the production database.
- Be available to support post migration issues.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
|