开始新对话

未解决

此帖子已超过 5 年

2727

2013年10月7日 19:00

Isilon可写 Snapshot/SyncIQ DR site

最近在学习Isilon,基于我能找到资料,我觉得Isilon没有可写Snapshot来测试,SyncIQ 的目标端也不能暂时变成可写来测试。问了英文的论坛,一个礼拜了没有人回答啊。我再贴到这里。

Hi,

After checking all the documents I can download from Powerlink, it seems there is no way to have writable snapshot and SyncIQ DR site.

Snapshot:

From the snapshot part of , I can only find the "File clones" which share blocks with existing files in order to save space on the cluster. Do we have the "Folder clones" in Isilon(Just like Flexclone in NetApp) or writable snapshot(just like Celerra/VNX FILE)?

SyncIQ DR site:


From ,

Target protection with restricted writes—replication domains

Previous versions of SynclQ strongly recommended that you restrict write permissions on target directories. This is now enforced by SynclQ via protected replication domains. As such, all writes outside of a SynclQ process are disabled on any directory that is a target for a SynclQ job. However, if you break the association between a target and a source, the target then returns to a writeable state. Resolving a broken association will force a full resynchronization to occur at the next job run. Every SynclQ policy has a direct 1:1 association with its target directory, and all sub-directories. Restricted writes prevent modification, creation, deletion, or movement of any files within the target path of a SynclQ job, and prevent movement or creation of hard links to any files into orout of the target path of a SynclQ job.

My understanding is there is NO way to make the DR writable for application test. If we touch the DR site data manually, we need a full copy. Hopefully, Isilon will provide the function like swithover in Celerra/VNX or we can manually change the state in DR site like NetApp. I know we can do failover/failback, but this is not the option for testing purpose.

Lack of the writable snapshot/DR site, we can't perform Application testing.

Thanks very much.

196 消息

2013年10月7日 22:00

7.0以后的SyncIQ据说是可以暂时断开让DR可写的,6.5以前的版本不可以。

这是经销商说的,我没有测试过

7 消息

2013年10月8日 02:00

大白亲自回复啊,真是快。我一会在好好研究测试一下。

50 消息

2013年10月8日 02:00

大侠开始摸Isilon了?呵呵

咨询了一下Isilon的同事,Snapshot是read only by design. 就在你看的那个白皮书里应该有提到从OneFS7.x version, SyncIQ的target是可以在target cluster上改为”allow_write"的。

希望有帮助。

7 消息

2013年10月15日 03:00

今天测试了2次,结果都一样(v7.0.2.1, 本地到本地syncIQ):

1. 正常情况下,target端在cluster命令行和cifs 端都是read -only.

2. failover测试失败:

将target cluster设为allow_write,target端命令行下可以写入文件,但是客户端还是不能写。此时primary段还是可写的。

ClusterTest1-1# isi sync target allow_write local_studentad2_to_local_studentad2_rep

Allowing writes for local_studentad2_to_local_studentad2_rep

ClusterTest1-1#

ClusterTest1-1# isi sync target list                                               

Policy                                   | Source       | Target Path              | Run     | FOFB State    

-----------------------------------------+--------------+--------------------------+---------+----------------

local_studentad2_to_local_studentad2_rep | ClusterTest1 | /ifs/data/studentad2_rep | Success | enabling writes

3. Failback测试:

“sync resync prep” 这个会将primary设为read only,这个和文档说的一样,并将其恢复为上一次同步后的快照,也就是说不管你在上一次同步后做了什么改变,该命令都会丢弃,很危险)

ClusterTest1-1# isi sync resync prep local_studentad2_to_local_studentad2_rep

Starting resync prep for local_studentad2_to_local_studentad2_rep

ClusterTest1-1# isi sync policy report                                            

local_studentad2_to_local_studentad2_rep:

    Start              Stop              Act             Status

    10/15/13 17:51:11  10/15/13 17:51:38 sync            Success

    10/15/13 17:52:19  10/15/13 17:53:09 allow_write     Success

    10/15/13 17:57:07  10/15/13 17:57:25 resync_prep     Success

    10/15/13 17:57:31  10/15/13 17:57:41 resync_prep_domain_mark Success

    10/15/13 17:57:49  10/15/13 17:58:30 resync_prep_restore Success

    10/15/13 17:58:41  10/15/13 17:59:02 resync_prep_finalize Success

"final failback differential sync" 成功结束后Primary端还是read only!!!,且此时的target状态还是和之前一样,即令行下可以写入文件,但是客户端

不能写。

ClusterTest1-1# isi sync policy run local_studentad2_to_local_studentad2_rep_mirror

Running local_studentad2_to_local_studentad2_rep_mirror

ClusterTest1-1# isi sync policy report
local_studentad2_to_local_studentad2_rep:
    Start              Stop              Act             Status
    10/15/13 17:51:11  10/15/13 17:51:38 sync            Success
    10/15/13 17:52:19  10/15/13 17:53:09 allow_write     Success
    10/15/13 17:57:07  10/15/13 17:57:25 resync_prep     Success
    10/15/13 17:57:31  10/15/13 17:57:41 resync_prep_domain_mark Success
    10/15/13 17:57:49  10/15/13 17:58:30 resync_prep_restore Success
    10/15/13 17:58:41  10/15/13 17:59:02 resync_prep_finalize Success

local_studentad2_to_local_studentad2_rep_mirror:
    Start              Stop              Act             Status
    10/15/13 18:00:46  10/15/13 18:01:29 sync            Success
ClusterTest1-1# isi domain list --long
ID    | Root Path               | Type           | Override Date | Def. Ret. | Min. Ret. | Max. Ret. | Autocommit Period| Priv. Del.
------+-------------------------+----------------+---------------+-----------+-----------+-----------+------------------+-----------
65546 | /ifs/data/studentad2_rep| SyncIQ,Writable| None          | None      | None      | None      | None             | Off      
65547 | /ifs/data/studentad2    | SyncIQ         | None          | None      | None      | None      | None             | Off

我觉得这个文档可能步骤不全,或者和我的环境有关(本地到本地syncIQ)。failover/failback都失败

2.8K 消息

2013年10月15日 18:00

帮主在香港很充实啊,看来公司EMC和NETAPP的设备用的都不少,谢谢提供测试反馈!

找不到事件!

Top