FortiAnalyzer
FortiAnalyzer can receive logs and Windows host events directly from endpoints connected to EMS, and you can use FortiAnalyzer to analyze the logs and run reports.
atahir
Staff
Staff
Article Id 339726
Description This article describes how to perform File system check on FortiAnalyzer when it is in a High Availability (HA) setup
Scope FortiAnalyzer
Solution

A file system check, also known as fsck, is a utility used to verify and repair the consistency of a file system on a storage device. When a file system check is performed, it scans the disk for errors, inconsistencies, and corruption in the file system structure.

 

The main purposes of a file system check are:

  1. Detecting and repairing errors: It identifies and fixes issues such as bad sectors, lost clusters, and directory errors that can cause data loss or system instability.
  2. Ensuring data integrity: Checking the file system structure, helps maintain the integrity of data stored on the disk.
  3. Optimizing performance: Resolving file system errors can improve the overall performance of the storage device.
  4. Preventing future problems: Regular file system checks can help prevent more serious issues from occurring in the future. Performing periodic file system checks is essential for maintaining the health and reliability of storage devices and ensuring the integrity of data stored on them.

Follow the steps below to perform a file system check on FortiAnalyzer units.

 

Verification Process (Pre-check):

  1. Verify HA Status: Ensure both units are synced and operational in the High Availability (HA) cluster.
  2. Check Log Synchronization: Confirm that logs between both units are fully synced.

 

File System Check Process:

FortiAnalyzer A – Primary Unit

  1. Access the primary unit of the FortiAnalyzer HA cluster.
  2. Run the following command to initiate the file system check:


diagnose system fsck harddisk

 

  1. When prompted, type ‘y’ to confirm the operation.
  2. The system will automatically reboot.
  3. During the reboot, FortiAnalyzer B will be promoted to primary status and will begin collecting logs.
  4. While FortiAnalyzer A is offline, it will check and repair its file system.
  5. Once the file system check is completed, FortiAnalyzer A will come back online as the secondary unit.
  6. Allow enough time for the log synchronization process to complete.
  7. Perform the verification steps outlined above to confirm HA status and log synchronization.
  8. After confirming that FortiAnalyzer A is fully synced and operational, proceed with the file system check on FortiAnalyzer B using the same steps.

 

Related document:

High Availability