This post is more than 5 years old
20 Posts
0
1804
SnapshotIQ expiration error/question
When we create a SnapshotIQ schedule with a specific duration, OneFS adds 1 to the duration. For example, if we create a expiration of 3 hours, after creation of the schedule, reveals a expiration time of 4 hours. When setting the expiration time to 1 weeks, isilon sets the the expiration time to 8 days It doens't matter if you use the GUI or CLI.. We are using OneFS 8.0.0.1. Anyone seen the behaviour and has a solution to this problem ?
sjones51
252 Posts
1
August 9th, 2016 10:00
Hi StefanWilmes,
It seems you are not the first to run into this issue. The workaround has been to use "isi_classic" commands to set the duration.
You may want to consider opening a service request so that a ticket can be logged for frequency within Isilon Support.
https://support.emc.com/servicecenter/createSR/
Newday3000
57 Posts
1
August 9th, 2016 11:00
Sr already open SR#81023102 and acknowledge bug in Papi
Regards
Andrew
On Tue, Aug 9, 2016 at 1:21 PM sjones5
StefanWilmes
20 Posts
0
August 9th, 2016 23:00
Thanks guys, you verified my conclusion,
Stefan.
StefanWilmes
20 Posts
0
August 10th, 2016 01:00
Anyone also struggling with the isi_classic command to do this :
isi_classic snapshot schedule modify schehulename --duration=2H (for example)
keeps giving me parser error at token 'H': syntax error, no matter what variant i try ...
sjones51
252 Posts
0
August 10th, 2016 10:00
Hi StefanWilmes,
I had one of my colleagues run the snapshot command on an 8.0.0.1 cluster and didn't see the syntax error. Here is the output:
X8001S-1# isi snapshot schedules list -v
ID: 1
Name: date
Path: /ifs/data
Pattern: date_hourly_%Y-%m-%d-_%H-%M
Schedule: every 1 days every 1 hours between 12:00 AM and 11:59 PM
Duration: -
Alias: -
Next Run: 2016-08-10T12:00:00
Next Snapshot: date_hourly_2016-08-10-_12-00
X8001S-1# isi snapshot schedules modify --schedule-name=date --duration=2H
X8001S-1#
sjones51
252 Posts
0
August 10th, 2016 10:00
Yes, you are correct. I missed that. I will ask him to run with the isi_classic command quick and then edit this response with the output.
Sorry about that. For the record, here is the list after running the regular isi snapshot command with 2H option:
X8001S-1# isi snapshot schedules modify --schedule-name=date --duration=2H X8001S-1# isi snapshot schedules list -v
ID: 1
Name: date
Path: /ifs/data
Pattern: date_hourly_%Y-%m-%d-_%H-%M
Schedule: every 1 days every 1 hours between 12:00 AM and 11:59 PM
Duration: 3H
Alias: -
Next Run: 2016-08-10T12:00:00
Next Snapshot: date_hourly_2016-08-10-_12-00
As you can see, it still added an extra hour. Here is the syntax for the isi_classic command:
X8001S-1# isi_classic snapshot schedule modify --schedule=date --duration="2 hours"
X8001S-1# isi_classic snapshot schedule list -l
-------------------- date --------------------
Schedule Id: 1
How Often: every 1 days every 1 hours between 12:00 AM and 11:59 PM
Starting When: 2016-08-10 11:55
Duration: 2 hours
Pattern: date_hourly_%Y-%m-%d-_%H-%M
Path: /ifs/data
X8001S-1# isi snapshot schedules list -v
ID: 1
Name: date
Path: /ifs/data
Pattern: date_hourly_%Y-%m-%d-_%H-%M
Schedule: every 1 days every 1 hours between 12:00 AM and 11:59 PM
Duration: 2H
Alias: -
Next Run: 2016-08-10T13:00:00
Next Snapshot: date_hourly_2016-08-10-_13-00
StefanWilmes
20 Posts
0
August 10th, 2016 10:00
You are not using the isi_classic command, the normal isi command works fine but sets the duration wrong. As i understood, isi_classic sets the duration ok.
StefanWilmes
20 Posts
0
August 11th, 2016 04:00
Thx sjones5, i was close at some point in time but now i am sure