Database backup considerations – DAVIS FMS 3.9.3 DriveRight (8186) User Manual
Page 32
DriveRight FMS User's manual
|
Database Backup Considerations
If you have GPS-enabled DriveRight and CarChip Fleet Pro devices, you will rapidly accumulate
a large amount of data in the
table due to the frequency of GPS logging and to the
database table due to the frequency of vehicle speed logging.
To avoid the database from becoming unmanageable, you can export both the GPS and CarChip
Parameter Logs database tables more frequently than your normal backup interval, and delete
GPS and Carchip Parameter Log data by using the
. By doing this you still have trip
data for your reports while at the same time decreasing the database size.
The following is an example of backing up and exporting information from the GPS table:
1. Set
(Preferences command in the Setup Menu) to select the
number of months you want to keep active in the database.
2. Suppose that you have some DriveRights and CarChips with GPS data enabled. Your
GPS Table will grow much more rapidly than the Trips Table. But you still want to keep
the last three (3) months of trip data for reporting purposes.
3. Since DriveRight FMS does not support backup of individual database tables, use
to create individual backups of the GPS Table.
4. Refer to the
Database Size Recommendations Table
to determine how frequently you
should
the GPS Table. Once you determine the export frequency, you will need to
manually repeat this process.
5. In this example, you want to keep one month of GPS data active in the database.
6. Select
Export GPS from the Export Menu.
7. Enter a file name for the GPS export data similar to this: gps_10_apr_2007.txt.
Note: Be careful about naming the GPS export file so that you don't lose previously exported
data.
9.
Go to the
Database > Maintenance > GPS command
and delete all GPS data older than
your export frequency from Step 5. In this example it is one month.
Note: The same process can be followed for exporting and deleting CarChip Parameter Log
records you no longer want to keep in your active database.
See also:
Active Database Size Recommendations
Back to
20