More on vmphyinv and bephyinv

Whether you run vmphyinv or bephyinv to inventory a robot is determined by what kind of robot and media server you have.

vmphyinv

Use vmphyinv on Backup Exec media to physically inventory the media contents of a robotic library or standalone drive and update the volume database. vmphyinv runs on all supported media server platforms. vmphyinv must be used when inventorying Backup Exec media on UNIX platforms, and before performing Phase I imports of fresh Backup Exec media.

bephyinv

Use bephyinv to inventory Backup Exec media in API robots on Windows media servers to make fresh Backup Exec media known to Backup Exec and NetBackup. bephyinv works with all robot types but runs only on Windows media server platforms.

If Backup Exec media needs to be used in API robots on UNIX media server platforms, the ADAMM GUID field of the Media Manager volume record needs to be manually updated using the unsupported options vmchange -g or vmadd -a.

To find out the media GUID of the Backup Exec media, mount the media in the drive and wait for the drive to become ready. Once the drive becomes ready, dump the ltid shared memory tables (ltid -tables option) and get the media GUID from the appl_guid field of the drive status table.

bephyinv may not be supported in future releases. Instead, vmphyinv will be used. vmphyinv cannot, however, be used with the -auto_correct option provided by bephyinv. Also, vmphyinv cannot be used for taking an inventory of API robots.