β06-04-2012 09:12 AM
Hi all,
The following statements keep appearing in all the Netbackup 7.5 guides:
"Beginning with the NetBackup 7.5 release, the images files are now stored in the NetBackup relational database.
The images files contain the metadata that describes the backups."
"Starting with NetBackup 7.5, all backup image metadata is stored in the NetBackup relational database (NBDB).
Previous versions stored this data in either the NBDB or the flat ASCII files (image header files),
depending on the source of the image information.
The following describes the advantages of this change:
- Eliminates the consistency issues for any data that previously existed in multiple databases.
- Improves the product search performance, especially in large catalogs.
- Improves the performance of restores, policy scheduling, and image cleanups."
The change makes perfect sense, but I am looking for some clarification for the following.
I understand that the so called "image database" is this directory structure that stores all the .f files for all the clients.
It is the "largest part of the NetBackup catalog".
Basically, it stores the metadata for every single file for every single backup, ever. So it is understandably big.
- Install_path\VERITAS\Netbackup\db\images
And then there is the directory that stores the "actual" SQL Anywhere database files (contains the all important NBDB.db):
- Install_path\VERITAS\NetbackupDB\data
I have a feeling that someone is going to point out that my understandings are totally off.
Regardless, the following is what I'm trying to find out.
In one of our environments, the image database directory with its thousands of .f files is around 400GB.
All the database files from the NetbackupDB\data directory combined don't even come close to that size.
I'm curious about what exactly do they mean when they say version 7.5 stores all image files in the NetBackup relational database (NBDB).
Does that mean that all .f files from the db\images directory will disappear, and the NBDB.db in the NetbackupDB\data directory would grow over 400GB?
Well, to find out, I setup a little testing environment with 7.5 installed.
And I don't see that happening.
Backups are still generating .f files in the Install_path\VERITAS\Netbackup\db\images directory for each client. Some are huge (broken down into multiple .f pieces).
So then, "what" exactly are now stored in the NetBackup relational database in version 7.5, that previous versions don't?
I ask because the .f image metadata files are definately still separated and are still being created in their same old db\images directory.
I hope my question makes sense.
Thanks all,
RLeon
Solved! Go to Solution.
β06-04-2012 10:37 AM
β06-04-2012 10:23 AM
I understand that the so called "image database" is this directory structure that stores all the .f files for all the clients.
It is the "largest part of the NetBackup catalog".
Basically, it stores the metadata for every single file for every single backup, ever. So it is understandably big.
- Install_path\VERITAS\Netbackup\db\images
100% correct
The EMM SQL DB in NetbackupDB\data is much smaller - this contains many things including the media DB, the volDB, device config, many config sttings and so on.
At 7.5 it is the header files that go into the EMM SQL DB, not the .f file.
The image DB (before 7.5) contains .
The image header file (<policy name>_<ctime>_FULL (or INCR or UBAK) )
This contains details of where the image is stored (and a few other bits).
The .f file (of the same name, but .f on the end) contains a list of what files were backed up, and correctly, is the big bit.
It is the header file that goes into EMM, the .f file stays where it is.
If the .f file exceeds (I think 2MB) the contents are broken into mutiple files in the catsore dir, and the .f file is then 72 bytes in size. This makes use of 'b trees' which is more efficient to search when the file gets big.
Martin
β06-04-2012 10:37 AM
β06-04-2012 06:23 PM
Everything makes sense now. Thanks for the detailed explanation Martin.
RLeon