Showing posts with label Isilon. Show all posts
Showing posts with label Isilon. Show all posts
Thursday, December 22, 2016
Friday, January 15, 2016
Isilon OneFS upgrade to 7.2.1.0
It's the time.. Time to UPGRADE
I recently performed a OneFS upgrade to 7.2.1. The entire process is categorized in three phase and below are the steps:
Pre-upgrade tasks:
Use the below commands and do the overall health check of the cluster
• isi status -D
• isi_for_array -s 'isi devices | grep -v HEALTHY'
• isi_for_array -s 'gmirror status'
• In the OneFS web administration interface, click Dashboard > Cluster Overview > Cluster Status.In the Status area, click the ID of a node.In the Chassis and drive status area, click Platform
• isi_for_array -s 'df -h' - Check the utilization of all file system and confirm that it is below 90%
• isi events list
Back up data.
• Backup all important data like corn jobs, etc.
• Ensure synciq jobs completed sucessfully
Collect cluster status.
isi status -D -w
Complete system jobs.
• isi services -a isi_job_d disable
Pause or cancel SyncIQ jobs.
• isi sync policy list -v
• isi sync jobs list"
• isi sync jobs pause --all
Cancel all running jobs:
Use command (isi job jobs list) to view any running jobs, use command ( isi job jobs cancel JobIDNumber) to cancel by ID number
Implementation plan
Check the upgrade image:
# isi update --check-only
when asked to specify the image to update then provide the path where the OneFS image is stored.
Check if you have any job running
# isi job jobs listFlush the cache
# isi_for_array isi_flush
Perform the upgrade
# isi updatewhen asked to specify the image to update then provide the path where the OneFS image is stored.
Are you sure you wish to upgrade (yes/no)? yes
Reboot to complete the process? (Yes/No) Yes
Now system run the upgrade process and you may need to reconnect to the cluster
Check the version
# isi version
Check the events
# isi event list -w
Install the patch if required/needed
Change to the directory where the patch image is stored
# cd <path>
# isi pkg install <file name>
Some times few drives may need firmware upgarde, run below command to do the same
# isi_disk_firmware_reboot -p
Check the services and enable if you have disabled it before performing the upgrade
# isi services -a supportiq enable
# isi services -a nfs enable
# isi services -a smb enable
Cancel all the events
#isi events cancel all
Gather the info and gave it to EMC for review
# isi_gather_info
Happy Learning!
Tuesday, September 1, 2015
Isilon Drive firmware upgrade
And i love this photo :-D
Well i recently performed a Drive firmware upgrade for one of our Isilon cluster and below are the steps.
Procedure for Isilon Drive Firmware Upgrade:
1. Download the package from support.emc.com link
2. Copy the package to Install directory of the cluster, example:
<cluster>:/ifs/data/2015/upgrade/software
3. Disable the notifications:
a. isi services -a
celog_notification disable
b. isi services -a supportiq
disable
4. Install the package (once per cluster)
Command: isi pkg install /ifs/data/2015/upgrade/software/<package_name.tar>
5. Flush the cache and reboot each node; normally prefer doing it in a bottom-up fashion
a.
Run isi_flush step prior rebooting
each node.
b.
After
this comand runs, it will reboot the node.
i. isi_disk_firmware_reboot
–p
6. After the node comes back online, verify the firmware status on that node
i. isi devices
ii. isi_disk_firmware_reboot -p
Note: if all drives have been updated then the message "no disks needs firmware update" will be displayed
7. Repeat step 5 & 6 for the rest of the nodes in the cluster
8. Clear the alerts with command
a. isi events quiet all
b.
isi
events cancel all
9. Enable the notifications with commands:
a. isi services -a celog_notification enable
b. isi services -a supportiq enable
Happy Learning!
Monday, August 10, 2015
SyncIQ Failover and Failback
SyncIq automated data failover & failback provides the high availability to OneFS which means in the event that a primary culster becomes unavailable, SyncIQ provides the ability to failover to a mirrored, DR cluster with minimal interruption.
Please note that: SyncIQ follows asynchronous replication not synchronous.
Below are the steps that needs to be executed for Isilon SyncIQ failover and failback; this can also be used for DR testing.
To initiate failover:
1) Set the target cluster as read-write
# isi sync recovery allow-write <policy_name>
Failback can be accomplished if the policy meets the following criteria:
1) source directory is not a smartlock directory
2) The policy has been failed over
3) The policy is a Sync Policy and not a copy policy
Steps in failback:
1) Resync-prep on the policy
# isi sync recovery resync-prep <policy_name>
2) Run a typical job on the mirror policy, a final failback differential sync is preformed:
# isi sync job start <policy_name_mirror>
3) Change the mirror local target to allow writes
# isi sync recovery allow-write <policy_name_mirror>
4) Run Resync-prep again on the mirror policy
# isi sync recovery resync-prep <policy_name_mirror>
5) Delete the mirror policy
# isi sync policies delete <policy_name_mirror>
Also read Isilon SyncIQ
Happy Learning!
Friday, May 29, 2015
Shutdown procedure of Isilon cluster via CLI
Below is the process of shutting down the EMC Isilon cluster via CLI
Step 1: Ensure there is no read/write operation on the cluster. You can do this by checking the smb/nfs sessions and ask the user to close the session:
# isi smb sessions list
# isi nfs nlm locks list
Step 2: Check the status of the client facing protocols running on the cluster and disable them:
# isi services apache2
# isi services isi_hdfs_d
# isi services isi_iscsi_d
# isi services ndmpd
# isi services nfs
# isi services smb
# isi services vsftpd
Now disable the services that are running
# isi services -a <service name> disable
Step 3: Flush the node journal to file system
# isi_for_array -s isi_flush
Note: Run the command once again if any node fails to flush the journal.
Step 4: Shutdown each on sequentially and don't run 'isi_for_array shutdown -p'
a) Connect to node and run command
# isi config
>> shutdown
Watch the console and ensure that the node is shutdown properly
Not: If you wish to shutdown all nodes simultaneously then run command:
# isi config
>>> shutdown all
Step 5: Once you power up the nodes, run the below command to check the status:
# isi status -q
Step 6: Enable all the services that you disabled in step 2
isi services apache2 enable
isi services isi_hdfs_d enable
isi services isi_iscsi_d enable
isi services ndmpd enable
isi services nfs enable
isi services smb enable
isi services vsftpd enable
Step 7: Verify client are able to connect to cluster and able to perform operation as usually.
Happy Learning!
Step 1: Ensure there is no read/write operation on the cluster. You can do this by checking the smb/nfs sessions and ask the user to close the session:
# isi smb sessions list
# isi nfs nlm locks list
Step 2: Check the status of the client facing protocols running on the cluster and disable them:
# isi services apache2
# isi services isi_hdfs_d
# isi services isi_iscsi_d
# isi services ndmpd
# isi services nfs
# isi services smb
# isi services vsftpd
Now disable the services that are running
# isi services -a <service name> disable
Step 3: Flush the node journal to file system
# isi_for_array -s isi_flush
Note: Run the command once again if any node fails to flush the journal.
Step 4: Shutdown each on sequentially and don't run 'isi_for_array shutdown -p'
a) Connect to node and run command
# isi config
>> shutdown
Watch the console and ensure that the node is shutdown properly
Not: If you wish to shutdown all nodes simultaneously then run command:
# isi config
>>> shutdown all
Step 5: Once you power up the nodes, run the below command to check the status:
# isi status -q
Step 6: Enable all the services that you disabled in step 2
isi services apache2 enable
isi services isi_hdfs_d enable
isi services isi_iscsi_d enable
isi services ndmpd enable
isi services nfs enable
isi services smb enable
isi services vsftpd enable
Step 7: Verify client are able to connect to cluster and able to perform operation as usually.
Happy Learning!
Thursday, April 23, 2015
Isilon Command Cheat Sheet
| Command | Sub-Command | Description |
| man isi | To check the man page of isi command | |
| isi license | To check the installed license | |
| isi license activate <key> | To install the license | |
| isi config | ||
| isi devices | ||
| isi get -a /ifs/data | Will give overall file system layout | |
| isi --help | ||
| isi networks | For internal and external network configuration | |
| isi devices -a add -d <device number> | To add the device back to cluster | |
| isi devices -a format -d <device number> | Often need to format the drive for OneFS use first | |
| isi_for_array -s isi_hw_status | grep -i 'power sup' | To check power supply status | |
| isi_hw_status | grep SerNo | To check the serial number of node | |
| isi auth ldap list | To list ldap details | |
| isi nfs | exports | Manage NFS exports |
| netgroup | Manage netgroup caching | |
| nlm | Manage NFS NLM sessions, locks, and waiters | |
| settings | Manage NFS default export and global protocol settings | |
| isi quota | quotas | Manage quotas |
| reports | Manage quota reports | |
| settings | Manage general quotas settings | |
| isi services | To check Isilon service | |
| Isi services <service name> disable | To disable any service | |
| Isi services <service name> enable | To enable any service | |
| isi set | ||
| isi smb | log-level | Configure the log level |
| openfiles | List and close open SBM files | |
| sessions | List and disconnect SMB sessions | |
| settings | Manage SMB default share and global protocol settings | |
| shares | Manage SMB shares and their permissions | |
| isi statistics | heat | Heat mode displays most active /ifs paths for a variety of metrics |
| pstat | Pstat mode displays a selection of cluster-wide and protocol data | |
| drive | Drive mode shows peformance by drive | |
| list | List valid arguments to given option | |
| isi snapshot | locks | manage snapshot locks |
| schedules | Manage scheduled creation of snapshots | |
| settings | Manage snapshot settings | |
| snapshots | Manage file system snapshots. | |
| isi status | To check cluster status | |
| isi statistics system --top --nodes --interval=2 | To check the top node at every two seconds | |
| isi statistics heat --classes=read,write | To check the hottest files on the cluster | |
| isi job | To check the running jobs / **only one job can one run at a time** | |
| LNN set | Command to change the logical node number | |
| # isi config | Go to config mode first | |
| # lnnset | Gives the current status | |
| # lnnset 3 7 | Changes the LNN ID of node 3 from 3 to 7 | |
| isi distill | ||
| isi_distill | Distill the essence of an IFS directory tree | |
| Example: isi_distill -k /ifs/data | ||
| Example: isi_distill -k -o /tmp/distill.txt /ifs/data | Allows to dump the output in a text file | |
| Reboot the Isilon Node | ||
| # isi config | To go to config mode | |
| # reboot 3 | To reboot node 3 | |
| # exit | To exit from config mode | |
# gmirror
status
Wednesday, April 8, 2015
Isilon SmartDedupe
Isilon SmartDedupe allows your cluster to be space efficient by removing redundant data ( it takes less amount of space to save files with similar blocks. SmartDedupe scans the cluster for identical data blocks and moves the single copy of redundant block to a hidden file called a shadow store. SmartDedupe then deletes the duplicated block and replaces the block with the pointer to the shadow store. Each shadow store consists of 255 blocks and each block can be referenced 32000 times.
Deduplication is applied to the directory level and files; targeting all files & directories underneath that directory.
Note: Dedupe should only be configured on data (folders) that are NOT compressed. Also don't configure dedupe for /ifs, always configure for the high level directory structure eg: /ifs/data/project_tango/
Steps to configure SmartDedupe via CLI on Isilon Cluster:
1) Check if the license is added or not as SmartDedupe is a licensed feature.
# isi license
2) Specify the file system or source directory:
# isi dedupe setting modify --path=/ifs/data/project1, /ifs/data/project2
3) Schedule the deduplication job:
# isi job types Dedupe --schedule "Every Saturday at 01:00 AM"
4) Check the stats:
# isi dedupe stats
5) Once job is completed, you can check its report:
# isi dedupe reports list
# isi dedupe reports view <report number>
6) To check settings, use:
# isi dedupe settings view
7) To check the events, user:
# isi job events list --job-type dedupe
Happy Learning!
Deduplication is applied to the directory level and files; targeting all files & directories underneath that directory.
Note: Dedupe should only be configured on data (folders) that are NOT compressed. Also don't configure dedupe for /ifs, always configure for the high level directory structure eg: /ifs/data/project_tango/
Steps to configure SmartDedupe via CLI on Isilon Cluster:
1) Check if the license is added or not as SmartDedupe is a licensed feature.
# isi license
2) Specify the file system or source directory:
# isi dedupe setting modify --path=/ifs/data/project1, /ifs/data/project2
3) Schedule the deduplication job:
# isi job types Dedupe --schedule "Every Saturday at 01:00 AM"
4) Check the stats:
# isi dedupe stats
5) Once job is completed, you can check its report:
# isi dedupe reports list
# isi dedupe reports view <report number>
6) To check settings, use:
# isi dedupe settings view
7) To check the events, user:
# isi job events list --job-type dedupe
Happy Learning!
Friday, March 27, 2015
NetApp To Isilon Migrations
Isilon provides a
built-in NDMP NetApp to Isilon utility called isi_vol_copy. This enables
admins to directly migrate a NetApp volume/qtree to an Isilon Folder.
1. Confirm NDMP is
configured and Running on the data source NetApp Filer.
a.
Check NDMP current status
ndmpd
status
b.
Enable NDMP
ndmpd on
2. Confirm NDMP is
configured on the Isilon Cluster.
isi services ndmpd
status
3. Run the isi_vol_copy
command to copy a Volume or Qtree to a target folder on the Isilon:
Usage:
isi_vol_copy <src_filer>:<src_dir> <dest_dir>
[-sa user: | user:password]
[-sport ndmp_src_port]
[-full | -incr]
[-dhost dest_ip_addr]
[-h]
e.g. # isi_vol_copy
Filer1:/vol/source_vol /ifs/migration -sa root:xxxxxx –full
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 1} {msg DUMP: creating
"/vol/source_vol/../snapshot_for_backup.28" snapshot.}
{associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 2} {msg DUMP: Using Full Volume Dump} {associated_msg
0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 3} {msg DUMP: Date of this level 0 dump: Wed Feb 11
11:47:28 2015.} {associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 4} {msg DUMP: Date of last level 0 dump: the epoch.}
{associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 5} {msg DUMP: Dumping /vol/source_vol to NDMP
connection} {associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 6} {msg DUMP: mapping (Pass I)[regular files]}
{associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 7} {msg DUMP: mapping (Pass II)[directories]} {associated_msg
0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 8} {msg DUMP: estimated 402939 KB.} {associated_msg 0}
{associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 9} {msg DUMP: dumping (Pass III) [directories]}
{associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 10} {msg DUMP: dumping (Pass IV) [regular files]}
{associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 11} {msg ACL_START is '512692480'} {associated_msg 0}
{associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 12} {msg DUMP: dumping (Pass V) [ACLs]}
{associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 13} {msg DUMP: 708016 KB} {associated_msg 0}
{associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 14} {msg DUMP: DUMP IS DONE} {associated_msg 0}
{associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 15} {msg DUMP: Deleting
"/vol/source_vol/../snapshot_for_backup.28" snapshot.}
{associated_msg 0} {associated_msg_seq 0}
LogMessage {type
NDMP_LOG_NORMAL} {msg_id 16} {msg DUMP_DATE is '567890354'} {associated_msg 0}
{associated_msg_seq 0}
The transfer is
complete.
Elapsed time: 0 hours,
10 minutes, 9 seconds.
Happy Learning!
Monday, March 16, 2015
Isilon Health Check Script
Thrive in what all you do... Okay i'm not writing any spiritual article here ;)
Actually i was tired of running manual commands on array to check the status on daily basis, which encouraged me to write a small health check script. I believe that's why man made the machine :-D
Anyways.. below is the script which does couple of tasks:
- Check the overall status of the cluster
- Mail the output to my e-mail id
In case you have a large setup then you can schedule it via cron or autosys as well...
Script::
#####################################################
#
# Script: To perform the health check on Isilon Array
#
#
# Script: To perform the health check on Isilon Array
#
# DATE: 2015-03-15
#
# Version Update: 1.0 Piyush Chawla
#
#####################################################
# Version Update: 1.0 Piyush Chawla
#
#####################################################
TODAY=$(date)
HOST=$(hostname)
sleep 15
#Move yesterday’s backups to an archive
location
mv /ifs/pc1611/*.txt
/ifs/pc1611/archive/
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “Date: $TODAY Host: $HOST” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
# To check the Isilon array health
status
/usr/bin/isi status -q >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo "Event List"
/usr/bin/isi event list | tail -10
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “SyncIQ Report” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
# To check the SyncIQ status
/usr/bin/isi sync reports list
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “File System Utilization”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
# To check the file system utilization
df -kh -a /ifs >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo ”-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
/usr/bin/isi storagepool list >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “Deduplication status” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
# To check the deduplication status
/usr/bin/isi dedupe stats >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
# To check the performance status
echo “Performance stats” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “-----------------------------”
>> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
sleep 1
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “–System Stats–” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
/usr/bin/isi statistics system >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
sleep 1
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “–Client Stats–” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
/usr/bin/isi statistics client >> /ifs/pc1611/"isilon_status-`date
'+%Y-%m-%d'`.txt"
sleep 1
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “–Protocol Stats–” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
/usr/bin/isi statistics protocol >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
sleep 1
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “–Protocol Data–” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
/usr/bin/isi statistics pstat >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
sleep 1
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo “–Drive Stats–” >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
echo ”
” >> /ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
/usr/bin/isi statistics drive >>
/ifs/pc1611/"isilon_status-`date '+%Y-%m-%d'`.txt"
# Mail the required output
cat /ifs/pc1611/isilon_status* | mail
-s "$TODAY Report" piyush.chawla@xyz.com
#End of Script
Happy Learning!
Saturday, March 14, 2015
Isilon: Access Zones
Technical demo: Access zones in EMC Isilon
Friday, March 13, 2015
SyncIQ
In Isilon, data replication is coordinated according to replication policies and jobs. Replication policies specify what data is replicated, where the data is replicated to, and how often the data is replicated. Replication jobs are the operations that replicate data from one Isilon cluster to another. SyncIQ generates replication jobs according to replication policies.
When SyncIQ transfers updates to a file
that was transferred during a previous SyncIQ job, SyncIQ transfers only the
blocks of that file that have changed since the last job, rather than
transferring the entire file.
Create replication policy:
# isi sync
policies create <policy name> sync <source path> <target cluster name> <target path> --schedule "<schedule name>"
--target-snapshot-archive on --target-snapshot-pattern
"%{PolicyName}-%{SrcCluster}-%Y-%m-%d_%H-%M"
Create SyncIQ domain:
It is required for the fail back operations.
# isi
job jobs start <domain name> --root <path> --dm-type SyncIQ
Assess a replication policy:
you can assess the status of a policy using below command. This can be useful if you want to preview the size of the data set that will be transferred if you run the policy
# isi sync jobs start <policy name> --test
# isi sync reports view <policy name> 1
Managing the replication:
You can manage the replication using the below commands
# isi sync jobs start <policy name>
# isi sync jobs pause <policy name>
# isi sync jobs resume <policy name>
# isi sync jobs cancel <policy name>
You can manage the replication using the below commands
# isi sync jobs start <policy name>
# isi sync jobs pause <policy name>
# isi sync jobs resume <policy name>
# isi sync jobs cancel <policy name>
View active replication jobs
# isi sync jobs list
# isi sync jobs view <policy name>
Delete replication policy
# isi sync policies delete <policy name>
Enable or disable a replication policy
# isi sync jobs list
# isi sync jobs view <policy name>
Delete replication policy
# isi sync policies delete <policy name>
Enable or disable a replication policy
# isi sync policies enable <policy name>
# isi sync policies disable <policy name>
View replication policies
# isi sync policies list
# isi sync policies view <policy name>
View replication policies targeting the local cluster
# isi sync target list
# isi sync target view <policy name>
View replication policies
# isi sync policies list
# isi sync policies view <policy name>
View replication policies targeting the local cluster
# isi sync target list
# isi sync target view <policy name>
Managing replication performance rules
# isi sync rules create
example: below command creates a network traffic rule that limits bandwidth consumption to 13500 kbps per second from 00:00 to 23:59 during Sun-Sat
# isi sync rules create bandwidth 00:00-23:59 Sun-Sat 13500
Below command creates a file-operations rule that limits the file-send rate to 3 files per second from 10:00 AM to 6:00 PM every weekday:
# isi sync rules create file_count 10:00-18:00 M-F 3
Enable or Disable the performance rule:
# isi sync rules list
# isi sync rules view --id bw-0
# isi sync rules modify bw-0 --enabled true
# isi sync rules modify bw-0 --enabled false
Managing replication reports:
# isi sync reports list
# isi sync reports view <policy name> 2
# isi sync reports subreports list <policy name> 1 -- to view sub-reports
Managing failed jobs:
If SyncIQ disables the replication due to policy error then you can resolve it using below command:
# isi sync policies resolve <policy name>
If you can't resolve the replication issue then you can reset the job as well. Resetting a policy causes OneFS to perform a full or differential replication the next time the policy is run
# isi sync policies reset <policy name>
Happy Learning!
# isi sync rules create
example: below command creates a network traffic rule that limits bandwidth consumption to 13500 kbps per second from 00:00 to 23:59 during Sun-Sat
# isi sync rules create bandwidth 00:00-23:59 Sun-Sat 13500
Below command creates a file-operations rule that limits the file-send rate to 3 files per second from 10:00 AM to 6:00 PM every weekday:
# isi sync rules create file_count 10:00-18:00 M-F 3
Enable or Disable the performance rule:
# isi sync rules list
# isi sync rules view --id bw-0
# isi sync rules modify bw-0 --enabled true
# isi sync rules modify bw-0 --enabled false
Managing replication reports:
# isi sync reports list
# isi sync reports view <policy name> 2
# isi sync reports subreports list <policy name> 1 -- to view sub-reports
Managing failed jobs:
If SyncIQ disables the replication due to policy error then you can resolve it using below command:
# isi sync policies resolve <policy name>
If you can't resolve the replication issue then you can reset the job as well. Resetting a policy causes OneFS to perform a full or differential replication the next time the policy is run
# isi sync policies reset <policy name>
Happy Learning!
Sunday, March 1, 2015
Isilon | InsightIQ Installation and configuration
Installation Guide:
Below are steps required for the installation and configuration of InsightIQ on Linux server.Pre-requisite checks:
Kindly check the IIQ installation guide for the system & operating system requirements. Make sure all required rpm are installed.
You can use below commands to do the pre-checks:
# cat /proc/cpuinfo
# cat /proc/meminfo
# df -kh
# cat /etc/redhat-release
# rpm -qa | grep <rpm name>
Download the package from support.emc.com and move it to the server/path from where you wish to install. I use winscp and scp command
# scp <username>@<servername>/<path> <destination-path>
Install the package:
# sudo yum install <path>
example:
[user@servername]# sudo yum install <path_for_rpm_file>
Loaded plugins: product-id, rhnplugin,
security, subscription-manager
This system is not registered to Red
Hat Subscription Management. You can use subscription-manager to register.
There was an error communicating with
RHN.
RHN channel support will be disabled.
Error communicating with server. The
message was:
Internal Server Error
Setting up Install Process
Examining
/root/isilon-insightiq-2.5.0.0007-1.x86_64.rpm: isilon-insightiq-2.5.0.0007-1.x86_64
Marking
/root/isilon-insightiq-2.5.0.0007-1.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package
isilon-insightiq.x86_64 0:2.5.0.0007-1 will be installed
--> Finished Dependency Resolution
Dependencies Resolved
=============================================================================================================================================================================================================================================
Package
Arch
Version
Repository
Size
=============================================================================================================================================================================================================================================
Installing:
isilon-insightiq
x86_64
2.5.0.0007-1
/isilon-insightiq-2.5.0.0007-1.x86_64 42 M
Transaction Summary
=============================================================================================================================================================================================================================================
Install 1 Package(s)
Total size: 42 M
Installed size: 42 M
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : isilon-insightiq-2.5.0.0007-1.x86_64 1/1
Running setup_config() from
insightiq.websetup
insightiq 0:off
1:off 2:on 3:on
4:on 5:on 6:off
Starting automount: automount: program
is already running.
[
OK ]
Starting insightiq: [ OK ]
There was an error communicating with
RHN.
Package profile information could not
be sent.
Error communicating with server. The
message was:
Internal Server Error
Verifying :
isilon-insightiq-2.5.0.0007-1.x86_64
1/1
Installed: isilon-insightiq.x86_64 0:2.5.0.0007-1
Complete!
You have new mail in
/var/spool/mail/root
[user@servername]#
Enable access to HTTP port 80
sudo /etc/init.d/iptables stop
sudo chkconfig iptables off
Configure the user account that IIQ will use:
1. Log on to OneFS GUI and go to cluster management > Access Management > Users
2. Go to user tab and submit the password, configure the home directory and enable the account.
Configuring the IIQ application:
1. Connect to IIQ using the web browser http://<IP address of sever>
2. Enter the username and password. I used root and mypassword
3. Accept the EULA
4. Specify the datastore location.

5. Add the first cluster: specify the cluster name, username and password ( that configured in step 2 of user configuration )
Adding new cluster:
In case you need to add a new cluster then go to menu setting > monitored clusters > add cluster

Also read IIQ upgrade
Happy Learning!
Wednesday, February 11, 2015
Isilon | How to configure SmartLock
SmartLock
What it is:
SmartLock is based on WORM (Write Once Read Many) approach. It provides non-rewritable, non-erasable feature which helps in protecting your data against accidental or intentional erasure. It is very useful for archived files that you need to retain for audit & compliance purpose; specially in Banking and Healthcare business units.
Advantage:
It helps you in storage space savings as you protect data at the directory level while in traditional WORM backup complete tape is utilized.
Steps to configure:
1) Check the license:
# isi license
2) Set the compliance clock
# isi worm cdate set
3) Create the root folder - All subfolders and files adopt the same retention settings as the root folder. So carefully decide your File System Hierarchy
# isi worm mkdir --path=<path of the file system>
3) Set the retention period
# isi worm modify --default-retention <time period> --min-retention <time period> -- max-retention <time period> --autocommit-offset <time period>--path=<file system path>
Note: Time period=4Y/ 3M ( 4 years / 3 months )
4) View SmartLock directory:
# isi worm domains list
# isi worm domains view <path>
5) Commit a file to a WORM state through UNIX;
# chmod ugo-w <file system path>
6) Commit a file to a WORM state through Windows Explorer:
# Select file/folder
# Righ-click and go to properties and then general tab
# Select Read-Only option and click OK
7) Delete a file committed to a WORM state
you can delete WORM committed file before expiration date using root or compliance administrator privilege.
Use the below command to set the privilege option for a particular directory:
# isi worm domains modify --path=<file system path> --privileged-delete true
Note: If privilege-delete option is OFF then you can't delete file until retention period is over.
8) View the status of WORM files:
# isi worm files view <path>
Also read: Design your own file-system
Happy Learning!
Subscribe to:
Posts (Atom)








