Start a Conversation

Unsolved

This post is more than 5 years old

885

September 20th, 2016 06:00

Snapcount high on Isilon cluster

We are seeing high number for snapcount on Isilon clusters which may due to to replication policies which is around 40K.  We don't have any scheduled snapshots.  Can we verify the snap count by per policy ?

252 Posts

September 20th, 2016 09:00

Hi khkris,

You can see the snapshot information by using

#isi snapshot snapshots list

However, in order to see the information by policy, grep should give you what you are looking for.

Where is the name of the snapshot policy you are inspecting.

#isi snapshot snapshots list | grep

Depending on the number of snapshots per policy, you may want to consider writing the output to a file, rather than just an onscreen display.

1.2K Posts

September 20th, 2016 09:00

grep also can do the counting, just use the -c flag:

#isi snapshot snapshots list | grep -c

2 Intern

 • 

20.4K Posts

September 20th, 2016 11:00

could be for a policy that replicates based on source change notification.

2 Intern

 • 

178 Posts

September 21st, 2016 06:00

Thanks for the inputs. 

There is count difference between the snapshots counts as below

isi snapshot snapshots list

Total: 38

isi_stf_test lsid |wc -l

     555

September 21st, 2016 09:00

> could be for a policy that replicates based on source change notification.

Been there, done that.  Didn't like it much.  Don't do that - if you're replicating with source change notification, don't create destination snapshots.  That's just asking for trouble (and 20,000 snapshots in a very short amount of time).  I put in a feature request to Isilon Engineering to declare those mutually-exclusive.

252 Posts

September 21st, 2016 09:00

Hi khkris,

If you run the following command, you should see a more accurate count between the two:

#isi snapshot snapshots list --state=all

The difference likely being that a majority of those snapshots are not in an active status.

On another note, the isi_stf_test command is considered a restricted command, even to Isilon Support Engineers and is only advised to be used under the direction of Escalation Engineering. You can really cause some damage with that one if not careful.

No Events found!

Top