Review these considerations before installing or upgrading mvBase 3.2.
CAUTION |
Do not uninstall an earlier release of mvBase already installed on your computer. Install mvBase over the resident version. That is, use the existing directories, files, and configurations. |
If you install mvBase on the same local drive where your operating system resides, check that you have sufficient disk space before installing. See Verifying Windows Disk Space.
If you are upgrading from mvBase 1.2.04, contact Customer Service.
If you are upgrading from mvBase 1.3 or later to 3.2, a FILELOAD is required.
Windows consumes disk space for virtual memory storage (VMS) files by these parameters:
Disk space for VMS files can be distributed up to a maximum of 50 files, each of which can be located on a separate disk volume.
Maximum collective allocation of disk space to VMS files on Windows is 2,097,152 MB (2 terabytes).
First VMS file cannot exceed 1024 MB in size.
NOTE |
To improve performance, the size of the first VMS file should be kept as small as possible. |
mvBase Administration Utility automatically enforces this minimum limit during the installation and upgrade procedure.
CAUTION |
We highly recommend that the first VMS file is larger than the minimum required size in order to improve the performance of mvBase. |
Remaining allocation of disk space to mvBase can be spread from VMS files 2 through 50 as required. The only size restriction for files 2 through 50 is that the total allocation for mvBase (including the first file) should not exceed 2 terabytes.
See Verifying Windows Disk Space for more information on system parameters.
For Windows Server 2008, Windows Server 2012, Windows 7 and Windows 8, you must run mvBase as administrator by right-clicking the mvBase Start menu option and selecting Run as Administrator.
See Also