Video Screencast Help

Reinitialized Backup Replicated Centera Vault Store

Created: 19 Mar 2013 • Updated: 02 Apr 2013 | 2 comments
This issue has been solved. See solution.


We have FSA Vault store in one centera, and we have a replicated centera for backup.

Both centera is confired as Mirror at disk level.

We want to reinitialized the backup centera and confiure that as parity. EV Data will be replicated again after reinitialization of backup replicated centera.

Has anyone had any experience with this? Will it cause any issues with EV?

Many Thanks

Operating Systems:

Comments 2 CommentsJump to latest comment

Tremaine's picture

There is the potential that this may well impact EV in some fashion.

1. For normal archiving purposes EV needs to check the replica before it can perform post processing of the archived content and based on your policy convert the originals to shortcuts. Ideally the replication should be replicating all your new content first and if so then you shouldn't have any issues, however if not then you may well have a problem in that regard as you could end up with a large backlog.

2. If you are using Centera collections then it would also be best to disable Storage Expiry if you are using that option until your replication is complete, as EV will check the Replica first and if it gets a failure creating a connection to it then it will stop Expiry. However if the connection succeeds and it just fails to find the replicated data then it will continue to expire from the Local (primary) as expected.

Other than that I only ever get to hear the worst case scenario's, never the good ones so cannot really comment on how uneventful it would be :(

Perhaps someone else has a good experience with this.