Please view the FAQs for more technical assistance
Backup Strategies
Backup
is done in a very unconventional, but more stable way than what you may be used to. It cannot be backed up by normal "file copy" programs that many IS groups use. This is because the transaction log must be "made dirty" into the database and truncated. Special SQL commands must be sent to the database engine on the server by a proprietary program for these things to happen. If your system was setup by On Time Support, your server is most likely backing itself up if you are using Windows NT Server or Windows NT Workstation on your server. For those that are using Windows 95/98 and Novell, the special program must still be executed, but it must be done manually. See our applications note
"Backing up your MET/BASE Server" to learn more about how to set this up on your system.
Windows 2000 Server problems with Sybase 5.5 (MET/CAL 6.1) and Metrology Xplorer
If you have updated your server to Windows 2000, you may have a problem with the Sybase data engine starting and initializing the TCP/IP Network Link. Another problem may occur if you have Metrology Xplorer installed on a Windows 2000 server, such as the CGI will not execute. Sybase has released a patch for Windows 2000 server. You should back up your system prior to applying the patch. Download the zip file and install the patch. Be sure to shut down the existing Sybase Data Engine first before applying the patch. You will probably have to reboot the server also. On Time Support does not accept any responsibility for the operation of the Sybase patch. You can
download the patch here.
Windows 2000 Client problems with Sybase 5.5
(MET/CAL 6.1)
There may be some cases where the client Network Requester may not connect to the server over your network TCP/IP link. You may get an error that the client computer cannot not connect to the server. If this occurs, there may be a broadcast problem with the Network Requester. Depending on how your ODBC is configured, you may need to make the following changes:
-x tcpip{HOST=servername;DOBROADCAST=NO}
Replace "servername" with the network name of your MET/CAL server. For Window 2000, you will also need the DOBROADCAST=NO.
NOTE: In some situations, you may need to reverse the order of "dobroadcast" and "host" so that the "dobroadcast" parameter is listed first, before "host". If for some reason the above listed command line does not operate properly, then switch the order as described and try again.