I will pass this information to the teammate handling this issue. The only thing I am concerned about is that it states that the association between the "policy and target has been broken and is then re-established." I am guessing that its eluding that we would intentionally brake this association in order to perform this task. Not having a real life setup to test these steps sort of prevents us from taking such steps, but if we find ourselves in a place where we can effectively perform a test of this magnitude on a much smaller scale it would prove to be interesting.
Any other Ideas by chance that may not be covered in the best practices, but should work?
Phil.Lam
3 Apprentice
•
635 Posts
0
November 2nd, 2016 10:00
chjatwork
You may be interested in "target aware" sync only via CLI.
https://www.emc.com/collateral/hardware/white-papers/h8224-replication-isilon-synciq-wp.pdf
# isi sync policy modify --policy --diff_sync=on
# isi sync policy ls -v | grep aware
Target aware initial sync: yes
chjatwork
2 Intern
•
356 Posts
0
November 3rd, 2016 04:00
Phil,
I will pass this information to the teammate handling this issue. The only thing I am concerned about is that it states that the association between the "policy and target has been broken and is then re-established." I am guessing that its eluding that we would intentionally brake this association in order to perform this task. Not having a real life setup to test these steps sort of prevents us from taking such steps, but if we find ourselves in a place where we can effectively perform a test of this magnitude on a much smaller scale it would prove to be interesting.
Any other Ideas by chance that may not be covered in the best practices, but should work?
Thank you,