Preparing you and your system for an mvBase Upgrade
Words for the Wise

We will produce new releases and patch sets for mvBase that offer numerous enhancements and resolutions to known problems. As a support customer we encourage you to install these on your systems. However, we have noted that a number of customers get themselves into trouble when they do not adequately prepare for an upgrade.

Below is a list of 10 important steps that you should follow when performing an upgrade. Please read them carefully and indicate that you have read them at the end of this document.

1. Download mvBase Quick Start Card or the Release Notes for the new release from our Web site. Read it. If you have any questions or concerns after reading it, please email them to techinfo@rainingdata.com and we will be more than happy to provide you with a detailed answer.
2. Read the instructions and understand them. Re-read the instructions and know them.
3. Get a good backup of your mvBase system by doing a full FILESAVE. Verify that it is a good backup. Backing up the Windows files which contain the mvBase database is not considered a backup for the purpose of preparing for an upgrade. A backup that encounters GFE's in the file system is not a good backup. You should contact Raining Data's technical support to resolve any GFE's prior to upgrade.
4. Make sure that you have the ability to re-install any 3rd party MultiValue software that you have installed. If you are performing an upgrade that requires recompiling (a very rare situation - but check in the Quick Start Card or Release Notes) and you do not have all the source code to your application, that application will NOT run after the upgrade.
5. Verify that all applications that you are running have been tested on the mvBase release. You may need to contact your application vendor for this confirmation. Even better would be to test your application and the upgrade procedure out on another system. You may request a short-life Temporary Authorization Code for this purpose by contacting our technical support.
6. Have a backup copy of all items that may have been modified. This would include SYSPROG, mvBase system accounts, and any item that you or your application might have altered. These items may need to be restored after the upgrade is complete. The upgrade updates the SYSPROG account and some items on all other accounts, which are reserved for mvBase use only. This includes all MD entries that come from the NEWAC file in each account and attribute 2 of all logon procs. Also have a copy of your current Permanent Authorization Code, your System ID, and server and workstation configuration information in the chance event that mvBase will need to be installed from scratch.
7. Schedule the upgrade for a time that would be convenient for business operations, for your Raining Data reseller, and within Raining Data's Software Maintenance Agreement (SMA) program hours. If you have purchased an SMA through an authorized Raining Data reseller and not directly from Raining Data, you must contact that reseller directly or you may be subject to per incident charges.
8. If something unexpected occurs during the upgrade, STOP. Call your Raining Data reseller. Trying to remedy a situation that is unexpected with actions which are not based on a clear understanding of what the problem is and what caused it can have serious ramifications and make the problem worse.
9. Be sure to have the latest patch set for the release that you are upgrading to available for you to install immediately after the upgrade is complete. Only the latest Patch Set should be applied. Note: Patch sets are designated for a particular mvBase release and should not be applied for any other mvBase release. See the mvBase Patch Area on our Web site. For your own benefit, read and follow exactly the Patch Set installation instructions (also on the Web).
10. Keep in mind that ALL mvBase components that are not located on the main server system will have to be upgraded as well. This includes any remote workstation components, the mvBase OCX and mvTERM components.