Maximum DB size in Netbackup 3.4.1 ? and other woes ...

Hi there,

Does anyone know what the maximum size the internal database of NetBackup
3.4.1 can reach ?
Ours has been running for about 3-4 years and the database is at 47Gb ...
lately we have been having some issues with Netbackup and are wondering if
it's starting to creak at the seams.

Netbackup has been loosing track of what tapes have been loaded in the
library drives and then flagging the drives as down ... we've picked over
the library and are fairly certain it is sound ...
also when a drive fails in one library it seems to constipate Netbackup to
the extent that the other drives in other libraries get downed as well ...
odd.

Are there any tools to quickly check the database ? "bpdbm -consistency" (I
think) takes FOREVER! Plus even if it should finish and find problem images
I don't think there is a built in tool to fix them!

Anyone have some words of wisdom to impart ?

Thanks

Mark

In theory the size of the NBU db can be as large as your filesystem
can handle. We ran into the 1TB limit on Solaris and had to split
masters. Methinks 47gb should not be an issue. Currently the 2
masters are again approaching 1TB, 850gb and 840gb respectively.

As for fixing it, the pre-4.5 cat was text and much easier to deal
with IMHO. I believe Veritas has some tools in their PS group but
that will cost you, obviously.

I doubt the issues you're having are cat related, they sound more like
bugs or media issues. What type of server, how beefy, how many
clients, are they backed over LAN and at what speeds, SSO, fiber
channel?

Given current info that's my wisdom wad for ya.

~F

On Sat, 31 Jan 2004 21:01:45 +1300, "Mark Smith"
wrote:

Hi there,

Does anyone know what the maximum size the internal database of NetBackup
3.4.1 can reach ?
Ours has been running for about 3-4 years and the database is at 47Gb ...
lately we have been having some issues with Netbackup and are wondering if
it's starting to creak at the seams.

Netbackup has been loosing track of what tapes have been loaded in the
library drives and then flagging the drives as down ... we've picked over
the library and are fairly certain it is sound ...
also when a drive fails in one library it seems to constipate Netbackup to
the extent that the other drives in other libraries get downed as well ...
odd.

Are there any tools to quickly check the database ? "bpdbm -consistency" (I
think) takes FOREVER! Plus even if it should finish and find problem images
I don't think there is a built in tool to fix them!

Anyone have some words of wisdom to impart ?

Thanks

Mark

Hmmm, thanks for that, food for thought.
We do have a new server on the way, think we will do some testing and see
what happens.

Thanks

Mark


"Faeandar" wrote in message
...
In theory the size of the NBU db can be as large as your filesystem
can handle. We ran into the 1TB limit on Solaris and had to split
masters. Methinks 47gb should not be an issue. Currently the 2
masters are again approaching 1TB, 850gb and 840gb respectively.

As for fixing it, the pre-4.5 cat was text and much easier to deal
with IMHO. I believe Veritas has some tools in their PS group but
that will cost you, obviously.

I doubt the issues you're having are cat related, they sound more like
bugs or media issues. What type of server, how beefy, how many
clients, are they backed over LAN and at what speeds, SSO, fiber
channel?

Given current info that's my wisdom wad for ya.

~F

On Sat, 31 Jan 2004 21:01:45 +1300, "Mark Smith"
wrote:

Hi there,

Does anyone know what the maximum size the internal database of NetBackup
3.4.1 can reach ?
Ours has been running for about 3-4 years and the database is at 47Gb ...
lately we have been having some issues with Netbackup and are wondering
if
it's starting to creak at the seams.

Netbackup has been loosing track of what tapes have been loaded in the
library drives and then flagging the drives as down ... we've picked over
the library and are fairly certain it is sound ...
also when a drive fails in one library it seems to constipate Netbackup
to
the extent that the other drives in other libraries get downed as well
....
odd.

Are there any tools to quickly check the database ? "bpdbm -consistency"
(I
think) takes FOREVER! Plus even if it should finish and find problem
images
I don't think there is a built in tool to fix them!

Anyone have some words of wisdom to impart ?

Thanks

Mark