How Indexing Works

In this article

    When you run a backup job with the file indexing option enabled, Veeam Backup & Replication indexes the machine file system, collects indexing data and writes it to the GuestIndexData.zip file. The GuestIndexData.zip file is first stored in a temporary folder on the Veeam backup server.

    As soon as the backup job completes, Veeam Backup & Replication notifies the local Veeam Backup Catalog service. The service saves indexing data in the Veeam Backup Catalog folder on the Veeam backup server. During the next catalog replication session started on Veeam Backup Enterprise Manager, indexing data from the Veeam backup server is replicated to the Veeam Backup Catalog on Veeam Backup Enterprise Manager server. By federating indexing data from all connected Veeam backup servers, the Veeam Backup Catalog service on Veeam Backup Enterprise Manager creates a global catalog for the whole backup infrastructure.

    Veeam Backup & Replication supports file-level restore not only for machines included in guest catalog but also for the machines that are not indexed. Indexing may be disabled at the time of restore point creation, or indexing operation may fail. In this case, the restore point of a Windows machine is mounted to the backup server that manages the job, and the restore point of a non-Windows machine is mounted to the helper appliance.

    Then a user will be able to locate the necessary files and folders and perform restore operation. To learn more about mount operation, refer to the Veeam Backup & Replication User Guide and to the Search and Restore of Machine Guest Files section of this guide.

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.