Veritas-bu

Re: [Veritas-bu] massive catalog growth

2011-11-14 13:07:44
Subject: Re: [Veritas-bu] massive catalog growth
From: "smpt" <smpt1 AT peppas DOT gr>
To: "'Sanders, Nate'" <sandersn AT dmotorworks DOT com>, "'Preston, Douglas'" <dlpreston AT lereta DOT com>, <VERITAS-BU AT mailman.eng.auburn DOT edu>
Date: Mon, 14 Nov 2011 20:07:32 +0200

The DD does not involve with NBU database.

Find the larger files in the image database and check what has change at the specific clients. (You may find that new files ware added)

 

 

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Sanders, Nate
Sent: Monday, November 14, 2011 6:50 PM
To: Preston, Douglas; 'VERITAS-BU AT mailman.eng.auburn DOT edu'
Subject: Re: [Veritas-bu] massive catalog growth

 

That makes sense for the 600mil image files, and was sort of my guess, but what about the existing policy that I simply changed the location of the image from DSSU to a Data Domain? Would just that change still warrant a 40GB growth in the catalog over a 24 hour period? We were only backing up < 100 unix hosts, I would guess.

 

From: Preston, Douglas [mailto:dlpreston AT lereta DOT com]
Sent: Monday, November 14, 2011 10:38 AM
To: Sanders, Nate (DS); 'VERITAS-BU AT mailman.eng.auburn DOT edu'
Subject: RE: massive catalog growth

 

There is an entry per file in the catalog, a million files at 1k each will cause more catalog space than a thousand  1tb files

 

Doug Preston

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Sanders, Nate
Sent: Monday, November 14, 2011 8:29 AM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] massive catalog growth

 

As of a few weeks ago we saw our NBU7 catalog explode from 80GB to a peak of 238GB. My initial belief was this was part of us standing up a 2nd media server for the office which was linked to a Data Domain 630. But after reviewing the historical graphs, it is very clear this increase happened just a couple weeks ago. The obvious thing I started doing 2 weeks ago, is backing up our new Isilon cluster and also introduced these backups to a new Data Domain 670. More specifically, our Isilon which contains around 600 million image files that are less than 128k each.

 

How in the world could 10TB of image data suddenly cause the catalog to triple in size? Yet previously adding 18TB of data from a new media server (the dd630) didn’t even cause more than a 20GB increase in the catalog ?

 

I’m at quite a loss here to understand how this increase happened so quickly. The real issue here is that the catalog filesystem has filled up 3 times, causing nbpem to crash, and backups to grind to a halt. The last time this happened had nothing to do with the Isilon backups, but happened as a result of changing the media destination from some existing OS backups to go to a Data Domain 670, instead of their old DSSU locations. The isilon also points to this same DD670. Could that be the real issue here? Is there something different about how the catalog stores information when it resides on a Data Domain?

 

and any attachments from your system.


This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu