Video Screencast Help

Estimating size for FSA Reporting Database

Created: 29 Oct 2012 • Updated: 29 Oct 2012 | 3 comments
Trafford's picture
This issue has been solved. See solution.

Is there a guideline for sizing FSA reporting databases for EV 9 and / or 10?

ie an indication of how much data per file scanned is stored in the data base, or conversely database size per million files scanned, or such like.

None of the Installation, Admin, Planning, Reporting, or Performance guides seem to have any indication.

I found the rather dated (2010)  Technote TECH70262 - Sizing guidelines for Enterprise Vault databases (EV8), which gives the default initial sizes, of the dbs, and then the rather unhelpful statement :-

"Ensure that there is adequate space for the database to grow as monitoring data is added."

That's exactly what I am trying to do, but I cannot find any info from which to make any kind of calculation as to what "Adequate" might be.

Perhaps someone with a running FSA reporting DB can make a rough calculation.

Thanks

 

Comments 3 CommentsJump to latest comment

JesusWept3's picture

So based on the SQL Best Practices that Rahul posted, its on page 23 and has the following

Estimated (MB) = ((4.248f)+(0.339fv)+(2.218fr)+(0.536tr)+(0.61fvur)+(0.11fvr))/1000

 

s

Total number of file servers

u

Average number of users per file server

v

Average volumes per file server

t

Total number of unique file types

r

Historical retention period (days – recommended 30)

 

Unfortunately, the documentations a little messed up, it says S = file servers, but i think it must mean F
Also MB should be /1024, not /1000

But basically
F/S = 100 (File Servers)
U = 1000 (avg users per server)
V = 5 (volumes per server)
T = 60 (unique file types)
R = 30 (Data Retention)

That would be 8.73GB according to that calculation

 

Trafford's picture

Thanks Guys, exactly what I was looking for.

as I mentioned I did find Tech70262, but it wasnt terribly helpful.

I spent a good couple of hours searching around FSA Size database etc, I am suprised it didn't turn up the excellent SQL sizing guide, possibly because I often included EV9.

You know it never ceases to amaze me that this kind of info isn't included in the documentation. This sizing is absolutely fundamental to implementing a product like EV.

It is ludicrous that one should have to go scratching around for it.

To supplement RahulG's Google link to the document, here is the link to DOC5365,

"Symantec Enterprise Vault 10.0: SQL Best Practices Guide" 

in the Symantec Knowledgebase

http://www.symantec.com/business/support/index?pag...

John Gowing - Symantec EV Exchange STS

DFA Solutions

Cape Town