Recreating the NetVault device tree (4043360)

Certain library failure conditions can be caused by a corruption in NetVault's internal Device tree. Issues could be:

• Library shows offline, drives show online...
• library showing online but no barcodes would show up.
• Run a job and it stays waiting for media, diagnose shows "No suitable media/drive pair available"

This could be the result of a corrupt NetVault device tree. A component of the NetVault database (NVDB)

Recreation of the Device Tree Structure in the Netvault Database

1. Make screenshots of the names of the Libraries, as well as the Configuration and Performance tabs of all the drives, so that when you re-add them, you can use the same names and settings.

• Run a NVDB backup.

• Stop the NetVault service.

• Browse to the MediaDatabase Directory(Paths Listed Below), you'll find two directories called "Index" and "Records"
  - Windows Default Locations: C:\Program Files\Quest Software\NetVault Backup\db\MediaDatabase\Indexes
  - Windows Default Locations: C:\Program Files\Quest Software\NetVault Backup\db\MediaDatabase\Records
  - Linux/Unix Default Locations: /usr/netvault/db/MediaDatabase/Indexes
  - Linux/Unix Default Locations /usr/netvault/db/MediaDatabase/Records

• Find the "Devicetree" file (one in each directory)... You must ONLY "Delete" the "Devicetree" file, or move it outside of it's home directory completely (cannot just rename it, if you just rename it... a new one will "NOT" regenerate when you restart NetVault).

• Restart the NetVault Service.
  This will remove the existance of any device you previously had (physical and virtual), so you will need to re-add them manually & reconfigure them. You'll want to take "note", prior to do any of this... the names of the Libraries, so that when you re-add them... you're bring them back with same name and do not have to reconfigure your backup jobs to look for the new Library name.