You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Mandar Barve (JIRA)" <ji...@apache.org> on 2013/11/25 09:10:36 UTC

[jira] [Commented] (CLOUDSTACK-285) Snapshots fail to respect retention period if schedule is deleted and re-created.

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831255#comment-13831255 ] 

Mandar Barve commented on CLOUDSTACK-285:
-----------------------------------------

I could not reproduce this issue with vesion 4.0.2. I tried creating hourly snapshot schedule with a keep value of 4. I could see 4 snapshots retained. Then as mentioned in the bug I deleted the schedule and recreated with same parameters except changing the keep value to 3. After this I could see only 3 snapshots retained.

Has this been resolved? Can it be closed?

> Snapshots fail to respect retention period if schedule is deleted and re-created.
> ---------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-285
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-285
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Snapshot
>    Affects Versions: pre-4.0.0
>            Reporter: Matthew Hartmann
>            Priority: Critical
>
> I created a recurring snapshot schedule for a volume; Daily, with a Keep of 5. After 10 days I decided to delete the schedule and re-create the SAME schedule except I only wanted to Keep 3. I noticed that this results in the Management Server falling back on the Global Parameter of rotating through 16 snapshots.
> I also performed the same test with an Hourly snapshot schedule. The trigger seems to be that if a schedule is deleted and recreated, the previous snapshots will be used but the retention period (Keep) is ignored.



--
This message was sent by Atlassian JIRA
(v6.1#6144)