Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Using Replicated CIFS share for EV Vault Store partition

Created: 29 May 2013 • Updated: 04 Jun 2013 | 7 comments
This issue has been solved. See solution.

Hi All,

I'm in the process of consolidating multiple EV Storage partitions across 15+ drive letters and its index drives into one big CIFS share for simplicity and replication reason, so is this configuration possible with EV 9.0.4 or do I need to migrate this into EV 10.0.3 then perform the consolidation afterwards ?

So here's the situation for the existing configuration on the block level storage replicated between two disk array (EMC SnapView):
2 x 511 GB Index drives RAID5
15 x 511 GB Vault Store Partition drives RAID5

proposed solution File level CIFS share replication using (VNX Replicator):

1 x 1 TB Index drives RAID5
2 x 5 TB Vault Store Partition drives RAID5 

any thoughts or comments would be greatly appreciated.

Operating Systems:

Comments 7 CommentsJump to latest comment

AndrewB's picture

CIFS isnt recommended for index volumes but i dont see any reason why you couldnt consolodate the vault store partitions. the process is not specific to any version of EV.

what you could do for the indexes is after you upgrade to EV10, create that new storage location for the 64bit indexes (EV10 only) and over time upgrade your old indexes from 32bit to 64bit. eventually they'd all be written to the new index drive and you could get rid of the old one.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

John Santana's picture

Andrew, that does make sense after all.

So in this case before the 64 bit index is created does this means that for the best practice or recommended by Symantec, the Index should resides onthe block level storage with drive letter assigned to it ?

if this is the case then the replication is more complex since it involves two different block types

CIFS for Vault Store partition : file level replication
Raw Disk Mapping LUN for Index partition : block level replication 

the reason I'm doing this apart from the low cost storage cosolidation is that I am running out of drive letters.

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

AndrewB's picture

Yes, it is best practice that the indexes are not on CIFS. See:

Enterprise Vault 10.0 - Indexing Design and Implementation Best Practices
padding: 1px;padding-bottom: 3px ;font: 12px Arial; text-align: left;">Article:DOC4250 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 0px;font: 12px Arial; text-align: left;">Created: 2011-06-08 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 1px;font: 12px Arial; text-align: left;">Updated: 2012-04-19 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 1px;font: 12px Arial; text-align: left;">Article URL http://www.symantec.com/docs/DOC4250

Moving your partitions from drive letters to CIFS will free up your drive letters. You can further this along and still keep the indexes on block storage but change them to mount points instead of drive letters.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

SOLUTION
John Santana's picture

ok, thanks for the suggestion and the best practice doco, I don't understand my predecessor who setup the drive before so I was guessing that the initial index partition was not enough therefore they add one more 512 GB LUN for the Index only.

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

AndrewB's picture

are you all set at this point?

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com

John Santana's picture

Hi Andrew,

At the moment I'm preparing the proof of concept as I need to migrate the EV Partition containing those drives out of the existing old SAN because it is running at capacity.

Therefore in this case I'll have to provision two different storage to the EV VM as per your suggestion above including using two different software to do the replication to the DR site, sounds complex and error prone but I guess that is the only way I can do so far.

Fell free to suggest some other low cost alternatives which supports replication to the DR site.

Kind regards,

John Santana
IT Professional

--------------------------------------------------

Please be nice to me as I'm newbie in this forum.

AndrewB's picture

another option since you just said it's a VM you could consider using some of the capabilities of your virtualization platform for DR purposes. probably beyond what we can get into on this forum since it's not EV specific at this point.

Andy Becker | Authorized Symantec Consultant | Trace3 | Symantec National Partner | www.trace3.com