Managing NerveCenter - Managing the Database - Backing up the Database - Backing up the Database Using the SerializeDB Application -
Previous: Backing up the Database     Next: Restoring the Database

Backing up the Database Using the SerializeDB Application

SerializeDB exports the data in your database to a text file. When you use the SerializeDB GUI on Windows, you can choose the text file format -- you can have SerializeDB export the data to a NerveCenter flat file database or a serialized ASCII file. You might want to export data from a database on Windows to a flat file database if you want to use the resulting file on a UNIX machine without having to import the data.

If you are backing up a UNIX flat file database, all of the files that make up the database must be in the db directory. See Database Formats for more information.

If your NerveCenter uses MS Access and want to serialize a NerveCenter v3.5 or v3.6 database, there are certain steps you need to take. See Upgrading an Access Database for more information.

 
  To back up the database using the SerializeDB application:

  1. Do one of the following to start SerializeDB:
  2. Select the Export database to file radio button.
  3. Specify the format by selecting one of the following radio buttons:
  4. Do one of the following:
  5. Select Start.

    On UNIX, SerializeDB starts exporting the data.

    On Windows, you must specify the data source for the database. The Select Data Source window is displayed.

    Select Data Source Window

    seldatasrc.gif

    1. Select the Machine Data Source tab.
    2. Select the data source for your NerveCenter database. Then select OK.

      See your Microsoft ODBC documentation for more information about selecting data sources.

When the data has been exported, SerializeDB displays a message letting you know that the data transfer was successful.

When running SerializeDB from the command line, you can only export to a serialized file (.asc file).


Previous: Backing up the Database Next: Restoring the Database
Please send comments or corrections to Information Development
This file was last updated on 10 October 2000