Log Files to be delete

[dolphin]

1)  nbdb.log which exist in C:\Program Files\VERITAS\NetBackupDB\data can be deleted?

2)  C:\Program Files\VERITAS\NetBackup\db\error\log*

3) C:\Program Files\VERITAS\Volmgr\debug\ltid\*.log

4)  C:\Program Files\VERITAS\NetBackup\db\jobs\ffilelogs\

Are the above files can be deleted?

We are running out of disk space in C Drive (our NBU  Master Servers )

We've diverted the unified logs and all debug logs into Another local drive

Please advise

Thanks

Message Edited by dolphin on 02-25-2009 06:56 PM

[S_H1]

Hi,

1) Do not delete the NBDB.log. This is the EMMDB transaction log file. The NBDB.log is truncated by Catalogbackup performed. Did you setup catalog backup?

2) Sorry, I don't know. Someone help you.

3) Yes. But I recommend to stop the NBU during delete. And, You can set up log rotation to insert DAYS_TO_KEEP_LOGS parameter in the vm.conf.

4) I suppose do not delete it.

Message Edited by S.H on 02-26-2009 12:17 PM

[dolphin]

Thanks.

Any other log files for Veritas which can be deleted?

[S_H1]

What type of log files?

You've diverted the unified logs and all debug logs into Another local drive.

Also, You mentioned the NBDB.log(1), the Error log(2), the MM debug log(3), and the JobDB log(4).

Anything else?

Message Edited by S.H on 02-26-2009 01:55 PM

[S_H1]

Sorry, The ffilelogs(4) can be deleted.

Check this.

"DOCUMENTATION: How to manually remove jobs from the NetBackup Activity Monitor which are in a queued state, and cannot be canceled or killed, or removed by cycling the NetBackup services/daemons. "

http://support.veritas.com/docs/278498

[Karthikeyan_Sun]

These should be the documents you should while handling with Logs !

http://seer.entsupport.symantec.com/docs/279590.htm

http://seer.entsupport.symantec.com/docs/281360.htm

http://seer.entsupport.symantec.com/docs/279339.htm

http://seer.entsupport.symantec.com/docs/279295.htm 

[F_J]

As it has already been mentioned, NetBackupDB\data\nbdb.log will never be truncated unless a catalog backup policy is run and finishes successfully. The only other workaround is to enable circular-style logging of nbdb with the new nbdbadmin.exe tool new included in 6.5.2 and above. There might be a command-line equivalent that I don't know... yet ;)

Message Edited by F J on 02-26-2009 02:22 PM