Averify
This is our (simplified) process for running Averify every month.
1. Clone Production > Test [1]
2. Averify against Test
3. Apply Fix to Test
3. Averify against Test
4. If fixed goto 5 else goto 3
5. Halt Production [2]
6. Apply fix to Production
7. Run Averify against Production
8. Start Production
9. Results to Oracle to validate the fix.
Some of us were standing around looking at this process [3] and we have a question:
Is step 7 required?
We _know_ the fix ran against a clone of Production and it's okay. However the time between steps 1 and 6 can be a 7-10 days - does that make a difference?
The reason this is a Big Deal is that averify can take 3-4 hours to run, and that's a lot of downtime in production.
1. Clone Production > Test [1]
2. Averify against Test
3. Apply Fix to Test
3. Averify against Test
4. If fixed goto 5 else goto 3
5. Halt Production [2]
6. Apply fix to Production
7. Run Averify against Production
8. Start Production
9. Results to Oracle to validate the fix.
Some of us were standing around looking at this process [3] and we have a question:
Is step 7 required?
We _know_ the fix ran against a clone of Production and it's okay. However the time between steps 1 and 6 can be a 7-10 days - does that make a difference?
The reason this is a Big Deal is that averify can take 3-4 hours to run, and that's a lot of downtime in production.
0