Procedure for upgrading a customer site

To upgrade a customer from Release<A> to Release<B>

1. Create a test environment. In the event a test environment is not practial/feasible refer to AllphonesRel9UpgradePlan.

   1. mkdir /u/cc.<B>/

   2. mkdir /u/cc.<B>/TEST<B>

   3. cp /u/cc/<CUSTOMER>/*.* /u/cc.<B>/TEST<B>

   4. cp -r /u/cc/adm /u/cc.<B>

   5. Create a new user called test<B>.

   6. Edit test<B>'s .bash_profile to export CCDIR=/u/cc.<B>

   7. Perform upgrade on test environment.
2. Ask customer to test the test environment.
3. When customer is happy with test environment, arrange time to perform upgrade. Preferably overnight.
4. Notify customer of upgrade and hope nothing went horribly wrong !!

To upgrade data and programs from Release<A> to Release<B>

1. Send all Release<B> programs, customised Release<B> programs, libraries, Release<B> standard company, the upgra<A> script and the upgra<B> script. Do NOT install. Place in a convienent location.

2. Disable all cron jobs
3. Backup existing data and programs.

4. Send and install the latest Release<A> utitliy and update programs.

5. Send the latest upgra<A> script.

6. Check that running the upgra<A> script will not be a problem and run. If running the whole script may cause problems, manually run the appropriate steps. To check if the script will cause problems, check /u/ccr.A/std/update.log and /u/ccr.A/std/update.txt.

7. Check that the data is okay. Some functionalitiy may not work correctly due to changes in data updates.
8. If there has been a significant amount of changes applied so far, it may be convient to keep a backup copy of the company as well. This can useful if the following steps fail.

9. Install new Release<B> programs, libraries and standard company.

10. Run the upgra<B> script.

11. Perform basic checks (eg. run sieat, run an aad program, etc.)
12. Reenable all cron jobs disabled in step 2.