Status Code 257

[Sam_Bailey]

Hi,

I'm trying to troubleshoot an issue on a Netbackup 5.1 Enterprise Server installation on a SunOS 5.9 machine. The vault jobs keep failing with error code 257 - cannot create log file. I have verified with the unix admin that the log folder exists based upon the log path information in the debug file and that the account, along with root, have rw access to it (they can go in and create files themselves under these accounts). There is also disk space available (133MB - low but the log files aren't that big).

Here is a snippet of the log file:

09:12:38.219 <2> vltrun: bpvInitEnv: bv_readxml.cpp.362: returning from function bpvInitEnv()
09:12:38.219 <2> bv_readstus(): entering function
09:12:38.219 <2> vltrun: vltrun: bv_readxml.cpp.598: Succeeded in reading parameters from XML
09:12:38.219 <2> vltrun: bpvault_env: bpvault_env.c.1394: change_command=/usr/openv/volmgr/bin/vmchange
09:12:38.219 <2> vltrun: bpvault_env: bpvault_env.c.1416: tl8_eject=/usr/openv/volmgr/bin/vmchange
09:12:38.219 <2> vltrun: bpvault_env: bpvault_env.c.1455: query_command=/usr/openv/volmgr/bin/vmquery
09:12:38.219 <2> vltrun: bpvault_env: bpvault_env.c.1537: mmhost=sun4800m1
09:12:38.219 <2> vltrun: bpvault_env: bpvault_env.c.1584: log_directory=/usr/openv/netbackup/vault/logs
09:12:38.219 <2> vltrun: bpvault_env: bpvault_env.c.1617: report_directory=
09:12:38.220 <2> vltrun: bpvault_env: bpvault_env.c.2099: returning from bpvault_env, status = cannot create log file (257)
09:12:38.220 <16> initOldVltEnv():
09:12:38.220 <32> vltrun main(): (cannot create log file )
Exit error: cannot create log file
EXIT status = 257

[zippy]

Sam,


http://www.sun.com/products-n-solutions/hardware/docs/pdf/875-3612-10.pdf
page 234



http://www.sun.com/products-n-solutions/hardware/docs/Software/Storage_Software/VERITAS_NetBackup/


JD

[Sam_Bailey]

Thanks for the reply but the link you gave me is to the standard troubleshooting error supplied by Veritas. I covered all of that in my initial paragraph. I will keep looking tho.

[zippy]

tell the admin to #touch log_whatever

look at the permissions on the parent dirs

JD

[Stumpr2]

Sam,
this is interesting item from your post:

>09:12:38.219 <2> vltrun: bpvault_env: bpvault_env.c.1584: log_directory=/usr/openv/netbackup/vault/logs


I'm not quite sure what is happenning there but that path is wrong. Please sse
Documentation: Vault logging information in the VERITAS NetBackup (tm) Vault 4.5 System Administrator's Guide for UNIX and Windows, Page 139, is incorrect.
http://support.veritas.com/docs/258600

It is for vault with 4.5 but it is interesting..??

Perhaps you have set a parameter wrong somewhere in the configuration?

There was a major change in vaulting from 4.5 to 5.x including the file structure under ...netbackup/vaultMessage was edited by:
Bob Stump

[Sam_Bailey]

It's very possible they upgraded from 4.5 to 5.1.

[Stumpr2]

There were a couple of vaulting patches that needed to be applied before migrating from 4.5 to 5.x or was it from 3.4 to 4.5??
I don't have the particulars because I've changed jobs again. But if you want to search through some old junk you can use this link to the peer-to-peer usergroup.
http://news.support.veritas.com/dnewsweb.exe?utag=&cmd=xsearch&group=veritas.netbackup.datacenter.english&group=veritas.netbackup.datacenter.english&key=vault&action=Search+Headers

myself, I would open a call with VERITAS , er symantec

[Ankur_Kumar]

Dear Sam,
I believe the path for the log files would be
/usr/openv/netbackup/logs/vault/

where you need to create the vault directory and in case of Netbackup 6.0 you need to create the nbvault directory as well

/usr/openv/netbackup/logs/nbvault/

i hope this works

chiao

Ankur Kumar