Brian_Houten's Posts

Brian_Houten's Posts

Deduplication on Isilon is a long running background job with very low impact to system resources or system performance. The job runs in very short cycles from sampling for duplication candidates... See more...
Deduplication on Isilon is a long running background job with very low impact to system resources or system performance. The job runs in very short cycles from sampling for duplication candidates, to creating the shadow stores. Think of it as being lots of very small jobs (start to finish) bundled into a very long running job. It is intended to just run during free cycles. I know some other storage put priority on deduplication having it inline during the write process and it can impact the performance. For Isilon, it is a post process to just help optimize the storage utilization.
If configured properly there should be a deletion scheduled for the snapshot, and they will remove themselves on schedule, if that is the concern. If you do not see a delete option under the "... See more...
If configured properly there should be a deletion scheduled for the snapshot, and they will remove themselves on schedule, if that is the concern. If you do not see a delete option under the "more" actions button next to the snapshot, I would guess you probably don't have the proper RBAC permissions, or as the other reply suggests, your SnapshotIQ license is expired. Both of these would cause the same situation. You might try running the CLI command available on Dell EMC support at https://support.emc.com/docu50219_OneFS-7.1.0-CLI-Administration-Guide.pdf?language=en_US on page 405 Procedure 1. Delete a snapshot by running the isi snapshot snapshots delete command. The following command deletes a snapshot named OldSnapshot: isi snapshot snapshots delete OldSnapshot 2. Optional: To increase the speed at which deleted snapshot data is freed on the cluster, start the snapshot delete job by running the following command: isi job jobs start snapshotdelete
You should also NEVER setup autocommit on the target. The retention should only be managed on the source domain. The information including the committed atime is transferred during the SyncIQ rep... See more...
You should also NEVER setup autocommit on the target. The retention should only be managed on the source domain. The information including the committed atime is transferred during the SyncIQ replication, so autocommit is not required. That guarantees consistency. For example if you only sync'd over part of the file as it was written to the source, and you do not sync again for 24 hours, then an autocommit on the target of 4 hours will lock those files. The autocommit on the source will not trigger until the complete file has been copied/written on the source because it is still changing during the process. You should modify all target policies to remove autocommit from them.
Here is the proper contact URL information to reach the Proven Help Desk with questions or concerns  - http://emc.force.com/EducationSupport
Taz: If you feel a question is unfair, you should go through the Proven Exam channel to report it for examination. We also do not post exam questions nor exam question answers on open forums s... See more...
Taz: If you feel a question is unfair, you should go through the Proven Exam channel to report it for examination. We also do not post exam questions nor exam question answers on open forums such as ECN. I can understand your frustration with the question and answer choices. This is not the appropriate forum to have the question resolved.  I can tell you the answer marked as correct is in the course materials. In planning, and not necessarily in actual execution, certain assumptions are applied. The answer comes from those assumptions.