To change the location of where the NetBackup 6.0 Unified logs are written to, perform the following steps:

From a command prompt, path to:
%install_path%\Veritas\NetBackup\bin

Now enter the following command:

vxlogcfg -a -p 51216 -o ALL -s LogDirectory="absolute path to new log location"

*Note: Include the quotes around the absolute path name.

To review the unified log configuration, run the following command:
vxlogcfg -p 51216 -o Default -l

DOCUMENTATION: How to manually change the path where NetBackup log files are located.

I tried Deeps ways, but it didn't work out.

I configured like this.

vxlogcfg -a -p 51216 -o ALL -s LogDirectory="\\servername\nbu logs\"

and fired a manual backup , but the logs were generating on the defualt location, even i tried restore too.

Is there something i need to configure after this??

You need to restart Netbackup services.

But you also need to verify changes to the nblog.conf file with the moved directory location according to this TN
All detailed inside here.

DOCUMENTATION: How to configure Veritas NetBackup (tm) 6.x to write unified log files to a different directory

Thanks Stuart for the guidance.
That pretty cool doc.

Thanks alot

Ritz

Hi Stuart ,

Oe morething i need to ask if i want to redirect the logs to network share drive or NAS, how can that be accomplished?

Ritz

You will need to ensure that the network/NAS drive is available at all times. Secondly, map the network drive as local drive letter.  Use this drive_letter:\folder when adding new location for logs. Thirdly, check that logon account for all NBU services have write permission to the share - LocalSystem will probably not have sufficient rights.
Methods given to you so far will only relocate unified logs. If you also need to move legacy logs (bprd, bpdbm, bpbrm, bptm, etc), there's another TechNote for that and requires registry changes.

Thans Stuart,
But in technote it states

Warning:  If the instructions in this technote are followed and the log directories are changed, unexpected behavior can occur in NetBackup.  Observed issues have included the inability to perform alternate client and alternate path restores. Vaulting and other areas of the product may also be affected.  Making these changes is not advised without first having guidance from Technical Support.

we perform alternate path restores most of the days.....
Please advice..

Thanks Ritz

It's a choice that you have to make. If you feel uncomfortable doing it, then log a call with Symantec. Personally I would not recommend using a network drive.

I have personally followed this TechNote in the past to move the logs to a different location on the master (local, not network) and the server is still running fine (was in the meantime upgraded from 5.1 to 6.5 and is still logging to new location).

Thanks all for the suggestions....

One other issue is that for audit purpose i need extract the reports from master server admin console.
In master server's properties cleanup is keep logs is set as 31 days.

I believe due to this setting i can able to view reports on admin console for 1 month.

If i need to view 1 year reports, i need to set to 366 days, doin so which logs are goin to remain in master server for 1 year, so that only that particular logs need to ship to another location...

Or is there any settings to be done to view 1 year report in admin console.

Please advice ..

Thanks
Ritz

@ ritesh

multiple issues in single thread will create future searches tizzzy.. since your query is perfectly answered marked this thread as solved and start a new thread for auditing.

Ok i will do that

Thanks
Ritesh