Re: Is it possible to have a SyncIQ policy not lock the target directory?

[Brad Schlicht]

I have played around with this and I believe the answer, at least to the best of my knowledge, is no. I have used rsync, robocopy, isi_vol_copy, or isi_vol_copy_vnx (depending on the source) in the past when I ran into this issue.

On Monday, August 3, 2015 at 12:54:57 PM UTC-5, ZacMatic wrote:

I'm using SyncIQ to migrate some data from one cluster to another. There are some cases where it would be nice to be able to merge several source directories into one target directory. Additionally, there is data on a non-Isilon NAS that is migrating to an Isilon cluster, and some of the target directories are the same.

It would be incredibly useful if there was a way I could unlock a SyncIQ target directory without losing the replication state. Is this possible?

Thanks,
Zac Buschmohle

[Josh Hampton]

Yes, you absolutely can.  It's an undocumented command and likely unsupported by EMC support.  You should only use this with a COPY policy and not a SYNC policy as you can cause some interesting behavior....  

Here are the directions:

On the target cluster:

1) Identify the Domain ID governing the policy

egrep 'policy-name|domain-id' /ifs/.ifsvar/modules/tsm/config/target_record.xml

The output looks something like this:

    <policy-name>doom-b52-test_mirror</policy-name>

    <domain-id>65539</domain-id>

    <policy-name>mannij1_mirror</policy-name>

    <domain-id>65537</domain-id>

    <policy-name>dottest</policy-name>

    <domain-id>65541</domain-id>

    <policy-name>dirmvtest</policy-name>

    <domain-id>65543</domain-id>

    <policy-name>cp_sync</policy-name>

    <domain-id>65545</domain-id>

    <policy-name>cp_sync2</policy-name>

    <domain-id>65547</domain-id>

    <policy-name>cp_sync3</policy-name>

    <domain-id>65550</domain-id>

    <policy-name>cp_sync4</policy-name>

    <domain-id>65553</domain-id>

2) Make the Domain read/write

/usr/libexec/isilon/isi_domain -x <domain-id>

Where <domain-id> is the output from Step 1

3) To revert after deleting the desired log files, use domain -r:

/usr/libexec/isilon/isi_domain -r <domain-id> 

[saurabh chaudhary]

As per in the Isilon while configuring SyncIQ policy at Source, the last directory stated in the Target Path becomes read-only at the target Isilon.

So in your case you have to create multiple policies at sub-folder level, so that the sub-folder\sub-directories will become read-only. And you can run other copy sessions from other source within the same parent folder.

As stated in my above example with the policy 1\2\3 on Isilon 2 sub-folder 1\2\3 will be read-only, Parent Folder A will be available to accept data from Isilon and other sources.

Use the Source and Target Path on Isilon as:

Source Isilon 1       Target Isilon 2            Policy

/ifs/1                       /ifs/A/1/                     1

/ifs/2                       /ifs/A/2/                     2

By this your Parent folder A will be write enable for other data copy.

Main Problem with this approach: creation and maintenance checkup of multiple policies.

Hope this may help you.

----- Saurabh ----