[Intel Navigation Header]

    StorageExpress(TM) System: Replacing a Corrupted File Tracker Database

    
    

    HOW TO REPLACE A CORRUPTED FTS DATABASE

    
       Symptoms:
    
       * Data not found in the FTS browser.
    
    
    
       * StorageExpress unit locks up frequently and unexpectedly.
    
    
    
       * An error message which contains "BO_ " will be displayed in the
    
       activity log.
    
    
    
       * A "Hotel California" error will be displayed on the LCD panel at the
    
       StorageExpress control unit
    
    
    
       * The FTS will constantly prune causing backups to take longer.
    
    
    
       Description:
    
       The power was cycled on the StorageExpress system without a proper
    
       shutdown in Central Console.  
    
    
    
       The StorageExpress system was rebooted during a backup, restore, merge,
    
       purge or prune job.
    
    
    
       Multiple merge jobs were submitted at once.
    
    
    
       Merge job was submitted when a backup job was going.
    
    
    
       Solutions:
    
       There are several methods to clean up the File Tracker System.  The
    
       methods are list below in the order of preference:
    
    
    
       *  If you are using Central Console v1.20.A.E or higher, and have been
    
       using the Self-Backup option, you may use the Self-Restore option to
    
       restore the FTS database.  Once the self restore job is finished, you
    
       can try the jobs again.
    
    
    
       *  Central Console v1.5x has a "Reset File Tracker" button available to
    
       clear the File Tracker.  From the main menu select "Restore," and then
    
       select "Browse File Tracker".  At that point you can click on the "Reset
    
       File Tracker" button.  If this doesn't clear up the corruption you can
    
       clean up the File Tracker manually by following the steps below:
    
    
    
       * Copy the *.btr files from the [SE_name]\sys:nullfts\ directory to the
    
       [SE_name\sys:engine directory.  You can do this by mapping 2 drives to
    
       each directory as follows:
    
            Attach to the StorageExpress system.
    
            map u:= [SE_name]\sys:engine
    
            map v:= [SE_name]\sys:nullfts Ncopy v:*.btr u:
    
    
    
       Note:  When trying to copy the files to the engine directory, an error
    
       may show that the file is in use and you will not be able to copy it. 
    
       This means that the file is in use by Btrieve.  If you are running
    
       Central Console v1.40AE or higher, and you receive an error when copying
    
       the files, click on the connect button that is on the upper left hand
    
       side of the menu bar.  Highlight the StorageExpress system that you are
    
       currently connected to, and disconnect by clicking on the disconnect
    
    
    
       button, then copy the files that start with "fts" from the
    
       SE\SYS:NULLFTS directory into the SE\SYS:ENGINE directory.
    
    
    
       If that does not release the file, you will have to reboot the
    
       StorageExpress system to release these files. 
    
    
    
       * If none of the above steps work, you may have to re-image the
    
       StorageExpress system hard drive from the StorageExpress system
    
       maintenance mode menu.  This will take about 20 minutes. See page 179 of
    
       the "Intel StorageExpress System Reference Guide" for details.
    
    

    Trademark information