Moving Windows files containing an mvBase Database

mvBase stores its entire MultiValue database in a file (or one or more files on Windows NT) in the Windows File System (whether FAT, FAT32, or NTFS). These files can be located in any directory on any disk drive and do not have to be all in the same directory, or on the same drive.

Administration of these files (called Virtual Memory Storage files, or VMS files for short) is done using the mvBase Administration Utility ñ mvADMIN. For more details, see the information found under ìVMSî in the mvBase, and mvBase Administration Utility, online help systems, as well as the (Re)Defining Virtual Memory Storage Files topic in the Configuring and Using the mvBase Server section of the mvBase Operation and Administration Guide. The latter reference is available on the mvBase CD-ROM, at the Pick Web site, and as a printed manual.

mvADMIN provides for the addition, deletion and resizing of VMS files, but does not supply an explicit mechanism for moving them from one directory to another (or from one disk to another, which is just a special case of moving them from one directory to another). This can be achieved by carefully following the simple procedure below.

NOTE: Although the early part of the procedure calls for a FileSave to be done as a precaution, a FileLoad will not be needed in the latter part if the procedure is done correctly.

If you are running on Windows NT and have a very large number of VMS files, then the procedure presented below is rather tedious, and hence offers opportunity for mistakes. If you currently have a Standard or Extended mvBase Support Contract, you may wish to contact an mvBase Support Specialist for an alternative method of moving VMS files, which involves the use of the Microsoft Registry Editor. Due to the potential for mis-use of the Registry Editor, this should not be the most favored method, but only considered an alternative to the procedure documented here. We do not recommend the use of the Microsoft Registry Editor by customers.

Preparation for moving the VMS files

• Make sure that all users are logged off the mvBase system.

• Stop any transaction logging to tape (or Virtual Tape Link to another system if you are using Fast Fault Recovery)

• Stop the mvBase Workstation on the mvBase server host system and the remote workstations on other systems (if any).

• Do a full FILE-SAVE of your entire system.

• Shutdown the mvBase server by using the :SHUTDOWN command on the SYSPROG account.

• Make a note of the names of your VMS files, their current locations, file sizes and the order in which they have been defined in the mvADMIN | Server | Configure | Files tab.

Moving the actual VMS files

• Using Windows Explorer (or any other method you choose) move the actual VMS file(s) in the Windows File System from their current locations to the desired new locations.

• If you are cautious, you may wish to copy the VMS file(s) to their new locations at this point rather than move them. When the procedure has been finished and everything is back up and running again, then you can delete the actual files from the Windows File System using Windows Explorer at that point.

Redefining the VMS file(s) to the mvBase server

Deleting the VMS files from mvBase usage

Using the mvADMIN | Server | Configure | Files tab, delete all the old definitions of all the VMS file(s). [Remember you noted their names, order and size earlier]

Trying to delete some VMS files and not deleting others may create confusion and cause VMS files to get re-ordered. This will cause a problem and may prevent your server from being restarted without doing a total FileLoad. It is much safer to delete them all and re-add them all if you are doing this yourself. [Remember you noted their names, order and size earlier].

It is vitally important to retain the order and size of the VMS files when they are re-added later.

• Select a VMS file by clicking on it.

• Click the Delete button

• If you only copied the actual files (instead of moving them) earlier on, then you should click the No button on the ëPhysically delete the Windows file as well as remove from mvBase usage?í message box when it appears. If you moved the actual files earlier on, then it doesnít matter whether you click the Yes or No button.

• Then click Yes to the ëALERT ñ Deleting the file will require a FileLoad. Do you want to continue?í message box.

• Click the Apply Button.

Repeat these steps for each VMS file.

Re-Adding the VMS files for use by the mvBase server

When all the VMS files have been deleted from mvBase usage, then they can be re-added so that they re-appear in the same order.

• Click on the Add button.

• Enter the full path of the VMS fileís new location (or old location if the VMS file is not being moved).

• Enter the existing size.

• If you have correctly entered both then you will get a message box saying
  
  ëFile physically exists (current size = xx MB, desired size = xx MB)
  Do you want to continue?
  
  Click the Yes button, then click the Apply Button. [Note that the sizes are equal]

Repeat these steps for each VMS file.

Notes

• If you enter the VMS size in MB incorrectly you will get a message box saying
  
  ëFile physically exists (current size = xx MB, desired size = yy MB)
  Do you want to continue?
  
  Click the No button [Note the sizes are unequal] and re-enter the correct size.

• If you entered the full path of the VMS file incorrectly, then you will NOT get a message box telling you that the file already exists and telling you the size. Click the Undo button, then try again by clicking the Add button.

Restarting the mvBase server

• On the mvADMIN | Server page, you will see that the FileLoad checkbox is now checked.

• Select the mvBase server service (if installed) or the mvBase server application.

• Uncheck the FileLoad checkbox. You will get a message box saying
  
  ëWARNING: a FileLoad is required due to VMS file modifications. Do you want to continue.í
  
  In this circumstance it is perfectly acceptable to start the server without doing a FileLoad. Click OK.

• Now start the mvBase server (application or service) clicking on the START button.

• Finally, if you had copied the VMS files earlier on instead of moving them, then now go back and physically delete them from their original locations using Windows Explorer.