The NetBackup Java Console shows incorrect filenames when browsing a NDMP backup

Problem

The NetBackup Java Console displays filenames incorrectly if the filename contains multibyte characters such as an alpha character.

Error Message

The ndmpagent log shows:

[Debug] NB 51216 ndmpagent [No context] 6 [ConnectionToNas::InputHandler] InputHandler entered - session = 0x8714f50
[Debug] NB 51216 ndmpagent [No context] 5 [ConnectionToBrm::SendFileHistory] FH TO BRM: Fsn - 0 0 0 0 0 0 0 11 X /vol/nbuvol
[Debug] NB 51216 ndmpagent [No context] 5 [ConnectionToBrm::SendFileHistory] FH TO BRM: Ddi - 0 0 0 0 102 0 0 22 2 this_is_a_test.t
[Debug] NB 51216 ndmpagent [No context] 5 [ConnectionToBrm::SendFileHistory] FH TO BRM: [!ERROR String -> wide character string]
[Debug] NB 51216 ndmpagent [No context] 5 [ConnectionToBrm::SendFileHistory] FH TO BRM: [!ERROR String -> wide character string]

To gather this log, please run the following command: 

/usr/openv/netbackup/bin/vxlogview -p nb -o ndmpagent -d all > /tmp/ndmp.log

Cause

Files stored in the NetApp filer can have filenames with multibyte characters such as the alpha character, for instance; RECUPERACIαN.

NDMP currently does not support unicode filenames as part of the file history database. Instead, the unicode names are converted into the NFS character set before being returned.

Therefore; NDMP clients that run on Unix platforms that can display the extended NFS character sets can display the file history database.

For more information, please consult the following document:

BUG ID 14965 - NDMP does not support unicode filenames and prints bogus file history databases.
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=14965

Both Java and Windows "Backup, Archive and Restore" consoles exhibit this behavior.

Additional Information:

http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=14965

https://now.netapp.com/NOW/knowledge/docs/ontap/rel732/html/ontap/tapebkup/frameset.html

http://now.netapp.com/NOW/knowledge/docs/ontap/rel733/html/ontap/tapebkup/GUID-DE8BF53F-706A-48CA-A6FD-ACFDC2D0FE8A.html

Solution

To resolve this, reconfigure the NDMP policy and add the following 2 lines in the top of "Backup Selection":

SET HIST = Y
SET NDMP_UNICODE_ FH = Y
<Path/to/data>

The NDMP_UNICODE_ FH specifies that a Unicode name is included in addition to the NFS name of the file in the file history information. This option is not used by most backup applications and should not be set unless the backup application is designed to receive these additional file names. The HIST variable must also be set.