|
HOW TO:
Use a FLEETMATE JET Database Backup Copy
Applies to:
FLEETMATE JET
database files. This does not apply if your FLEETMATE database is on SQL
Server.
Background:
As you exit FLEETMATE, by default it will make a backup copy of your
JET database file. Also by default the backup directory path will be set to C:\Users\Public\FLEETMATE\Backup.
This path should be adjusted under Options | Preferences... to an
external device, such as an external hard drive, USB Drive, or similar storage
device. When you exit the software, FLEETMATE makes a copy of your live
JET database, appends a date/time-stamp to the
end of the file name, and then stores the backup copy into the specified backup folder.
A database
backup copy will look like:
FLEETMATE.fdb.20060701-113233
Where:
-
FLEETMATE.fdb
is your database name
-
.20060701
is the date (yyyymmdd) the copy was made
-
-113233
is the time of day the copy was made
Locating the
Most Recent Backup Copy:
The date/time-stamp represents the date/time that the backup copy was made,
NOT the last time the file was updated internally. This enables you to
distinguish between these two criteria. Use the Date/Time-stamp to locate your
most recent backup copy. The greater the serialized time value, the later it was
in the day.
Replace the Damaged database with your most recent backup:
You should NEVER open and use a backup copy as-is. You must first rename
the backup copy to what your actual database is currently named, then place the
renamed backup copy into the appropriate folder. This process involves simply
removing the date/time-stamp from the end if the filename. Once this is done,
you can use this file to replace (overwrite) your damaged database file.
When you restart FLEETMATE, you will see the prior contents of your database at
the time it was last backed up.
IMPORTANT:
If you're
running FLEETMATE on a stand-alone PC, you must redefine the Backup Path to an
external storage device. This way, if the hard drive in your PC fails, you
will have an externally stored backup copy to rely upon.
Any server that contains your FLEETMATE
JET database should always be configured to run nightly backups. Having backups on
external media will protect you in the event of a hard drive failure.
|