WallySimmonds
16 years agoLevel 3
Vault Store Growth
Hey guys,
Another potentially noobie question.
I've inherited another site where I've just created another vault store partition as the last one was reaching critical levels. I've since been called to discuss what the site can do to reduce the amount of growth they have on the vault store volumes - judging by current trend information, it's using around 12gb p/w. This is for a 1000 (approx) user site. Now, we've got a similar setup elsewhere, and growth is similar there, so I'm not really sure we *can* do anything.
Now, I've been told to see if SIS is working correctly (I'm not entirely sure how to do this). The other option is to look at retention policies I guess, atm it is archiving from the Journal after 30 days. Does anyone else have any suggestions?
Forgive me if my question is retarded, I'm only slowly getting my head around this product and only have a limited amount of time to dedicate learning it.
Thanks,
Wally
Another potentially noobie question.
I've inherited another site where I've just created another vault store partition as the last one was reaching critical levels. I've since been called to discuss what the site can do to reduce the amount of growth they have on the vault store volumes - judging by current trend information, it's using around 12gb p/w. This is for a 1000 (approx) user site. Now, we've got a similar setup elsewhere, and growth is similar there, so I'm not really sure we *can* do anything.
Now, I've been told to see if SIS is working correctly (I'm not entirely sure how to do this). The other option is to look at retention policies I guess, atm it is archiving from the Journal after 30 days. Does anyone else have any suggestions?
Forgive me if my question is retarded, I'm only slowly getting my head around this product and only have a limited amount of time to dedicate learning it.
Thanks,
Wally
- Wally,
How can you be arching the Journal after 30 days this is nearly instant? So unless you using mailbox archiving for the journal there is no way in doing this.
As for your question I would consider setting up retention and expiry, if space is an issue. There is no way you can really stop ingesting data as you will just move the problem to Exchange which is not a good idea.
You can look at upgrading to Enterprise Vault v8 as this brings OSIS between Vault Stores which you don't have in 2007, in 2007 you only get SIS within Vault Stores.
--wayne