You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Khosrow Moossavi (JIRA)" <ji...@apache.org> on 2018/02/06 19:39:00 UTC

[jira] [Resolved] (CLOUDSTACK-10222) Clean previous snaphosts from primary storage when taking new one

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-10222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Khosrow Moossavi resolved CLOUDSTACK-10222.
-------------------------------------------
    Resolution: Fixed

> Clean previous snaphosts from primary storage when taking new one
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10222
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10222
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Secondary Storage, Snapshot, XenServer
>    Affects Versions: 4.10.0.0, 4.11.0.0
>         Environment: XenServer, Swift
>            Reporter: Khosrow Moossavi
>            Priority: Major
>              Labels: easyfix
>             Fix For: 4.11.1.1
>
>
> When user creates a snapshot (manual or recurring), snapshot remains on the primary storage, even if the snapshot is transferred successfully to secondary storage. This is causing issues because XenServer can only hold a limited number of snapshots in its VDI chain, preventing the user from creating new snapshots after some time, when too many old snapshots are present on the primary storage. 
> {code:java}
> reason: SR_BACKEND_FAILURE_109 The snapshot chain is too long
> {code}
> Proposed solution:
> Keep only one snapshot (last successful) on the primary storage regardless that it was a full or partial snapshot.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)