In NetBackup 3.4, 4.5, 5.0, and 5.1, what does "Fatal Global Database consistency" error message mean?

Page 1 of 3

Support Home | Supported Products A to Z

Knowledge Base
Document ID: 291323 Search
http://support.veritas.com/docs/291323
E-Mail this document to a colleague Advanced Search Op
Other Support Re
In NetBackup 3.4, 4.5, 5.0, and 5.1, what does "Fatal Global Database consistency"

Support Forum
error message mean? Ask an expert. J
product discussi
Forum communi

Manage Cases
Details: Submit and man
cases using MyS
Question: In NetBackup 3.4, 4.5, 5.0, and 5.1, what does "Fatal Global Database
Contact Techni
consistency" error message mean? Find the support
for your region.

Changes:
Was this article h

Adding or replacing tape drive. j Yes n

k
l
m
n j No
k
l
m

Change Controllers/HBAs. If any information wa

Change firmware on drives, controllers, switches, bridges, etc. information you were
provided, please let u

Change in zoning in SAN switches. feedback will help us
service.
(Enter comment her

Environment: NetBackup 5.X, 4.5, and 3.X. Does not apply to NetBackup 6.X and later
with EMM Database. The documentation with change(s) applied to environment are no (Optional Email Add
longer available.

Condition: Accessing device management in NetBackup Graphical Administrative NOTE: Comments e

Console, and/or running tpautoconf command. NOT receive support
need Symantec Ente
support, please click

Cause: In NetBackup version 5.X, 4.5, and 3.X, the media server's the devices databases
are three flat files (ltidevs, robotic_def, and globDB). These databases along with
actual hardware information must be consistent. An inconsistency is when there is at least
one information among these four that is out-of-sync with the other.

Additionally, in an SSO environment where there are multiple media server sharing the
same set of tape drives, these 4 areas also must be consistent among media server
sharing drive(s). Two common inconsistencies are differences or changes in serial
number(s) and/or device path(s) between one or more media servers, and/or one or more
database(s).

Inconsistency can also occur if there is a direct modification to a database without making
the similar modification to the other databases to keep the consistency. Default UNIX path
to the flat file databases is: /usr/openv/volmgr/database/. Default Windows path is:
C:\Program Files\Veritas\Volmgr\database\.

file://H:\study\netbackup\New Folder\Fatal Global Database consistency.htm 7/6/2010

In NetBackup 3.4, 4.5, 5.0, and 5.1, what does "Fatal Global Database consistency" error message mean? Page 2 of 3

Preventive Care:
When any changes are being made to devices that are defined to be used under
NetBackup's databases, all changes must be updated. For example, when a drive is
being replaced, the NetBackup database record drive it is replacing should be noted, then
after it is replaced, updated on the media server where the change occurs. If the drive is
shared among different media server, than the update must also occur on each media
server impacted. Practice to replace the tape drive are documented in these various
technotes: 259835, 269870 (4.5FP7 and later), 271366 (4.5FP7 and later).

Solution:
Delete and rebuild the devices databases:
(a) Backup devices databases (globDB, ltidevs, robotic_def)
(b) Print out current configuration.
(c) Delete all devices from the media servers
(d) Delete the devices databases.
(e) Re-configure new database for the devices.

NOTE: Deleting the devices from all devices databases is not the only solution, but is
proven to be the quickest, and easiest solution. It is possible and yet very time consuming
to find and identify the inconsistent data, the use advance command line techniques to
edit the database and make corrections. For any corrections and changes to take affect
stopping and restarting services on the master server and the media server(s) where
correction are being made is necessary.

Supplemental Material:

System: Ref.# Description

DEFECT:
ATGID: 2336

Products Applied:
NetBackup Enterprise Server 5.0 MP7, 5.1
MP6

Last Updated: April 29 2008 12:57 AM GMT

Expires on: 12-20-2008
Subscribe to receive critical updates

file://H:\study\netbackup\New Folder\Fatal Global Database consistency.htm 7/6/2010

In NetBackup 3.4, 4.5, 5.0, and 5.1, what does "Fatal Global Database consistency" error message mean? Page 3 of 3

NetBackup Enterprise Server

Application: Documentation, Faq, Informational

Languages:
English (US)

Operating Systems:
Solaris
8.0, 9.0

Symantec World Headquarters:

20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support:
http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or
http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY
OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC
SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR
LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT
APPLY.

file://H:\study\netbackup\New Folder\Fatal Global Database consistency.htm 7/6/2010