Migration from VNX to Isilon

[Anubhav]

We are migrating some VNX shares (around 15K) to isilon using isi_vol_copy_VNX. There are around 1500 Departments shares and rest 13500 User Shares. 

Setup on VNX

The shares are sitting on VNX Cifs Server, there are 26 cifs servers with each cifs server having it own department and user shares. Departments shares are in Department$ and User shares are in Users$. Each share (also sub-shares)has a $ sign appended at the end. for e.g. share “test_dept” and share “test_user” are like

share name file system path Data Mover

test_dept$ xyz \xyz\department\test_dept xyz

test_user$ abc \abc\users\test_user abc

There is a default department$ and users$ share and all dept and user shares are sub share under department$ and user$. In short all the shares are hidden because the client is using mmc snap in to manage shares. 

There are 26 cifs services on VNX with some department and user shares. We have decided to create 26 access zone, one access zone on isilon per cifs service on VNX and each access zone will have corresponding department$ and user$ shares. The reason for this is because the helpdesk team will connect to each access zone using the smart connect zone name using MMC as they are connect to VNX cifs server today. In short they want to keep the same setup.

base directory path for access zone /ifs/name-of-cluster/name-of-org/cifs-server-name-on-vnx

The issue we are facing

1. isi_vol_copy_vnx is solid in moving directories, but it lacks the ability to create shares and copy local groups and permissions. - So is there any utility which copy the shares/share permission
2. We tried using the "sharename$" utility to create a share with a $ at the enc in isilon to connect to MMC snap in, but the problem is that we can only go down till Dept$ or User$ (and all the sub-shares under department$ and users$ have “$” sign at the end), so basically we want to drill down to one more level to see all the shares under dept and users, Which means either we create all 15000 shares in isilon with $ at the end so that they can be managed by MMC Snap IN.
3. Can we use the %U expansion variable utility to work around this issue.

A little lost here on how to tackle this situation, any help would be appreciated.

Thanks

Anubhav

[saurabh chaudhary]

Have tried with lgdupe; sharedupe and emcopy utility by EMC.

That may help in your case to migrate shares and local groups from virtual cifs server on vnx to isi-smart zone name.

Regards,

Saurabh

--
You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-group+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.