1. Support
  2. Knowledge base
  3. 100034093

Important Update: Cohesity Products Knowledge Base Articles

All Cohesity Knowledge Base Articles are now managed via the Cohesity Support Portal: https://support.cohesity.com/s/searchunify. The Knowledge Base articles available here will not reflect the latest information or may no longer be accessible.

NetBackup device mappings file shows a version mismatch between EMM and local file.

Article: 100034093
Last Published: 2017-05-26
Ratings: 0 0
Product(s): NetBackup

Problem

After updating the device mappings file, the tpext -get_dev_mappings_ver command reveals a version mismatch:

C:\Program Files\Veritas\Volmgr\bin>tpext -get_dev_mappings_ver
device mappings version in the EMM database is 1.140
device mappings version from the local file is 1.127
Local device mappings file is not up-to-date
 

Error Message

Local device mappings file is not up-to-date.

Cause

This is an indication that the NetBackup Device Manager service was not restarted after applying the updated mappings file.  For general background see:

Veritas NetBackup (tm) Server / Enterprise Server Device Mappings Package for Windows Servers
http://www.veritas.com/docs/000025758

Solution

Restart the NetBackup Device Manager service as shown in the following example.  At the conclusion, the versions should match.

C:\Program Files\Veritas\Volmgr\bin> net stop "netbackup device manager"
The NetBackup Device Manager service is stopping.
The NetBackup Device Manager service was stopped successfully.


C:\Program Files\Veritas\Volmgr\bin> net start "netbackup device manager"
The NetBackup Device Manager service is starting.
The NetBackup Device Manager service was started successfully.


C:\Program Files\Veritas\Volmgr\bin> tpext -get_dev_mappings_ver
device mappings version in the EMM database is 1.140
device mappings version from the local file is 1.140
Local device mappings file is up-to-date

Was this content helpful?

Article Languages