Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to enable UTF-8

Created: 17 Nov 2011 • Updated: 21 Nov 2011 | 12 comments
This issue has been solved. See solution.

I am trying to enable UTF-8 on Netbackup 7.1  I tried the solution on Symantec site by myself and it did not work.

http://www.symantec.com/business/support/index?pag...

The link above states not to edit without support. I tried, and now know why you need supports help. I thought I would ask here before trying to place a call.

Symantec recommends that this file not be edited without assistance from technical support. NetBackup may not start if the server.conf file is edited.

Install_path\VERITAS\NetBackupDB\conf\server.conf is read when the SQL Anywhere service is started. The SQL Anywhere service gets all configuration information from this file:

 -n NB_server_name -x tcpip(LocalOnly=YES;ServerPort=13785) -gd DBA

-gk DBA -gl DBA -gp 4096 -ti 0 -c 25M -ch 500M -cl 25M -zl -os 1M -o

"C:\Program Files\Veritas\NetBackupDB\log\server.log"

In this example, server_name indicates the name of the SQL Anywhere server. Each Sybase server has a unique name. Use the same name that was used during installation. If a fully qualified name was used at that time, use a fully qualified name here.

Note:
If this name is changed, the Enterprise Media Manager cannot connect to the database.
Table: Commands used in the server.conf file

Comments 12 CommentsJump to latest comment

Marianne's picture

Not sure what exactly you are asking?

Did you add -ct+ and now NBU services won't start?

Please post your server.conf before and after the change? As well as <Install Directory>\NetBackupDB\log\server.log.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

nasguy's picture

Yes, I added -ct and the service did not start.

Yasuhisa Ishikawa's picture

What do you want to enable UTF-8 for? Changing Sybase parameters have no effect to backup behavior.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Yogesh9881's picture

Let us know why you are editing that file ?

what you want to achive ?

If this post has helped you, please vote or mark as solution.

Before break-up, make sure you have a good backup.....  ;-)

Nicolai's picture
I haven't heard any need for changing Netbackup  Character encoding yet. Netbackup will out of the box backup localized files files with non-us charters.
 
Please take a look at the Netbackup 7.1 Release notes Titled : NetBackup Internationalization and localization
 
http://www.symantec.com/docs/DOC3643

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

SOLUTION
nasguy's picture

Thanks Nicolai.

From the release notes, Pages 70 and 71 it looks like chinese character name not supported in policy backup selection, But I don't see any of these to be installed on my system (it is a test bed environmnet so not production). There are enough restrictions in the release notes whcih lead me to believe chinese volume name may not be supported, on a Windows Master Server Policy type. The search goes on, and if thats the case, I will make sure to mark this as solved.

Certain database agents have restricted support of localized environments.
At the time of this release, the following database agents have restricted
support of localized environments:
■ NetBackup for DB2
■ NetBackup for Informix
■ NetBackup for Oracle
■ NetBackup for SAP
■ NetBackup for SharePoint
■ NetBackup for SQL Server with Snapshot Client
■ NetBackup for Sybase ASE
When you use any of these agents, the use of localized characters (for example,
non-ASCII, multi-byte characters) is not supported in:
Operational notes
NetBackup Internationalization and localization
70/71

■ The path names that are specified in the policy Backup Selections, like <<<<<<<<
script, template, or batch file locations
That applies to all supported platforms, including the use of previous
versions of those NetBackup database agents with NetBackup 6.0 servers.

nasguy's picture

I'll say this is the solution, its not supported without much configuration. I am afraid I can't change my locale settings on my server, so for now, its not supported, and is a problem with the vendor. Thanks to all

nasguy's picture

My impression was the server.conf needed to be edited for UTF to work. This is an NDMP backup. Here is the message I get. I am able to backup this volume using Backup Exec so it apears that NDMP NAS server is able to translate the Chinese named volume.

11/17/2011 11:45:51 AM - begin writing

11/17/2011 11:45:52 AM - Error ndmpagent(pid=3964) NDMP_LOG_ERROR 0 ERROR: FILESYSTEM var [/流水线式的数量] is not in a valid FileSystem.

11/17/2011 11:45:52 AM - Error ndmpagent(pid=3964) NDMP backup failed, path = /流水线式的数量      

11/17/2011 11:45:52 AM - Error bptm(pid=5176) none of the NDMP backups for client 172.22.112.14 completed successfully  

11/17/2011 11:45:53 AM - Info bptm(pid=5176) EXITING with status 99 <----------       

11/17/2011 11:45:53 AM - end writing; write time: 00:00:02

NDMP backup failure(99)

11/17/2011 11:45:58 AM - Info ndmpagent(pid=0) done. status: 99: NDMP backup failure 

Marianne's picture

What is the current status of the master server since the server.conf update?
All services up and running?

Which make/model NAS?

Please post your policy config:
bpllist <policy-name> -U

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

nasguy's picture

Marianne,

When service conf was changed, service would not start. I removed -ct and the service started again.

I was banging my head on bpllist syntax, but see its bppllist smiley

I think this nails it down. Failing to translate it from syntax, see below. Whats odd it that GUI lists it correctly. Perhaps I do need to modify that serverconf file.

C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist.exe UTF -U
------------------------------------------------------------

Policy Name:       UTF

  Policy Type:         NDMP
  Active:              yes
  Effective date:      10/26/2011 14:09:51
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           MyDickStoragePool
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no
  Application Discovery:      no
  Discovery Lifetime:      28800 seconds

  Granular Restore Info:  no
  Ignore Client Direct:  no
  HW/OS/Client:  NDMP          NDMP          172.23.101.14

  Include:  /µ╡üµ░┤τ║┐σ╝ÅτÜäµò░ΘçÅ                                <<<< Failed to Translate it.

  Schedule:          Full
    Type:            Full Backup
    Frequency:       every 175 days
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 1 (2 weeks)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     18:00:00  -->  Monday     05:00:00
          Monday     18:00:00  -->  Tuesday    05:00:00
          Tuesday    18:00:00  -->  Wednesday  05:00:00
          Wednesday  18:00:00  -->  Thursday   05:00:00
          Thursday   18:00:00  -->  Friday     05:00:00
          Friday     18:00:00  -->  Saturday   05:00:00
          Saturday   18:00:00  -->  Sunday     05:00:00

  Schedule:          Differential-Inc
    Type:            Differential Incremental Backup
    Frequency:       every 25 days
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 1 (2 weeks)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
          Sunday     18:00:00  -->  Monday     05:00:00
          Monday     18:00:00  -->  Tuesday    05:00:00
          Tuesday    18:00:00  -->  Wednesday  05:00:00
          Wednesday  18:00:00  -->  Thursday   05:00:00
          Thursday   18:00:00  -->  Friday     05:00:00
          Friday     18:00:00  -->  Saturday   05:00:00
          Saturday   18:00:00  -->  Sunday     05:00:00

nasguy's picture

here is my server conf

C:\Program Files\Veritas\NetBackupDB\CONF>cat server.conf

 -n NB_w2k8-shrike1 -x tcpip(LocalOnly=YES;ServerPort=13785) -gd DBA -gk DBA -gl
 DBA -gp 4096 -ti 0 -c 25M -ch 500M -cl 25M -zl -os 1M -o "C:\Program Files\Veri
tas\NetBackupDB\log\server.log"

Yasuhisa Ishikawa's picture

Check locale settings of master server host and the host on which you launched Administration Console to edit file list. If both are UTF-8, pathname will be registered in UTF-8 into file list, and will be passed to NDMP host as it is.
I suppose that either or both is not UTF-8, and you registered some non-UTF-8 multi-byte strings into file list.
For example, in Japanese mixed encoding environment(eg, UTF-8 RHEL master with SJIS Windows client), multi-byte pathname leads to backup failure.

FYI: By Release Notes page 68.

Do not mix non-English version of Windows and UNIX platforms.
If you mix non-English versions of Windows and UNIX platforms, differences
in operating system architecture and encodings may cause non-English file
names and folder names to be displayed incorrectly within the user interface.
That may cause functional failures.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan