-
Title
Newly created VTL shows all media as FOREIGN as nvremovemedia does not delete all media entries -
Description
Following disk failure, a VTL has been removed from NetVault as follows:
- VTL removed from Manage Devices
- VTL entries removed from NV/config/diskdevices.cfg
- All of its associated media deleted from the NVDB using CLI tool 'nvremovemedia'
- VTL folder deleted from disk
After successful removal the VTL is recreated using the same device name and media barcode prefix.
However, once added to NV all media shows as FOREIGN, suggesting there are still entries for the old media in the NVDB despite removal.
-
Cause
This issue is due to a limitation in CLI tool nvremovemedia, tracked under NVBU-17749.When removing media with 'nvremovemedia' CLI tool, media is not deleted from the 'medmgrbarcode' table.When the same media is re-added it is seen as FOREIGN since entries already exist for it in the netvault_mediamanagement database. -
Resolution
For a complete removal of a VTL, including all of its associated media, please follow these steps:
- Remove the VTL from 'Manage Devices'
- Remove the VTL entries from NV/config/diskdevices.cfg
- Delete All of the VTLs associated media from the NVDB using CLI tool 'nvremovemedia'
- Delete the VTL folder from disk
***** At this point it is recommended to perform a NetVault Database Backup ******
- Delete the associated VTL media from the netvault_mediamanagement database under the medmgrbarcode table as follows:
1) Open a elevated command prompt as Administrator
2) Navigate to the ..\NetVault Backup\pgsql\bin folder:
Example:
cd "C:\Program Files (x86)\Quest\NetVault Backup\pgsql\bin"
3) Connect to the NetVault PostgreSQL Database Server:
Example:
C:\Program Files (x86)\Quest\NetVault Backup\pgsql\bin>psql -p 51486 -U postgres
psql (9.2.8)
WARNING: Console code page (437) differs from Windows code page (1252)
8-bit characters might not work correctly. See psql reference
page "Notes for Windows users" for details.
Type "help" for help.
4) Connect to the 'netvault_mediamanagement' database:
Example:
postgres=# \c netvault_mediamanagement
WARNING: Console code page (437) differs from Windows code page (1252)
8-bit characters might not work correctly. See psql reference
page "Notes for Windows users" for details.
You are now connected to database "netvault_mediamanagement" as user "postgres".
5) Verify there are still entries for your old VTL by querying the 'medmgrbarcode' table:
Example:
netvault_mediamanagement=# SELECT barcode from medmgrbarcode where barcode like 'VTL1%' order by barcode;
barcode
---------
VTL1001
VTL1002
VTL1003
VTL1004
(4 rows)
6) Delete the barcode entries left over by the nvremovemedia tool:
netvault_mediamanagement=# DELETE from medmgrbarcode where barcode like 'VTL1%';
DELETE 4
7) Verify there are no more entries in the medmgrbarcode table:
netvault_mediamanagement=# SELECT barcode from medmgrbarcode where barcode like 'VTL1%' order by barcode;
barcode
---------
(0 rows)
You have now removed all entries from the old VTL and you can now recreate the same VTL without having all its media set as FOREIGN.
-
Defect ID
NVBU-17749