06-21-2021 12:23 AM
06-21-2021 12:29 AM
the easy way:
check the size of the directory
c:/program files/veritas/netbackupdb/data for windows
or
\usr\openv\db\data for linux
06-21-2021 12:56 AM
If my memory is correct, you can also use "NbDbAdmin.exe" command to get detailed status on Windows or dbadm option 2 on Linux/Linux.
/Nicolai
06-21-2021 03:20 AM
Your memory is correct Nicolai ...
You will need to reset the nbdb passwd first, as by default it is random
nbdb_admin -dba <new passwd> (can answer 'n' to the question)
A NBDB rebuild might bring the size down , will take a while though during which time you'll need to stop NBU and only have NBDB running.
It could be the case that one of the db tables is massive - I think one of the audit tables can be an issue. Not sure of anyway to find this other than to run :
/usr/openv/db/nbdb_unload </some output dir with 1TB space> and then see which .dat files are the biggest, then look these up in reload.sql to see what they are.
06-21-2021 04:33 AM
If i change nbdb password will it effect the backups?
actually we are planning to upgrade from 8.1.1 to 8.3.0.1 before that do i need to perform rebuild/reorganize of EMM if its size is more then 4-5GB?
06-22-2021 03:21 AM
No, changing NBDB is safe, but now I think about it you should restart the services on the master as it can upset secure comms on occasion.
06-22-2021 04:45 AM
Hi @Dav1234
More simply, look at the last catalog backup (incremental or full). The first stream that runs AND writes data (it shoud be the third stream of the backup) is backing up the NBDB. This will give you the size of the EMM (aka NBDB).
David