Loss of Recording Files

Procedure

1. Check whether recording index data in the database is lost.
2. Log in to the database using the pgAdmin client. Select a camera on which recording files are lost, and obtain camera_id of the camera.
   NOTE:

   The following operations use camera_XXXX as an example.

3. Choose Databases > scu > Schemas > public > Tables, find out the recording index list device_XXXX and recording event list event_XXXX, as shown in Figure 1.
   Figure 1 Data tables
   
   
4. Click  . In the Query dialog box, enter the following command:

   select to_char(to_timestamp(start_time), 'yyyy-MM-dd HH24:MI:SS'), to_char(to_timestamp(stop_time), 'yyyy-MM-dd HH24:MI:SS') from device_XXXX;

5. Click
   
   to execute the command. In the Output pane window shown in Figure 2, you can view the recording start time and end time as well as check whether recording files are lost.
   Figure 2 Viewing the recording time
      
   
   • If no recording file is lost in at least one table, go to 2.
   • If recording files are lost in both the tables, go to the next step.
6. Check whether index file data of the lost recording exists.
   1. Log in to the server as the root user.
   2. Run the cd /RecordIndexFile/bsm/XXXX command.
   3. Run the ls -l command to check whether recording index files are lost based on the index file creation time, as shown in Figure 3.
      Figure 3 Viewing recording index files
      
           

      If yes, go to 2.

      If no, go to 3.

      public_sys-resources/icon-note.gif NOTE:

      A recording index file is generated every hour on the hour, recording index information in the hour.

7. Repeat the preceding operations to check for loss of database index data and files on other cameras.

 NOTICE:

1. Log in to the backup server as the root user.
2. Run the cd /home/ivstool/bin command. You enter the bin directory.
3. Run the ./restore.sh command.

   The system asks you whether to continue the restoration. The message is as follows:

   Please confirm to continue restoring ivs service. (yes or no)?

4. Enter yes.

   The system prompts you to enter backup data to be restored.

   NOTE:

   If the timeout duration is 10s and you do not enter anything after 10s, the system exits the restoration operation by default.

5. Enter the digit as prompted.     

             NOTE:

1. Verify that the system starts data restoration. After the system displays a message indicating the restoration is complete, the system restarts.

1. Run the su - postgres -c "/home/postgres/bin/pg_ctl status -D /DB_DATA/data/" command to view the database status.
   • If the database is normal and the following command output is displayed, go to 4.

     pg_ctl: server is running (PID: 16858)
     /home/postgres/bin/postgres "-D" "/DB_DATA/data"

   • If the database is abnormal, go to the next step.
2. Run the /home/ivstool/bin/service.sh restart pgdb command to restart the database.

• If the restart fails, go to /DB_DATA/data/pg_log, obtain database logs, and contact Huawei technical support engineers.
• If the database can be restarted, go to the next step.

If the fault is rectified, no further action is required. If the fault persists, contact Huawei technical support engineers.