Enable SIS on existing mailbox and Journal archives

[Itegral]

Current Environment: WIndows 2012, EV 10 and SQL 2012 and Exchange 2010

Quick question: around single instance; we have  exchange mailbox archives and Journaling Archives under the same VSG. SIS is not enabled at the monent. If we enable it now, will it apply on all the existing archives and reduce the archives sizes?

1. What potentially be the impact on resources (EV, SQL.. finger print DB size etc. and SQL performance)? and,
2. Potential impact on storage.. performance and size (of course that depends on amount of duplication) but thoughts are welcome.

[ChrisLangevin]

Quick answer: no.

From the EV Administrator's Guide > Day-to-day administration > About managing vault store groups and sharing > Changing the sharing level of a vault store:

"Note: You can rerun the Configure Sharing wizard at any time, but changes you make to the vault store sharing levels do not act retrospectively."

I expect that that answer moots your other two questions as well.

--Chris

[GertjanA]

SIS is not retro-active. Whatever is in the archives now, is not 're-sissed'. If you enable SIS, from that point on anything that is archived will be SIS'ed, but not what is already in the archive.

the performance guide has guidelines on what to expect. It all depends on how much you archive.

The fingerprint database will not grow huge, but will grow ofcourse. Indexes remain the same, data storage used will be less. You need to take in account that if you have expiry running, data storage might not shrink as much as you expect it to, due to shared items needing to stay available. I suggest to have 2 VSg's (thus 2 FPdb's) one for Journal Archives, one for Mailbox Archives, but that is up to you.

Here is a starting document: http://www.veritas.com/docs/000102276

[Itegral]

Thank you guys. Having said that, is there a 3rd party tool that would assist in achieving SIS on historical archives, just wanted to understand?

[GertjanA]

not as far as I know. I believe the only way to achieve this is to move the archives (using move archive) into a new VSG which has 'share within group'. After the move, you will need to delete the original archive, to free space on storage, but that will put pressure on storage, indexes and SQL.

[Itegral]

you mean move both mailbox and jorunal archives to new one VSG, not two separate VSGs and enable sharing. This may apply SIS on the existing archives?

[GertjanA · Accepted solution]

Wether you use 1 or 2 VSG's is up to you. If you want to follow this route, you need to create the VSG, a Vault Store, a Vault Store Partition, enable SIS, then migrate. If you migrate before configuring SIS, you have the same situation (except you have twice the data :) )