Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Netbackup Relational Database Netbackup 7.0

Created: 14 Nov 2010 | 2 comments
Ialahmad's picture
Ialahmad
0 0 Votes
Login to vote

Dear All;

today my netbackup services stop I check and I found the cause is from full Log directry No free space

I delete log but some problem exist

I try to run Netbackup Relational Database but It not running.

for your Info Netbackup 7.0 installed on VCS

Discussion Filed Under:
, , , ,
Group Ownership:
PartnerNet Group

Comments

Riaan Badenhorst's picture
14
Nov
2010
1 Vote +1
Login to vote
Riaan Badenhorst
Accredited
Certified

Hi,   What O/S?   Have you

Hi,

 

What O/S?

 

Have you offline your service group and tried to online it again?

 

What errors are you seeing in the system logs?

Regards,

Riaan Badenhorst

ITs easy ;)

***If the answer provided resolves your issue, please mark the appropriate solution.***

Zahid.Haseeb's picture
14
Nov
2010
0 Votes 0
Login to vote
Zahid.Haseeb
Accredited

For your future

For your future reference: 

(Netbackup Admin Guide for Windows-I Page # 77 )

 

TIP: For future there is a TIP for you. Manage your logs lenght so your space cant full 

 

Keep logs
The Keeplogs property specifies the length of time, in days, that the master server
keeps its error catalog, job catalog, and debug log information. NetBackup derives
the Backup Status, Problems, All Log Entries, and Media Log reports from the
error catalog. Also limits the time period that these reports can cover. When this
time expires, NetBackup also deletes these logs (that exist) on UNIX media servers
and UNIX clients.
Specify how many days you want to keep the logs in case you need the logs to
evaluate failures. For example, if you check the backups every day, you can delete
the logs sooner than if you check the backups once a month. However, the logs
can consume a large amount of disk space, so do not keep the logs any longer than
necessary. The default is 28 days.
 
 
 
 
Netbackup Admin Guide for Windows-I ( Page # 64 )
 
 
Resolving full disk problems
If the NetBackup installation directory fills up, such as with logging files, a number of problems can result. NetBackup may become unresponsive. For example, NetBackup jobs may remain queued for long periods, even though all NetBackup processes and services are running.
To diagnose the problem, check the following:
■ The NetBackup Resource Broker (nbrb) log may have database connection errors in it. These errors indicate failed attempts to establish connections to the nbemm database. The following is an example of such errors in the nbrb log:
7/20/2005 12:33:47.239 [RBDatabase::connectDatabase()] ODBC
connection failed.
ErrMsg: [Sybase][ODBC Driver][Adaptive Server Anywhere]Disk
write failure
'Fatal error: disk write failure C:\Program
Files\VERITAS\NetBackupDB\data\NBDB.log' -- transaction rolled
back ErrCode:
-1Sqlstate: HY000
The nbrb log (originator ID 118) is written in /usr/openv/logs (UNIX) or
install_path\NetBackup\logs (Windows).
See the “Using logs and reports” chapter for more information on unified
logging.
To correct the situation, do the following:
1 Clear up disk space in the directory where NetBackup is installed.
■
You may need to delete log files manually, reduce logging levels, and adjust log retention to have log files automatically deleted sooner. Refer to the sections on logging levels, log file retention, and how to configure unified logging in the following chapter for assistance: “Using logs and reports.”
■
Consider moving the NetBackup unified logging files to a different file system. See “Changing log file locations” on page 82 for assistance.
2 Use the Activity Monitor to verify that the NetBackup relational database service is running. This service is the NB_dbsrv daemon on UNIX and the “Adaptive Server Anywhere - Veritas_NB” service on Windows.
 
3 If the NetBackup relational database service is stopped, note the following:
■
Do NOT stop the nbrb service. If you stop the nbrb service while the NetBackup relational database service is down, it can result in errors.
■
Restart the NetBackup relational database service.
 
Note: Verify that the NetBackup relational database service is running. If it is not and you remove files to free up disk space, you may not fix the problem. The relational database service must be restarted to allow the Resource Broker (nbrb) to allocate job resources.

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
270,016