An administrator navigates to NetBackup Management > Catalog, and selects Action: Import. After clicking the Search Now button, the following message…

The error message "Found no images matching the selection criteria that were ready for phase 2 import" indicates that the prerequisite first phase of the import process has not been completed. Cohesity's integration with NetBackup uses a two-phase catalog import. Phase 1 involves initiating the import from the NetBackup Master Server, which prepares the necessary backup image metadata. Phase 2 is performed from the Cohesity UI to search for and import the prepared images. The administrator is attempting Phase 2 without having first executed Phase 1. Therefore, running the "Initiate Import" command is the required step to make the catalog images discoverable by Cohesity.

A. increase the “Catalog cleanup wait time” in the Clean-up host property: This NetBackup setting controls retention of expired catalog entries and is unrelated to preparing active catalog data for import into Cohesity.

B. run the “Recover the catalogs” wizard: This is a NetBackup disaster recovery tool used to restore the NetBackup catalog itself from a backup. It is not part of the Cohesity integration workflow.

C. enable Catalog > Override default priority, and increase the Job Priority value: This setting adjusts the execution priority of an import job that has already started. It cannot resolve an issue where no importable images can be found.

1. Cohesity TechDocs

"Veritas NetBackup Integration Guide": In the section "Import NetBackup Catalog and Data

" the guide details the two-phase workflow. It states

"On the NetBackup Master Server

run the nbuimporthandler.py script to start Phase 1 of the import process... This script prepares the metadata of the NetBackup backup images that you want to import... In the Cohesity Dashboard

start Phase 2 of the import process." This confirms that initiating the import (Phase 1) is a mandatory prerequisite to searching for images in the Cohesity UI (Phase 2). The error message directly results from skipping Phase 1.