Video Screencast Help

EV 8.0 - Adding New Vault store partition

Created: 10 Feb 2010 • Updated: 21 May 2010 | 3 comments
-The GodFather-'s picture
This issue has been solved. See solution.

 Hi anyone here kind to help me on Enterprise Vault 8.0 Service Pack 1? I'm planning to add a new vault store partition, but then it states on the EV wizard that the connection is "very bad". Can I proceed on this wizard and just ignore it or should I do something else? Thanks!

Comments 3 CommentsJump to latest comment

GertjanA's picture

Hello Godfather,

It seems to be a ' look at this and improve'  feature.
I have found that if you click test several times, it suddenly shows ' good '  everywhere.

Having a ' bad' / very bad, does not stop you from creating a new partition. You should however look into the possible cause of this. (networkconnectivity, processor usage etc.)

Thank you, Gertjan, MCSE, MCITP,MCTS, SCS, STS

MirrorSphere's picture

I have also experienced this little beauty as well, firstly it says bad initially then flicks to everything being good and dandy!
Can Symantec expand as to what the code is actually doing in this check?  Is it a latency check?

What do you want to do with your data today?

TonySterling's picture

I believe all that is occurring is a ping between servers.  It is taking an average of the results.

there is this tidbit in the Install and Config guide.

"Enterprise Vault provides a connectivity test to estimate connection speeds across sample network connections. The relevant wizards prompt you to run the connectivity test when you create a new vault store group or partition, or when you configure sharing. The connectivity test can help you create a sharing regime with an acceptable level of performance. To assess performance, the connectivity test measures the average round-trip time for a number of ping requests. If you have disabled ping in your environment, use your own tools to decide if the performance is acceptable. We recommend a round-trip time of 1 millisecond or less."

Could be that the code doesn't see all the results so when it averages them out it comes up 'very bad'.  :)

Just run the test again as Gertjana and EV-Assist say and make sure it is ok.